iptel.org To-dos

iptel.org To-dos

The below is a to-do list for iptel.org, everything non-development related. Anybody wanting to help out, are welcome to do so.

This is how you do it:

1. Put your name in boldface behind an item when you start working on it. Ex. (Greger). 
2. Create the new content and/or do the task :-)
3. If you need somebody's particular review, request review. If not, let the alert function of iptel.org work its magic and people who want to have a look, will do so
4. Strike out the item from the list below, ex. Create to-do page You can also add a link to the new content you created if you like

The groupings below will change over time dependent on the focus of the work.

Prepare for Release Candidate of 2.0.x

• Declare feature freeze (Greger)
• Make What's new section complete enough to support people testing:
• Improve select documentation
• Remove seri.cfg config in overview of changes and refer to ser.cfg in etc/
• Complete the overview of changes to ser.cfg
• Finalize a complete example ser.cfg to be used for simple testing (Nils)
• Create test instructions (web page for how to get started)
• Create tar-package with release candidiate

Release of 2.0.x

• Update Getting Started configuration files and document to Issue 6 for 2.0 (Greger)
• Create m4 build system for generation of ser.cfg Getting Started files and maintenance of people's own ser.cfg (Greger)
• Add Big picture (SERi, SERwebi, SEMSi etc) first chapter to SER - Getting Started
• Make auto-generated module docs available commentable (Steve + Greger); Just a few mdoules are missing now
• Review copyright and maintenance developer for each module (Greger)
• Move docs to a separate CVSi tree (Jan)
• Go through and clean-up all text files in the CVS tree
• Write reference guide using pieces from what's new 2.0 and SER Getting Started
• grep the code to find all defined: selects, functions, parameters and make sure ALL are covered in the docs (new search tool allows reporting missing docs)
• Change What's New into a migration guide (Simon Miles, editor)
• Generate html and pdfs of manuals, getting started, and module docs (only when released!!)

Beyond 2.0.x release

• Go through wishlist and agree to a roadmap for 2.1
• Review copyright policies
• Review release management and agree to release procedures

Resources/Content

• Complete Who's who
• Migrate all how-tos/FAQs from ONsip.org (Lakmal)
• Migrate all relevant content from http://old.iptel.org/(Lakmal)
• Write development guidelines (code styles etc) (Jan)

General iptel.org Management

• Install calender and countdown modules  http://drupal.org/project/Modules/category/61
• Create system for export of manuals, like admin guide and SER - Getting Started, to Drupal books (with ability to comment)(Greger)
• Create system for export of SER module docs to drupal pages (for each release)