Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Robert Burrell Donkin]

On Thu, Nov 17, 2011 at 1:40 AM, Sam Ruby  wrote:
> On Wed, Nov 16, 2011 at 8:17 PM, Mohammad Nour El-Din
>  wrote:
>> Hi...
>>
>>   The idea sounds good in general more specifically that should be clear
>> and documented on the incubator site for future incubating projects. But,
>> IMHO, we should categorize projects mentioned in that list from very old to
>> recent ones and each group of mentors get in touch with their mentored
>> projects and get with some feedback about such plan, so we can be more fair
>> and give people a chance either to do some progress, more specifically for
>> recent incubated projects and even for the older projects to revive if that
>> is possible.
>>
>> Thoughts ?
>
> Nobody is proposing immediate expulsion of any PPMC based solely on a metric.
>
> On the other hand, it should not be a surprise to mentors that they
> are responsible for[1] "assessment of the Podling status with respect
> to continuation/exit strategy".  Reports for PPMCs that are older than
> a year should be expected to contain this information.  Repeated
> failure to include such information and/or demonstrate forward
> progress towards meeting these objectives should cause the Incubator
> (not the Board!) to take action.

I think this is more about pushing ourselves, and less about pushing podlings

The Incubator now has a process which works okay for many podlings.
The challenge now is to focus more effort on those cases where the
process isn't working. Metrics are useful in discovering and
highlighting sub-populations.

Robert

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Change in Due Dates for Board reports

[Mohammad Nour El-Din]

Hi Sam...

On Thu, Nov 17, 2011 at 4:18 AM, Sam Ruby  wrote:

> On Wed, Nov 16, 2011 at 8:56 PM, Mohammad Nour El-Din
>  wrote:
> > On Thu, Nov 17, 2011 at 3:44 AM, Sam Ruby 
> wrote:
> >
> >> On Wed, Nov 16, 2011 at 8:22 PM, Mohammad Nour El-Din
> >>  wrote:
> >> > Hi...
> >> >
> >> > On Thu, Nov 17, 2011 at 3:07 AM, Sam Ruby 
> >> wrote:
> >> >
> >> >> On Wed, Nov 16, 2011 at 3:47 PM, Noel J. Bergman 
> >> wrote:
> >> >> > PLEASE NOTE!
> >> >> >
> >> >> > From the ASF Board:
> >> >> >
> >> >> >  For now on, all reports to the board for review/inclusion at the
> >> >> >  board meetings will now be due 1 WEEK before the meeting. Reports
> >> >> >  submitted late will be declined and you'll need to resubmit the
> >> >> >  next month.
> >> >> >
> >> >> > This means that Incubator reports really need to be finished by the
> >> end
> >> >> of
> >> >> > the FIRST week of the month.
> >> >>
> >> >> Why not make it easy?  Make incubator reports due by the first of the
> >> >> month.  Doing so doesn't increase workload, doesn't meaningfully
> >> >> increase latency/relevance, and gives the incubator more of a chance
> >> >> to recover (and actually obtain a report in time) when a deadline is
> >> >> missed.
> >> >
> >> > IMHO one week before the board meeting as a final date is fine and at
> the
> >> > same time will give the chance for review and resolving any issues if
> >> they
> >> > exist.
> >>
> >> Can you support this belief with evidence?  It is not uncommon for
> >> podlings to miss being included in board report, and this month the
> >> incubator report itself wasn't reviewed due to it being late.
> >>
> >> I can tell you (as a Director) that if those problems are fixed,
> >> nobody on the board would care if the deadline was mere hours before
> >> forwarding onto the board, but I do want to point out that there is a
> >> real problem that needs some solution, even if it isn't the one I
> >> proposed.
> >>
> >
> > Well from my own experience that this time frame is  good, but for some
> > projects mentors are not that active and hence they are not pushing
> things
> > forward till it is too late, and hence either way you will get delayed
> > reports, only this time you can get more delayed reports.
> >
> > I totally understand the point you are trying to make, but what I am
> trying
> > to say that time limits are not the problem, from what I saw it is either
> > the problem of mentors, not being active, or podling developers are not
> > active or even both, these are the real reasons and having delayed
> reports
> > are just one symptom.
>
> I'll agree, but what I would like to see is that incubator taking a
> greater role in identifying inactive mentors and inactive podlings and
> taking corrective action.  Note: that includes me both in (a) needing
> to take a greater role and (b) as an inactive mentor for at least one
> PPMC.
>
> To be fair: this month's incubator report demonstrates an intent to do
> exactly that.  Please don't interpret what I am saying as "bad
> incubator: change", please interpret it as "good incubator: more!".
>

No worries I totally understand you Sam :)


>
> - Sam Ruby
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Thanks
- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein

Re: incubator is a single group

[David Crossley]

sebb wrote:
> David Crossley wrote:
> > Dennis E. Hamilton wrote:
> >> It is the case that Initial Committers are eligible to serve on the PPMC, 
> >> though not all choose to do so.
> >>
> >> Also, it is apparently a recommendation that invited committers be invited 
> >> to the PPMC, but it doesn't seem to be a requirement.  Again, not all that 
> >> are so invited choose to serve on the PPMC.
> >
> > Yes Seb, i intended that to be separate list,
> > as it is when they are a TLP.
> >
> > I know we do encourage new committers to simultaneously
> > be on PPMC. As is for TLPs, there are cases.
> >
> > Trying to align with current TLP processes,
> > if possible while keeping it simple.
> 
> In that case, I agree that keeping PPMC members in a separate file
> that corresponds with committee-info.txt is a good idea, so long as
> that file has a standard name and location so it can easily be found.
> 
> However, I don't think the committer list (currently in
> asf-auth-template) belongs in podlings.xml.
> 
> I think that might be better as another file, or perhaps as a marker -
> or another section - in the PPMC file.

Okay. Actually i wondered that to start with, but suggested
the podlings.xml instead.

So podling-committee-info.txt with markers.
Good. Similar to TLP.

This could also align with the TLP way of managing the
report schedule in committee-info.txt

Rather than list the mentors/committers in each
podling status page, then could just link directly, e.g.
 http://incubator.apache.org/projects/#giraph (fixme)
 http://people.apache.org/committers-by-project.html#giraph
because those are correlated and generated from
the podlings.xml and podling-committee-info.txt etcetera.

Sorry for the rushed comments: spread too thin.

-David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Graduate ACE from the Apache Incubator

[Marcel Offermans]

In my opinion, ACE is ready to begin the process of graduating from the Apache 
Incubator to a Top Level Project.

Since joining the incubator in in May 2009 we've added 4 new committers (12 in 
total now) from diverse organizations and did a release in May this year to 
demonstrate we follow the Apache guidelines. We've shown an ability to 
self-govern using accepted Apache practices and ACE continues to attract new 
contributors and users.

The first step is to vote as a community, demonstrating that ACE is ready and 
willing to graduate. Once this vote is succesful we create a board resolution 
proposal or Charter and start a vote on the general incubator list. The full 
process is described at 
http://incubator.apache.org/guides/graduation.html#toplevel

The vote is open for at least 72 hours.

Greetings, Marcel

Re: [VOTE] Graduate ACE from the Apache Incubator

[Jean-Baptiste Onofré]

+1

Regards
JB

On 11/17/2011 11:42 AM, Marcel Offermans wrote:

In my opinion, ACE is ready to begin the process of graduating from the Apache 
Incubator to a Top Level Project.

Since joining the incubator in in May 2009 we've added 4 new committers (12 in 
total now) from diverse organizations and did a release in May this year to 
demonstrate we follow the Apache guidelines. We've shown an ability to 
self-govern using accepted Apache practices and ACE continues to attract new 
contributors and users.

The first step is to vote as a community, demonstrating that ACE is ready and 
willing to graduate. Once this vote is succesful we create a board resolution 
proposal or Charter and start a vote on the general incubator list. The full 
process is described at 
http://incubator.apache.org/guides/graduation.html#toplevel

The vote is open for at least 72 hours.

Greetings, Marcel




--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Alexander Broekhuis]

Great news, succes with this!

+1

2011/11/17 Jean-Baptiste Onofré 

> +1
>
> Regards
> JB
>
>
> On 11/17/2011 11:42 AM, Marcel Offermans wrote:
>
>> In my opinion, ACE is ready to begin the process of graduating from the
>> Apache Incubator to a Top Level Project.
>>
>> Since joining the incubator in in May 2009 we've added 4 new committers
>> (12 in total now) from diverse organizations and did a release in May this
>> year to demonstrate we follow the Apache guidelines. We've shown an ability
>> to self-govern using accepted Apache practices and ACE continues to attract
>> new contributors and users.
>>
>> The first step is to vote as a community, demonstrating that ACE is ready
>> and willing to graduate. Once this vote is succesful we create a board
>> resolution proposal or Charter and start a vote on the general incubator
>> list. The full process is described at http://incubator.apache.org/**
>> guides/graduation.html#**toplevel
>>
>> The vote is open for at least 72 hours.
>>
>> Greetings, Marcel
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> --**--**-
> To unsubscribe, e-mail: 
> general-unsubscribe@incubator.**apache.org
> For additional commands, e-mail: 
> general-help@incubator.apache.**org
>
>


-- 
Met vriendelijke groet,

Alexander Broekhuis

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Nick Burch]

On Wed, 16 Nov 2011, Sam Ruby wrote:

Meanwhile, I will personally focus on JSPWiki.  If others wish to join
me, here is a a current list of projects that have been incubating
more than a year:


I've been meaning to try to help out with JSPWiki for a while, but I've 
not yet had the time. If there's going to be more than one of us though, 
then hopefully the work involved will be something I can commit to


Currently the JSPWiki mentors are listed as:
 * snoopdave - Dave Johnson
 * clr - Craig Russell
 * henning - Henning Schmiedehausen
 * rubys - Sam Ruby

Are any of the others currently active and able to help?

(My hunch from having spoken to a few jspwiki community members is that we 
need to have another go at helping them understand the apache way, then 
give a deadline, but I've not looked in detail to be sure)


Nick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Suitable Names Search [WAS Re: Trademark Kill Searches...]

[Robert Burrell Donkin]

On Mon, Nov 14, 2011 at 1:56 PM, Robert Burrell Donkin
 wrote:
> On Thu, Nov 10, 2011 at 5:47 PM, Robert Burrell Donkin
>  wrote:
>> On Wed, Nov 9, 2011 at 1:22 PM, Robert Burrell Donkin
>>  wrote:
>>
>> 
>>
>>> Unless anyone jumps in soon, I'll set up a "Suitable Names Search"
>>> JIRA project
>>
>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH
>>
>> Please jump in to fill out details and permissions. Improvements,
>> suggestions, objections, welcomed.
>
> Should we send notifications to this list?



Unless someone jumps in with objections soon, I'll set up
notifications to this list.

Robert

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[sebb]

On 17 November 2011 10:42, Marcel Offermans  wrote:
> In my opinion, ACE is ready to begin the process of graduating from the 
> Apache Incubator to a Top Level Project.
>
> Since joining the incubator in in May 2009 we've added 4 new committers (12 
> in total now) from diverse organizations and did a release in May this year 
> to demonstrate we follow the Apache guidelines. We've shown an ability to 
> self-govern using accepted Apache practices and ACE continues to attract new 
> contributors and users.
>
> The first step is to vote as a community, demonstrating that ACE is ready and 
> willing to graduate. Once this vote is succesful we create a board resolution 
> proposal or Charter and start a vote on the general incubator list. The full 
> process is described at 
> http://incubator.apache.org/guides/graduation.html#toplevel
>
> The vote is open for at least 72 hours.

The last (and only) release was 0.8, as far as I can tell.

There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
and there does not appear to be a full source archive of the project
anywhere.
The download page does not have a link to any source archives as far
as I can tell.
It does link to KEYS in SVN, but almost all other ASF projects have a
copy of KEYS in the appropriate /dist directory.

Normally releases are divided into binaries/ and source/ directories,
with a KEYS file in the top-level, i.e.

/dist/incubator/ace
- KEYS
- binaries/ace zip
- sources/acezip

Most of the files in the /dist/incubator/ace directory appear to be
Maven artifacts; normally these are not stored in /dist but only in
the Maven repo.
Indeed most of the files are also in Maven Central. The only non-Maven
files appear to be

org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip

neither of which contains the source.

I would expect the above zips to be in

/dist/incubator/ace/binaries

with corresponding source files in

/dist/incubator/ace/source

The SVN layout [1] is also a bit unusual.
There is no tags/ directory for release tags, although there is a
releases/ directory containing individual entries for each release for
each component.
This is likely to become unmanageable very quickly, if every release
adds another 63 directory entries under releases/

[1] https://svn.apache.org/repos/asf/incubator/ace/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Karl Pauls]

I'm not sure what this has to do with the graduation vote. The release
as such has been accepted by the incubator pmc and there only need to
be one release. The source for each artifact is there, it is just per
artifact in the -source.jar.

There might be different set-up then a lot of other projects have it
but we release our stuff on a per artifact basis how it is done by for
example Apache Felix as well and never has been an issue (and didn't
become unmanageably either -  also ymmv).

I agree about the KEYS file. We should have uploaded it to the dist
dir as well but at least we have it at some place so it should be easy
to fix.

regards,

Karl

On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
> On 17 November 2011 10:42, Marcel Offermans  
> wrote:
>> In my opinion, ACE is ready to begin the process of graduating from the 
>> Apache Incubator to a Top Level Project.
>>
>> Since joining the incubator in in May 2009 we've added 4 new committers (12 
>> in total now) from diverse organizations and did a release in May this year 
>> to demonstrate we follow the Apache guidelines. We've shown an ability to 
>> self-govern using accepted Apache practices and ACE continues to attract new 
>> contributors and users.
>>
>> The first step is to vote as a community, demonstrating that ACE is ready 
>> and willing to graduate. Once this vote is succesful we create a board 
>> resolution proposal or Charter and start a vote on the general incubator 
>> list. The full process is described at 
>> http://incubator.apache.org/guides/graduation.html#toplevel
>>
>> The vote is open for at least 72 hours.
>
> The last (and only) release was 0.8, as far as I can tell.
>
> There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
> and there does not appear to be a full source archive of the project
> anywhere.
> The download page does not have a link to any source archives as far
> as I can tell.
> It does link to KEYS in SVN, but almost all other ASF projects have a
> copy of KEYS in the appropriate /dist directory.
>
> Normally releases are divided into binaries/ and source/ directories,
> with a KEYS file in the top-level, i.e.
>
> /dist/incubator/ace
> - KEYS
> - binaries/ace zip
> - sources/acezip
>
> Most of the files in the /dist/incubator/ace directory appear to be
> Maven artifacts; normally these are not stored in /dist but only in
> the Maven repo.
> Indeed most of the files are also in Maven Central. The only non-Maven
> files appear to be
>
> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
>
> neither of which contains the source.
>
> I would expect the above zips to be in
>
> /dist/incubator/ace/binaries
>
> with corresponding source files in
>
> /dist/incubator/ace/source
>
> The SVN layout [1] is also a bit unusual.
> There is no tags/ directory for release tags, although there is a
> releases/ directory containing individual entries for each release for
> each component.
> This is likely to become unmanageable very quickly, if every release
> adds another 63 directory entries under releases/
>
> [1] https://svn.apache.org/repos/asf/incubator/ace/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>



-- 
Karl Pauls
karlpa...@gmail.com
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Guillaume Nodet]

As much as I don't like this layout, this is not the first projet to use
it, and I don't really see how / why the IPMC should decide the svn layout
for the project.   You won't be the one to manage it daily afaik, so that's
not up to you to decide imho.
Sling and Felix already use such a layout and they are both TLP, so I
really don't see that as a problem.

On Thu, Nov 17, 2011 at 13:07, sebb  wrote:

> On 17 November 2011 10:42, Marcel Offermans 
> wrote:
> > In my opinion, ACE is ready to begin the process of graduating from the
> Apache Incubator to a Top Level Project.
> >
> > Since joining the incubator in in May 2009 we've added 4 new committers
> (12 in total now) from diverse organizations and did a release in May this
> year to demonstrate we follow the Apache guidelines. We've shown an ability
> to self-govern using accepted Apache practices and ACE continues to attract
> new contributors and users.
> >
> > The first step is to vote as a community, demonstrating that ACE is
> ready and willing to graduate. Once this vote is succesful we create a
> board resolution proposal or Charter and start a vote on the general
> incubator list. The full process is described at
> http://incubator.apache.org/guides/graduation.html#toplevel
> >
> > The vote is open for at least 72 hours.
>
> The last (and only) release was 0.8, as far as I can tell.
>
> There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
> and there does not appear to be a full source archive of the project
> anywhere.
> The download page does not have a link to any source archives as far
> as I can tell.
> It does link to KEYS in SVN, but almost all other ASF projects have a
> copy of KEYS in the appropriate /dist directory.
>
> Normally releases are divided into binaries/ and source/ directories,
> with a KEYS file in the top-level, i.e.
>
> /dist/incubator/ace
> - KEYS
> - binaries/ace zip
> - sources/acezip
>
> Most of the files in the /dist/incubator/ace directory appear to be
> Maven artifacts; normally these are not stored in /dist but only in
> the Maven repo.
> Indeed most of the files are also in Maven Central. The only non-Maven
> files appear to be
>
> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
>
> neither of which contains the source.
>
> I would expect the above zips to be in
>
> /dist/incubator/ace/binaries
>
> with corresponding source files in
>
> /dist/incubator/ace/source
>
> The SVN layout [1] is also a bit unusual.
> There is no tags/ directory for release tags, although there is a
> releases/ directory containing individual entries for each release for
> each component.
> This is likely to become unmanageable very quickly, if every release
> adds another 63 directory entries under releases/
>
> [1] https://svn.apache.org/repos/asf/incubator/ace/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 

Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com

Re: [VOTE] Graduate ACE from the Apache Incubator

[sebb]

On 17 November 2011 12:29, Karl Pauls  wrote:
> I'm not sure what this has to do with the graduation vote. The release
> as such has been accepted by the incubator pmc and there only need to
> be one release. The source for each artifact is there, it is just per
> artifact in the -source.jar.

AFAICT the full source (as in SVN trunk) is not actually present in
the distribution directory.

For example, where are the top-level files in SVN (BUILDING, README) ?
And the etc/ directory?

If I wanted to build any or all of the components, there does not
appear to be a way to do this from the files in the distribution.

> There might be different set-up then a lot of other projects have it
> but we release our stuff on a per artifact basis how it is done by for
> example Apache Felix as well and never has been an issue (and didn't
> become unmanageably either -  also ymmv).

The ASF primarily releases source; releases must include full source.

> I agree about the KEYS file. We should have uploaded it to the dist
> dir as well but at least we have it at some place so it should be easy
> to fix.
>
> regards,
>
> Karl
>
> On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
>> On 17 November 2011 10:42, Marcel Offermans  
>> wrote:
>>> In my opinion, ACE is ready to begin the process of graduating from the 
>>> Apache Incubator to a Top Level Project.
>>>
>>> Since joining the incubator in in May 2009 we've added 4 new committers (12 
>>> in total now) from diverse organizations and did a release in May this year 
>>> to demonstrate we follow the Apache guidelines. We've shown an ability to 
>>> self-govern using accepted Apache practices and ACE continues to attract 
>>> new contributors and users.
>>>
>>> The first step is to vote as a community, demonstrating that ACE is ready 
>>> and willing to graduate. Once this vote is succesful we create a board 
>>> resolution proposal or Charter and start a vote on the general incubator 
>>> list. The full process is described at 
>>> http://incubator.apache.org/guides/graduation.html#toplevel
>>>
>>> The vote is open for at least 72 hours.
>>
>> The last (and only) release was 0.8, as far as I can tell.
>>
>> There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
>> and there does not appear to be a full source archive of the project
>> anywhere.
>> The download page does not have a link to any source archives as far
>> as I can tell.
>> It does link to KEYS in SVN, but almost all other ASF projects have a
>> copy of KEYS in the appropriate /dist directory.
>>
>> Normally releases are divided into binaries/ and source/ directories,
>> with a KEYS file in the top-level, i.e.
>>
>> /dist/incubator/ace
>> - KEYS
>> - binaries/ace zip
>> - sources/acezip
>>
>> Most of the files in the /dist/incubator/ace directory appear to be
>> Maven artifacts; normally these are not stored in /dist but only in
>> the Maven repo.
>> Indeed most of the files are also in Maven Central. The only non-Maven
>> files appear to be
>>
>> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
>> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
>>
>> neither of which contains the source.
>>
>> I would expect the above zips to be in
>>
>> /dist/incubator/ace/binaries
>>
>> with corresponding source files in
>>
>> /dist/incubator/ace/source
>>
>> The SVN layout [1] is also a bit unusual.
>> There is no tags/ directory for release tags, although there is a
>> releases/ directory containing individual entries for each release for
>> each component.
>> This is likely to become unmanageable very quickly, if every release
>> adds another 63 directory entries under releases/
>>
>> [1] https://svn.apache.org/repos/asf/incubator/ace/
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
> http://twitter.com/karlpauls
> http://www.linkedin.com/in/karlpauls
> https://profiles.google.com/karlpauls
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[sebb]

On 17 November 2011 12:51, Guillaume Nodet  wrote:
> As much as I don't like this layout, this is not the first projet to use
> it, and I don't really see how / why the IPMC should decide the svn layout
> for the project.   You won't be the one to manage it daily afaik, so that's
> not up to you to decide imho.

The SVN layout is less of a concern, although the lack of a single tag
for a release is odd.
Not all of the files in SVN trunk appear in releases/

> Sling and Felix already use such a layout and they are both TLP, so I
> really don't see that as a problem.

> On Thu, Nov 17, 2011 at 13:07, sebb  wrote:
>
>> On 17 November 2011 10:42, Marcel Offermans 
>> wrote:
>> > In my opinion, ACE is ready to begin the process of graduating from the
>> Apache Incubator to a Top Level Project.
>> >
>> > Since joining the incubator in in May 2009 we've added 4 new committers
>> (12 in total now) from diverse organizations and did a release in May this
>> year to demonstrate we follow the Apache guidelines. We've shown an ability
>> to self-govern using accepted Apache practices and ACE continues to attract
>> new contributors and users.
>> >
>> > The first step is to vote as a community, demonstrating that ACE is
>> ready and willing to graduate. Once this vote is succesful we create a
>> board resolution proposal or Charter and start a vote on the general
>> incubator list. The full process is described at
>> http://incubator.apache.org/guides/graduation.html#toplevel
>> >
>> > The vote is open for at least 72 hours.
>>
>> The last (and only) release was 0.8, as far as I can tell.
>>
>> There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
>> and there does not appear to be a full source archive of the project
>> anywhere.
>> The download page does not have a link to any source archives as far
>> as I can tell.
>> It does link to KEYS in SVN, but almost all other ASF projects have a
>> copy of KEYS in the appropriate /dist directory.
>>
>> Normally releases are divided into binaries/ and source/ directories,
>> with a KEYS file in the top-level, i.e.
>>
>> /dist/incubator/ace
>> - KEYS
>> - binaries/ace zip
>> - sources/acezip
>>
>> Most of the files in the /dist/incubator/ace directory appear to be
>> Maven artifacts; normally these are not stored in /dist but only in
>> the Maven repo.
>> Indeed most of the files are also in Maven Central. The only non-Maven
>> files appear to be
>>
>> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
>> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
>>
>> neither of which contains the source.
>>
>> I would expect the above zips to be in
>>
>> /dist/incubator/ace/binaries
>>
>> with corresponding source files in
>>
>> /dist/incubator/ace/source
>>
>> The SVN layout [1] is also a bit unusual.
>> There is no tags/ directory for release tags, although there is a
>> releases/ directory containing individual entries for each release for
>> each component.
>> This is likely to become unmanageable very quickly, if every release
>> adds another 63 directory entries under releases/
>>
>> [1] https://svn.apache.org/repos/asf/incubator/ace/
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
>
> --
> 
> Guillaume Nodet
> 
> Blog: http://gnodet.blogspot.com/
> 
> Open Source SOA
> http://fusesource.com
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Karl Pauls]

Again, we had this discussion before namely, when the actual release
vote happened. I'm still confused why we have to go through this
again. You should be able to build all of the components by using the
-source.jar's that are provided. They contain what is necessary i.e.,
the full source.

regards,

Karl

On Thu, Nov 17, 2011 at 2:30 PM, sebb  wrote:
> On 17 November 2011 12:29, Karl Pauls  wrote:
>> I'm not sure what this has to do with the graduation vote. The release
>> as such has been accepted by the incubator pmc and there only need to
>> be one release. The source for each artifact is there, it is just per
>> artifact in the -source.jar.
>
> AFAICT the full source (as in SVN trunk) is not actually present in
> the distribution directory.
>
> For example, where are the top-level files in SVN (BUILDING, README) ?
> And the etc/ directory?
>
> If I wanted to build any or all of the components, there does not
> appear to be a way to do this from the files in the distribution.
>
>> There might be different set-up then a lot of other projects have it
>> but we release our stuff on a per artifact basis how it is done by for
>> example Apache Felix as well and never has been an issue (and didn't
>> become unmanageably either -  also ymmv).
>
> The ASF primarily releases source; releases must include full source.
>
>> I agree about the KEYS file. We should have uploaded it to the dist
>> dir as well but at least we have it at some place so it should be easy
>> to fix.
>>
>> regards,
>>
>> Karl
>>
>> On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
>>> On 17 November 2011 10:42, Marcel Offermans  
>>> wrote:
 In my opinion, ACE is ready to begin the process of graduating from the 
 Apache Incubator to a Top Level Project.

 Since joining the incubator in in May 2009 we've added 4 new committers 
 (12 in total now) from diverse organizations and did a release in May this 
 year to demonstrate we follow the Apache guidelines. We've shown an 
 ability to self-govern using accepted Apache practices and ACE continues 
 to attract new contributors and users.

 The first step is to vote as a community, demonstrating that ACE is ready 
 and willing to graduate. Once this vote is succesful we create a board 
 resolution proposal or Charter and start a vote on the general incubator 
 list. The full process is described at 
 http://incubator.apache.org/guides/graduation.html#toplevel

 The vote is open for at least 72 hours.
>>>
>>> The last (and only) release was 0.8, as far as I can tell.
>>>
>>> There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
>>> and there does not appear to be a full source archive of the project
>>> anywhere.
>>> The download page does not have a link to any source archives as far
>>> as I can tell.
>>> It does link to KEYS in SVN, but almost all other ASF projects have a
>>> copy of KEYS in the appropriate /dist directory.
>>>
>>> Normally releases are divided into binaries/ and source/ directories,
>>> with a KEYS file in the top-level, i.e.
>>>
>>> /dist/incubator/ace
>>> - KEYS
>>> - binaries/ace zip
>>> - sources/acezip
>>>
>>> Most of the files in the /dist/incubator/ace directory appear to be
>>> Maven artifacts; normally these are not stored in /dist but only in
>>> the Maven repo.
>>> Indeed most of the files are also in Maven Central. The only non-Maven
>>> files appear to be
>>>
>>> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
>>> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
>>>
>>> neither of which contains the source.
>>>
>>> I would expect the above zips to be in
>>>
>>> /dist/incubator/ace/binaries
>>>
>>> with corresponding source files in
>>>
>>> /dist/incubator/ace/source
>>>
>>> The SVN layout [1] is also a bit unusual.
>>> There is no tags/ directory for release tags, although there is a
>>> releases/ directory containing individual entries for each release for
>>> each component.
>>> This is likely to become unmanageable very quickly, if every release
>>> adds another 63 directory entries under releases/
>>>
>>> [1] https://svn.apache.org/repos/asf/incubator/ace/
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Karl Pauls
>> karlpa...@gmail.com
>> http://twitter.com/karlpauls
>> http://www.linkedin.com/in/karlpauls
>> https://profiles.google.com/karlpauls
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@i

Re: [VOTE] Graduate ACE from the Apache Incubator

[Benson Margulies]

+1 (binding)

On Thu, Nov 17, 2011 at 8:35 AM, Karl Pauls  wrote:
> Again, we had this discussion before namely, when the actual release
> vote happened. I'm still confused why we have to go through this
> again. You should be able to build all of the components by using the
> -source.jar's that are provided. They contain what is necessary i.e.,
> the full source.
>
> regards,
>
> Karl
>
> On Thu, Nov 17, 2011 at 2:30 PM, sebb  wrote:
>> On 17 November 2011 12:29, Karl Pauls  wrote:
>>> I'm not sure what this has to do with the graduation vote. The release
>>> as such has been accepted by the incubator pmc and there only need to
>>> be one release. The source for each artifact is there, it is just per
>>> artifact in the -source.jar.
>>
>> AFAICT the full source (as in SVN trunk) is not actually present in
>> the distribution directory.
>>
>> For example, where are the top-level files in SVN (BUILDING, README) ?
>> And the etc/ directory?
>>
>> If I wanted to build any or all of the components, there does not
>> appear to be a way to do this from the files in the distribution.
>>
>>> There might be different set-up then a lot of other projects have it
>>> but we release our stuff on a per artifact basis how it is done by for
>>> example Apache Felix as well and never has been an issue (and didn't
>>> become unmanageably either -  also ymmv).
>>
>> The ASF primarily releases source; releases must include full source.
>>
>>> I agree about the KEYS file. We should have uploaded it to the dist
>>> dir as well but at least we have it at some place so it should be easy
>>> to fix.
>>>
>>> regards,
>>>
>>> Karl
>>>
>>> On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
 On 17 November 2011 10:42, Marcel Offermans  
 wrote:
> In my opinion, ACE is ready to begin the process of graduating from the 
> Apache Incubator to a Top Level Project.
>
> Since joining the incubator in in May 2009 we've added 4 new committers 
> (12 in total now) from diverse organizations and did a release in May 
> this year to demonstrate we follow the Apache guidelines. We've shown an 
> ability to self-govern using accepted Apache practices and ACE continues 
> to attract new contributors and users.
>
> The first step is to vote as a community, demonstrating that ACE is ready 
> and willing to graduate. Once this vote is succesful we create a board 
> resolution proposal or Charter and start a vote on the general incubator 
> list. The full process is described at 
> http://incubator.apache.org/guides/graduation.html#toplevel
>
> The vote is open for at least 72 hours.

 The last (and only) release was 0.8, as far as I can tell.

 There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
 and there does not appear to be a full source archive of the project
 anywhere.
 The download page does not have a link to any source archives as far
 as I can tell.
 It does link to KEYS in SVN, but almost all other ASF projects have a
 copy of KEYS in the appropriate /dist directory.

 Normally releases are divided into binaries/ and source/ directories,
 with a KEYS file in the top-level, i.e.

 /dist/incubator/ace
 - KEYS
 - binaries/ace zip
 - sources/acezip

 Most of the files in the /dist/incubator/ace directory appear to be
 Maven artifacts; normally these are not stored in /dist but only in
 the Maven repo.
 Indeed most of the files are also in Maven Central. The only non-Maven
 files appear to be

 org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
 org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip

 neither of which contains the source.

 I would expect the above zips to be in

 /dist/incubator/ace/binaries

 with corresponding source files in

 /dist/incubator/ace/source

 The SVN layout [1] is also a bit unusual.
 There is no tags/ directory for release tags, although there is a
 releases/ directory containing individual entries for each release for
 each component.
 This is likely to become unmanageable very quickly, if every release
 adds another 63 directory entries under releases/

 [1] https://svn.apache.org/repos/asf/incubator/ace/

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org


