Re: [MINA] Should it stay here? (Was: Re: [scm][VOTE] Reorganizing the re-organized structure.)

[da...@daune-consult.com]

Moving Mina does not necessarily imply changing who contributes/leads.

It is just a matter of convenience: separate tree structure, its own mailing
list (not having to use prefixes [MINA], [DIREVE]...)

Cheers,

J-F

> Alex wrote:
>
>> Projects don't jump out into their own umbrella every day or by 
>> themselves :-).  It takes people.  This project (MINA) was born here 
>> through the ideas and collaboration of a few people.  Trustin of 
>> course was and is to a large degree the main driver and this must 
>> change to go further.  We've been thinking about this for some time 
>> as you may have seen from previous emails.
>
> I totally understand
>
>> Perhaps you guys can start getting more involved to make your wishes 
>> come true ;).
>
> yes, I'd love to, not sure if my boss would too.
>
>>
>> FYI - the MINA mailing list is on order from infrastructure.
>
> great
>
> by the way, I would not like mina to become part of jakarta-commons.
> I guess that's not gonna happen soon, right ?
>
>

Re: [MINA] Should it stay here? (Was: Re: [scm][VOTE] Reorganizing the re-organized structure.)

[Brett Porter <br...@gmail.com>]

This has been brought up a lot now. Time for a FAQ on the MINA page?

For those points:
* separate tree structure: this can be done within the Directory tree
if necessary. It can have a separate trunk again if that makes things
easier as well.

* separate mailing list: as already said, this is being done

So, can anyone list a benefit of moving MINA now rather than later? And where?

The downsides are that it will take more work, and the *only* place it
can go right now is Jakarta (commons) - which would imply either
staying there or another move. I don't see any benefit in that. No
other TLP would be suitable right now, and it's got a long way to go
before being ready to be self-sustaining as a TLP.

Cheers,
Brett

On 1/8/06, daune.jf@daune-consult.com <da...@daune-consult.com> wrote:
>
> Moving Mina does not necessarily imply changing who contributes/leads.
>
> It is just a matter of convenience: separate tree structure, its own mailing
> list (not having to use prefixes [MINA], [DIREVE]...)
>
> Cheers,
>
> J-F
>
> > Alex wrote:
> >
> >> Projects don't jump out into their own umbrella every day or by
> >> themselves :-).  It takes people.  This project (MINA) was born here
> >> through the ideas and collaboration of a few people.  Trustin of
> >> course was and is to a large degree the main driver and this must
> >> change to go further.  We've been thinking about this for some time
> >> as you may have seen from previous emails.
> >
> > I totally understand
> >
> >> Perhaps you guys can start getting more involved to make your wishes
> >> come true ;).
> >
> > yes, I'd love to, not sure if my boss would too.
> >
> >>
> >> FYI - the MINA mailing list is on order from infrastructure.
> >
> > great
> >
> > by the way, I would not like mina to become part of jakarta-commons.
> > I guess that's not gonna happen soon, right ?
> >
> >
>
>
>
>