History: Developers Team
Preview of version: 25
- «
- »
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
- DevTwoDogFood
- fix bugs 😀
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"
- 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.)
Projects
- Cleanup
Interaction with other communities
- SourceForge.net
- 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 Summer of Code, Chrome issues, etc.
- Microsoft (Greg Martin & Marc Laporte)
- Clipperz + our community account (Marc)
- Piwik (changi?)
- Firefox
- PHPIDS (Marc & Amette)
- HTMLPurifier
- CKEditor
- jQuery.sheet (Robert)
- jQuery.s5 (Robert)
- SabreDAV
Sub Teams
- Quality Team
- Wishlist Team
- Testing Team
- Security Team
- Performance Team
- Packaging Team
- Later on, we may make teams by components (front-end, etc.) or by Major use cases.