>>>
>>>
>>>
>>> --
>>> Karl Pauls
>>> karlpa...@gmail.com
>>> http://twitter.com/karlpauls
>>> http://www.linkedin.com/in/karlpauls
>>> https://profiles.google.com/karlpauls
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.o

Re: [VOTE] Graduate ACE from the Apache Incubator

[Karl Pauls]

On Thu, Nov 17, 2011 at 2:34 PM, sebb  wrote:
> On 17 November 2011 12:51, Guillaume Nodet  wrote:
>> As much as I don't like this layout, this is not the first projet to use
>> it, and I don't really see how / why the IPMC should decide the svn layout
>> for the project.   You won't be the one to manage it daily afaik, so that's
>> not up to you to decide imho.
>
> The SVN layout is less of a concern, although the lack of a single tag
> for a release is odd.
> Not all of the files in SVN trunk appear in releases/


Why would they have to? We don't release the complete svn trunk but
only the part of it that we want to release. Again, we have a modular
layout and we only release the modules we want to at a given time
_without_ releasing the complete trunk every time. Yes, that is more
work but we from the osgi/modular world prefer it over the problems we
get with big-bang releases.

That said, each binary artifact contains the necessary legal files and
-source.jar's are provided that contain the full source and necessary
legal files. I admit that it might take some getting used to if you
don't know maven well or are not used to modular osgi bundle releases
but please, look at the artifacts that have been released - not at the
svn trunk. We don't release the trunk, we release releases. They must
have legal files and full source and they do.

regards,

Karl

>> Sling and Felix already use such a layout and they are both TLP, so I
>> really don't see that as a problem.
>
>> On Thu, Nov 17, 2011 at 13:07, sebb  wrote:
>>
>>> On 17 November 2011 10:42, Marcel Offermans 
>>> wrote:
>>> > In my opinion, ACE is ready to begin the process of graduating from the
>>> Apache Incubator to a Top Level Project.
>>> >
>>> > Since joining the incubator in in May 2009 we've added 4 new committers
>>> (12 in total now) from diverse organizations and did a release in May this
>>> year to demonstrate we follow the Apache guidelines. We've shown an ability
>>> to self-govern using accepted Apache practices and ACE continues to attract
>>> new contributors and users.
>>> >
>>> > The first step is to vote as a community, demonstrating that ACE is
>>> ready and willing to graduate. Once this vote is succesful we create a
>>> board resolution proposal or Charter and start a vote on the general
>>> incubator list. The full process is described at
>>> http://incubator.apache.org/guides/graduation.html#toplevel
>>> >
>>> > The vote is open for at least 72 hours.
>>>
>>> The last (and only) release was 0.8, as far as I can tell.
>>>
>>> There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
>>> and there does not appear to be a full source archive of the project
>>> anywhere.
>>> The download page does not have a link to any source archives as far
>>> as I can tell.
>>> It does link to KEYS in SVN, but almost all other ASF projects have a
>>> copy of KEYS in the appropriate /dist directory.
>>>
>>> Normally releases are divided into binaries/ and source/ directories,
>>> with a KEYS file in the top-level, i.e.
>>>
>>> /dist/incubator/ace
>>> - KEYS
>>> - binaries/ace zip
>>> - sources/acezip
>>>
>>> Most of the files in the /dist/incubator/ace directory appear to be
>>> Maven artifacts; normally these are not stored in /dist but only in
>>> the Maven repo.
>>> Indeed most of the files are also in Maven Central. The only non-Maven
>>> files appear to be
>>>
>>> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
>>> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
>>>
>>> neither of which contains the source.
>>>
>>> I would expect the above zips to be in
>>>
>>> /dist/incubator/ace/binaries
>>>
>>> with corresponding source files in
>>>
>>> /dist/incubator/ace/source
>>>
>>> The SVN layout [1] is also a bit unusual.
>>> There is no tags/ directory for release tags, although there is a
>>> releases/ directory containing individual entries for each release for
>>> each component.
>>> This is likely to become unmanageable very quickly, if every release
>>> adds another 63 directory entries under releases/
>>>
>>> [1] https://svn.apache.org/repos/asf/incubator/ace/
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>
>>
>> --
>> 
>> Guillaume Nodet
>> 
>> Blog: http://gnodet.blogspot.com/
>> 
>> Open Source SOA
>> http://fusesource.com
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>



-- 
Karl Pauls
karlpa...@gmail.com
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls

---

Re: [VOTE] Graduate ACE from the Apache Incubator

[ant elder]

To try that I just went to the ACE downloads page which has a bunch of
jars and source jars to download, i downloaded the source of the first
one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and
looking inside there is the source to some Java classes but no build
scripts or pom.xml file, so how would I go about building this?

   ...ant

On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls  wrote:
> Again, we had this discussion before namely, when the actual release
> vote happened. I'm still confused why we have to go through this
> again. You should be able to build all of the components by using the
> -source.jar's that are provided. They contain what is necessary i.e.,
> the full source.
>
> regards,
>
> Karl
>
> On Thu, Nov 17, 2011 at 2:30 PM, sebb  wrote:
>> On 17 November 2011 12:29, Karl Pauls  wrote:
>>> I'm not sure what this has to do with the graduation vote. The release
>>> as such has been accepted by the incubator pmc and there only need to
>>> be one release. The source for each artifact is there, it is just per
>>> artifact in the -source.jar.
>>
>> AFAICT the full source (as in SVN trunk) is not actually present in
>> the distribution directory.
>>
>> For example, where are the top-level files in SVN (BUILDING, README) ?
>> And the etc/ directory?
>>
>> If I wanted to build any or all of the components, there does not
>> appear to be a way to do this from the files in the distribution.
>>
>>> There might be different set-up then a lot of other projects have it
>>> but we release our stuff on a per artifact basis how it is done by for
>>> example Apache Felix as well and never has been an issue (and didn't
>>> become unmanageably either -  also ymmv).
>>
>> The ASF primarily releases source; releases must include full source.
>>
>>> I agree about the KEYS file. We should have uploaded it to the dist
>>> dir as well but at least we have it at some place so it should be easy
>>> to fix.
>>>
>>> regards,
>>>
>>> Karl
>>>
>>> On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
 On 17 November 2011 10:42, Marcel Offermans  
 wrote:
> In my opinion, ACE is ready to begin the process of graduating from the 
> Apache Incubator to a Top Level Project.
>
> Since joining the incubator in in May 2009 we've added 4 new committers 
> (12 in total now) from diverse organizations and did a release in May 
> this year to demonstrate we follow the Apache guidelines. We've shown an 
> ability to self-govern using accepted Apache practices and ACE continues 
> to attract new contributors and users.
>
> The first step is to vote as a community, demonstrating that ACE is ready 
> and willing to graduate. Once this vote is succesful we create a board 
> resolution proposal or Charter and start a vote on the general incubator 
> list. The full process is described at 
> http://incubator.apache.org/guides/graduation.html#toplevel
>
> The vote is open for at least 72 hours.

 The last (and only) release was 0.8, as far as I can tell.

 There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
 and there does not appear to be a full source archive of the project
 anywhere.
 The download page does not have a link to any source archives as far
 as I can tell.
 It does link to KEYS in SVN, but almost all other ASF projects have a
 copy of KEYS in the appropriate /dist directory.

 Normally releases are divided into binaries/ and source/ directories,
 with a KEYS file in the top-level, i.e.

 /dist/incubator/ace
 - KEYS
 - binaries/ace zip
 - sources/acezip

 Most of the files in the /dist/incubator/ace directory appear to be
 Maven artifacts; normally these are not stored in /dist but only in
 the Maven repo.
 Indeed most of the files are also in Maven Central. The only non-Maven
 files appear to be

 org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
 org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip

 neither of which contains the source.

 I would expect the above zips to be in

 /dist/incubator/ace/binaries

 with corresponding source files in

 /dist/incubator/ace/source

 The SVN layout [1] is also a bit unusual.
 There is no tags/ directory for release tags, although there is a
 releases/ directory containing individual entries for each release for
 each component.
 This is likely to become unmanageable very quickly, if every release
 adds another 63 directory entries under releases/

 [1] https://svn.apache.org/repos/asf/incubator/ace/

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org


>>>
>>>
>>>
>>> --
>>> Karl Pauls
>>> karlpa.

Re: [VOTE] Graduate ACE from the Apache Incubator

[Karl Pauls]

$ mkdir org.apache.ace.client.automation-0.8.0-incubator
$ cd org.apache.ace.client.automation-0.8.0-incubator/
$ wget 
http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar
$ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar
$ wget 
http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
$ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
$ mvn clean install

regards,

Karl

On Thu, Nov 17, 2011 at 2:54 PM, ant elder  wrote:
> To try that I just went to the ACE downloads page which has a bunch of
> jars and source jars to download, i downloaded the source of the first
> one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and
> looking inside there is the source to some Java classes but no build
> scripts or pom.xml file, so how would I go about building this?
>
>   ...ant
>
> On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls  wrote:
>> Again, we had this discussion before namely, when the actual release
>> vote happened. I'm still confused why we have to go through this
>> again. You should be able to build all of the components by using the
>> -source.jar's that are provided. They contain what is necessary i.e.,
>> the full source.
>>
>> regards,
>>
>> Karl
>>
>> On Thu, Nov 17, 2011 at 2:30 PM, sebb  wrote:
>>> On 17 November 2011 12:29, Karl Pauls  wrote:
 I'm not sure what this has to do with the graduation vote. The release
 as such has been accepted by the incubator pmc and there only need to
 be one release. The source for each artifact is there, it is just per
 artifact in the -source.jar.
>>>
>>> AFAICT the full source (as in SVN trunk) is not actually present in
>>> the distribution directory.
>>>
>>> For example, where are the top-level files in SVN (BUILDING, README) ?
>>> And the etc/ directory?
>>>
>>> If I wanted to build any or all of the components, there does not
>>> appear to be a way to do this from the files in the distribution.
>>>
 There might be different set-up then a lot of other projects have it
 but we release our stuff on a per artifact basis how it is done by for
 example Apache Felix as well and never has been an issue (and didn't
 become unmanageably either -  also ymmv).
>>>
>>> The ASF primarily releases source; releases must include full source.
>>>
 I agree about the KEYS file. We should have uploaded it to the dist
 dir as well but at least we have it at some place so it should be easy
 to fix.

 regards,

 Karl

 On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
> On 17 November 2011 10:42, Marcel Offermans  
> wrote:
>> In my opinion, ACE is ready to begin the process of graduating from the 
>> Apache Incubator to a Top Level Project.
>>
>> Since joining the incubator in in May 2009 we've added 4 new committers 
>> (12 in total now) from diverse organizations and did a release in May 
>> this year to demonstrate we follow the Apache guidelines. We've shown an 
>> ability to self-govern using accepted Apache practices and ACE continues 
>> to attract new contributors and users.
>>
>> The first step is to vote as a community, demonstrating that ACE is 
>> ready and willing to graduate. Once this vote is succesful we create a 
>> board resolution proposal or Charter and start a vote on the general 
>> incubator list. The full process is described at 
>> http://incubator.apache.org/guides/graduation.html#toplevel
>>
>> The vote is open for at least 72 hours.
>
> The last (and only) release was 0.8, as far as I can tell.
>
> There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
> and there does not appear to be a full source archive of the project
> anywhere.
> The download page does not have a link to any source archives as far
> as I can tell.
> It does link to KEYS in SVN, but almost all other ASF projects have a
> copy of KEYS in the appropriate /dist directory.
>
> Normally releases are divided into binaries/ and source/ directories,
> with a KEYS file in the top-level, i.e.
>
> /dist/incubator/ace
> - KEYS
> - binaries/ace zip
> - sources/acezip
>
> Most of the files in the /dist/incubator/ace directory appear to be
> Maven artifacts; normally these are not stored in /dist but only in
> the Maven repo.
> Indeed most of the files are also in Maven Central. The only non-Maven
> files appear to be
>
> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
>
> neither of which contains the source.
>
> I would expect the above zips to be in
>
> /dist/incubator/ace/binaries
>
> with corresponding source files in
>
> /dist/incubator/ace/source
>
> The SVN layout [

Re: Suitable Names Search [WAS Re: Trademark Kill Searches...]

[Shane Curcuru]

+1 to the JIRA project and the notifications coming here.  Thanks for 
driving this one!


- Shane

On 2011-11-17 6:55 AM, Robert Burrell Donkin wrote:

On Mon, Nov 14, 2011 at 1:56 PM, Robert Burrell Donkin
  wrote:

On Thu, Nov 10, 2011 at 5:47 PM, Robert Burrell Donkin
  wrote:

On Wed, Nov 9, 2011 at 1:22 PM, Robert Burrell Donkin
  wrote:




Unless anyone jumps in soon, I'll set up a "Suitable Names Search"
JIRA project


https://issues.apache.org/jira/browse/PODLINGNAMESEARCH

Please jump in to fill out details and permissions. Improvements,
suggestions, objections, welcomed.


Should we send notifications to this list?




Unless someone jumps in with objections soon, I'll set up
notifications to this list.

Robert

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

svn tags for releases? (was: [VOTE] Graduate ACE from the Apache Incubator)

[Bertrand Delacretaz]

On Thu, Nov 17, 2011 at 3:07 PM, Karl Pauls  wrote:
> $ mkdir org.apache.ace.client.automation-0.8.0-incubator
> $ cd org.apache.ace.client.automation-0.8.0-incubator/
> $ wget 
> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar
> $ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar
> $ wget 
> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
> $ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
> $ mvn clean install

I agree with others that having an svn tag for that release would be
much more convenient, and it's the expected way. IIRC you're only
expected to keep the latest release under /dist, so the above URLs
will change over time, and it's too easy to delete those files by
mistake.

What prevents you from creating svn tags when releasing bundles?

Sling does release bundles individually, and we do have svn tags under
http://svn.apache.org/repos/asf/sling/tags/

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: svn tags for releases? (was: [VOTE] Graduate ACE from the Apache Incubator)

[Bertrand Delacretaz]

On Thu, Nov 17, 2011 at 3:37 PM, Bertrand Delacretaz
 wrote:
> ...I agree with others that having an svn tag for that release would be
> much more convenient...

oops sorry, wrong list - moving this thread to ace-...@incubator.apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Guillaume Nodet]

On Thu, Nov 17, 2011 at 14:30, sebb  wrote:

> On 17 November 2011 12:29, Karl Pauls  wrote:
> > I'm not sure what this has to do with the graduation vote. The release
> > as such has been accepted by the incubator pmc and there only need to
> > be one release. The source for each artifact is there, it is just per
> > artifact in the -source.jar.
>
> AFAICT the full source (as in SVN trunk) is not actually present in
> the distribution directory.
>
> For example, where are the top-level files in SVN (BUILDING, README) ?
> And the etc/ directory?
>
> If I wanted to build any or all of the components, there does not
> appear to be a way to do this from the files in the distribution.
>

The svn tree is not supposed to be a source distribution so looking at it
as a buildable thing is not required.


> > There might be different set-up then a lot of other projects have it
> > but we release our stuff on a per artifact basis how it is done by for
> > example Apache Felix as well and never has been an issue (and didn't
> > become unmanageably either -  also ymmv).
>
> The ASF primarily releases source; releases must include full source.
>

I agree on the first part, but not the *full* source.
 @ace you should look at the felix way which always include a source
distribution for each bundle.


