Hi Linus, if you wish to remove any mailing list or the separate issuezilla, then I'm more than happy with that, just go ahead! I just subscribed to everything available to not miss anything by accident. With the Java module we have the comfortable situation that it's functionality was always part of the core ArgoUML, and it will always be part of the ArgoUML distribution, so no separation of bug db or mailing lists is needed. Good for the user!
Just keep the commits mailing list if you want, I don't care as long as commit mails are sent to any address. Regarding dev mailing list: not needed for now, unless someone complains about too detailed discussions about Java support related code here in this dev mailing list. Thomas -------- Original-Nachricht -------- > Datum: Wed, 14 May 2008 08:01:20 +0200 > Von: "Linus Tolke" <[EMAIL PROTECTED]> > An: [email protected] > Betreff: Re: [argouml-dev] argouml-java > I think the developers of each project must decide for themselves what is > the most convenient way to deal with it. The problem appears if the > developers of a project are not active. In that case the maintenance of > the > project should, at some basic level, be taken care of by the group of > developers of the main project, to keep the project up to date with the > changes in ArgoUML. For that purpose it is more convenient to keep the > issues in the same issuezilla. > > I have not been very active in following up inactivity in different > projects. We could have a process for that, including at some point moving > issues to the main project issuezilla. We don't have a process for > creating > projects either. Sofar I have set up the projects from a list of steps in > my > head (including removing the announce mailing list and Discussion forums > and > pointing to the main issuezilla). For the argouml-java project I have > forgotten the of the Discussion forum and pointing to the main issuezilla > as > you can see. Please fix that! > > /Linus > > > 2008/5/14, Luis Sergio Oliveira <[EMAIL PROTECTED]>: > > > > Linus Tolke wrote: > > > > > Hello! > > > Separating in another project definately splits the commits mailing > > > lists. My reasoning there is that developers interested in several > project > > > can subscribe to both while developers interested in only one of the > > > projects need the split to avoid receiving mail from the other part. > > > When it comes to announce and users' mailing list, I have removed > most > > > of them for the subprojects. It looks like I haven't removed the > users' > > > mailing list for the argouml-java project. Shall I do that? > > > This leaves two mailing lists: issues and dev. I agree with Tom that > we > > > should try to keep the whole of the project together for the time > being. The > > > dev list is available when needed. I could remove it to show the > intent even > > > more clearly. > > > I don't think the issues list can be removed. It is there to notify > > > everyone when an issue is entered. I also think that we should, for > issues, > > > keep the projects together in the argouml project. This requires > > > contributors to the argouml-java project to also get an Observer role > in the > > > argouml project granted to be able to work with the issues but I think > that > > > is simple enough. > > > > > NOTE (and slightly OT): in argouml-cpp we're using the issues db there > and > > I'm happy with it, although some times I get users creating issues in > core > > argouml issues db, I wouldn't remove the sub-project issues db. > > > > So, I hope that the above won't become guidelines for all > sub-projects... > > > > Luís > > > > > /Linus > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
