Re: Feasibility/Requirements/Wishes of xAL (was: Standard Library Interest?)

[Ching Bon Lam <c.lam_REMOVE_THIS@student.utwente.nl>]

I'd like to talk about something i'm not experienced in:

1. Setting up a project.
2. Managing a project.

You need some kind of mission statement. This statement will include goals 
like "Having a consistent interface througout the whole library".

You need some sort of infrastructure/platform for communication between 
people. A good way is a dynamic website, with information about people and 
such things.

You need documentation about procedures such as "how to add a component to 
the library". This procedure would contain stuff like "First write an API, 
documentation and examples and let it be reviewed. Once that's approved, 
implement it. etc".

You need to have development tools that everybody have access to it and say 
that you are going to use those tools for everything you want to program. 
For example (not sure if it is a good one), I've the impression that the 
GNU Make tool is not well supported in a Win32 environment. So we should 
use a more portable "make" tool.

You need a periodic cycle for revision/release. A period for new 
components, a period for checking and cleaning the code etc.

I'm sure i've missed a lot of other stuff as i've no experience in setting 
up/managing big projects, as xAL will be IF it's going to be set up.

I would like to hear your thoughts about it, and if you have, suggestions, 
additions etc.

Bon