Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

For ECMA, each document needs to not have a separate SCOPE, terminology and reference section

Open
  • Is something wrong?
#341 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Domain
documentation

Research direction

Review the ECMA documentation structure in the repository to understand the current separation of SCOPE, terminology, and reference sections. Identify where these sections are defined and how they can be consolidated per ECMA requirements. Check for existing documentation files or specifications to see the formatting standards.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
Shell
Stars
116
Forks
23
Avg merge
2d 11h
Merged PRs (30d)
63

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CycloneDX/transparency-exchange-api

All issues in CycloneDX/transparency-exchange-api

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.