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.
/Linus
2008/5/13, Tom Morris <[EMAIL PROTECTED]>:
>
> On Tue, May 13, 2008 at 3:32 AM, Thomas N. <[EMAIL PROTECTED]> wrote:
>
> > 2. The module should be loaded and appear in the import dialog (manifest
> problem?).
>
> This is unlikely to be a manifest problem. Does the new module
> implement ImportInterface and ModuleInterface? Is it getting found
> and initialized correctly? If you're testing from Eclipse, you'll
> probably want to include the module explicitly using
> -Dargouml.modules=... in your launch definition.
>
> > I'm also subscribed to all mailing lists of argouml-java. Please feel
> invited to join,
> > there's not much traffic yet, and further progress should be
> discussed/documented there.
>
> I would strongly encourage you to not fork the mailing lists until
> there is too much traffic on the main argouml lists and people
> complain about it. We really don't need dozens of email lists with
> two or three messages a year each. Ditto for the bug databases.
>
> Speaking of bugs, I've been focusing on fixing bugs in the current
> Java RE module. Is it safe to assume that those bug fixes will be
> ported to the shiny new module? What's the transition plan?
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
