opensearch-project / opensearch-project/.github
[PROPOSAL] Organizational rules of engagement
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?
What are the processes that each repo in this org can modify, and which processes can't they?
What is the problem? What is preventing you from meeting the requirements?
Coming from https://github.com/opensearch-project/.github/pull/59#discussion_r838771253 where someone asked whether maintainers of the project can modify the maintainer rules in their own repo.
What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?
A doc of what it means to be part of the org, e.g. "must adopt code of conduct", "must adopt maintainers.md", "free to adopt whatever programming language".
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 with the discussion linked from the issue and review the existing templates and resources in the .github repository. Done means an agreed organizational document defines which processes each repository may modify and the shared requirements, including the code of conduct and maintainers.md.
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
- Mostly clear
- Newbie friendliness
- 25/100