An Official Request For Moving Cactus In The Incubator

------=_Part_54432_28160717.1173119371511
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello guys,

first of all let me introduce myself. My name is Petar Tahchiev and I am
from Bulgaria.

I wanted to enroll in the last-years Google Summer Of Code
where I applied with the
project of migrating the Cactus build system to Maven. Unfortunatelly me and
Felipe Leme (my mentor), who I would like to thank once again for the
encouragement
and the help he provided me, weren't qualified. Later I had a
few personal issues to solve, but the point is that I continued to work on
my own and sooner I managed to
migrate the Cactus project to be built with Maven.

When everything was done I started submitting patches in the cactus jira,
for some known bugs. The problem with the patch of the build system was that
it turned out to be very large so I couldn't apply it in the jira. Then me
and Felipe agreed that it would be better to move the cactus to a separate
repository
and test the build system there (you understand that the new build structure
was absolutely different from the old one and merging was a kind of a tough
task).
So I got my work and imported it in my own repository at the
sourceforge.netwhere we began testing. The point is that when we
wanted to apply the
changes in the
cactus trunk in the Apache repository we were adviced by Martin van den Bemt
that we have to ask that the project be moved in the incubator first and
then when the
code is appropriate for the cactus's trunk move it in the trunk.

Now the process of moving Cactus in the incubator is stalled, as well as our
work on it, because I want to move it in the incubator, before I
continue making

additional changes and implementing new features.

So my request to you guys is this: if anyone can help us move the code in
the incubator, he is more than wellcome.
Thank you very much.

P.S. You may find additional information of the whole process here:

[1] http://www.mail-archive.com/cactus-dev@jakarta.apache.org/ms g08579.html
[2] http://www.nabble.com/Question-About-the-Current-State-Of
-Cactus-In-the-Incubator-t3222261.html

--
Regards, Petar!
Karlovo, Bulgaria.

Public PGP Key at: http://keyserver.linux.it/pks
/lookup?op=get&search=0x1A15B53B761500F9
Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9

------=_Part_54432_28160717.1173119371511--

Re: An Official Request For Moving Cactus In The Incubator

will come back to this on friday..

Mvgr,
Martin

Petar Tahchiev wrote:
> Hello guys,
>
> first of all let me introduce myself. My name is Petar Tahchiev and I am
> from Bulgaria.
>
> I wanted to enroll in the last-years Google Summer Of Code
> where I applied with the
> project of migrating the Cactus build system to Maven. Unfortunatelly me
> and
> Felipe Leme (my mentor), who I would like to thank once again for the
> encouragement
> and the help he provided me, weren't qualified. Later I had a
> few personal issues to solve, but the point is that I continued to work on
> my own and sooner I managed to
> migrate the Cactus project to be built with Maven.
>
> When everything was done I started submitting patches in the cactus jira,
> for some known bugs. The problem with the patch of the build system was
> that
> it turned out to be very large so I couldn't apply it in the jira. Then me
> and Felipe agreed that it would be better to move the cactus to a separate
> repository
> and test the build system there (you understand that the new build
> structure
> was absolutely different from the old one and merging was a kind of a tough
> task).
> So I got my work and imported it in my own repository at the
> sourceforge.netwhere we began testing. The point is that when we
> wanted to apply the
> changes in the
> cactus trunk in the Apache repository we were adviced by Martin van den
> Bemt
> that we have to ask that the project be moved in the incubator first and
> then when the
> code is appropriate for the cactus's trunk move it in the trunk.
>
> Now the process of moving Cactus in the incubator is stalled, as well as
> our
> work on it, because I want to move it in the incubator, before I
> continue making
>
> additional changes and implementing new features.
>
> So my request to you guys is this: if anyone can help us move the code in
> the incubator, he is more than wellcome.
> Thank you very much.
>
> P.S. You may find additional information of the whole process here:
>
> [1] http://www.mail-archive.com/cactus-dev@jakarta.apache.org/ms g08579.html
> [2] http://www.nabble.com/Question-About-the-Current-State-Of
> -Cactus-In-the-Incubator-t3222261.html
>

Re: An Official Request For Moving Cactus In The Incubator

