[openi18n-im:01250] Re: Communications & Tools for the project

Suraj,

Good summary. I always like to improve information management so that
all of us that involves in the project can retrieve and submit
information more effectively.

We already have most of the tools in place, all we need is find some
ways to enhance the usage. Wiki is the only thing that we haven't
implement and from the replies and seems agreed it sounds like a good
tool for contributors and users.

What are your thoughts on development tools?

Leon

On Wed, 2005-03-02 at 22:14 -0800, Suraj Kurapati wrote:
> SUMMARY
> 
> (high change) IRC -> Mailing List -> Wiki -> IIIMF Website (low change)
> 
> 
> PROPOSAL
> 
> I think a combination of a few of these methods would serve us best. For 
> example, IRC is good for quick up-to-the-minute discussions. The 
> mailing-lists may be used for the purpose of announcements and major 
> changes. Next, a Wiki can hold all the interesting design decisions, 
> group decisions, etc. And finally, there is the official IIIMF website 
> for mostly permanent information like project road-map, related 
> projects, etc.
> 
> Perhaps this is too exhaustive, but I think it would organize 
> information and decisions in a logical manner. This organization is 
> also similar to how some projects have separate mailing lists for 
> developers, announcements, etc.
> 
> 
> RISKS
> 
> The proposed method of organization presents a major task of passing 
> information from frequently changing mediums to infrequently changing 
> ones (i.e. from left to right on the summary above). That is, someone 
> must monitor a medium, look for useful information/decisions, and pass 
> them to the next medium of infrequent-change.
> 
> Though this may sound daunting at first, we all do perform such tasks to 
> some degree, such as storing interesting items from mailing lists in our 
> computer. Thus interesting information/decisions will naturally be 
> passed to infrequently changing mediums by us.
> 
> Now that we have some system of (somewhat) automatic passing of relevant 
> information to infrequently changing medium, we run into a problem of 
> disorganization. There will be too many interesting items; all of which 
> are thrown together randomly. Also, old interesting items may not be too 
> relevant for us anymore, so those need to be removed from the 
> main-stream and put into archives.
> 
> Once again, this is not as bad as it sounds, because there are already 
> some of authority amongst us, who administer the mailing lists, official 
> IIIMF website, etc.
> 
> 
> CONCLUSION
> 
> Those are my overall thoughts for the information-management problem. I 
> am eager to see what ideas others have and what decision is made on this 
> problem.
> 
> Cheers!
> 
> > -- Development --
> > Bug Tracking system. This is important because it is a central place for
> > user/QA/Developers to exchange information. Have we used it well enough?
> > If not what is the obstacle that prevent you using it?
> > 
> > Version control system. Do you find any difficulties or thought of
> > enhancements we should make?
> > 
> > I hope this will open a dialog for us to create some discussions on
> > improvements.
> > 
> > Regards,
> > Leon
> > 
> > 
>