OATSoft Trac
Welcome to the Oatsoft management trac
This TRAC is being restructured following the OATSOFT site launch. The next set of the objectives for the site development are now listed on the site. Please file feature requests and bugs as tickets (click new ticket above). Use this WIKI part of the TRAC for general discussion - any actions/deliverables noted in the WIKI should be replicated as tickets.
Post-Launch Requirements
Summary: The use of the software centre needs to be streamlined, particularly with respect to adding software downloads. The final tools for developers need to be finalised and the structure of the forge pages of the site need to be finalised.
Summary: The next main steps are to complete the addition of the software and restructuring of the Forge content. In addition the use of noticeboards/other communications tools needs to be looked into.
Summary: The update of software listings needs to be addressed and a policy developed, maybe in combination with some automation (e.g. auto-emailing authors). Also, non-floss authors need to be contacted to ask them to consider to use floss. In general, communications need to be looked into. Consider what to so about commercial software
Technical Notes and Requirements
- Server Setup - Needs updating
- Server Documentation - Needs updating
- Accessibility
Pre-Launch Archive information
- OATS Site, suggestions and work for the oatsoft Plone.
- AlphaTestFeedback, BetaTesting, BetaStageAddedRecords
- Floss, definitions, descriptions and useful resource on flossing.
- Germination, proposals for projects to work on in detail.
- Cultivation, projects in progress ready for release into the forge.
Using Trac
This is a trac site, here are some helpful pages on using trac and the wiki.
Local trac information. User comments and suggestions about the use of the OATS trac.
