-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Update CONTRIBUTING.md #603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dipree/org-readme
Are you sure you want to change the base?
Conversation
Updating security.md file
To reduce spam
The old link is broken, this is updating the link to the current Safe Harbor Policy
Allow CODEOWNERS file detection to see into the .github directory
Updating the link for the Safe Harbor Policy
Add period to list item
## Changelog Since 2.0 - Emphasizes 'community' over 'project' scope, effectively merging the Community Covenant into the Contributor Covenant - Adds expectation about accepting responsibility and apologizing to those affected by mistakes, and learning from the experience to the list - Adds sexual attention and advances of any kind as unacceptable behavior example - Moves enforcement responsibilities from project maintainers to community leaders - Adds responsibility to communicate reasons for moderation decisions when removing, editing, or rejecting contributions not aligned to the Code of Conduct - Requires community leaders to respect privacy and security of the reporter of any incident, not just confidentiality - Provides a template for code of conduct enforcement Since 2.1 - Adds 'caste' and 'color' to the preamble https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md
Bump Code of Conduct version from 1.4 to 2.1
Co-authored-by: Zack Koppert <zkoppert@github.com>
changed the content structure in CODE_OF_CONDUCT.md
😃 Move emojis after punctuation
…rd-git Capitalize the word git
apollo0914282
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| @@ -1,4 +1,4 @@ | |||
| ## Contributing | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Contributing
Reporting issues
If you find an issue in the roadmap, you can use our Issue Tracker. Make sure that it hasn't yet been reported by searching first.
Remember to include the following information:
- Description of the issue
- Steps to reproduce (if applicable)
- Expected behavior
- Actual behavior
- Screenshots or examples (if relevant)
Optional:
- Environment details
- Browser/OS information
- Additional context
Suggesting Features
Have an idea for the roadmap? We'd love to hear it! Please:
- Open an issue with your suggestion
- Provide clear description of the feature
- Explain why this feature would be valuable
- Include any relevant context or examples
Code Style
We follow standard coding practices:
- Clean, readable code
- Meaningful variable and function names
- Proper indentation and formatting
- Comments for complex logic
- Consistent style throughout the codebase
The current code base doesn't follow it entirely, but new code should follow it.
Pull Request Process
- Fork the repository
- Create a new branch for your feature (
git checkout -b feature/amazing-feature) - Make your changes
- Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request with a clear description of your changes
License
By contributing to this project, you agree that your contributions will be licensed under the same license as the project.
Thank you for contributing to the GitHub Public Roadmap!
/ † Rxx