From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c78684b2d4add105 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-10-11 14:56:41 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!surfnet.nl!news.utwente.nl!not-for-mail From: Ching Bon Lam Newsgroups: comp.lang.ada Subject: Re: Feasibility/Requirements/Wishes of xAL (was: Standard Library Interest?) Date: Sat, 11 Oct 2003 21:56:40 +0000 (UTC) Organization: Universiteit Twente Sender: s0046388@@utwente.nl Message-ID: References: NNTP-Posting-Host: sheep.xs4all.nl X-Trace: netlx020.civ.utwente.nl 1065909400 17369 213.84.97.6 (11 Oct 2003 21:56:40 GMT) X-Complaints-To: abuse@utwente.nl NNTP-Posting-Date: Sat, 11 Oct 2003 21:56:40 +0000 (UTC) User-Agent: Xnews/5.04.25 Xref: archiver1.google.com comp.lang.ada:686 Date: 2003-10-11T21:56:40+00:00 List-Id: 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