RE: (FC-Devel) New project coordinator

["Vipul Kocher" <vipul@riverrun.com>]

Hi all,
Good luck Sami.

IMHO we might require to do some of the following things for sooth running
of FreeCASE.
May be we should add to this list/compile a similar list. This might help in
formalizing some aspects of this PROJECT which is required for a project of
this nature and size, with teams distributed across continents.

1. Project management (non-technical)
	(A.) A knowledge base of SKILL SET: A list of all people interested in
contributing. This list should be more detailed than the one present on the
website, right now. The list SHOULD include the following along with an
indicator of proficiency (Good, OK, do not know
	1. Expertise area (CASE tools, Design, Testing, etc...)
	2. Languages comfortable with (e.g. c, C++, Java)
	3. OS (Unix, NT, Linux)
	4. Languages willing to learn for the FREECASE project, if needed (To be
filled later once the debate starts
	5. NUMBER OF HOURS YOU CAN SPEND (AVERAGE) ON FREECASE Project: This is
very important
	6. CASE TOOL
	7. UML
	8. METHODOLOGY (BOOCH, OMT...)

	(B.)Some mechanism for the following:
	1. Reviews: Some person or group made responsible for reviewing/getting the
reviews done for every single item. This group should also be responsible
for review follow-ups as  compilation of review comments, their
incorporation, taking decision not to incorporate some things etc. Good
reviews are extremely critical to the success of any project, as you all
know.
	2. Schedule tracking: Some mechanism by which every body can see, what all
is going on right now. Slips, if any, should be communicated as soon as
possible.
	3. Dependency management: How best to do the development in parallel.
(Should I put it under technical head? :-) )

	(C.)Version control system:
	1. A repository/Version control system for every document (code or
otherwise) produced, including the review comments.

	(D.) A BODY which will have the final say in all cases of contentions.
VOTING FOR ALL ISSUES MAY NOT BE A PRACTICAL thing.

Please feel free to add to it (if you think it is worth it :-) )

2. Project management (Technical)
	(A.) Do we need to follow/decide on any methodology. Of course our
Analysis/design should be done using UML. What tool would we use to draw
these diagrams? etc.
	(B.) Design/Coding guidelines, Naming conventions etc.
	TBD

3. Support
	(A.) Support for existing, ON-WORK, people
		Committees for helping people working on a particular area. For example a
'UML' committee could help the developers on any issues related to UML. They
would also answer non-contributing members on these questions (may be at a
lower priority.) This would greatly help in gaining knowledge.

	(B.) support for people NEW TO THE GROUP
	1. Documents telling Project vision and history, making available all the
required documents as requirements, design etc., having a group help out
these people to get oriented and answering questions.
	2. A FAQ. Some how things are not complete without a FAQ. ;-)
	3. Collection of links for information on various topics relevant to us as
UML, OO analysis and design etc.
	4. A progress report, telling where we are currently.
	5. Areas we need help in/where we can accommodate people.

	(C.) External interface committee:
	People to be active on comp.Object and OTUG list etc. where we can get
advice from experts. I intend to write to some NEUTRAL (No commercial CASE
TOOL RELATED interest) experts for help, if needed. The names I have in mind
are Robert C. Martin (www.oma.com), Bertrand Meyer of Eiffel fame, Andrew
Koenig and Strostrup. May be we can compile a list of such highly respected
experts, communicate with them asking would they lend a helping hand in case
we are stuck somewhere and/or require their advise.

I see quiet some load on the web page maintainer. Some people might be
interested in this.

I would appreciate comments on this. (No, not the PERSONAL kind. :-) ).
Regards,
Vipul Kocher.