Structures

The Tiki community is a heavy user of SVN. While many open source communities have a send-a-patch-and-someone-else-will-commit approach*

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

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 foo@users.sourceforge.net.

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

Keywords

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.