>
> > I agree about the KEYS file. We should have uploaded it to the dist
> > dir as well but at least we have it at some place so it should be easy
> > to fix.
> >
> > regards,
> >
> > Karl
> >
> > On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
> >> On 17 November 2011 10:42, Marcel Offermans <
> marcel.offerm...@luminis.nl> wrote:
> >>> In my opinion, ACE is ready to begin the process of graduating from
> the Apache Incubator to a Top Level Project.
> >>>
> >>> Since joining the incubator in in May 2009 we've added 4 new
> committers (12 in total now) from diverse organizations and did a release
> in May this year to demonstrate we follow the Apache guidelines. We've
> shown an ability to self-govern using accepted Apache practices and ACE
> continues to attract new contributors and users.
> >>>
> >>> The first step is to vote as a community, demonstrating that ACE is
> ready and willing to graduate. Once this vote is succesful we create a
> board resolution proposal or Charter and start a vote on the general
> incubator list. The full process is described at
> http://incubator.apache.org/guides/graduation.html#toplevel
> >>>
> >>> The vote is open for at least 72 hours.
> >>
> >> The last (and only) release was 0.8, as far as I can tell.
> >>
> >> There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
> >> and there does not appear to be a full source archive of the project
> >> anywhere.
> >> The download page does not have a link to any source archives as far
> >> as I can tell.
> >> It does link to KEYS in SVN, but almost all other ASF projects have a
> >> copy of KEYS in the appropriate /dist directory.
> >>
> >> Normally releases are divided into binaries/ and source/ directories,
> >> with a KEYS file in the top-level, i.e.
> >>
> >> /dist/incubator/ace
> >> - KEYS
> >> - binaries/ace zip
> >> - sources/acezip
> >>
> >> Most of the files in the /dist/incubator/ace directory appear to be
> >> Maven artifacts; normally these are not stored in /dist but only in
> >> the Maven repo.
> >> Indeed most of the files are also in Maven Central. The only non-Maven
> >> files appear to be
> >>
> >> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
> >> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
> >>
> >> neither of which contains the source.
> >>
> >> I would expect the above zips to be in
> >>
> >> /dist/incubator/ace/binaries
> >>
> >> with corresponding source files in
> >>
> >> /dist/incubator/ace/source
> >>
> >> The SVN layout [1] is also a bit unusual.
> >> There is no tags/ directory for release tags, although there is a
> >> releases/ directory containing individual entries for each release for
> >> each component.
> >> This is likely to become unmanageable very quickly, if every release
> >> adds another 63 directory entries under releases/
> >>
> >> [1] https://svn.apache.org/repos/asf/incubator/ace/
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
> >
> >
> > --
> > Karl Pauls
> > karlpa...@gmail.com
> > http://twitter.com/karlpauls
> > http://www.linkedin.com/in/karlpauls
> > https://profiles.google.com/karlpauls
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 

Re: [VOTE] Graduate ACE from the Apache Incubator

[Karl Pauls]

On Thu, Nov 17, 2011 at 3:45 PM, Guillaume Nodet  wrote:
> On Thu, Nov 17, 2011 at 14:30, sebb  wrote:
>
>> On 17 November 2011 12:29, Karl Pauls  wrote:
>> > I'm not sure what this has to do with the graduation vote. The release
>> > as such has been accepted by the incubator pmc and there only need to
>> > be one release. The source for each artifact is there, it is just per
>> > artifact in the -source.jar.
>>
>> AFAICT the full source (as in SVN trunk) is not actually present in
>> the distribution directory.
>>
>> For example, where are the top-level files in SVN (BUILDING, README) ?
>> And the etc/ directory?
>>
>> If I wanted to build any or all of the components, there does not
>> appear to be a way to do this from the files in the distribution.
>>
>
> The svn tree is not supposed to be a source distribution so looking at it
> as a buildable thing is not required.
>
>
>> > There might be different set-up then a lot of other projects have it
>> > but we release our stuff on a per artifact basis how it is done by for
>> > example Apache Felix as well and never has been an issue (and didn't
>> > become unmanageably either -  also ymmv).
>>
>> The ASF primarily releases source; releases must include full source.
>>
>
> I agree on the first part, but not the *full* source.
>  @ace you should look at the felix way which always include a source
> distribution for each bundle.

Yeah, we could have configured the source-release, i agree. However, i
don't think that is a show-stopper (as much as it could be anyhow, as
the release already happend) as we have the source and what is need to
build. Another way to get this is to go to the tags at:

http://svn.apache.org/repos/asf/incubator/ace/releases/$subproject

regards,

Karl

>
>>
>> > I agree about the KEYS file. We should have uploaded it to the dist
>> > dir as well but at least we have it at some place so it should be easy
>> > to fix.
>> >
>> > regards,
>> >
>> > Karl
>> >
>> > On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
>> >> On 17 November 2011 10:42, Marcel Offermans <
>> marcel.offerm...@luminis.nl> wrote:
>> >>> In my opinion, ACE is ready to begin the process of graduating from
>> the Apache Incubator to a Top Level Project.
>> >>>
>> >>> Since joining the incubator in in May 2009 we've added 4 new
>> committers (12 in total now) from diverse organizations and did a release
>> in May this year to demonstrate we follow the Apache guidelines. We've
>> shown an ability to self-govern using accepted Apache practices and ACE
>> continues to attract new contributors and users.
>> >>>
>> >>> The first step is to vote as a community, demonstrating that ACE is
>> ready and willing to graduate. Once this vote is succesful we create a
>> board resolution proposal or Charter and start a vote on the general
>> incubator list. The full process is described at
>> http://incubator.apache.org/guides/graduation.html#toplevel
>> >>>
>> >>> The vote is open for at least 72 hours.
>> >>
>> >> The last (and only) release was 0.8, as far as I can tell.
>> >>
>> >> There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
>> >> and there does not appear to be a full source archive of the project
>> >> anywhere.
>> >> The download page does not have a link to any source archives as far
>> >> as I can tell.
>> >> It does link to KEYS in SVN, but almost all other ASF projects have a
>> >> copy of KEYS in the appropriate /dist directory.
>> >>
>> >> Normally releases are divided into binaries/ and source/ directories,
>> >> with a KEYS file in the top-level, i.e.
>> >>
>> >> /dist/incubator/ace
>> >> - KEYS
>> >> - binaries/ace zip
>> >> - sources/acezip
>> >>
>> >> Most of the files in the /dist/incubator/ace directory appear to be
>> >> Maven artifacts; normally these are not stored in /dist but only in
>> >> the Maven repo.
>> >> Indeed most of the files are also in Maven Central. The only non-Maven
>> >> files appear to be
>> >>
>> >> org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
>> >> org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
>> >>
>> >> neither of which contains the source.
>> >>
>> >> I would expect the above zips to be in
>> >>
>> >> /dist/incubator/ace/binaries
>> >>
>> >> with corresponding source files in
>> >>
>> >> /dist/incubator/ace/source
>> >>
>> >> The SVN layout [1] is also a bit unusual.
>> >> There is no tags/ directory for release tags, although there is a
>> >> releases/ directory containing individual entries for each release for
>> >> each component.
>> >> This is likely to become unmanageable very quickly, if every release
>> >> adds another 63 directory entries under releases/
>> >>
>> >> [1] https://svn.apache.org/repos/asf/incubator/ace/
>> >>
>> >> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >>
>> >
>> >
>> 

Re: [VOTE] Graduate ACE from the Apache Incubator

[sebb]

On 17 November 2011 14:07, Karl Pauls  wrote:
> $ mkdir org.apache.ace.client.automation-0.8.0-incubator
> $ cd org.apache.ace.client.automation-0.8.0-incubator/
> $ wget 
> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar

s/source/sources/

> $ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar
> $ wget 
> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
> $ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
> $ mvn clean install

=

Not exactly trivial compared with

$ svn co 
http://svn.apache.org/repos/asf/incubator/ace/releases/org.apache.ace.client.automation-0.8.0-incubator
-- or --
$ unzip org.apache.ace.client.automation-0.8.0-incubator-source.zip
(if it existed)
and then
$ cd org.apache.ace.client.automation-0.8.0-incubator
$ mvn clean install

There's another (bigger) problem with the existing -sources.jar files.
They don't contain any unit tests, as far as I can tell, yet there are
some unit tests in SVN.

Surely the unit tests should be distributed as part of the source release?

==

This is quite easy to fix, just (vote on and) release zip/tar.gz
archives of the tags for each component.
I would drop the -sources.jar files from /dist as they aren't all that
useful for non-Maven downloads.

==

To make it easier to navigate the dist/ directory, may I suggest
creating binaries/ and source/ folders?
The source/ folder would contain all the current source zips/tgz archives
The binaries folders would contain binary jars and javadoc jars
The *.pom files would be removed, as the pom.xml files would be in the
appropriate source/ archive.


> regards,
>
> Karl
>
> On Thu, Nov 17, 2011 at 2:54 PM, ant elder  wrote:
>> To try that I just went to the ACE downloads page which has a bunch of
>> jars and source jars to download, i downloaded the source of the first
>> one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and
>> looking inside there is the source to some Java classes but no build
>> scripts or pom.xml file, so how would I go about building this?
>>
>>   ...ant
>>
>> On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls  wrote:
>>> Again, we had this discussion before namely, when the actual release
>>> vote happened. I'm still confused why we have to go through this
>>> again. You should be able to build all of the components by using the
>>> -source.jar's that are provided. They contain what is necessary i.e.,
>>> the full source.
>>>
>>> regards,
>>>
>>> Karl
>>>
>>> On Thu, Nov 17, 2011 at 2:30 PM, sebb  wrote:
 On 17 November 2011 12:29, Karl Pauls  wrote:
> I'm not sure what this has to do with the graduation vote. The release
> as such has been accepted by the incubator pmc and there only need to
> be one release. The source for each artifact is there, it is just per
> artifact in the -source.jar.

 AFAICT the full source (as in SVN trunk) is not actually present in
 the distribution directory.

 For example, where are the top-level files in SVN (BUILDING, README) ?
 And the etc/ directory?

 If I wanted to build any or all of the components, there does not
 appear to be a way to do this from the files in the distribution.

> There might be different set-up then a lot of other projects have it
> but we release our stuff on a per artifact basis how it is done by for
> example Apache Felix as well and never has been an issue (and didn't
> become unmanageably either -  also ymmv).

 The ASF primarily releases source; releases must include full source.

> I agree about the KEYS file. We should have uploaded it to the dist
> dir as well but at least we have it at some place so it should be easy
> to fix.
>
> regards,
>
> Karl
>
> On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
>> On 17 November 2011 10:42, Marcel Offermans 
>>  wrote:
>>> In my opinion, ACE is ready to begin the process of graduating from the 
>>> Apache Incubator to a Top Level Project.
>>>
>>> Since joining the incubator in in May 2009 we've added 4 new committers 
>>> (12 in total now) from diverse organizations and did a release in May 
>>> this year to demonstrate we follow the Apache guidelines. We've shown 
>>> an ability to self-govern using accepted Apache practices and ACE 
>>> continues to attract new contributors and users.
>>>
>>> The first step is to vote as a community, demonstrating that ACE is 
>>> ready and willing to graduate. Once this vote is succesful we create a 
>>> board resolution proposal or Charter and start a vote on the general 
>>> incubator list. The full process is described at 
>>> http://incubator.apache.org/guides/graduation.html#toplevel
>>>
>>> The vote is open for at least 72 hours.
>>
>> The last (and only) release was 0.8, as far as 

Re: [VOTE] Graduate ACE from the Apache Incubator

[Karl Pauls]

Again, I'm not against doing things differently for future release
(and the reason this release looks like it does is because that is
configured like this in the apache-parent iirc). However, I'm still
confused what all of this has to do with the graduation proposal vote
and why this has to be on general@.

The release vote has passed a while ago and I don't see that the
release is invalid because we don't use a certain svn layout or maven
config. The source is in dist and the tags are in svn. I suggest we
move discussion about future release layouts to the ace-dev list and
into a separate thread unless you disagree.

regards,

Karl

On Thu, Nov 17, 2011 at 4:09 PM, sebb  wrote:
> On 17 November 2011 14:07, Karl Pauls  wrote:
>> $ mkdir org.apache.ace.client.automation-0.8.0-incubator
>> $ cd org.apache.ace.client.automation-0.8.0-incubator/
>> $ wget 
>> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar
>
> s/source/sources/
>
>> $ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar
>> $ wget 
>> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
>> $ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
>> $ mvn clean install
>
> =
>
> Not exactly trivial compared with
>
> $ svn co 
> http://svn.apache.org/repos/asf/incubator/ace/releases/org.apache.ace.client.automation-0.8.0-incubator
> -- or --
> $ unzip org.apache.ace.client.automation-0.8.0-incubator-source.zip
> (if it existed)
> and then
> $ cd org.apache.ace.client.automation-0.8.0-incubator
> $ mvn clean install
>
> There's another (bigger) problem with the existing -sources.jar files.
> They don't contain any unit tests, as far as I can tell, yet there are
> some unit tests in SVN.
>
> Surely the unit tests should be distributed as part of the source release?
>
> ==
>
> This is quite easy to fix, just (vote on and) release zip/tar.gz
> archives of the tags for each component.
> I would drop the -sources.jar files from /dist as they aren't all that
> useful for non-Maven downloads.
>
> ==
>
> To make it easier to navigate the dist/ directory, may I suggest
> creating binaries/ and source/ folders?
> The source/ folder would contain all the current source zips/tgz archives
> The binaries folders would contain binary jars and javadoc jars
> The *.pom files would be removed, as the pom.xml files would be in the
> appropriate source/ archive.
>
>
>> regards,
>>
>> Karl
>>
>> On Thu, Nov 17, 2011 at 2:54 PM, ant elder  wrote:
>>> To try that I just went to the ACE downloads page which has a bunch of
>>> jars and source jars to download, i downloaded the source of the first
>>> one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and
>>> looking inside there is the source to some Java classes but no build
>>> scripts or pom.xml file, so how would I go about building this?
>>>
>>>   ...ant
>>>
>>> On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls  wrote:
 Again, we had this discussion before namely, when the actual release
 vote happened. I'm still confused why we have to go through this
 again. You should be able to build all of the components by using the
 -source.jar's that are provided. They contain what is necessary i.e.,
 the full source.

 regards,

 Karl

 On Thu, Nov 17, 2011 at 2:30 PM, sebb  wrote:
> On 17 November 2011 12:29, Karl Pauls  wrote:
>> I'm not sure what this has to do with the graduation vote. The release
>> as such has been accepted by the incubator pmc and there only need to
>> be one release. The source for each artifact is there, it is just per
>> artifact in the -source.jar.
>
> AFAICT the full source (as in SVN trunk) is not actually present in
> the distribution directory.
>
> For example, where are the top-level files in SVN (BUILDING, README) ?
> And the etc/ directory?
>
> If I wanted to build any or all of the components, there does not
> appear to be a way to do this from the files in the distribution.
>
>> There might be different set-up then a lot of other projects have it
>> but we release our stuff on a per artifact basis how it is done by for
>> example Apache Felix as well and never has been an issue (and didn't
>> become unmanageably either -  also ymmv).
>
> The ASF primarily releases source; releases must include full source.
>
>> I agree about the KEYS file. We should have uploaded it to the dist
>> dir as well but at least we have it at some place so it should be easy
>> to fix.
>>
>> regards,
>>
>> Karl
>>
>> On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:
>>> On 17 November 2011 10:42, Marcel Offermans 
>>>  wrote:
 In my opinion, ACE is ready to begin the process of graduating from 
 the Apache Incubator to a Top Level Project.

 Since joining the inc

Re: [VOTE] Graduate ACE from the Apache Incubator

[Jean-Baptiste Onofré]

Hi Karl,

we can simply need to revert the changes just before the 0.8.0-incubator 
release.
When upgrading the ACE build to use Maven, firstly, we used the tags scm 
with Maven sub-modules.
So I'm quite sure that reverting just before the 0.8.0-incubator, I can 
prepare that for the next ACE release.