------=_Part_1111_15751163.1173443904469
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 3/7/07, Martin van den Bemt wrote:
>
> will come back to this on friday..
>
> Mvgr,
> Martin
>
> Petar Tahchiev wrote:
> > Hello guys,
> >
> > first of all let me introduce myself. My name is Petar Tahchiev and I am
> > from Bulgaria.
> >
> > I wanted to enroll in the last-years Google Summer Of Code
> > where I applied with the
> > project of migrating the Cactus build system to Maven. Unfortunatelly me
> > and
> > Felipe Leme (my mentor), who I would like to thank once again for the
> > encouragement
> > and the help he provided me, weren't qualified. Later I had a
> > few personal issues to solve, but the point is that I continued to work
> on
> > my own and sooner I managed to
> > migrate the Cactus project to be built with Maven.
> >
> > When everything was done I started submitting patches in the cactus
> jira,
> > for some known bugs. The problem with the patch of the build system was
> > that
> > it turned out to be very large so I couldn't apply it in the jira. Then
> me
> > and Felipe agreed that it would be better to move the cactus to a
> separate
> > repository
> > and test the build system there (you understand that the new build
> > structure
> > was absolutely different from the old one and merging was a kind of a
> tough
> > task).
> > So I got my work and imported it in my own repository at the
> > sourceforge.netwhere we began testing. The point is that when we
> > wanted to apply the
> > changes in the
> > cactus trunk in the Apache repository we were adviced by Martin van den
> > Bemt
> > that we have to ask that the project be moved in the incubator first and
> > then when the
> > code is appropriate for the cactus's trunk move it in the trunk.
> >
> > Now the process of moving Cactus in the incubator is stalled, as well as
>
> > our
> > work on it, because I want to move it in the incubator, before I
> > continue making
> >
> > additional changes and implementing new features.
> >
> > So my request to you guys is this: if anyone can help us move the code
> in
> > the incubator, he is more than wellcome.
> > Thank you very much.
> >
> > P.S. You may find additional information of the whole process here:
> >
> > [1]
> http://www.mail-archive.com/cactus-dev@jakarta.apache.org/ms g08579.html
> > [2] http://www.nabble.com/Question-About-the-Current-State-Of
> > -Cactus-In-the-Incubator-t3222261.html
> >
>
> ------------------------------------------------------------ ---------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
Ok, no problem.

I know that you are busy, but I have another idea that came to me reading
the Matt Benson's post. In fact the guys are
dealing with a project that seems to be inspired the jakarta commons Convert
project and so it would be possible to
accept the code without passing through the incubator. So why isnt' this
situation possible for Cactus (I mean I have refactored existing code and
added the maven xml files - it is not a new project).

I also agree that passing through the incubator is the best solution in the
great majority of cases, but in my opinion there are still some cases (like
Cactus for instance) that are threatened of stalling even more.

P.S. Personaly for me, I am happy with both of the solutions - with or
without the incubator. My desire is to start working on the project as soon
as possible because we are planning of implementing some new features and
then releasing a RC.

Looking forward to your reply.
--
Regards, Petar!
Karlovo, Bulgaria.

Public PGP Key at:
http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53 B761500F9
Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9

------=_Part_1111_15751163.1173443904469--

Re: An Official Request For Moving Cactus In The Incubator

Hence the reason I wanted to wait for a response till I had more time (still busy).. My approach for
you would have been : get a software grant, ccla and icla on file and start a vote on you being a
committer for cactus, I just failed horribly to send out that mail (btw sending in those documents
is what legal incubation is about).

I will send you some links for this, if you didn't figure it out earlier or someone else beats me to
it..

Since there is still enough interest in Cactus I think that new activity will be enough to get more
people aboard and get the ball rolling again :)

Mvgr,
Martin

