|
|
| | + Tikiwiki is both software and a community. The mix of both, contextualized in the Internet and the real life, is called ''The Environment''. Any change in Tikiwiki should take in account its effect on the entire Tiki community and should allow for a balanced evolution with respect for the humans that use it. Please make sure any code you commit [http://tikiwiki.org/tiki-index.php?page=LibLicense|respects the LGPL license] and that you allowed to share it. | | + Tikiwiki is both software and a community. The mix of both, contextualized in the Internet and the real life, is called ''The Environment''. Any change in Tikiwiki should take in account its effect on the entire Tiki community and should allow for a balanced evolution with respect for the humans that use it. Please make sure any code you commit [http://tikiwiki.org/tiki-index.php?page=LibLicense|respects the LGPL license] and that you allowed to share it. |
| | # __Commit early, Commit often__ | | # __Commit early, Commit often__ |
| - | + CVS is the central point in tikiwiki collaborative development. CVS commits should be frequent, even in the early stages, to offer an opportunity of interaction between contributors. Early commits provide more chances for feedback and for the community to start to assimilate the ideas you propose |
+ | + CVS (<1.9) and SVN (>1.10) are the central points in tikiwiki collaborative development. Commits should be frequent, even in the early stages, to offer an opportunity of interaction between contributors. Early commits provide more chances for feedback and for the community to start to assimilate the ideas you propose |
| | # __Make it Optional__ | | # __Make it Optional__ |
| | + Tikiwiki 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. | | + Tikiwiki 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. |
| | # __Share Early, Share Often__ | | # __Share Early, Share Often__ |
| | +If you have an idea for an improvement, new feature, performance enhancement, or anything else of that nature, be quick to share it. Be proud of your idea and get it out there on the e-mail list or IRC channel. Be open to questions and ideas that others may have. As you work out your ideas and implementations, share your progress and approach often. Ask for advice and feedback. There are many smart people in the Tiki Community who love to help. Documenting what you are doing on TikiWiki.org keeps others up to date with changes. You are encouraged to create a wiki page for your idea so others can comment. Create a showcase site to show off your work in progress. Once it basically works and the community likes it, commit your code to CVS. Yes, it may be imperfect, nevertheless by following the maxim of Release Early, Rlease Often others are more able to help with development and debugging. | | +If you have an idea for an improvement, new feature, performance enhancement, or anything else of that nature, be quick to share it. Be proud of your idea and get it out there on the e-mail list or IRC channel. Be open to questions and ideas that others may have. As you work out your ideas and implementations, share your progress and approach often. Ask for advice and feedback. There are many smart people in the Tiki Community who love to help. Documenting what you are doing on TikiWiki.org keeps others up to date with changes. You are encouraged to create a wiki page for your idea so others can comment. Create a showcase site to show off your work in progress. Once it basically works and the community likes it, commit your code to CVS. Yes, it may be imperfect, nevertheless by following the maxim of Release Early, Rlease Often others are more able to help with development and debugging. |
| - | +__One BIG caution__: Don't commit sweeping or wide reaching changes to CVS until there is community consensus, or at least approval from one or more of the project administrators. They are those who have that designation in the list of developers. Checking with others is the right way to develop code and helps us to avoid really screwing up other people's lives and projects. When in doubt, communicate! This could be on IRC, by email, or some other agreed upon method. |
+ | +__One BIG caution__: Don't commit sweeping or wide reaching changes to CVS or SVN until there is community consensus, or at least approval from one or more of the project administrators. They are those who have that designation in the list of developers. Checking with others is the right way to develop code and helps us to avoid really screwing up other people's lives and projects. When in doubt, communicate! This could be on IRC, by email, or some other agreed upon method. |
| | + ''__A caution about the BIG caution__ : I feel it is impossible to reach consensus without effective code. Asking before is a matter of gathering information, not getting prior acceptance of something. Good decisions can provide bad implementations and in such cases there is a difficulty in correcting what was mutually agreed beforehand (without really knowing). Of course, that only applies to experienced coders __who are supposed to know what they are doing__. People who learn to code need to be particularly cautious. You decide whether this is for authoritative reasons or as a means of obtaining wisdom (if available). That's my 2 cents. -- mose'' | | + ''__A caution about the BIG caution__ : I feel it is impossible to reach consensus without effective code. Asking before is a matter of gathering information, not getting prior acceptance of something. Good decisions can provide bad implementations and in such cases there is a difficulty in correcting what was mutually agreed beforehand (without really knowing). Of course, that only applies to experienced coders __who are supposed to know what they are doing__. People who learn to code need to be particularly cautious. You decide whether this is for authoritative reasons or as a means of obtaining wisdom (if available). That's my 2 cents. -- mose'' |
| | # __Make It Optional__ | | # __Make It Optional__ |