Regards
JB

On 11/17/2011 04:14 PM, Karl Pauls wrote:

Again, I'm not against doing things differently for future release
(and the reason this release looks like it does is because that is
configured like this in the apache-parent iirc). However, I'm still
confused what all of this has to do with the graduation proposal vote
and why this has to be on general@.

The release vote has passed a while ago and I don't see that the
release is invalid because we don't use a certain svn layout or maven
config. The source is in dist and the tags are in svn. I suggest we
move discussion about future release layouts to the ace-dev list and
into a separate thread unless you disagree.

regards,

Karl

On Thu, Nov 17, 2011 at 4:09 PM, sebb  wrote:

On 17 November 2011 14:07, Karl Pauls  wrote:

$ mkdir org.apache.ace.client.automation-0.8.0-incubator
$ cd org.apache.ace.client.automation-0.8.0-incubator/
$ wget 
http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar


s/source/sources/


$ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar
$ wget 
http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
$ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
$ mvn clean install


=

Not exactly trivial compared with

$ svn co 
http://svn.apache.org/repos/asf/incubator/ace/releases/org.apache.ace.client.automation-0.8.0-incubator
-- or --
$ unzip org.apache.ace.client.automation-0.8.0-incubator-source.zip
(if it existed)
and then
$ cd org.apache.ace.client.automation-0.8.0-incubator
$ mvn clean install

There's another (bigger) problem with the existing -sources.jar files.
They don't contain any unit tests, as far as I can tell, yet there are
some unit tests in SVN.

Surely the unit tests should be distributed as part of the source release?

==

This is quite easy to fix, just (vote on and) release zip/tar.gz
archives of the tags for each component.
I would drop the -sources.jar files from /dist as they aren't all that
useful for non-Maven downloads.

==

To make it easier to navigate the dist/ directory, may I suggest
creating binaries/ and source/ folders?
The source/ folder would contain all the current source zips/tgz archives
The binaries folders would contain binary jars and javadoc jars
The *.pom files would be removed, as the pom.xml files would be in the
appropriate source/ archive.



regards,

Karl

On Thu, Nov 17, 2011 at 2:54 PM, ant elder  wrote:

To try that I just went to the ACE downloads page which has a bunch of
jars and source jars to download, i downloaded the source of the first
one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and
looking inside there is the source to some Java classes but no build
scripts or pom.xml file, so how would I go about building this?

   ...ant

On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls  wrote:

Again, we had this discussion before namely, when the actual release
vote happened. I'm still confused why we have to go through this
again. You should be able to build all of the components by using the
-source.jar's that are provided. They contain what is necessary i.e.,
the full source.

regards,

Karl

On Thu, Nov 17, 2011 at 2:30 PM, sebb  wrote:

On 17 November 2011 12:29, Karl Pauls  wrote:

I'm not sure what this has to do with the graduation vote. The release
as such has been accepted by the incubator pmc and there only need to
be one release. The source for each artifact is there, it is just per
artifact in the -source.jar.


AFAICT the full source (as in SVN trunk) is not actually present in
the distribution directory.

For example, where are the top-level files in SVN (BUILDING, README) ?
And the etc/ directory?

If I wanted to build any or all of the components, there does not
appear to be a way to do this from the files in the distribution.


There might be different set-up then a lot of other projects have it
but we release our stuff on a per artifact basis how it is done by for
example Apache Felix as well and never has been an issue (and didn't
become unmanageably either -  also ymmv).


The ASF primarily releases source; releases must include full source.


I agree about the KEYS file. We should have uploaded it to the dist
dir as well but at least we have it at some place so it should be easy
to fix.

regards,

Karl

On Thu, Nov 17, 2011 at 1:07 PM, sebb  wrote:

On 17 November 2011 10:42, Marcel Offermans  wrote:

In my opinion, ACE is ready to begin the process of graduating from the Apache 
Incubator to a Top Level Project.

Since joining the incubator in in May 2009 we've added 4 new committers (12 in 
tota

Re: [VOTE] Graduate ACE from the Apache Incubator

[Karl Pauls]

JB,

please, lets move this to the ace-dev list.

regards,

Karl

On Thu, Nov 17, 2011 at 4:21 PM, Jean-Baptiste Onofré  wrote:
> Hi Karl,
>
> we can simply need to revert the changes just before the 0.8.0-incubator
> release.
> When upgrading the ACE build to use Maven, firstly, we used the tags scm
> with Maven sub-modules.
> So I'm quite sure that reverting just before the 0.8.0-incubator, I can
> prepare that for the next ACE release.
>
> Regards
> JB
>
> On 11/17/2011 04:14 PM, Karl Pauls wrote:
>>
>> Again, I'm not against doing things differently for future release
>> (and the reason this release looks like it does is because that is
>> configured like this in the apache-parent iirc). However, I'm still
>> confused what all of this has to do with the graduation proposal vote
>> and why this has to be on general@.
>>
>> The release vote has passed a while ago and I don't see that the
>> release is invalid because we don't use a certain svn layout or maven
>> config. The source is in dist and the tags are in svn. I suggest we
>> move discussion about future release layouts to the ace-dev list and
>> into a separate thread unless you disagree.
>>
>> regards,
>>
>> Karl
>>
>> On Thu, Nov 17, 2011 at 4:09 PM, sebb  wrote:
>>>
>>> On 17 November 2011 14:07, Karl Pauls  wrote:

 $ mkdir org.apache.ace.client.automation-0.8.0-incubator
 $ cd org.apache.ace.client.automation-0.8.0-incubator/
 $ wget
 http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar
>>>
>>> s/source/sources/
>>>
 $ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar
 $ wget
 http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
 $ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
 $ mvn clean install
>>>
>>> =
>>>
>>> Not exactly trivial compared with
>>>
>>> $ svn co
>>> http://svn.apache.org/repos/asf/incubator/ace/releases/org.apache.ace.client.automation-0.8.0-incubator
>>> -- or --
>>> $ unzip org.apache.ace.client.automation-0.8.0-incubator-source.zip
>>> (if it existed)
>>> and then
>>> $ cd org.apache.ace.client.automation-0.8.0-incubator
>>> $ mvn clean install
>>>
>>> There's another (bigger) problem with the existing -sources.jar files.
>>> They don't contain any unit tests, as far as I can tell, yet there are
>>> some unit tests in SVN.
>>>
>>> Surely the unit tests should be distributed as part of the source
>>> release?
>>>
>>> ==
>>>
>>> This is quite easy to fix, just (vote on and) release zip/tar.gz
>>> archives of the tags for each component.
>>> I would drop the -sources.jar files from /dist as they aren't all that
>>> useful for non-Maven downloads.
>>>
>>> ==
>>>
>>> To make it easier to navigate the dist/ directory, may I suggest
>>> creating binaries/ and source/ folders?
>>> The source/ folder would contain all the current source zips/tgz archives
>>> The binaries folders would contain binary jars and javadoc jars
>>> The *.pom files would be removed, as the pom.xml files would be in the
>>> appropriate source/ archive.
>>>
>>>
 regards,

 Karl

 On Thu, Nov 17, 2011 at 2:54 PM, ant elder  wrote:
>
> To try that I just went to the ACE downloads page which has a bunch of
> jars and source jars to download, i downloaded the source of the first
> one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and
> looking inside there is the source to some Java classes but no build
> scripts or pom.xml file, so how would I go about building this?
>
>   ...ant
>
> On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls
>  wrote:
>>
>> Again, we had this discussion before namely, when the actual release
>> vote happened. I'm still confused why we have to go through this
>> again. You should be able to build all of the components by using the
>> -source.jar's that are provided. They contain what is necessary i.e.,
>> the full source.
>>
>> regards,
>>
>> Karl
>>
>> On Thu, Nov 17, 2011 at 2:30 PM, sebb  wrote:
>>>
>>> On 17 November 2011 12:29, Karl Pauls  wrote:

 I'm not sure what this has to do with the graduation vote. The
 release
 as such has been accepted by the incubator pmc and there only need
 to
 be one release. The source for each artifact is there, it is just
 per
 artifact in the -source.jar.
>>>
>>> AFAICT the full source (as in SVN trunk) is not actually present in
>>> the distribution directory.
>>>
>>> For example, where are the top-level files in SVN (BUILDING, README)
>>> ?
>>> And the etc/ directory?
>>>
>>> If I wanted to build any or all of the components, there does not
>>> appear to be a way to do this from the files in the distribution.
>>>
 There might be different set-up then a lot of other

Re: [VOTE] Graduate ACE from the Apache Incubator

[Jean-Baptiste Onofré]

Sorry my mistake.

Regards
JB

On 11/17/2011 04:27 PM, Karl Pauls wrote:

JB,

please, lets move this to the ace-dev list.

regards,

Karl

On Thu, Nov 17, 2011 at 4:21 PM, Jean-Baptiste Onofré  wrote:

Hi Karl,

we can simply need to revert the changes just before the 0.8.0-incubator
release.
When upgrading the ACE build to use Maven, firstly, we used the tags scm
with Maven sub-modules.
So I'm quite sure that reverting just before the 0.8.0-incubator, I can
prepare that for the next ACE release.

Regards
JB

On 11/17/2011 04:14 PM, Karl Pauls wrote:


Again, I'm not against doing things differently for future release
(and the reason this release looks like it does is because that is
configured like this in the apache-parent iirc). However, I'm still
confused what all of this has to do with the graduation proposal vote
and why this has to be on general@.

The release vote has passed a while ago and I don't see that the
release is invalid because we don't use a certain svn layout or maven
config. The source is in dist and the tags are in svn. I suggest we
move discussion about future release layouts to the ace-dev list and
into a separate thread unless you disagree.

regards,

Karl

On Thu, Nov 17, 2011 at 4:09 PM, sebbwrote:


On 17 November 2011 14:07, Karl Paulswrote:


$ mkdir org.apache.ace.client.automation-0.8.0-incubator
$ cd org.apache.ace.client.automation-0.8.0-incubator/
$ wget
http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar


s/source/sources/


$ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar
$ wget
http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
$ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
$ mvn clean install


=

Not exactly trivial compared with

$ svn co
http://svn.apache.org/repos/asf/incubator/ace/releases/org.apache.ace.client.automation-0.8.0-incubator
-- or --
$ unzip org.apache.ace.client.automation-0.8.0-incubator-source.zip
(if it existed)
and then
$ cd org.apache.ace.client.automation-0.8.0-incubator
$ mvn clean install

There's another (bigger) problem with the existing -sources.jar files.
They don't contain any unit tests, as far as I can tell, yet there are
some unit tests in SVN.

Surely the unit tests should be distributed as part of the source
release?

==

This is quite easy to fix, just (vote on and) release zip/tar.gz
archives of the tags for each component.
I would drop the -sources.jar files from /dist as they aren't all that
useful for non-Maven downloads.

==

To make it easier to navigate the dist/ directory, may I suggest
creating binaries/ and source/ folders?
The source/ folder would contain all the current source zips/tgz archives
The binaries folders would contain binary jars and javadoc jars
The *.pom files would be removed, as the pom.xml files would be in the
appropriate source/ archive.



regards,

Karl

On Thu, Nov 17, 2011 at 2:54 PM, ant elderwrote:


To try that I just went to the ACE downloads page which has a bunch of
jars and source jars to download, i downloaded the source of the first
one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and
looking inside there is the source to some Java classes but no build
scripts or pom.xml file, so how would I go about building this?

   ...ant

On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls
  wrote:


Again, we had this discussion before namely, when the actual release
vote happened. I'm still confused why we have to go through this
again. You should be able to build all of the components by using the
-source.jar's that are provided. They contain what is necessary i.e.,
the full source.

regards,

Karl

On Thu, Nov 17, 2011 at 2:30 PM, sebbwrote:


On 17 November 2011 12:29, Karl Paulswrote:


I'm not sure what this has to do with the graduation vote. The
release
as such has been accepted by the incubator pmc and there only need
to
be one release. The source for each artifact is there, it is just
per
artifact in the -source.jar.


AFAICT the full source (as in SVN trunk) is not actually present in
the distribution directory.

For example, where are the top-level files in SVN (BUILDING, README)
?
And the etc/ directory?

If I wanted to build any or all of the components, there does not
appear to be a way to do this from the files in the distribution.


There might be different set-up then a lot of other projects have it
but we release our stuff on a per artifact basis how it is done by
for
example Apache Felix as well and never has been an issue (and didn't
become unmanageably either -  also ymmv).


The ASF primarily releases source; releases must include full source.


I agree about the KEYS file. We should have uploaded it to the dist
dir as well but at least we have it at some place so it should be
easy
to fix.

regards,

Karl

On Thu, Nov 17, 2011 at 1:07 PM, sebbwrote:


On 17 November 2011 10:42, Marcel
O

Re: [VOTE] Graduate ACE from the Apache Incubator

[Carsten Ziegeler]

Big +1

Carsten

2011/11/17 Marcel Offermans :
> In my opinion, ACE is ready to begin the process of graduating from the 
> Apache Incubator to a Top Level Project.
>
> Since joining the incubator in in May 2009 we've added 4 new committers (12 
> in total now) from diverse organizations and did a release in May this year 
> to demonstrate we follow the Apache guidelines. We've shown an ability to 
> self-govern using accepted Apache practices and ACE continues to attract new 
> contributors and users.
>
> The first step is to vote as a community, demonstrating that ACE is ready and 
> willing to graduate. Once this vote is succesful we create a board resolution 
> proposal or Charter and start a vote on the general incubator list. The full 
> process is described at 
> http://incubator.apache.org/guides/graduation.html#toplevel
>
> The vote is open for at least 72 hours.
>
> Greetings, Marcel
>
>



-- 
Carsten Ziegeler
cziege...@apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Carsten Ziegeler]

2011/11/17 Karl Pauls :
> Again, I'm not against doing things differently for future release
> (and the reason this release looks like it does is because that is
> configured like this in the apache-parent iirc). However, I'm still
> confused what all of this has to do with the graduation proposal vote
> and why this has to be on general@.
>
> The release vote has passed a while ago and I don't see that the
> release is invalid because we don't use a certain svn layout or maven
> config. The source is in dist and the tags are in svn. I suggest we
> move discussion about future release layouts to the ace-dev list and
> into a separate thread unless you disagree.
>

Exactly and I fail to see what this all has to do with the graduation vote.

Carsten

> regards,
>
> Karl
>
> On Thu, Nov 17, 2011 at 4:09 PM, sebb  wrote:
>> On 17 November 2011 14:07, Karl Pauls  wrote:
>>> $ mkdir org.apache.ace.client.automation-0.8.0-incubator
>>> $ cd org.apache.ace.client.automation-0.8.0-incubator/
>>> $ wget 
>>> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar
>>
>> s/source/sources/
>>
>>> $ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar
>>> $ wget 
>>> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
>>> $ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
>>> $ mvn clean install
>>
>> =
>>
>> Not exactly trivial compared with
>>
>> $ svn co 
>> http://svn.apache.org/repos/asf/incubator/ace/releases/org.apache.ace.client.automation-0.8.0-incubator
>> -- or --
>> $ unzip org.apache.ace.client.automation-0.8.0-incubator-source.zip
>> (if it existed)
>> and then
>> $ cd org.apache.ace.client.automation-0.8.0-incubator
>> $ mvn clean install
>>
>> There's another (bigger) problem with the existing -sources.jar files.
>> They don't contain any unit tests, as far as I can tell, yet there are
>> some unit tests in SVN.
>>
>> Surely the unit tests should be distributed as part of the source release?
>>
>> ==
>>
>> This is quite easy to fix, just (vote on and) release zip/tar.gz
>> archives of the tags for each component.
>> I would drop the -sources.jar files from /dist as they aren't all that
>> useful for non-Maven downloads.
>>
>> ==
>>
>> To make it easier to navigate the dist/ directory, may I suggest
>> creating binaries/ and source/ folders?
>> The source/ folder would contain all the current source zips/tgz archives
>> The binaries folders would contain binary jars and javadoc jars
>> The *.pom files would be removed, as the pom.xml files would be in the
>> appropriate source/ archive.
>>
>>
>>> regards,
>>>
>>> Karl
>>>
>>> On Thu, Nov 17, 2011 at 2:54 PM, ant elder  wrote:
 To try that I just went to the ACE downloads page which has a bunch of
 jars and source jars to download, i downloaded the source of the first
 one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and
 looking inside there is the source to some Java classes but no build
 scripts or pom.xml file, so how would I go about building this?

   ...ant

 On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls  wrote:
> Again, we had this discussion before namely, when the actual release
> vote happened. I'm still confused why we have to go through this
> again. You should be able to build all of the components by using the
> -source.jar's that are provided. They contain what is necessary i.e.,
> the full source.
>
> regards,
>
> Karl
>
> On Thu, Nov 17, 2011 at 2:30 PM, sebb  wrote:
>> On 17 November 2011 12:29, Karl Pauls  wrote:
>>> I'm not sure what this has to do with the graduation vote. The release
>>> as such has been accepted by the incubator pmc and there only need to
>>> be one release. The source for each artifact is there, it is just per
>>> artifact in the -source.jar.
>>
>> AFAICT the full source (as in SVN trunk) is not actually present in
>> the distribution directory.
>>
>> For example, where are the top-level files in SVN (BUILDING, README) ?
>> And the etc/ directory?
>>
>> If I wanted to build any or all of the components, there does not
>> appear to be a way to do this from the files in the distribution.
>>
>>> There might be different set-up then a lot of other projects have it
>>> but we release our stuff on a per artifact basis how it is done by for
>>> example Apache Felix as well and never has been an issue (and didn't
>>> become unmanageably either -  also ymmv).
>>
>> The ASF primarily releases source; releases must include full source.
>>
>>> I agree about the KEYS file. We should have uploaded it to the dist
>>> dir as well but at least we have it at some place so it should be easy
>>> to fix.
>>>
>>> regards,
>>>
>>> Karl
>>>
>>> On Thu, Nov 17, 2011 at 1:07 PM, sebb  

Re: [VOTE] Graduate ACE from the Apache Incubator

[ant elder]

On Thu, Nov 17, 2011 at 3:14 PM, Karl Pauls  wrote:
> Again, I'm not against doing things differently for future release
> (and the reason this release looks like it does is because that is
> configured like this in the apache-parent iirc). However, I'm still
> confused what all of this has to do with the graduation proposal vote
> and why this has to be on general@.
>

I think why its come up here now is because part of judging if a
poddling is ready to graduate is if they understand how to make and
review ASF releases properly. And with whats be said here and how the
source has to be built i'm wondering if anyone who voted +1 for the
release would have actually tried to build any of the source.

   ...ant

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Karl Pauls]

On Thu, Nov 17, 2011 at 4:38 PM, ant elder  wrote:
> On Thu, Nov 17, 2011 at 3:14 PM, Karl Pauls  wrote:
>> Again, I'm not against doing things differently for future release
>> (and the reason this release looks like it does is because that is
>> configured like this in the apache-parent iirc). However, I'm still
>> confused what all of this has to do with the graduation proposal vote
>> and why this has to be on general@.
>>
>
> I think why its come up here now is because part of judging if a
> poddling is ready to graduate is if they understand how to make and
> review ASF releases properly. And with whats be said here and how the
> source has to be built i'm wondering if anyone who voted +1 for the
> release would have actually tried to build any of the source.

I guess the point is: are you arguing that the release should not
haven been accepted by the incubator in the first place on the grounds
that you find it hard to build and hence, you want to see a new one
before the we can vote on approaching the incubator for a graduation?

If yes, lets have that debate. If no, lets move this to a new thread
on the ace-dev list.

regards,

Karl

>   ...ant
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>



-- 
Karl Pauls
karlpa...@gmail.com
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[ant elder]

On Thu, Nov 17, 2011 at 3:47 PM, Karl Pauls  wrote:
> On Thu, Nov 17, 2011 at 4:38 PM, ant elder  wrote:
>> On Thu, Nov 17, 2011 at 3:14 PM, Karl Pauls  wrote:
>>> Again, I'm not against doing things differently for future release
>>> (and the reason this release looks like it does is because that is
>>> configured like this in the apache-parent iirc). However, I'm still
>>> confused what all of this has to do with the graduation proposal vote
>>> and why this has to be on general@.
>>>
>>
>> I think why its come up here now is because part of judging if a
>> poddling is ready to graduate is if they understand how to make and
>> review ASF releases properly. And with whats be said here and how the
>> source has to be built i'm wondering if anyone who voted +1 for the
>> release would have actually tried to build any of the source.
>
> I guess the point is: are you arguing that the release should not
> haven been accepted by the incubator in the first place on the grounds
> that you find it hard to build and hence, you want to see a new one
> before the we can vote on approaching the incubator for a graduation?
>

I'm not arguing anything yet. Some valid comments and questions were
made in the vote thread, you asked why they were happening here and i
tried to answer that. The Incubator people should have an opportunity
to discuss a graduation, perhaps some of that might be better on a
graduation discussion thread but there wasn't one of those before the
vote.

The release does look a bit dubious to me.

   ...ant

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Karl Pauls]

On Thu, Nov 17, 2011 at 4:56 PM, ant elder  wrote:
> On Thu, Nov 17, 2011 at 3:47 PM, Karl Pauls  wrote:
>> On Thu, Nov 17, 2011 at 4:38 PM, ant elder  wrote:
>>> On Thu, Nov 17, 2011 at 3:14 PM, Karl Pauls  wrote:
 Again, I'm not against doing things differently for future release
 (and the reason this release looks like it does is because that is
 configured like this in the apache-parent iirc). However, I'm still
 confused what all of this has to do with the graduation proposal vote
 and why this has to be on general@.

>>>
>>> I think why its come up here now is because part of judging if a
>>> poddling is ready to graduate is if they understand how to make and
>>> review ASF releases properly. And with whats be said here and how the
>>> source has to be built i'm wondering if anyone who voted +1 for the
>>> release would have actually tried to build any of the source.
>>
>> I guess the point is: are you arguing that the release should not
>> haven been accepted by the incubator in the first place on the grounds
>> that you find it hard to build and hence, you want to see a new one
>> before the we can vote on approaching the incubator for a graduation?
>>
>
> I'm not arguing anything yet. Some valid comments and questions were
> made in the vote thread, you asked why they were happening here and i
> tried to answer that. The Incubator people should have an opportunity
> to discuss a graduation, perhaps some of that might be better on a
> graduation discussion thread but there wasn't one of those before the
> vote.
>
> The release does look a bit dubious to me.

Well, I understand that part and I agree that this is worthwhile to
discuss. I'm just trying to get this sorted-out into something that we
can discuss on the incubator level i.e., based on incubator
requirements. In that sense, what are dubious points with the release
that we as incubator pmc overlooked when voting on it?

regards,

Karl

p.s.: Regarding the vote, let me make clear (in case it got missed):
marcel did cc general@ on the community vote on whether we want to ask
for graduation.This is not yet the actual incubator vote. Obviously,
we better catch problems now so I think its good we have this
discussion.

>   ...ant
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>



-- 
Karl Pauls
karlpa...@gmail.com
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Kafka 0.7.0-incubating

[Jun Rao]

Sebb,

Just to want to clarify on the source distribution. It seems there are
other Apache projects that release a single distribution with both source
code and jars. For example,
http://mirror.metrocast.net/apache//zookeeper/zookeeper-3.3.3/ . So, is
source distribution strictly required?

Thanks,

Jun

On Tue, Nov 15, 2011 at 7:27 AM, sebb  wrote:

> On 15 November 2011 15:05, Jun Rao  wrote:
> > The distribution does include source code in it. Are you saying that we
> > should have a separate source distribution with no jars in it?
>
> Yes, that is the normal way to do things.
>
> The source archive should basically be a copy of the SVN tag,
> excluding any SVN-only files.
>
> It should be possible to unpack the source archive, download any
> required external dependencies (the procedure to do this should be
> documented, e.g. in a README or BUILDING text file) and then
> build/test the software from the unpacked source.
>
> By the way, I don't understand why the RAT jar is in SVN; normally one
> would expect that to be an external dependency.
>
> > Thanks,
> >
> > Jun
> >
> > On Mon, Nov 14, 2011 at 5:37 PM, sebb  wrote:
> >
> >> On 14 November 2011 19:52, Neha Narkhede 
> wrote:
> >> > Hi,
> >> >
> >> > Kafka community is excited to share that RC for release of
> >> > Kafka-0.7.0-incubating has been +1'd over at kafka-user@incubator.
> >> > Please try it out and vote for the Apache Kafka 0.7.0-incubating
> release.
> >> > This is the first release of Kafka since we've joined the Apache
> >> incubator.
> >> >
> >> > Vote thread
> >> > http://markmail.org/message/pqsla5furf7nzpe2?q=kafka+candidate+6
> >> >
> >> > Release artifacts
> >> >
> >>
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-6/
> >>
> >> -1
> >> There's no source archive.
> >> ASF primarily releases source; binary archives are optional (but
> >> almost always provided).
> >> Source archives are required.
> >>
> >> -0
> >> The binary archive is huge; this is mainly because it contains
> >> multiple copies of many jars.
> >> It would be better for users if there was a single copy of each jar,
> >> and an installation script to copy them after unpacking.
> >>
> >> > SVN revision
> >> > https://svn.apache.org/repos/asf/incubator/kafka/branches/0.7@1199132
> >>
> >> The normal practice is to use an SVN tag for the release vote, for
> example:
> >>
> >>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/0.7.0-incubating-RC1
> >>
> >> If the vote succeeds, rename/copy it to
> >> https://svn.apache.org/repos/asf/incubator/kafka/tags/0.7.0-incubating
> >>
> >> If the vote fails, create a new tag:
> >>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/0.7.0-incubating-RC2
> >>
> >> -1:
> >> There is no DISCLAIMER
> >>
> >> The NOTICE file does not follow standards.
> >> The first 5 lines should look like the lines in === below:
> >>
> >> ===
> >> Apache Kafka
> >> Copyright ?-2011 The Apache Software Foundation.
> >>
> >> This product includes software developed at
> >> The Apache Software Foundation (http://www.apache.org/).
> >> ===
> >>
> >> The rest of the NOTICE file should be for *required* notices only; it
> >> is not required to list other Apache projects.
> >>
> >> The NOTICE file also contains a license, that should be in LICENSE.
> >> No mention of sbt, which is in SVN - as that is also included in the
> >> binary release, should that be mentioned in the NOTICE file?
> >>
> >> > PGP release keys
> >> > http://svn.apache.org/repos/asf/incubator/kafka/KEYS
> >> >
> >> > This vote is open until Thursday, Nov 17th 12 pm
> >> >
> >> > Thanks,
> >> > Neha
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Suitable Names Search [WAS Re: Trademark Kill Searches...]

[Robert Burrell Donkin]

On Thu, Nov 17, 2011 at 2:08 PM, Shane Curcuru  wrote:
> +1 to the JIRA project and the notifications coming here.  Thanks for
> driving this one!

I've done some customisation on PODLINGNAMESEARCH[1] (Hopefully Noel
will forgive me for assigning him as project lead without asking
first; just seemed appropriate.) Please jump with comments,
observations or improvements - or those with karma should feel free to
dive in and make changes.

I plan to use Rat to pilot the PODLINGNAMESEARCH set up sometime soon

Robert

[1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (PODLINGNAMESEARCH-1) Establish whether "Apache Rat" is a suitable name

[Robert Burrell Donkin (Created) (JIRA)]

Establish whether "Apache Rat" is a suitable name
-

 Key: PODLINGNAMESEARCH-1
 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Robert Burrell Donkin




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Updated] (PODLINGNAMESEARCH-1) Establish whether "Apache Rat" is a suitable name