Petar Tahchiev wrote:
> On 3/7/07, Martin van den Bemt wrote:
>>
>> will come back to this on friday..
>>
>> Mvgr,
>> Martin
>>
>> Petar Tahchiev wrote:
>> > Hello guys,
>> >
>> > first of all let me introduce myself. My name is Petar Tahchiev and
>> I am
>> > from Bulgaria.
>> >
>> > I wanted to enroll in the last-years Google Summer Of Code
>> > where I applied with the
>> > project of migrating the Cactus build system to Maven.
>> Unfortunatelly me
>> > and
>> > Felipe Leme (my mentor), who I would like to thank once again for the
>> > encouragement
>> > and the help he provided me, weren't qualified. Later I had a
>> > few personal issues to solve, but the point is that I continued to work
>> on
>> > my own and sooner I managed to
>> > migrate the Cactus project to be built with Maven.
>> >
>> > When everything was done I started submitting patches in the cactus
>> jira,
>> > for some known bugs. The problem with the patch of the build system was
>> > that
>> > it turned out to be very large so I couldn't apply it in the jira. Then
>> me
>> > and Felipe agreed that it would be better to move the cactus to a
>> separate
>> > repository
>> > and test the build system there (you understand that the new build
>> > structure
>> > was absolutely different from the old one and merging was a kind of a
>> tough
>> > task).
>> > So I got my work and imported it in my own repository at the
>> > sourceforge.netwhere we began testing. The point is that when we
>> > wanted to apply the
>> > changes in the
>> > cactus trunk in the Apache repository we were adviced by Martin van den
>> > Bemt
>> > that we have to ask that the project be moved in the incubator first
>> and
>> > then when the
>> > code is appropriate for the cactus's trunk move it in the trunk.
>> >
>> > Now the process of moving Cactus in the incubator is stalled, as
>> well as
>>
>> > our
>> > work on it, because I want to move it in the incubator, before I
>> > continue making
>> >
>> > additional changes and implementing new features.
>> >
>> > So my request to you guys is this: if anyone can help us move the code
>> in
>> > the incubator, he is more than wellcome.
>> > Thank you very much.
>> >
>> > P.S. You may find additional information of the whole process here:
>> >
>> > [1]
>> http://www.mail-archive.com/cactus-dev@jakarta.apache.org/ms g08579.html
>> > [2] http://www.nabble.com/Question-About-the-Current-State-Of
>> > -Cactus-In-the-Incubator-t3222261.html
>> >
>>
>> ------------------------------------------------------------ ---------
>> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: general-help@jakarta.apache.org
>>
>>
> Ok, no problem.
>
> I know that you are busy, but I have another idea that came to me reading
> the Matt Benson's post. In fact the guys are
> dealing with a project that seems to be inspired the jakarta commons
> Convert
> project and so it would be possible to
> accept the code without passing through the incubator. So why isnt' this
> situation possible for Cactus (I mean I have refactored existing code and
> added the maven xml files - it is not a new project).
>
> I also agree that passing through the incubator is the best solution in the
> great majority of cases, but in my opinion there are still some cases (like
> Cactus for instance) that are threatened of stalling even more.
>
> P.S. Personaly for me, I am happy with both of the solutions - with or
> without the incubator. My desire is to start working on the project as soon
> as possible because we are planning of implementing some new features and
> then releasing a RC.
>
> Looking forward to your reply.

Re: An Official Request For Moving Cactus In The Incubator

