opensearch-project / opensearch-project/.github
[PROPOSAL] Process for moving a project to maintenance mode
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 41
- Forks
- 74
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 1
Description
What kind of business use case are you trying to solve? What are your requirements?
The OpenSearch-Project needs language to provide guidance on moving a project to maintenance mode. (see need in #59).
What is the problem? What is preventing you from meeting the requirements?
No guidance yet and this will be useful if a repo becomes stale / unmaintained
What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?
Something along the lines of The Linux Foundation
What are your assumptions or prerequisites?
Project no longer maintained
What are remaining open questions?
What's a good process for OpenSearch-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 need described in issue #59 and the Linux Foundation guidance linked in this issue. Define and document an agreed process for moving an OpenSearch project to maintenance mode, including the requirements and decisions needed to determine when it is complete.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100