Version 1 (modified by 13 years ago) (diff) | ,
---|
Quattor Initial Backlog
TracNav
Table of Contents
This page contains the initial backlog for Quattor development that will be used to start the CRUM-based process.
Web site
- Landing page for quattor.org on SF (David)
- Develop a stylesheet that could be reused by pages generated from Maven
- Fix Trac server certificate CA (Michel)
- Remove Trac request for a user certificate for anonymous access (Michel)
- Enable Trac indexing by robots (Michel)
- Fix navigation menu behaviour: discuss by email what we want to implement, then implement it (Michel)
Documentation
- Better integration of former MediaWiki content into existing section, remove duplicates
- Update SINDES related documentation, improve based on BEGrid wiki and RAL experience
- Clarify or add missing material to answer Ronald's questions after his QWG migration experience
- Implement changes based on Andrea's review (to be monitored in monthly meetings)
- Fix/improve Quattor description in Wikipedia and Freshmeat
- Ensure Quattor is reference on the appropriate open-source or software project portals
- Ohloh
- Krugle
Build tools
- Final cleanups (Cal)
Configuration Modules
New SPMA
- Test at GRIF (Victor) and CERN (Luis)
QWG
- Organize initial development meeting based on today's proposal (Michel)
- Implement namespace improvements as suggested by Nic
- standard/hardware/... including a vendor directory
- vendor/version-arch or vendor/version/arch for OS templates
Monitoring
- Implement NIKHEF suggestions to add flexibility and support hierarchy of Nagios servers (Ronald?)
- Collect existing Nagios probes related to Quattor activity monitoring, put them in SF and package them as a RPM (Christos)
SINDES
- Check with CERN agreement to import it in SF repository (Véronique)
- Check licensing (Véronique)
- Clarify official distribution point/channel (CERN)
- Integration Quattor server configuration (RAL)
Miscellaneous
- Create a developer's mailing list
- Document/encourage the use of Git as a front-end to SVN to better evaluate potential benefits of a migration
- Check how Git repositories can be configured on SF, migration from SVN, how many repositories by project...
- Enable and create for new bits like Aquilon
- Calendar of events on the wiki or in SF
- May use "news" feature rather than calendar