------=_Part_1471_21838506.1173445380116
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 3/9/07, Martin van den Bemt wrote:
>
> Hence the reason I wanted to wait for a response till I had more time
> (still busy).. My approach for
> you would have been : get a software grant, ccla and icla on file and
> start a vote on you being a
> committer for cactus, I just failed horribly to send out that mail (btw
> sending in those documents
> is what legal incubation is about).
>
> I will send you some links for this, if you didn't figure it out earlier
> or someone else beats me to
> it..
>
> Since there is still enough interest in Cactus I think that new activity
> will be enough to get more
> people aboard and get the ball rolling again :)
>
> Mvgr,
> Martin
>
> Petar Tahchiev wrote:
> > On 3/7/07, Martin van den Bemt wrote:
> >>
> >> will come back to this on friday..
> >>
> >> Mvgr,
> >> Martin
> >>
> >> Petar Tahchiev wrote:
> >> > Hello guys,
> >> >
> >> > first of all let me introduce myself. My name is Petar Tahchiev and
> >> I am
> >> > from Bulgaria.
> >> >
> >> > I wanted to enroll in the last-years Google Summer Of Code
> >> > where I applied with the
> >> > project of migrating the Cactus build system to Maven.
> >> Unfortunatelly me
> >> > and
> >> > Felipe Leme (my mentor), who I would like to thank once again for the
> >> > encouragement
> >> > and the help he provided me, weren't qualified. Later I had a
> >> > few personal issues to solve, but the point is that I continued to
> work
> >> on
> >> > my own and sooner I managed to
> >> > migrate the Cactus project to be built with Maven.
> >> >
> >> > When everything was done I started submitting patches in the cactus
> >> jira,
> >> > for some known bugs. The problem with the patch of the build system
> was
> >> > that
> >> > it turned out to be very large so I couldn't apply it in the jira.
> Then
> >> me
> >> > and Felipe agreed that it would be better to move the cactus to a
> >> separate
> >> > repository
> >> > and test the build system there (you understand that the new build
> >> > structure
> >> > was absolutely different from the old one and merging was a kind of a
> >> tough
> >> > task).
> >> > So I got my work and imported it in my own repository at the
> >> > sourceforge.netwhere we began testing. The point is that when we
> >> > wanted to apply the
> >> > changes in the
> >> > cactus trunk in the Apache repository we were adviced by Martin van
> den
> >> > Bemt
> >> > that we have to ask that the project be moved in the incubator first
> >> and
> >> > then when the
> >> > code is appropriate for the cactus's trunk move it in the trunk.
> >> >
> >> > Now the process of moving Cactus in the incubator is stalled, as
> >> well as
> >>
> >> > our
> >> > work on it, because I want to move it in the incubator, before I
> >> > continue making
> >> >
> >> > additional changes and implementing new features.
> >> >
> >> > So my request to you guys is this: if anyone can help us move the
> code
> >> in
> >> > the incubator, he is more than wellcome.
> >> > Thank you very much.
> >> >
> >> > P.S. You may find additional information of the whole process here:
> >> >
> >> > [1]
> >> http://www.mail-archive.com/cactus-dev@jakarta.apache.org/ms g08579.html
> >> > [2] http://www.nabble.com/Question-About-the-Current-State-Of
> >> > -Cactus-In-the-Incubator-t3222261.html
> >> >
> >>
> >> ------------------------------------------------------------ ---------
> >> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: general-help@jakarta.apache.org
> >>
> >>
> > Ok, no problem.
> >
> > I know that you are busy, but I have another idea that came to me
> reading
> > the Matt Benson's post. In fact the guys are
> > dealing with a project that seems to be inspired the jakarta commons
> > Convert
> > project and so it would be possible to
> > accept the code without passing through the incubator. So why isnt' this
> > situation possible for Cactus (I mean I have refactored existing code
> and
> > added the maven xml files - it is not a new project).
> >
> > I also agree that passing through the incubator is the best solution in
> the
> > great majority of cases, but in my opinion there are still some cases
> (like
> > Cactus for instance) that are threatened of stalling even more.
> >
> > P.S. Personaly for me, I am happy with both of the solutions - with or
> > without the incubator. My desire is to start working on the project as
> soon
> > as possible because we are planning of implementing some new features
> and
> > then releasing a RC.
> >
> > Looking forward to your reply.
>
> ------------------------------------------------------------ ---------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
It would be better you send me those links, since I have no idea what a
software grant, ccla and icla is :-).

Ok waiting for the links.

Greetings.

--
Regards, Petar!
Karlovo, Bulgaria.

Public PGP Key at:
http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53 B761500F9
Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9

------=_Part_1471_21838506.1173445380116--

Re: An Official Request For Moving Cactus In The Incubator

