The Developers Team are the umbrella group responsible to make Tiki better as an application. Please see how to get commit access.
Release responsibilities
- Make Tiki good enough (fix bugs, etc.) so that it can be released by the Packaging Team
- Provide Documentation Team with basic information about features.
- Update all Developer documentation to take into account new version number and features. Ex.: Download, Commit, Hello World, etc....
- Review all Experimental branches and delete if appropriate (could be done at any time, but a 6-month reminder is good).
Todos
Ongoing responsibilities
- Semi-automatic merging period: handling them and deciding when to stop
- Fix bugs
- Add features
- Keep branches and trunk in a dogfood quality and "releasable on relatively short notice"
- SourceForge.net: Keep our space there tidy there
- Keep up to date and useful all the developers documentation workspace at http://dev.tiki.org (while bug report & wish list triage is handled by the Wishlist Team.)
- See Interaction with other communities below
Projects
- Clean-up review documentation for developers (intro for new devs)
- Migrate to Allura (who can take the lead on this?)
- Cleanup
Interaction with other communities
In collaboration with Partnership Team
- Track all code included in Tiki External Libs (Karen)
- Make sure we are up to date for supported versions
- For security issues, an update may be warranted in the LTS versions with Security Team. Ex. ZF security updates can make it to 6.x if they affect our features.
- Make sure the list below has a contact name for each
- Be in touch with various projects for cross promotion (Tiki moved to Smarty 3, Tiki uses latest version of HTML Purifier, and thus, this should be indicated on their site) in coordination with Partnership Team
- Keep list of included libs up to date (so at any give time, we know what could/should be upgraded)
Included code
- jQuery community (Jonny?)
- Smarty community (Stéphane?)
- Zend Framework community
- PHP community
- MySQL/MariaDB communities
- cclite software and their main developer (Xavi)
- R software and their community (Xavi)
- jCapture and their community (Marc)
- Kaltura. They requested a cleanup of our documentation page. Also, the special license exception needs clarifying. Also dogfood at tv.tiki.org needs to be decided/cleared up
- Google: Google Translation, Google Summer of Code, Chrome issues, etc.
- Microsoft Translations (Greg Martin & Pascal St-Jean)
- Clipperz + our community account (Marc)
- Piwik (changi?)
- HTMLPurifier
- CKEditor (Geoff?)
- jQuery.sheet (Robert)
- jQuery.s5 (Robert)
- PHPIDS (Integration on hold for now, but Marc is the contact)
- SabreDAV (not yet integrated, but is on roadmap)
Sub Teams
alias