[Robert Burrell Donkin (Updated) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Burrell Donkin updated PODLINGNAMESEARCH-1:
--

Evidence Of Open Source Adoption: 

Searched for "Rat" projects at http://www.ohloh.net/
 
  Apache Rat is listed first out of 109 hits
  FatRat Library [OPC DA (Data Access) Server Toolkit]
  PackRat [PackRat is a personal media collection manager for Android 
phones.] 
  n00bRAT [An undetectable Remote Administration Tool -OR- trojan, an all 
new approach]
  Radar Tools(RAT) [RAT (Radar Tools) is a powerful open-source software 
tool for processing SAR (Synthetic Aperture Radar) remote sensing data.] 
  Rats SysLog Demon [Rats Syslog Demon.NT service which listens at port 514 
for Syslog msgs. ] 
  RandomRat [RandomRat is a program for generating random sets that meet 
specific criteria]
  ratpwf [Rat - similar to many, different from all] 
  RAT [RAT is a library for the construction of real time systems in both 
conventional VM\\\'s and embedded/real-time environments.] 
  Steel RATS [Steel Rats is a gui wrapper for the command line source code 
auditing tool RATS]
  and many more

Searched for "Rat" at http://sourceforge.net/ and found 62 results with 
some good matches including

RAT - Remote Assistance Tool
Recurring Alarm Timer (RAT) 
RAT - Refractor2 Archive Tool 
Rat Mind Map
The Rat CMS 
RAT Remote Applications Tiny Basic 
Rat Rip
RAT
RAT:// 
Rats SysLog Demon 




Evidence of adoption by open source projects at Ohloh and Sourceforge. A small 
number of exact matches discovered. Rat is used as part of several project 
names.

> Establish whether "Apache Rat" is a suitable name
> -
>
> Key: PODLINGNAMESEARCH-1
> URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Robert Burrell Donkin
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Updated] (PODLINGNAMESEARCH-1) Establish whether "Apache Rat" is a suitable name

[Robert Burrell Donkin (Updated) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Burrell Donkin updated PODLINGNAMESEARCH-1:
--

Evidence Of Open Source Adoption: 
Searched for "Rat" projects at http://www.ohloh.net/
  * Apache Rat is listed first out of 109 hits
* FatRat Library [OPC DA (Data Access) Server Toolkit]
* PackRat [PackRat is a personal media collection manager for Android 
phones.] 
* n00bRAT [An undetectable Remote Administration Tool -OR- trojan, an all 
new approach]
* Radar Tools(RAT) [RAT (Radar Tools) is a powerful open-source software 
tool for processing SAR (Synthetic Aperture Radar) remote sensing data.]
* Rats SysLog Demon [Rats Syslog Demon.NT service which listens at port 514 
for Syslog msgs. ]
* RandomRat [RandomRat is a program for generating random sets that meet 
specific criteria]
* ratpwf [Rat - similar to many, different from all]
* RAT [RAT is a library for the construction of real time systems in both 
conventional VM\\\'s and embedded/real-time environments.]
* Steel RATS [Steel Rats is a gui wrapper for the command line source code 
auditing tool RATS]
   (and more)

Searched for "Rat" at http://sourceforge.net/ and found 62 results with some 
good matches including:
  * RAT - Remote Assistance Tool
  * Recurring Alarm Timer (RAT) 
  * RAT - Refractor2 Archive Tool 
  * Rat Mind Map
  * The Rat CMS 
  * RAT Remote Applications Tiny Basic 
  * Rat Rip
  * RAT
  * RAT:// 
  * Rats SysLog Demon 

  was:

Searched for "Rat" projects at http://www.ohloh.net/
 
  Apache Rat is listed first out of 109 hits
  FatRat Library [OPC DA (Data Access) Server Toolkit]
  PackRat [PackRat is a personal media collection manager for Android 
phones.] 
  n00bRAT [An undetectable Remote Administration Tool -OR- trojan, an all 
new approach]
  Radar Tools(RAT) [RAT (Radar Tools) is a powerful open-source software 
tool for processing SAR (Synthetic Aperture Radar) remote sensing data.] 
  Rats SysLog Demon [Rats Syslog Demon.NT service which listens at port 514 
for Syslog msgs. ] 
  RandomRat [RandomRat is a program for generating random sets that meet 
specific criteria]
  ratpwf [Rat - similar to many, different from all] 
  RAT [RAT is a library for the construction of real time systems in both 
conventional VM\\\'s and embedded/real-time environments.] 
  Steel RATS [Steel Rats is a gui wrapper for the command line source code 
auditing tool RATS]
  and many more

Searched for "Rat" at http://sourceforge.net/ and found 62 results with 
some good matches including

RAT - Remote Assistance Tool
Recurring Alarm Timer (RAT) 
RAT - Refractor2 Archive Tool 
Rat Mind Map
The Rat CMS 
RAT Remote Applications Tiny Basic 
Rat Rip
RAT
RAT:// 
Rats SysLog Demon 





> Establish whether "Apache Rat" is a suitable name
> -
>
> Key: PODLINGNAMESEARCH-1
> URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Robert Burrell Donkin
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Updated] (PODLINGNAMESEARCH-1) Establish whether "Apache Rat" is a suitable name

[Robert Burrell Donkin (Updated) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Burrell Donkin updated PODLINGNAMESEARCH-1:
--

Evidence Of Open Source Adoption: 
Searched for "Rat" projects at http://www.ohloh.net/
  * Apache Rat is listed first out of 109 hits
* FatRat Library [OPC DA (Data Access) Server Toolkit]
* PackRat [PackRat is a personal media collection manager for Android 
phones.] 
* n00bRAT [An undetectable Remote Administration Tool -OR- trojan, an all 
new approach]
* Radar Tools(RAT) [RAT (Radar Tools) is a powerful open-source software 
tool for processing SAR (Synthetic Aperture Radar) remote sensing data.]
* Rats SysLog Demon [Rats Syslog Demon.NT service which listens at port 514 
for Syslog msgs. ]
* RandomRat [RandomRat is a program for generating random sets that meet 
specific criteria]
* ratpwf [Rat - similar to many, different from all]
* RAT [RAT is a library for the construction of real time systems in both 
conventional VM\\\'s and embedded/real-time environments.]
* Steel RATS [Steel Rats is a gui wrapper for the command line source code 
auditing tool RATS]
   (and more)

Searched for "Rat" at http://sourceforge.net/ and found 62 results with some 
good matches including:
  * RAT - Remote Assistance Tool
  * Recurring Alarm Timer (RAT) 
  * RAT - Refractor2 Archive Tool 
  * Rat Mind Map
  * The Rat CMS 
  * RAT Remote Applications Tiny Basic 
  * Rat Rip
  * RAT
  * RAT:// 
  * Rats SysLog Demon 

Searched for "Rat" at https://github.com/ and found 90 repositories listed; 
some good matches include
 * elliottcable / rat (Ruby)
 * majek / rats (Ruby) 
 * cenize / rat (Ruby) 
 * DHS / rat (Ruby)
 * koops / rat (Ruby) 
 * ojii / django-rat (Python) 
 * ScottyB / RAT (Java) 
  

  was:
Searched for "Rat" projects at http://www.ohloh.net/
  * Apache Rat is listed first out of 109 hits
* FatRat Library [OPC DA (Data Access) Server Toolkit]
* PackRat [PackRat is a personal media collection manager for Android 
phones.] 
* n00bRAT [An undetectable Remote Administration Tool -OR- trojan, an all 
new approach]
* Radar Tools(RAT) [RAT (Radar Tools) is a powerful open-source software 
tool for processing SAR (Synthetic Aperture Radar) remote sensing data.]
* Rats SysLog Demon [Rats Syslog Demon.NT service which listens at port 514 
for Syslog msgs. ]
* RandomRat [RandomRat is a program for generating random sets that meet 
specific criteria]
* ratpwf [Rat - similar to many, different from all]
* RAT [RAT is a library for the construction of real time systems in both 
conventional VM\\\'s and embedded/real-time environments.]
* Steel RATS [Steel Rats is a gui wrapper for the command line source code 
auditing tool RATS]
   (and more)

Searched for "Rat" at http://sourceforge.net/ and found 62 results with some 
good matches including:
  * RAT - Remote Assistance Tool
  * Recurring Alarm Timer (RAT) 
  * RAT - Refractor2 Archive Tool 
  * Rat Mind Map
  * The Rat CMS 
  * RAT Remote Applications Tiny Basic 
  * Rat Rip
  * RAT
  * RAT:// 
  * Rats SysLog Demon 


A number of repositories named "rat" hosted by GitHub 

> Establish whether "Apache Rat" is a suitable name
> -
>
> Key: PODLINGNAMESEARCH-1
> URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Robert Burrell Donkin
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Updated] (PODLINGNAMESEARCH-1) Establish whether "Apache Rat" is a suitable name

[Robert Burrell Donkin (Updated) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Burrell Donkin updated PODLINGNAMESEARCH-1:
--

Evidence Of Open Source Adoption: 
Searched for "Rat" projects at http://www.ohloh.net/
  * Apache Rat is listed first out of 109 hits
* FatRat Library [OPC DA (Data Access) Server Toolkit]
* PackRat [PackRat is a personal media collection manager for Android 
phones.] 
* n00bRAT [An undetectable Remote Administration Tool -OR- trojan, an all 
new approach]
* Radar Tools(RAT) [RAT (Radar Tools) is a powerful open-source software 
tool for processing SAR (Synthetic Aperture Radar) remote sensing data.]
* Rats SysLog Demon [Rats Syslog Demon.NT service which listens at port 514 
for Syslog msgs. ]
* RandomRat [RandomRat is a program for generating random sets that meet 
specific criteria]
* ratpwf [Rat - similar to many, different from all]
* RAT [RAT is a library for the construction of real time systems in both 
conventional VM\\\'s and embedded/real-time environments.]
* Steel RATS [Steel Rats is a gui wrapper for the command line source code 
auditing tool RATS]
   (and more)

Searched for "Rat" at http://sourceforge.net/ and found 62 results with some 
good matches including:
  * RAT - Remote Assistance Tool
  * Recurring Alarm Timer (RAT) 
  * RAT - Refractor2 Archive Tool 
  * Rat Mind Map
  * The Rat CMS 
  * RAT Remote Applications Tiny Basic 
  * Rat Rip
  * RAT
  * RAT:// 
  * Rats SysLog Demon 

Searched for "Rat" at https://github.com/ and found 90 repositories listed; 
some good matches include
 * elliottcable / rat (Ruby)
 * majek / rats (Ruby) 
 * cenize / rat (Ruby) 
 * DHS / rat (Ruby)
 * koops / rat (Ruby) 
 * ojii / django-rat (Python) 
 * ScottyB / RAT (Java) 
  
Search for "open source rat" at 
 * www.google.com returned 6,350,000 results 
   * open source projects where "Remote administration tool" is abbreviated to 
RAT turn up high in the rankings
   * Apache project is ranked 4
   * Other high ranked Rats include "Robust Audio Tool (RAT) ... an open-source 
audio conferencing and streaming application"
 * http://search.yahoo.com returned 39,400,000 results
   * Two Rat projects hosted at sourceforge are highly ranked
   * Other high ranked Rats include "Robust Audio Tool (RAT) ... an open-source 
audio conferencing and streaming application"
 * http://www.bing.com/ returned 38,800,000 results
  * Several open source projects named Rat were returned on the first of results

  was:
Searched for "Rat" projects at http://www.ohloh.net/
  * Apache Rat is listed first out of 109 hits
* FatRat Library [OPC DA (Data Access) Server Toolkit]
* PackRat [PackRat is a personal media collection manager for Android 
phones.] 
* n00bRAT [An undetectable Remote Administration Tool -OR- trojan, an all 
new approach]
* Radar Tools(RAT) [RAT (Radar Tools) is a powerful open-source software 
tool for processing SAR (Synthetic Aperture Radar) remote sensing data.]
* Rats SysLog Demon [Rats Syslog Demon.NT service which listens at port 514 
for Syslog msgs. ]
* RandomRat [RandomRat is a program for generating random sets that meet 
specific criteria]
* ratpwf [Rat - similar to many, different from all]
* RAT [RAT is a library for the construction of real time systems in both 
conventional VM\\\'s and embedded/real-time environments.]
* Steel RATS [Steel Rats is a gui wrapper for the command line source code 
auditing tool RATS]
   (and more)

Searched for "Rat" at http://sourceforge.net/ and found 62 results with some 
good matches including:
  * RAT - Remote Assistance Tool
  * Recurring Alarm Timer (RAT) 
  * RAT - Refractor2 Archive Tool 
  * Rat Mind Map
  * The Rat CMS 
  * RAT Remote Applications Tiny Basic 
  * Rat Rip
  * RAT
  * RAT:// 
  * Rats SysLog Demon 

Searched for "Rat" at https://github.com/ and found 90 repositories listed; 
some good matches include
 * elliottcable / rat (Ruby)
 * majek / rats (Ruby) 
 * cenize / rat (Ruby) 
 * DHS / rat (Ruby)
 * koops / rat (Ruby) 
 * ojii / django-rat (Python) 
 * ScottyB / RAT (Java) 
  


> Establish whether "Apache Rat" is a suitable name
> -
>
> Key: PODLINGNAMESEARCH-1
> URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Robert Burrell Donkin
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe

[jira] [Commented] (PODLINGNAMESEARCH-1) Establish whether "Apache Rat" is a suitable name

[Robert Burrell Donkin (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152195#comment-13152195
 ] 

Robert Burrell Donkin commented on PODLINGNAMESEARCH-1:
---

Evidence of several established open source projects called Rat ranked highly 
by search engines.

> Establish whether "Apache Rat" is a suitable name
> -
>
> Key: PODLINGNAMESEARCH-1
> URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-1
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Robert Burrell Donkin
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Marcel Offermans]

Hello Ant,

On Nov 17, 2011, at 16:56 PM, ant elder wrote:
> On Thu, Nov 17, 2011 at 3:47 PM, Karl Pauls  wrote:
>> On Thu, Nov 17, 2011 at 4:38 PM, ant elder  wrote:
>>> On Thu, Nov 17, 2011 at 3:14 PM, Karl Pauls  wrote:
 Again, I'm not against doing things differently for future release
 (and the reason this release looks like it does is because that is
 configured like this in the apache-parent iirc). However, I'm still
 confused what all of this has to do with the graduation proposal vote
 and why this has to be on general@.
 
>>> 
>>> I think why its come up here now is because part of judging if a
>>> poddling is ready to graduate is if they understand how to make and
>>> review ASF releases properly. And with whats be said here and how the
>>> source has to be built i'm wondering if anyone who voted +1 for the
>>> release would have actually tried to build any of the source.
>> 
>> I guess the point is: are you arguing that the release should not
>> haven been accepted by the incubator in the first place on the grounds
>> that you find it hard to build and hence, you want to see a new one
>> before the we can vote on approaching the incubator for a graduation?
> 
> I'm not arguing anything yet. Some valid comments and questions were
> made in the vote thread, you asked why they were happening here and i
> tried to answer that. The Incubator people should have an opportunity
> to discuss a graduation, perhaps some of that might be better on a
> graduation discussion thread but there wasn't one of those before the
> vote.

Starting with that last remark, the vote that was started earlier today is the 
"Community Graduation Vote" where we as the ACE community vote to confirm that 
we are ready and willing to start the graduation process (as explained here 
http://incubator.apache.org/guides/graduation.html#tlp-community-vote). Before 
that, on the ACE list, and in the last board report, we already expressed that 
we feel we're ready to graduate. Whilst I don't mind adding a step before this 
one in the graduation guide, I am not aware of skipping a step in the process.

> The release does look a bit dubious to me.

Point taken, we appreciate all the feedback and will take that into account 
when doing the next release.

Greetings, Marcel

Re: [VOTE] Release Kafka 0.7.0-incubating

[sebb]

On 17 November 2011 16:30, Jun Rao  wrote:
> Sebb,
>
> Just to want to clarify on the source distribution. It seems there are
> other Apache projects that release a single distribution with both source
> code and jars. For example,
> http://mirror.metrocast.net/apache//zookeeper/zookeeper-3.3.3/ . So, is

I don't think that's a good example to follow.

> source distribution strictly required?

In my opinion, yes.

> Thanks,
>
> Jun
>
> On Tue, Nov 15, 2011 at 7:27 AM, sebb  wrote:
>
>> On 15 November 2011 15:05, Jun Rao  wrote:
>> > The distribution does include source code in it. Are you saying that we
>> > should have a separate source distribution with no jars in it?
>>
>> Yes, that is the normal way to do things.
>>
>> The source archive should basically be a copy of the SVN tag,
>> excluding any SVN-only files.
>>
>> It should be possible to unpack the source archive, download any
>> required external dependencies (the procedure to do this should be
>> documented, e.g. in a README or BUILDING text file) and then
>> build/test the software from the unpacked source.
>>
>> By the way, I don't understand why the RAT jar is in SVN; normally one
>> would expect that to be an external dependency.
>>
>> > Thanks,
>> >
>> > Jun
>> >
>> > On Mon, Nov 14, 2011 at 5:37 PM, sebb  wrote:
>> >
>> >> On 14 November 2011 19:52, Neha Narkhede 
>> wrote:
>> >> > Hi,
>> >> >
>> >> > Kafka community is excited to share that RC for release of
>> >> > Kafka-0.7.0-incubating has been +1'd over at kafka-user@incubator.
>> >> > Please try it out and vote for the Apache Kafka 0.7.0-incubating
>> release.
>> >> > This is the first release of Kafka since we've joined the Apache
>> >> incubator.
>> >> >
>> >> > Vote thread
>> >> > http://markmail.org/message/pqsla5furf7nzpe2?q=kafka+candidate+6
>> >> >
>> >> > Release artifacts
>> >> >
>> >>
>> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-6/
>> >>
>> >> -1
>> >> There's no source archive.
>> >> ASF primarily releases source; binary archives are optional (but
>> >> almost always provided).
>> >> Source archives are required.
>> >>
>> >> -0
>> >> The binary archive is huge; this is mainly because it contains
>> >> multiple copies of many jars.
>> >> It would be better for users if there was a single copy of each jar,
>> >> and an installation script to copy them after unpacking.
>> >>
>> >> > SVN revision
>> >> > https://svn.apache.org/repos/asf/incubator/kafka/branches/0.7@1199132
>> >>
>> >> The normal practice is to use an SVN tag for the release vote, for
>> example:
>> >>
>> >>
>> https://svn.apache.org/repos/asf/incubator/kafka/tags/0.7.0-incubating-RC1
>> >>
>> >> If the vote succeeds, rename/copy it to
>> >> https://svn.apache.org/repos/asf/incubator/kafka/tags/0.7.0-incubating
>> >>
>> >> If the vote fails, create a new tag:
>> >>
>> https://svn.apache.org/repos/asf/incubator/kafka/tags/0.7.0-incubating-RC2
>> >>
>> >> -1:
>> >> There is no DISCLAIMER
>> >>
>> >> The NOTICE file does not follow standards.
>> >> The first 5 lines should look like the lines in === below:
>> >>
>> >> ===
>> >> Apache Kafka
>> >> Copyright ?-2011 The Apache Software Foundation.
>> >>
>> >> This product includes software developed at
>> >> The Apache Software Foundation (http://www.apache.org/).
>> >> ===
>> >>
>> >> The rest of the NOTICE file should be for *required* notices only; it
>> >> is not required to list other Apache projects.
>> >>
>> >> The NOTICE file also contains a license, that should be in LICENSE.
>> >> No mention of sbt, which is in SVN - as that is also included in the
>> >> binary release, should that be mentioned in the NOTICE file?
>> >>
>> >> > PGP release keys
>> >> > http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>> >> >
>> >> > This vote is open until Thursday, Nov 17th 12 pm
>> >> >
>> >> > Thanks,
>> >> > Neha
>> >> >
>> >>
>> >> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >>
>> >
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate ACE from the Apache Incubator

[Mattmann, Chris A (388J)]

+1 (binding) congrats!

Cheers,
Chris

On Nov 17, 2011, at 2:42 AM, Marcel Offermans wrote:

> In my opinion, ACE is ready to begin the process of graduating from the 
> Apache Incubator to a Top Level Project.
> 
> Since joining the incubator in in May 2009 we've added 4 new committers (12 
> in total now) from diverse organizations and did a release in May this year 
> to demonstrate we follow the Apache guidelines. We've shown an ability to 
> self-govern using accepted Apache practices and ACE continues to attract new 
> contributors and users.
> 
> The first step is to vote as a community, demonstrating that ACE is ready and 
> willing to graduate. Once this vote is succesful we create a board resolution 
> proposal or Charter and start a vote on the general incubator list. The full 
> process is described at 
> http://incubator.apache.org/guides/graduation.html#toplevel
> 
> The vote is open for at least 72 hours.
> 
> Greetings, Marcel
> 


++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Accumulo 1.3.5-incubating

[Billie J Rinaldi]

Please vote on releasing the following candidate as Apache Accumulo 
(incubating) version 1.3.5.  This will be the first incubator release for 
Accumulo.

This candidate has received 4 binding +1 votes (1 IPMC, 3 PPMC) and 1 
non-binding +1 vote, with no -1 votes.  We need 2 additional IPMC votes for 
release.

The PPMC vote result can be found here:
http://mail-archives.apache.org/mod_mbox/incubator-accumulo-dev/20.mbox/%3c1465679136.27503.1321560055469.javamail.r...@linzimmb04o.imo.intelink.gov%3e

The Accumulo release process is described here:
  http://incubator.apache.org/accumulo/governance/releasing.html

Tarball, checksums, signatures:
  http://people.apache.org/~ecn/accumulo-1.3.5rc6/

SVN tag:
  https://svn.apache.org/repos/asf/incubator/accumulo/tags/1.3.5rc6/

Keys:
  http://www.apache.org/dist/incubator/accumulo/KEYS

The vote will be held open for the next 72 hours.

Thanks,
Billie

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Kafka 0.7.0-incubating

[Kevan Miller]

On Nov 17, 2011, at 2:10 PM, sebb wrote:

> On 17 November 2011 16:30, Jun Rao  wrote:
>> Sebb,
>> 
>> Just to want to clarify on the source distribution. It seems there are
>> other Apache projects that release a single distribution with both source
>> code and jars. For example,
>> http://mirror.metrocast.net/apache//zookeeper/zookeeper-3.3.3/ . So, is
> 
> I don't think that's a good example to follow.
> 
>> source distribution strictly required?
> 
> In my opinion, yes.

I agree with Sebb.

--kevan

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE CLOSED] Accept Openmeetings to Apache Incubator

[David Crossley]

Welcome. I have done the first steps as explained here [1]
adding to the ReportingSchedule and a default entry to podlings.xml
The latter still needs the project description and list of mentors.

This is just to get things started, and also enables Clutch
to help guide your project. No rush.

[1] http://incubator.apache.org/clutch.html#steps

[2] http://incubator.apache.org/clutch.html#openmeetings

-David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Kafka 0.7.0-incubating

[David Crossley]

sebb wrote:
> Jun Rao wrote:
> > Sebb,
> >
> > Just to want to clarify on the source distribution. It seems there are
> > other Apache projects that release a single distribution with both source
> > code and jars. For example,
> > http://mirror.metrocast.net/apache//zookeeper/zookeeper-3.3.3/ . So, is
> 
> I don't think that's a good example to follow.
> 
> > source distribution strictly required?
> 
> In my opinion, yes.

I reckon it is too.

http://apache.org/dev/#releases
http://apache.org/dev/release.html#what

-David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Kafka 0.7.0-incubating

[Kevan Miller]

I took a look at the svn source and the binary artifact and have some 
additional comments.

1) Your svn contains a number of jar files. I don't believe that the 
LICENSE/NOTICE file properly reflects the license/notice requirements of these 
jar files. 
2) Why are these jars being stored in your svn at all?
3) Your LICENSE file only includes the ALv2 license. Yet your binary artifact 
(and your source) include artifacts with non-ALv2 licenses. For instance 
jopt-simple is MIT. All of the relevant licenses need to be included in your 
LICENSE file. You have the SCALA license in the notice file. I would expect it 
to be in the LICENSE file
4) Your NOTICE file includes lot's of "This product includes X, developed by 
X.org" Your notice file should only include notices that you are *required* to 
have. Don't include acknowledgements in your notice file just for completeness. 
Furthermore, when a notice is required, make sure it is accurate. For instance, 
ALv2 requires that you include a readable copy of the notices in the NOTICE 
file. If there isn't a NOTICE file, you should not provide a "notice". 
joda-time-1.6.jar includes a NOTICE file. It's content is:
"This product includes software developed by
Joda.org (http://www.joda.org/)."
That's what needs to be included in your NOTICE file. For differently licensed 
artifacts, you need to follow the requirements of their licenses.
BTW, it looks like hadoop and pig projects are distributing jars without 
license/notice files?
5) Your source/binary don't have a DISCLAIMER. An incubation disclaimer is 
required.

--kevan


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Kafka 0.7.0-incubating

[Chris Douglas]

Thanks Sebb and Kevan. This is helpful.

On Thu, Nov 17, 2011 at 5:41 PM, Kevan Miller  wrote:
> 1) Your svn contains a number of jar files. I don't believe that the 
> LICENSE/NOTICE file properly reflects the license/notice requirements of 
> these jar files.
> 2) Why are these jars being stored in your svn at all?
> 3) Your LICENSE file only includes the ALv2 license. Yet your binary artifact 
> (and your source) include artifacts with non-ALv2 licenses. For instance 
> jopt-simple is MIT. All of the relevant licenses need to be included in your 
> LICENSE file. You have the SCALA license in the notice file. I would expect 
> it to be in the LICENSE file

Most of the licenses I found included among/in jar files. Aggregating
licenses for all included jars in the top level LICENSE is required?

Plans to avoid distributing jars have been discussed on the dev list.
That will probably be part of a subsequent release.

A source tarball shouldn't be too difficult to produce, as long as
it's just a tarball of the release tag.

> 4) Your NOTICE file includes lot's of "This product includes X, developed by 
> X.org" Your notice file should only include notices that you are *required* 
> to have. Don't include acknowledgements in your notice file just for 
> completeness.