On 3/9/07, Petar Tahchiev wrote:
> On 3/7/07, Martin van den Bemt wrote:
> >
> > will come back to this on friday..
> >
> > Mvgr,
> > Martin
> >
> > Petar Tahchiev wrote:
> > > Hello guys,
> > >
> > > first of all let me introduce myself. My name is Petar Tahchiev and I am
> > > from Bulgaria.
> > >
> > > I wanted to enroll in the last-years Google Summer Of Code
> > > where I applied with the
> > > project of migrating the Cactus build system to Maven. Unfortunatelly me
> > > and
> > > Felipe Leme (my mentor), who I would like to thank once again for the
> > > encouragement
> > > and the help he provided me, weren't qualified. Later I had a
> > > few personal issues to solve, but the point is that I continued to work
> > on
> > > my own and sooner I managed to
> > > migrate the Cactus project to be built with Maven.
> > >
> > > When everything was done I started submitting patches in the cactus
> > jira,
> > > for some known bugs. The problem with the patch of the build system was
> > > that
> > > it turned out to be very large so I couldn't apply it in the jira. Then
> > me
> > > and Felipe agreed that it would be better to move the cactus to a
> > separate
> > > repository
> > > and test the build system there (you understand that the new build
> > > structure
> > > was absolutely different from the old one and merging was a kind of a
> > tough
> > > task).
> > > So I got my work and imported it in my own repository at the
> > > sourceforge.netwhere we began testing. The point is that when we
> > > wanted to apply the
> > > changes in the
> > > cactus trunk in the Apache repository we were adviced by Martin van den
> > > Bemt
> > > that we have to ask that the project be moved in the incubator first and
> > > then when the
> > > code is appropriate for the cactus's trunk move it in the trunk.
> > >
> > > Now the process of moving Cactus in the incubator is stalled, as well as
> >
> > > our
> > > work on it, because I want to move it in the incubator, before I
> > > continue making
> > >
> > > additional changes and implementing new features.
> > >
> > > So my request to you guys is this: if anyone can help us move the code
> > in
> > > the incubator, he is more than wellcome.
> > > Thank you very much.
> > >
> > > P.S. You may find additional information of the whole process here:
> > >
> > > [1]
> > http://www.mail-archive.com/cactus-dev@jakarta.apache.org/ms g08579.html
> > > [2] http://www.nabble.com/Question-About-the-Current-State-Of
> > > -Cactus-In-the-Incubator-t3222261.html
> > >
> >
> > ------------------------------------------------------------ ---------
> > To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: general-help@jakarta.apache.org
> >
> >
> Ok, no problem.
>
> I know that you are busy, but I have another idea that came to me reading
> the Matt Benson's post. In fact the guys are
> dealing with a project that seems to be inspired the jakarta commons Convert
> project and so it would be possible to
> accept the code without passing through the incubator. So why isnt' this
> situation possible for Cactus (I mean I have refactored existing code and
> added the maven xml files - it is not a new project).
>
> I also agree that passing through the incubator is the best solution in the
> great majority of cases, but in my opinion there are still some cases (like
> Cactus for instance) that are threatened of stalling even more.

Martin or others may answer this better - but AIUI one of the two
primary goals of the incubator is building community around code
bases. This is not just a "nice thing" at Apache - its an absolute
necessity. As an example under Apache rules without 3 votes from the
PMC (project management committee) responsible for a project you can't
release anything. Once a project falls below that critical level of
involved people its basically dead in the water as far as releasing
any software goes. In the case of a project like Cactus the main
reason for going back to the incubator would be to re-create a viable
community.

Niall

> P.S. Personaly for me, I am happy with both of the solutions - with or
> without the incubator. My desire is to start working on the project as soon
> as possible because we are planning of implementing some new features and
> then releasing a RC.
>
> Looking forward to your reply.
> --
> Regards, Petar!
> Karlovo, Bulgaria.
>
> Public PGP Key at:
> http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53 B761500F9
> Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
>

Re: An Official Request For Moving Cactus In The Incubator

