Skip to content

Latest commit

 

History

History
69 lines (42 loc) · 3.1 KB

CONTRIBUTING.md

File metadata and controls

69 lines (42 loc) · 3.1 KB

Contribution Standards for Week-end Development Community

Introduction

Welcome to the Week-end Development Community! We value your contributions and encourage active participation from all members. To maintain a collaborative and positive environment, we have established these contribution standards. Please read and adhere to these guidelines when contributing to our community.

Code of Conduct

Before contributing, familiarize yourself with our Code of Conduct, which outlines the expected behavior and interactions within our community. All contributors are expected to abide by these principles.

Types of Contributions

1. Note Sharing

  • Purpose: Share educational notes, resources, and learning materials related to weekend development projects.
  • How to Contribute: Create a new repository or contribute to existing ones with informative README files. Clearly label and organize your notes for easy navigation.

2. Project Collaboration

  • Purpose: Collaborate on weekend development projects, share ideas, and work together to enhance skills.
  • How to Contribute: Fork the project, create a new branch, and submit a pull request with your enhancements or bug fixes. Communicate with project maintainers through issues or discussions.

3. Issue Reporting

  • Purpose: Report bugs, suggest improvements, or request new features.
  • How to Contribute: Open a new issue, providing a detailed description, steps to reproduce, and any relevant information. Engage in discussions to clarify or provide additional details.

Contribution Process

  1. Fork the Repository:

    • Fork the repository to your GitHub account.

  2. Create a Branch:

    • Create a new branch for your contributions.

  3. Make Changes:

    • Make your changes or additions, following any coding or documentation standards in the project.

  4. Commit Changes:

    • Commit your changes with clear and concise messages.

  5. Submit a Pull Request:

    • Submit a pull request from your branch to the original repository's main branch.

  6. Review Process:

    • Project maintainers will review your pull request, providing feedback and addressing any necessary changes.

  7. Merge and Release:

    • Once approved, your changes will be merged into the main branch and included in the next release.

Community Guidelines

  1. Respect Others:

    • Be respectful and considerate of other community members. Avoid offensive language or behavior.

  2. Help Each Other:

    • Encourage a supportive environment by offering help, guidance, and constructive feedback.

  3. Ownership and Licensing:

    • Clearly state the ownership and licensing terms for your contributions.

  4. Stay Informed:

    • Keep yourself updated with community discussions, announcements, and any changes to contribution standards.

Conclusion

Thank you for contributing to the Week-end Development Community! Your engagement and collaboration are key to the success of our community. If you have any questions or need assistance, feel free to reach out to the community moderators or project maintainers.

Happy coding! 🚀