Just to be clear: why not?

> That's what needs to be included in your NOTICE file. For differently 
> licensed artifacts, you need to follow the requirements of their licenses.
> BTW, it looks like hadoop and pig projects are distributing jars without 
> license/notice files?

Very likely, but if we could leave that off of Kafka's critical path
that would be appreciated.

> 5) Your source/binary don't have a DISCLAIMER. An incubation disclaimer is 
> required.

http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer

Doesn't list the text for this disclaimer (used the one from RAT below)

Just to summarize this round of feedback, the contents of the NOTICE,
DISCLAIMER, and LICENSE should be as follows:

NOTICE
Apache Kafka
Copyright ?-2011 The Apache Software Foundation.

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).



DISCLAIMER

Apache Kafka is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Incubator PMC. Incubation is
required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection
of the completeness or stability of the code, it does indicate that
the project has yet to be fully endorsed by the ASF.

LICENSE



Is this correct? -C

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Kafka 0.7.0-incubating

[sebb]

On 18 November 2011 02:17, Chris Douglas  wrote:
> Thanks Sebb and Kevan. This is helpful.
>
> On Thu, Nov 17, 2011 at 5:41 PM, Kevan Miller  wrote:
>> 1) Your svn contains a number of jar files. I don't believe that the 
>> LICENSE/NOTICE file properly reflects the license/notice requirements of 
>> these jar files.
>> 2) Why are these jars being stored in your svn at all?
>> 3) Your LICENSE file only includes the ALv2 license. Yet your binary 
>> artifact (and your source) include artifacts with non-ALv2 licenses. For 
>> instance jopt-simple is MIT. All of the relevant licenses need to be 
>> included in your LICENSE file. You have the SCALA license in the notice 
>> file. I would expect it to be in the LICENSE file
>
> Most of the licenses I found included among/in jar files. Aggregating
> licenses for all included jars in the top level LICENSE is required?
>
> Plans to avoid distributing jars have been discussed on the dev list.
> That will probably be part of a subsequent release.
>
> A source tarball shouldn't be too difficult to produce, as long as
> it's just a tarball of the release tag.
>
>> 4) Your NOTICE file includes lot's of "This product includes X, developed by 
>> X.org" Your notice file should only include notices that you are *required* 
>> to have. Don't include acknowledgements in your notice file just for 
>> completeness.
>
> Just to be clear: why not?

The NOTICE file should be as short as possible, but no shorter.

>> That's what needs to be included in your NOTICE file. For differently 
>> licensed artifacts, you need to follow the requirements of their licenses.
>> BTW, it looks like hadoop and pig projects are distributing jars without 
>> license/notice files?
>
> Very likely, but if we could leave that off of Kafka's critical path
> that would be appreciated.
>
>> 5) Your source/binary don't have a DISCLAIMER. An incubation disclaimer is 
>> required.

Should also be in SVN under trunk (if not already there).

There is one on the website, which is good, but the first sentence says:

"Apache Kafka is an effort undergoing incubation at The Apache
Software Foundation (ASF), sponsored by Chris Douglas."

The sponsoring entity is normally the Incubator, sometimes another PMC.
According to podlings.xml the sponsor is the Incubator, so please fix the site.

> http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer
>
> Doesn't list the text for this disclaimer (used the one from RAT below)
>
> Just to summarize this round of feedback, the contents of the NOTICE,
> DISCLAIMER, and LICENSE should be as follows:
>
> NOTICE
> Apache Kafka
> Copyright ?-2011 The Apache Software Foundation.

The ? needs to be replaced by the initial year (or dropped if it is
2011, which appears to be the case).

> This product includes software developed at
> The Apache Software Foundation (http://www.apache.org/).
>
> 

Not exactly. The product will generally have some text which it
requires be included; it's not necessarily the whole NOTICE file.

> DISCLAIMER
>
> Apache Kafka is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Incubator PMC. Incubation is
> required of all newly accepted projects until a further review
> indicates that the infrastructure, communications, and decision making
> process have stabilized in a manner consistent with other successful
> ASF projects. While incubation status is not necessarily a reflection
> of the completeness or stability of the code, it does indicate that
> the project has yet to be fully endorsed by the ASF.
>
> LICENSE
> 
> 

Yes, it would help to prefix each distinct license text with the
license name and the included products to which it applies.

> Is this correct? -C
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Henri Yandell]

On Wed, Nov 16, 2011 at 12:36 PM, Sam Ruby  wrote:
> On Tue, Nov 15, 2011 at 11:41 PM, Noel J. Bergman  wrote:
>>
>> We are, however, recognizing that we've had growth issues of our own.  As
>> David Crossley pointed out, he made mistakes last month related to the
>> Reporting Schedule, and we continue to have issues.  The Incubator is almost
>> as big as the rest of the ASF combined.  David posted a plot chart
>> reflecting our growth: http://incubator.apache.org/history/
>
> Excellent plot chart.  As with most plot charts, the end result is a
> Rorschach test.  I'll tell you what I (personally) see in this chart:
> a failure to perform garbage collection.  My personal perspective is
> that incubation shouldn't generally take more than a year.  That
> doesn't mean that there won't be exceptions, and in a few rare cases,
> some that go well beyond that arbitrary time limit, but the point is
> that those should be the exception rather than the rule.

Now that time is freeing up a tiny bit, I need to document a thread
from August that would put pressure on projects who haven't done their
IP handling. I'm less worried about a podling who haven't graduated
after 12 months and more worried about a podling who haven't managed
to get their CLAs right within 3 months. We still have far too many
podlings who haven't signed off on that (first) part of their
incubation.

So +1 in sentiment, but a different focus.

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Latest copyright sign-off status [Was: Podlings needing copyright sign-off]

[Henri Yandell]

On Wed, Nov 16, 2011 at 12:16 AM, Robert Burrell Donkin
 wrote:
> On Wed, Nov 16, 2011 at 8:14 AM, Robert Burrell Donkin
>  wrote:
>> On Fri, Nov 11, 2011 at 12:14 AM, Henri Yandell  wrote:
>>
>> 
>>
>>> 2009-02-09  kato
>>
>> I'm comfortable that this is safe enough copyright-wise. I would
>> prefer the podling community to do the checking themselves but it's
>> stalled until the JCR is sorted out.
>
> There is occasional interest in the codebase but work by the original
> team seems to be halted until standards issues are sorted out.
>
> Maybe we need a "stalled" status, perhaps allowing new contributors to
> boot-strap

You're a mentor, so if you're comfortable that the copyright rights
have been licensed (or there's nothing to license) then go ahead and
update the status page :)

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Latest copyright sign-off status [Was: Podlings needing copyright sign-off]

[Henri Yandell]

You should define 'very small' for Joao and work with legal-discuss
and the Incubator PMC to decide if the item can be signed off or not.

[me=bean counter who points to a field not being signed off :) ]

Hen

On Wed, Nov 16, 2011 at 4:53 AM, Jörn Kottmann  wrote:
> Hello,
>
> can OpenNLP be signed-off?
>
> OpenNLP was hosted for some years over at SourceForge before
> we moved to the Apache Incubator.
> Over at SourceForge a couple of people worked on it.
>
> Most SourceForge committers are also committers here, they
> all signed an ICLA, these are:
>
> - Thilo Goetz
> - Jörn Kottmann
> - Jason Baldridge
> - James Kosin
> - William Silvia
> - Tom Morton
>
> The following people didn't maintain their commit rights:
>
> - Gann Bierner
> - Eric Friedman
> - Joao Cavalcanti
>
> Of these three people Gann Bierner and Eric Friedman signed
> the software grant. Joao Cavalcanti didn't because the amount of his
> contribution
> was very small.
>
> Is there anything else what we need to do to get the copyright item signed
> off?
>
> Thanks,
> Jörn
>
> On 11/11/11 1:14 AM, Henri Yandell wrote:
>>
>> Updating this, half of the items without sign-off in July are now
>> signed off. I've updated the list below (though I've not yet added new
>> PMCs since June).
>>
>> Here's the previous email:
>>
>> On Thu, Jul 7, 2011 at 7:20 PM, Henri Yandell  wrote:
>>>
>>> Here's a list of the projects in the Incubator who need to sign off
>>> their copyright item; namely:
>>>
>>> "Check and make sure that the papers that transfer rights to the ASF
>>> been received.
>>>  It is only necessary to transfer rights for the package, the core
>>> code, and any
>>>  new code produced by the project.  "
>>
>> Here's the latest list:
>>
>> 2008-09-29  olio
>> 2009-02-09  kato
>> 2009-02-13  stonehenge
>> 2009-05-08  ace
>> 2009-05-13  socialsite
>> 2009-06-25  wink
>> 2009-11-08  hise
>> 2010-01-27  manifoldcf
>> 2010-05-19  amber
>> 2010-05-24  zetacomponents
>> 2010-09-05  nuvem
>> 2010-11-02  celix
>> 2010-11-12  kitty
>> 2010-11-24  stanbol
>> 2010-12-02  jena
>> 2010-12-02  opennlp
>> 2011-06-13  openofficeorg
>>
>> Hen
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org