On 3/9/07, Petar Tahchiev wrote:
> On 3/9/07, Martin van den Bemt wrote:
> >
> > Hence the reason I wanted to wait for a response till I had more time
> > (still busy).. My approach for
> > you would have been : get a software grant, ccla and icla on file and
> > start a vote on you being a
> > committer for cactus, I just failed horribly to send out that mail (btw
> > sending in those documents
> > is what legal incubation is about).
> >
> > I will send you some links for this, if you didn't figure it out earlier
> > or someone else beats me to
> > it..
> >
> > Since there is still enough interest in Cactus I think that new activity
> > will be enough to get more
> > people aboard and get the ball rolling again :)
> >
> > Mvgr,
> > Martin
> >
> > Petar Tahchiev wrote:
> > > On 3/7/07, Martin van den Bemt wrote:
> > >>
> > >> will come back to this on friday..
> > >>
> > >> Mvgr,
> > >> Martin
> > >>
> > >> Petar Tahchiev wrote:
> > >> > Hello guys,
> > >> >
> > >> > first of all let me introduce myself. My name is Petar Tahchiev and
> > >> I am
> > >> > from Bulgaria.
> > >> >
> > >> > I wanted to enroll in the last-years Google Summer Of Code
> > >> > where I applied with the
> > >> > project of migrating the Cactus build system to Maven.
> > >> Unfortunatelly me
> > >> > and
> > >> > Felipe Leme (my mentor), who I would like to thank once again for the
> > >> > encouragement
> > >> > and the help he provided me, weren't qualified. Later I had a
> > >> > few personal issues to solve, but the point is that I continued to
> > work
> > >> on
> > >> > my own and sooner I managed to
> > >> > migrate the Cactus project to be built with Maven.
> > >> >
> > >> > When everything was done I started submitting patches in the cactus
> > >> jira,
> > >> > for some known bugs. The problem with the patch of the build system
> > was
> > >> > that
> > >> > it turned out to be very large so I couldn't apply it in the jira.
> > Then
> > >> me
> > >> > and Felipe agreed that it would be better to move the cactus to a
> > >> separate
> > >> > repository
> > >> > and test the build system there (you understand that the new build
> > >> > structure
> > >> > was absolutely different from the old one and merging was a kind of a
> > >> tough
> > >> > task).
> > >> > So I got my work and imported it in my own repository at the
> > >> > sourceforge.netwhere we began testing. The point is that when we
> > >> > wanted to apply the
> > >> > changes in the
> > >> > cactus trunk in the Apache repository we were adviced by Martin van
> > den
> > >> > Bemt
> > >> > that we have to ask that the project be moved in the incubator first
> > >> and
> > >> > then when the
> > >> > code is appropriate for the cactus's trunk move it in the trunk.
> > >> >
> > >> > Now the process of moving Cactus in the incubator is stalled, as
> > >> well as
> > >>
> > >> > our
> > >> > work on it, because I want to move it in the incubator, before I
> > >> > continue making
> > >> >
> > >> > additional changes and implementing new features.
> > >> >
> > >> > So my request to you guys is this: if anyone can help us move the
> > code
> > >> in
> > >> > the incubator, he is more than wellcome.
> > >> > Thank you very much.
> > >> >
> > >> > P.S. You may find additional information of the whole process here:
> > >> >
> > >> > [1]
> > >> http://www.mail-archive.com/cactus-dev@jakarta.apache.org/ms g08579.html
> > >> > [2] http://www.nabble.com/Question-About-the-Current-State-Of
> > >> > -Cactus-In-the-Incubator-t3222261.html
> > >> >
> > >>
> > >> ------------------------------------------------------------ ---------
> > >> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> > >> For additional commands, e-mail: general-help@jakarta.apache.org
> > >>
> > >>
> > > Ok, no problem.
> > >
> > > I know that you are busy, but I have another idea that came to me
> > reading
> > > the Matt Benson's post. In fact the guys are
> > > dealing with a project that seems to be inspired the jakarta commons
> > > Convert
> > > project and so it would be possible to
> > > accept the code without passing through the incubator. So why isnt' this
> > > situation possible for Cactus (I mean I have refactored existing code
> > and
> > > added the maven xml files - it is not a new project).
> > >
> > > I also agree that passing through the incubator is the best solution in
> > the
> > > great majority of cases, but in my opinion there are still some cases
> > (like
> > > Cactus for instance) that are threatened of stalling even more.
> > >
> > > P.S. Personaly for me, I am happy with both of the solutions - with or
> > > without the incubator. My desire is to start working on the project as
> > soon
> > > as possible because we are planning of implementing some new features
> > and
> > > then releasing a RC.
> > >
> > > Looking forward to your reply.
> >
> > ------------------------------------------------------------ ---------
> > To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: general-help@jakarta.apache.org
> >
> >
> It would be better you send me those links, since I have no idea what a
> software grant, ccla and icla is :-).
>
> Ok waiting for the links.

http://www.apache.org/licenses/#clas

Niall

> Greetings.
>
> --
> Regards, Petar!
> Karlovo, Bulgaria.
>
> Public PGP Key at:
> http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53 B761500F9
> Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
>

Re: An Official Request For Moving Cactus In The Incubator

>>
>> I know that you are busy, but I have another idea that came to me reading
>> the Matt Benson's post. In fact the guys are
>> dealing with a project that seems to be inspired the jakarta commons
>> Convert
>> project and so it would be possible to
>> accept the code without passing through the incubator. So why isnt' this
>> situation possible for Cactus (I mean I have refactored existing code and
>> added the maven xml files - it is not a new project).
>>
>> I also agree that passing through the incubator is the best solution
>> in the
>> great majority of cases, but in my opinion there are still some cases
>> (like
>> Cactus for instance) that are threatened of stalling even more.
>
> Martin or others may answer this better - but AIUI one of the two
> primary goals of the incubator is building community around code
> bases. This is not just a "nice thing" at Apache - its an absolute
> necessity. As an example under Apache rules without 3 votes from the
> PMC (project management committee) responsible for a project you can't
> release anything. Once a project falls below that critical level of
> involved people its basically dead in the water as far as releasing
> any software goes. In the case of a project like Cactus the main
> reason for going back to the incubator would be to re-create a viable
> community.
>

