We use this method for commits to the stable branch (Ex.: 3.1 -> 3.2 -> 3.3) but when developing the new major version (ex.: 3.x to 4.0), all contributors commit directly to the main code base. We feel this is a great balance of
- having lots of innovation and low coordination overhead when developing the future version.
- while having minor versions with as few regressions as possible.
So if you need a lot of stability you should skip .0 releases (which really, you should avoid for any project) and have an upgrade pattern of 3.1 -> 3.2 -> 4.1 -> 4.2 -> 5.1, etc, in Tiki, we encourage everyone to commit directly to the source code. Think of it as applying the Wiki Way to software development. Over 340 people have done it so far and it works very well.
- Read and agree to the 3 Rules
- Get an account on SourceForge.net
- Make sure User Messages, in the preferences of your SourceForge account, is set to "Allow anyone to send mail", so that you can be joined with your commit address. If your SourceForge username is foo, that will allow everyone to write to the email address you defined on SourceForge via the alias email@example.com.
- Get an account on tiki.org
- Read Where to commit
A good idea
- Read Hello World
- Read about the Tiki Model
- Join the developers mailing list
- Join the code commit mailing list
- Come on the IRC channel, and ask one of the admins (see: WhoWhat for list) about the ceremony for joining the community and getting SVN commit access. Please do put this channel in your favorites and hang out with us. If no admin is around, please contact MarcLaporte
- Get code via SVN so you can easily keep up to date and share back fixes and enhancements.
- Read TikiDevNewbie
- Get familiar with the The Wiki Way and The Cathedral and the Bazaar
- Join Tiki community members on various social networking sites such as Facebook, Twitter, LinkedIn, Black Duck Open Hub or others
If you don't know how to use SVN or it's not convenient to set it up or learn at the moment, you are most welcome to submit a patch.