Requirements document.
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 224
- Avg merge
- 22h 46m
- Merged PRs (30d)
- 1
Description
Hello I would like to make the document of requirements for the project. Could you give me some information about the project?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository description and existing project information to determine what a requirements document should cover. The issue provides no files, tests, or concrete requirements, so clarify the project's scope and expected document contents before drafting; done means an agreed requirements document is available.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100