WhatAreTheRegulationsIMustFollow.md

̆‿ ̆

What are the regulations I must follow?

We believe that it is rules that make us humans and without them, we are no different than animals. Even our community has a set of rules mandated to ensure the smooth functioning of all operations. The fact that you are a member of the community means you accept the regulations stated below.

1. Every project maintained in the community have a standard set of guidelines and rules for acceptable contributions that must be followed in order to be able to contribute to it.
2. None of the projects would have a change of license or would be taken down once set afloat to respect contributions made till date by every fellow contributor in the community.
3. The core team would be present in all the projects and workflows to monitor activities performed by the fellow contributors but all major positions or responsibility are up for grabs.
4. To pursue a personal project collectively, the ownership of a personal repository must be first transferred to the our organization to enable members of the community to contribute to it.
5. The owner of the transferred repository would retain their rights to accept or deny the pull requests made by the contributors but every denial must be accompanied with suggestions.
6. The owner of the transferred repository would relinquish their right to transfer ownership back to their personal version control account once it has been opened up to the community.
7. A member of the release workflow is expected to make at least five considerable contributions per week and without which they may be asked to step down from their current workflow.
8. A member of the rolling workflow is expected to make at least three considerable contributions per week and without which they may be asked to step down from their current workflow.
9. A long duration inactivity of a member without prior information would lead to an immediate inquiry and without a proper justification, they may be asked to step down from their current workflow.
10. Tampering with the project codebase and assets without proper permission would lead to an immediate inquiry and justification would be asked leading to this action.
11. The functionality of the project is expected to be maintained exclusively by the members of the architecture division and any unexpected change would lead to an immediate inquiry.
12. The codebase of the project is expected to be maintained exclusively by the members of the development division and any unexpected change would lead to an immediate inquiry.
13. The innovation of the project is expected to maintained exclusively by the members of the design division and any unexpected change would lead to an immediate inquiry.
14. The look-and-feel of the project is expected to maintained exclusively by the members of the frontend division and any unexpected change would lead to an immediate inquiry.
15. The testing of the project is expected to maintained exclusively by the members of the service division and any unexpected change would lead to an immediate inquiry.
16. The documentation of the project is expected to maintained exclusively by the members of the documentation division and any unexpected change would lead to an immediate inquiry.
17. The publicity of the project is expected to maintained exclusively by members of the the outreach division and any unexpected change would lead to an immediate inquiry.
18. The documentation is expected to contain the information about the active project contributors and their active position of responsibility within that particular project.
19. Members of the community making continued and consistent contributions would be stepped up to a higher privilege level, greater responsibility and possibly welcomed in the core team.
20. Pull requests made with deliberate changes targeted at the master of the source repository would be accepted so changes should be made in a branch of a forked repository.
21. The core team reserves the right to accept or reject the pull requests made by the contributors and any rejection would be followed by constructive suggestions as to what should be added.
22. All project related discussions and decision are expected to be done in their respective channels of Slack server and Space board created for serving the community members.
23. Addressing requests may take some time so members are expected not to spam the channels of Slack server and Space board created for serving the community members.
24. Avoid making offtopic discussions or sending endorsement messages on the Slack server and Space board – A separate channel would be provided for all these conversations.
25. Members are free to use any of the projects on the community for study purposes as long as citations are provided appropriately and the active contributors are credited for their work.
26. Members are free to publish any of the projects on the community in the digital media like Reddit, Dev.to with proper citations and complete remarks to credit their active contributors.
27. An amicable behavior is expected from all the members during their conduct and any controversial behavior or demeaning comment made by a member would lead to immediate enquiry.
28. A community member can be a passive member in upto three divisions thus contributing in quantity which would make them ineligible to for any position of responsibility in those divisions.
29. A contributing member can hold a position of responsibility in upto one division thus contributing in quality which would make them ineligible for membership in multiple divisions.
30. Discussion about changes are encouraged though an implementation would be possible only after the unanimous agreement of the core team and voting by the community members.
31. The projects made in the community would be made open-source and licensed under General Public License 3.0 until stated otherwise in rare circumstances by the core team.