| | # __Respect the Environment__ | | # __Respect the Environment__ |
| - | + Tiki is both a software project and a community. The mix of both, contextualized on the Internet and in real life, is called The Environment. Any change in Tiki should take into account its effect on the entire Tiki community and should allow for a balanced evolution with respect for the people and organizations that use it. Please make sure any code you commit [http://tiki.org/License|respects the LGPL license] and that you are allowed to share it. Do not duplicate code or features, as this just creates more work for everyone to maintain. Reuse and extend code instead, and ask for help if you are unsure how, or unsure if there is similar code lying around. |
+ | + Tiki is both a software project and a community. The mix of both, contextualized on the Internet and in real life, is called The Environment. Any change in Tiki should take into account its effect on the entire Tiki community and should allow for a balanced evolution with respect for the people and organizations that use it. Please make sure any code you commit ((tw:License|respects the LGPL license)) and that you are allowed to share it. Do not duplicate code or features, as this just creates more work for everyone to maintain. Reuse and extend code instead, and ask for help if you are unsure how, or unsure if there is similar code lying around. |
| | # __Commit early, Commit often__ | | # __Commit early, Commit often__ |
| - | + [https://gitlab.com/tikiwiki/tiki|Git] is the central point in Tiki's collaborative development. Contributions should be frequent, even in the early stages, to offer an opportunity for interaction between contributors. Early merge requests in draft provide more chances for feedback and for the community to start to assimilate the ideas you propose. [http://community.redhat.com/blog/2015/03/upstream-first-turning-openstack-into-an-nfv-platform/|"Upstream first" is the cheapest, most sustainable way to innovate on an open source platform]. |
+ | + [https://gitlab.com/tikiwiki/tiki|Git] is the central point in Tiki's collaborative development. Contributions should be frequent, even in the early stages, to offer an opportunity for interaction between contributors. Early merge requests in draft provide more opportunities for feedback and for the community to start to assimilate the ideas you propose. [http://community.redhat.com/blog/2015/03/upstream-first-turning-openstack-into-an-nfv-platform/|"Upstream first" is the cheapest, most sustainable way to innovate on an open source platform]. |
| | + Tiki is used in many smaller contexts and its modularity is key to adoption in those areas. Help preserve this flexibility by making your changes optional whenever possible, accessible for tuning to the admin at least, via admin panels. This is also good for security as if a security vulnerability is discovered, a feature can be deactivated. | | + Tiki is used in many smaller contexts and its modularity is key to adoption in those areas. Help preserve this flexibility by making your changes optional whenever possible, accessible for tuning to the admin at least, via admin panels. This is also good for security as if a security vulnerability is discovered, a feature can be deactivated. |