From what I understood from current people that have cactus on their radar and have sufficient
"power" to vote, Cactus will be able to get a release out the door.
An another note : After incubation it could still be that you cannot get a release out the door if
you end up at Jakarta, depending on the fact if you actually make it on the Jakarta PMC.
This is also one of the reasons an Incubator project should have 3 mentors, so they can actually
release, without depending on the time of people not directly involved.

Mvgr,
Martin

Re: An Official Request For Moving Cactus In The Incubator

------=_Part_2015_22631274.1173448238347
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 3/9/07, Martin van den Bemt wrote:
>
> >>
> >> I know that you are busy, but I have another idea that came to me
> reading
> >> the Matt Benson's post. In fact the guys are
> >> dealing with a project that seems to be inspired the jakarta commons
> >> Convert
> >> project and so it would be possible to
> >> accept the code without passing through the incubator. So why isnt'
> this
> >> situation possible for Cactus (I mean I have refactored existing code
> and
> >> added the maven xml files - it is not a new project).
> >>
> >> I also agree that passing through the incubator is the best solution
> >> in the
> >> great majority of cases, but in my opinion there are still some cases
> >> (like
> >> Cactus for instance) that are threatened of stalling even more.
> >
> > Martin or others may answer this better - but AIUI one of the two
> > primary goals of the incubator is building community around code
> > bases. This is not just a "nice thing" at Apache - its an absolute
> > necessity. As an example under Apache rules without 3 votes from the
> > PMC (project management committee) responsible for a project you can't
> > release anything. Once a project falls below that critical level of
> > involved people its basically dead in the water as far as releasing
> > any software goes. In the case of a project like Cactus the main
> > reason for going back to the incubator would be to re-create a viable
> > community.
> >
>
> From what I understood from current people that have cactus on their radar
> and have sufficient
> "power" to vote, Cactus will be able to get a release out the door.
> An another note : After incubation it could still be that you cannot get a
> release out the door if
> you end up at Jakarta, depending on the fact if you actually make it on
> the Jakarta PMC.
> This is also one of the reasons an Incubator project should have 3
> mentors, so they can actually
> release, without depending on the time of people not directly involved.
>
> Mvgr,
> Martin
>
> ------------------------------------------------------------ ---------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
All right,

I get it now. Thank you Martin. Yes, It sounds now more reasonable to move
in the incubator.
On more thing: when we move to incubator, who is going to be the incubation
champion and the projecty
mentors?

Thank you Niall for the link. I read the licenses that are listed
there. Sorry my negligence about this stuff. :-)


Waiting for the further annotation on the status of setting the project in
the incubator.


P.S. If there is anything I can help, please feel free to let me know.

--
Regards, Petar!
Karlovo, Bulgaria.

Public PGP Key at:
http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53 B761500F9

Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9

------=_Part_2015_22631274.1173448238347--

Re: An Official Request For Moving Cactus In The Incubator

>>
> All right,
>
> I get it now. Thank you Martin. Yes, It sounds now more reasonable to move
> in the incubator.

Sorry you didn't get it :) (probably me though, mailing too much today). I was saying that I think
Cactus can gather enough votes in the current situation for eg a release (so without a need to go
through the incubator), so the Incubator path isn't needed (at least the way I look at it).
Exception of course is the legal part :), besides that we are taling about an existing Jakarta
codebase here.
If people think the cactus should go back to the incubator, because of a lack of vibrant community
and not being able to release, because of the 3 +1's, we probably shouldn't stop there , and start
shipping other Jakarta (sub and subsub) projects to the incubator.

In this case Felipe was keeping tabs on what you were doing (and if I understood correctly Felipe
currently hasn't much time left to work on Cactus, but is still interested) and Kenney Westerhof
also worked on a cactus plugin for maven2, so he could also be a candidate to become active on cactus..

So the path will probable be (got no objections on this when sending this to private)

- Get your paperwork done (Code grant, icla, ccla)
- Have a vote on cactus-dev / general to accept your codebase into Cactus
- Do the incubator paperwork, start a vote there (based on lazy consensus, so if no one objects, the
code is accepted)
- Start a vote (on cactus-dev / general) to add you as a Jakarta committer.

No difference in this scenario with Mantissa/Luc path (to give an example)

Mvgr,
Martin