Re: [VOTE] RAT to enter incubator

[Bertrand Delacretaz]

> [X ] +1 Allow RAT to enter incubator, sponsored by IPMC

-Bertrand

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] RAT to enter incubator

[Gilles Scokart]

+1 (non-binding)

Gilles

2007/10/30, Robert Burrell Donkin <[EMAIL PROTECTED]>:
>
> i'd like to propose that the IPMC sponsors the entry of RAT into the
> incubator
>
> - robert
>
>
> --8<-
> [ ] +1 Allow RAT to enter incubator, sponsored by IPMC
> [ ] +0
> [ ] -0
> [ ] -1 Do no allow RAT to enter incubator
>
> ---
>
> Rat Proposal
> ==
> Abstract
> 
> RAT is comprehension and auditing for distributions and source code.
>
> Proposal
> --
> RAT will provide a focus for components, applications and integration
> tools for the comprehension and audit of distributions and source
> code. It will collect data and meta-data as required. It will create
> suitable schemas for this data and meta-data as required.
>
> Background
> --
> RAT began as an attempt to automate the technical part of reviewing
> releases in the incubator. Following requests for access from release
> managers, RAT was developed as an open source project under the Apache
> License 2.0.
>
> Rationale
> ---
> Reviewing releases for compliance with Apache technical criteria and
> policies is time consuming. The Incubator requires that all releases
> are reviewed. Though small mistakes are common, this process typically
> adds only a little value. It is common for candidates to be presented
> with small but significant defects which then must be fixed and the
> candidate represented. Significant energy and good will is wasted by
> this process.
>
> This is unnecessary. Given effort, these technical criteria are
> capable of automation.
>
> Automated continuous checking of the source would allow the Incubator
> PMC to be alerted promptly to potential issues. Integration with build
> tools (such as Apache Ant and Apache Maven) would allow releases to be
> checked automatically and continuously.
>
> Initial Goals
> --
> * Read standard license meta-data for documents without license
> headers
> * Improved RAT reporting
> * RAT source reporting for major build tools
> * Continuous RAT
> * RAT analytics: using meta-data to verify rules
>   o Apache third party documents policy analysis
>   o license compatibility analysis
> * Discordia integration to allow distributed binaries to be recognised
> * RAT analytic integration for major build tools
> * Improved recursive RAT scripts for better analysis of release
> with many distributables
>
> Current Status
> ===
> Meritocracy
> --
> I'm very happy to move from a solo development model towards a
> collective one as more active developers are recruited.
>
> Community
> --
> The RAT community needs to be developed. Having RAT here at Apache
> will hopefully encourage release managers to take a more active role
> in developing RAT.
>
> Core Developers
> --
> It has been developed principally by myself but with significant
> contributions of small amounts of code from other Apache members and
> committers.
>
> Alignment
> 
> RAT has found itself becoming a standard part of the Apache release
> infrastructure. The Incubator needs fully featured release tools. It
> makes sense to bring the project here.
>
> Known Risks
> ==
> Orphaned Projects
> -
> This is a project with a set of definite goals aimed at serving the
> wider Apache community. There may well come a time when the coding is
> actually finished. It has a small set of developers who all have many
> other calls on their time. The target user audience is relatively
> small. So, this risk is real.
>
> I think that it's clear that something similar to RAT is required. So,
> unless another better product is developed, time will be found to push
> RAT forward. Even if one day, RAT is orphaned then it will have done
> it's job.
>
> Inexperience With Open Source
> -
> The contributors are Apache members or experienced Apache committers.
>
> Reliance On Salaried Developers
> 
> I know of no one who's paid to work on RAT.
>
> Relationships with Other Apache Products
> --
> RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting
> plugin. Analytic plugins for Ant and Maven will be developed. There
> are overlaps with Tika and there has been some talk of collaboration.
> The discordia lab will likely be used for license and artifact
> meta-data. RAT may integrate with Gump for continuous code scanning.
>
> Initial Source
> 
> * [WWW] http://code.google.com/p/arat/source
> * [WWW] http://mojo.codehaus.org/rat-maven-plugin
>
> External Depen

Re: [VOTE] RAT to enter incubator

[Felix Meschberger]

+1 (non binding)

Regards
Felix

Am Dienstag, den 30.10.2007, 22:03 + schrieb Robert Burrell Donkin:
> i'd like to propose that the IPMC sponsors the entry of RAT into the incubator
> 
> - robert
> 
> --8<-
> [ ] +1 Allow RAT to enter incubator, sponsored by IPMC
> [ ] +0
> [ ] -0
> [ ] -1 Do no allow RAT to enter incubator
> ---
> 
> Rat Proposal
> ...


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Java Jabber Server

[Bernd Fondermann]

On 10/30/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
> Petar Tahchiev wrote:
> > Hi guys,
> >
> > today I was looking for a Jabber server implemented entirely in Java,
> > and the only results
> > that I got was this:
> >
> > ---(free)---
> > http://www.codecobra.com/chime/
> > http://www.open-im.net/
> > http://www.tigase.org/
> > http://www.igniterealtime.org/projects/openfire/index.jsp
> >
> > (commercial)---
> > http://www.adobe.com/special/antepo/?products.opnserver (no longer
> > available - bought by Adobe)
> >
> > Does anyone (besides me) think that we can build something better?
> >
> > Waiting for your suggestions.
> >
> I also like to contribute to this , if you are going to implement.
> sometimes ago I wanted to build a Jabber (XMPP) implementation based
> Stax implementation. May be this is a good chance for that.

I'd like to invite you to contribute to Apache Lab Vysper. I had to
implement (reinvent) a XML streaming parser, because those available
didn't quite fit (for various reasons). But that's probably due to my
lack of expertise in this field. There is still high need for a 'real'
XML parser. So, if you have some cycles to spare, help out there.

Thanks,

  Bernd

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Java Jabber Server

[Bernd Fondermann]

On 10/30/07, Petar Tahchiev <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> today I was looking for a Jabber server implemented entirely in Java,
> and the only results
> that I got was this:
>
> ---(free)---
> http://www.codecobra.com/chime/
> http://www.open-im.net/
> http://www.tigase.org/
> http://www.igniterealtime.org/projects/openfire/index.jsp
>
> (commercial)---
> http://www.adobe.com/special/antepo/?products.opnserver (no longer
> available - bought by Adobe)
>
> Does anyone (besides me) think that we can build something better?
>
> Waiting for your suggestions.

Sure. Definitively. :-)
I am working on a Jabber server in an Apache lab called Vysper
(pronounced: "whisper").
See http://labs.apache.org/labs.html and
http://svn.apache.org/repos/asf/labs/vysper/

Any contributions more than welcome!
Discussion should happen on [EMAIL PROTECTED]
And eventually, if the project gains track, we could aim for incubation.

  Bernd

>
> --
> Regards, Petar!
> Karlovo, Bulgaria.
>
> EOOXML objections
> http://www.grokdoc.net/index.php/EOOXML_objections
>
> Public PGP Key at:
> http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53B761500F9
> Key Fingerprint: AA16 8004 AADD 9C76 EF5B  4210 1A15 B53B 7615 00F9
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] RAT to enter incubator

[Rahul Akolkar]

On 10/30/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
> i'd like to propose that the IPMC sponsors the entry of RAT into the incubator
>


+1 (non-binding)

-Rahul


> - robert
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] RAT to enter incubator

[Stefan Bodewig]

On Tue, 30 Oct 2007, Robert Burrell Donkin
<[EMAIL PROTECTED]> wrote:
> i'd like to propose that the IPMC sponsors the entry of RAT into the
> incubator

+1

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Diversity requirement

[William A. Rowe, Jr.]

Matthieu Riou wrote:

On 10/30/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote:


On Oct 30, 2007, at 11:58 PM, Matthieu Riou wrote:


"there are at least 3 legally independent committers and there is no single
company or entity that is vital to the success of the project"

What does legally independent mean?  Not paid by the same company to
work on a project?  I'd be ok with that.


My interpretation is not paid by anybody to work on the project. Could be
the wrong interpretation though, but then the phrasing is maybe not that
clear. They should be described as being independent from *each other*.


:)  Yes you read too much into it, independent of one another (not partners,
employees etc of the same organization, other than the ASF itself).

This would /include/ a pending assemblage of people, so if five folks get
together and plan to launch an incubating project, and kick off a company
from that together, they do need to ensure they have at least two independent
individuals join that project who aren't one of that group at graduation.

Strange things will happen as projects evolve, of course.  That's not the
incubator's concern once they had graduated.  But like you point out, folks
who learn to think and contribute critically to a project will keep doing so
even when they work together at the same company.

We don't know enough about the corporate culture of an existing group of folk
to say they can speak independently of their employer, and honestly, we don't
care as long as there is sufficient diversity on the project in the first place.

Bill

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Diversity requirement

[Matthieu Riou]

On 10/30/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
>
>
> On Oct 30, 2007, at 11:58 PM, Matthieu Riou wrote:
>
> > "there are at least 3 legally independent committers and there is no
> > single
> > company or entity that is vital to the success of the project"
>
> What does legally independent mean?  Not paid by the same company to
> work on a project?  I'd be ok with that.


My interpretation is not paid by anybody to work on the project. Could be
the wrong interpretation though, but then the phrasing is maybe not that
clear. They should be described as being independent from *each other*.

Matthieu

-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Diversity requirement

[Matt Hogstrom]

On Oct 30, 2007, at 11:16 PM, Erik Abele wrote:

Well, usually our voting guidelines require three +1 etc. so for  
example having only three committers from a single company makes  
voting kind of pointless :-)




Perhaps.  I know on Geronimo, and i suspect other projects as well,  
that there have been many times that people that worked for the same  
company voted differently so I don't think its totally pointless but I  
understand the concern.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Diversity requirement

[Matt Hogstrom]

On Oct 30, 2007, at 11:58 PM, Matthieu Riou wrote:

"there are at least 3 legally independent committers and there is no  
single

company or entity that is vital to the success of the project"


What does legally independent mean?  Not paid by the same company to  
work on a project?  I'd be ok with that.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Diversity requirement

[Matthieu Riou]

On 10/30/07, Erik Abele <[EMAIL PROTECTED]> wrote:
>
> 
> So the absolute minimum should be three committers with at least two
> different entities behind them (e.g. two companies, or at least one
> independent, etc.) - OTOH I think the current rules outlined at [1]
> are perfectly fine.


I'd be fine with that as well but that's not what the policy says [1]:

"there are at least 3 legally independent committers and there is no single
company or entity that is vital to the success of the project"

IMHO 3 legally independent committers can be very hard requirement,
especially for small sized project.

Cheers,
Matthieu

[1]
http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator

Re: Java Jabber Server

[Jason van Zyl]

I have the port to Plexus in a tree and I'm sure alag would be fine  
with it coming along here.


On 30 Oct 07, at 8:43 AM 30 Oct 07, J Aaron Farr wrote:


"Petar Tahchiev" <[EMAIL PROTECTED]> writes:


Hi guys,

today I was looking for a Jabber server implemented entirely in Java,
and the only results
that I got was this:

---(free)---
http://www.codecobra.com/chime/
http://www.open-im.net/


OpenIM was originally developed using Apache Avalon containers and now
uses Plexus (which is entering incubation).  The developer, alag, was
a regular on the mailing lists at the time.  I'm not sure how active
the project is today (looks like it's moved to Codehaus).  It's under
the MIT license.

And while I haven't used this particular feature of ActiveMQ, it does
advertise XMPP support:

 http://activemq.apache.org/xmpp.html

--
 J Aaron Farr jadetower.com[US] +1 724-964-4515
   馮傑仁  cubiclemuses.com [HK] +852 8123-7905

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
--




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] RAT to enter incubator

[Niall Pemberton]

+1

Niall

On Oct 30, 2007 10:03 PM, Robert Burrell Donkin
<[EMAIL PROTECTED]> wrote:
> i'd like to propose that the IPMC sponsors the entry of RAT into the incubator
>
> - robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Diversity requirement

[Erik Abele]

On 31.10.2007, at 03:54, Matt Hogstrom wrote:

I didn't see a thread get started on this topic yet but I've been  
mulling this over for a bit so perhaps we can continue the  
discussion in this thread?


I'm not sure that there should be a hard requirement for 3, 5 or n  
unique committers.  As a guideline I think three is a good working  
number but the more important issue is the Incubator PMC's  
understanding of the community as they've conducted themselves and  
the iPMC's collective view on the project's viability going  
forward


Well, usually our voting guidelines require three +1 etc. so for  
example having only three committers from a single company makes  
voting kind of pointless :-)


Or at least it creates the impression for other contributors that the  
project is solely led by that company...


So the absolute minimum should be three committers with at least two  
different entities behind them (e.g. two companies, or at least one  
independent, etc.) - OTOH I think the current rules outlined at [1]  
are perfectly fine.



...
Anyway, with my recent changes it caused me to think more about the  
people than a set of requirements.  IMO Jim and Noel expressing  
their concern and causing this discussion and deeper inspection of  
the project is the right process and makes a lot of sense.


Absolutely but IMHO we simply need some rules/requirements/guidelines  
to set a suitable framework.


Cheers,
Erik

[1] http://incubator.apache.org/guides/graduation.html#community

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Diversity requirement

[Matt Hogstrom]

I didn't see a thread get started on this topic yet but I've been  
mulling this over for a bit so perhaps we can continue the discussion  
in this thread?


I'm not sure that there should be a hard requirement for 3, 5 or n  
unique committers.  As a guideline I think three is a good working  
number but the more important issue is the Incubator PMC's  
understanding of the community as they've conducted themselves and the  
iPMC's collective view on the project's viability going forward.  This  
is an ASF wide issue but the Incubator is the gateway for healthy  
communities to be brought into the ASF so my context for this  
discussion is the Incubator.


The reason I make this comment is I recently changed roles at my  
company and will be investing less time in Geronimo than I was  
previously.  This doesn't change my desire to participate and work on  
the project, it changes the amount of time I have to participate :)


For the record, I work for IBM but have no stake in Tuscany one way or  
the other from an IBM perspective (heh, my new role is playing with  
hardware and virtualization technology) and generally I tend to be  
more critical of IBM heavy projects so I can do my best to have a  
balanced view (perhaps even leaning  a little against IBM).


With this recent change in my role it occurred to me that my  
affiliation with the Geronimo is more about my personal interest in  
the project as opposed to it being part of a job requirement.   
Certainly not all committers are in that same position so we can't  
simply assume that everyone's interest in a project is a personal  
passion either. The point being that our confidence in a project  
should be based on the individuals and their behaviours rather than a  
hard and fast affiliation requirement; which does change over time.


As far as Tuscany is concerned, the community has been chugging for  
quite some time and it appears that they are not losing steam (sure  
they can later, but so can every project when its goals are met).   
They've weathered some challenging storms (a fork of the code base and  
community normalization issues) and yet despite the challenges they  
are still making progress.  I think they are in pretty good shape and  
I respect the opinion of the mentors which seem to indicate they are  
satisfied as well.


My point is that we have sufficient evidence that the community  
conducts itself well, can weather the storms and has a growing base of  
interest. I think once they complete their resolution text (and with  
their new committers ta boot) they should probably bring their vote  
forward again.


Anyway, with my recent changes it caused me to think more about the  
people than a set of requirements.  IMO Jim and Noel expressing their  
concern and causing this discussion and deeper inspection of the  
project is the right process and makes a lot of sense.


Just my $0.02


On Oct 23, 2007, at 2:22 AM, Bertrand Delacretaz wrote:

Agred, community diversity is an ASF-wide issue, not only an  
Incubator concern.


But, as there have been some constructive discussions about it here
recently, we might want to get the ball rolling by submitting some
concrete ideas to the ASF membership?

If we agree on that, I'll start a thread here to discuss a set of
guidelines about how we define and handle diversity.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] RAT to enter incubator

[Yoav Shapira]

Hey,

On Oct 30, 2007 6:03 PM, Robert Burrell Donkin
<[EMAIL PROTECTED]> wrote:
> i'd like to propose that the IPMC sponsors the entry of RAT into the incubator
>
> - robert
>
> --8<-
> [ X ] +1 Allow RAT to enter incubator, sponsored by IPMC

Gladly.

Yoav

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] RAT to enter incubator

[Craig L Russell]

+1

you go, rat-man.

Craig

On Oct 30, 2007, at 3:03 PM, Robert Burrell Donkin wrote:

i'd like to propose that the IPMC sponsors the entry of RAT into  
the incubator


- robert



Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] RAT to enter incubator

[Matt Hogstrom]

+1

On Oct 30, 2007, at 6:03 PM, Robert Burrell Donkin wrote:

i'd like to propose that the IPMC sponsors the entry of RAT into the  
incubator


- robert

--8 
< 
-

[ ] +1 Allow RAT to enter incubator, sponsored by IPMC
[ ] +0
[ ] -0
[ ] -1 Do no allow RAT to enter incubator
---



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] RAT to enter incubator

[Kevan Miller]

+1--kevan

On 10/30/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
>
> i'd like to propose that the IPMC sponsors the entry of RAT into the
> incubator
>
> - robert
>
>
> --8<-
> [ ] +1 Allow RAT to enter incubator, sponsored by IPMC
> [ ] +0
> [ ] -0
> [ ] -1 Do no allow RAT to enter incubator
>
> ---
>

Re: [Proposal Draft]BlueSky-Wish to ADD

[Carl Trieloff]

J Aaron Farr wrote:

"Ting Peng" <[EMAIL PROTECTED]> writes:

  

Now, we are going to move our project BlueSky (Blue Sky Distance
Collaboration System) to Apache Incubator for future development...



你好

The proposal is interesting, but I have a few concerns.

I can't get to http://202.117.16.176/ from Hong Kong, so I cannot see
the code or website.  

  

link also does not work from US.
Carl.

Re: [Proposal Draft]BlueSky-Wish to ADD

[J Aaron Farr]

"Ting Peng" <[EMAIL PROTECTED]> writes:

> Now, we are going to move our project BlueSky (Blue Sky Distance
> Collaboration System) to Apache Incubator for future development...

你好

The proposal is interesting, but I have a few concerns.

I can't get to http://202.117.16.176/ from Hong Kong, so I cannot see
the code or website.  

Is the code already under an open source license?

How did the team grow from 2 to 20 developers?  Are these developers
paid to work in this project?

The project seems very interesting, but I'm concerned that it's very
different from the other Apache software.  This will make it difficult
to to get help from other Apache committers.

That said, if there's enough interest, I'll do what I can to help.

-- 
  J Aaron Farr jadetower.com[US] +1 724-964-4515 
馮傑仁  cubiclemuses.com [HK] +852 8123-7905  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] RAT to enter incubator

[Martijn Dashorst]

+1, binding (yeah!)

Martijn

On 10/30/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
> i'd like to propose that the IPMC sponsors the entry of RAT into the incubator
>
> - robert
>
> --8<-
> [ ] +1 Allow RAT to enter incubator, sponsored by IPMC
> [ ] +0
> [ ] -0
> [ ] -1 Do no allow RAT to enter incubator
> ---
>
> Rat Proposal
> ==
> Abstract
> 
> RAT is comprehension and auditing for distributions and source code.
>
> Proposal
> --
> RAT will provide a focus for components, applications and integration
> tools for the comprehension and audit of distributions and source
> code. It will collect data and meta-data as required. It will create
> suitable schemas for this data and meta-data as required.
>
> Background
> --
> RAT began as an attempt to automate the technical part of reviewing
> releases in the incubator. Following requests for access from release
> managers, RAT was developed as an open source project under the Apache
> License 2.0.
>
> Rationale
> ---
> Reviewing releases for compliance with Apache technical criteria and
> policies is time consuming. The Incubator requires that all releases
> are reviewed. Though small mistakes are common, this process typically
> adds only a little value. It is common for candidates to be presented
> with small but significant defects which then must be fixed and the
> candidate represented. Significant energy and good will is wasted by
> this process.
>
> This is unnecessary. Given effort, these technical criteria are
> capable of automation.
>
> Automated continuous checking of the source would allow the Incubator
> PMC to be alerted promptly to potential issues. Integration with build
> tools (such as Apache Ant and Apache Maven) would allow releases to be
> checked automatically and continuously.
>
> Initial Goals
> --
> * Read standard license meta-data for documents without license headers
> * Improved RAT reporting
> * RAT source reporting for major build tools
> * Continuous RAT
> * RAT analytics: using meta-data to verify rules
>   o Apache third party documents policy analysis
>   o license compatibility analysis
> * Discordia integration to allow distributed binaries to be recognised
> * RAT analytic integration for major build tools
> * Improved recursive RAT scripts for better analysis of release
> with many distributables
>
> Current Status
> ===
> Meritocracy
> --
> I'm very happy to move from a solo development model towards a
> collective one as more active developers are recruited.
>
> Community
> --
> The RAT community needs to be developed. Having RAT here at Apache
> will hopefully encourage release managers to take a more active role
> in developing RAT.
>
> Core Developers
> --
> It has been developed principally by myself but with significant
> contributions of small amounts of code from other Apache members and
> committers.
>
> Alignment
> 
> RAT has found itself becoming a standard part of the Apache release
> infrastructure. The Incubator needs fully featured release tools. It
> makes sense to bring the project here.
>
> Known Risks
> ==
> Orphaned Projects
> -
> This is a project with a set of definite goals aimed at serving the
> wider Apache community. There may well come a time when the coding is
> actually finished. It has a small set of developers who all have many
> other calls on their time. The target user audience is relatively
> small. So, this risk is real.
>
> I think that it's clear that something similar to RAT is required. So,
> unless another better product is developed, time will be found to push
> RAT forward. Even if one day, RAT is orphaned then it will have done
> it's job.
>
> Inexperience With Open Source
> -
> The contributors are Apache members or experienced Apache committers.
>
> Reliance On Salaried Developers
> 
> I know of no one who's paid to work on RAT.
>
> Relationships with Other Apache Products
> --
> RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting
> plugin. Analytic plugins for Ant and Maven will be developed. There
> are overlaps with Tika and there has been some talk of collaboration.
> The discordia lab will likely be used for license and artifact
> meta-data. RAT may integrate with Gump for continuous code scanning.
>
> Initial Source
> 
> * [WWW] http://code.google.com/p/arat/source
> * [WWW] http://mojo.codehaus.org/rat-maven-plugin
>
> External Depe

Re: [VOTE] RAT to enter incubator

[Richard S. Hall]

+1

-> richard

Robert Burrell Donkin wrote:

i'd like to propose that the IPMC sponsors the entry of RAT into the incubator

- robert

--8<-
[ ] +1 Allow RAT to enter incubator, sponsored by IPMC
[ ] +0
[ ] -0
[ ] -1 Do no allow RAT to enter incubator
---

Rat Proposal
==
Abstract

RAT is comprehension and auditing for distributions and source code.

Proposal
--
RAT will provide a focus for components, applications and integration
tools for the comprehension and audit of distributions and source
code. It will collect data and meta-data as required. It will create
suitable schemas for this data and meta-data as required.

Background
--
RAT began as an attempt to automate the technical part of reviewing
releases in the incubator. Following requests for access from release
managers, RAT was developed as an open source project under the Apache
License 2.0.

Rationale
---
Reviewing releases for compliance with Apache technical criteria and
policies is time consuming. The Incubator requires that all releases
are reviewed. Though small mistakes are common, this process typically
adds only a little value. It is common for candidates to be presented
with small but significant defects which then must be fixed and the
candidate represented. Significant energy and good will is wasted by
this process.

This is unnecessary. Given effort, these technical criteria are
capable of automation.

Automated continuous checking of the source would allow the Incubator
PMC to be alerted promptly to potential issues. Integration with build
tools (such as Apache Ant and Apache Maven) would allow releases to be
checked automatically and continuously.

Initial Goals
--
* Read standard license meta-data for documents without license headers
* Improved RAT reporting
* RAT source reporting for major build tools
* Continuous RAT
* RAT analytics: using meta-data to verify rules
  o Apache third party documents policy analysis
  o license compatibility analysis
* Discordia integration to allow distributed binaries to be recognised
* RAT analytic integration for major build tools
* Improved recursive RAT scripts for better analysis of release
with many distributables

Current Status
===
Meritocracy
--
I'm very happy to move from a solo development model towards a
collective one as more active developers are recruited.

Community
--
The RAT community needs to be developed. Having RAT here at Apache
will hopefully encourage release managers to take a more active role
in developing RAT.

Core Developers
--
It has been developed principally by myself but with significant
contributions of small amounts of code from other Apache members and
committers.

Alignment

RAT has found itself becoming a standard part of the Apache release
infrastructure. The Incubator needs fully featured release tools. It
makes sense to bring the project here.

Known Risks
==
Orphaned Projects
-
This is a project with a set of definite goals aimed at serving the
wider Apache community. There may well come a time when the coding is
actually finished. It has a small set of developers who all have many
other calls on their time. The target user audience is relatively
small. So, this risk is real.

I think that it's clear that something similar to RAT is required. So,
unless another better product is developed, time will be found to push
RAT forward. Even if one day, RAT is orphaned then it will have done
it's job.

Inexperience With Open Source
-
The contributors are Apache members or experienced Apache committers.

Reliance On Salaried Developers

I know of no one who's paid to work on RAT.

Relationships with Other Apache Products
--
RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting
plugin. Analytic plugins for Ant and Maven will be developed. There
are overlaps with Tika and there has been some talk of collaboration.
The discordia lab will likely be used for license and artifact
meta-data. RAT may integrate with Gump for continuous code scanning.

Initial Source

* [WWW] http://code.google.com/p/arat/source
* [WWW] http://mojo.codehaus.org/rat-maven-plugin

External Dependencies

Compliant with current Apache policy.

Cryptography
-
Required to check signatures.

Required Resources

Mailing lists:
* rat-private
* rat-dev
* rat-commits
Subvers

Re: [VOTE] RAT to enter incubator

[Thilo Goetz]

+1 (non-binding)

--Thilo

Robert Burrell Donkin wrote:
> i'd like to propose that the IPMC sponsors the entry of RAT into the incubator
> 
> - robert
> 
> --8<-
> [ ] +1 Allow RAT to enter incubator, sponsored by IPMC
> [ ] +0
> [ ] -0
> [ ] -1 Do no allow RAT to enter incubator
> ---
> 
> Rat Proposal
> ==
> Abstract
> 
> RAT is comprehension and auditing for distributions and source code.
> 
> Proposal
> --
> RAT will provide a focus for components, applications and integration
> tools for the comprehension and audit of distributions and source
> code. It will collect data and meta-data as required. It will create
> suitable schemas for this data and meta-data as required.
> 
> Background
> --
> RAT began as an attempt to automate the technical part of reviewing
> releases in the incubator. Following requests for access from release
> managers, RAT was developed as an open source project under the Apache
> License 2.0.
> 
> Rationale
> ---
> Reviewing releases for compliance with Apache technical criteria and
> policies is time consuming. The Incubator requires that all releases
> are reviewed. Though small mistakes are common, this process typically
> adds only a little value. It is common for candidates to be presented
> with small but significant defects which then must be fixed and the
> candidate represented. Significant energy and good will is wasted by
> this process.
> 
> This is unnecessary. Given effort, these technical criteria are
> capable of automation.
> 
> Automated continuous checking of the source would allow the Incubator
> PMC to be alerted promptly to potential issues. Integration with build
> tools (such as Apache Ant and Apache Maven) would allow releases to be
> checked automatically and continuously.
> 
> Initial Goals
> --
> * Read standard license meta-data for documents without license headers
> * Improved RAT reporting
> * RAT source reporting for major build tools
> * Continuous RAT
> * RAT analytics: using meta-data to verify rules
>   o Apache third party documents policy analysis
>   o license compatibility analysis
> * Discordia integration to allow distributed binaries to be recognised
> * RAT analytic integration for major build tools
> * Improved recursive RAT scripts for better analysis of release
> with many distributables
> 
> Current Status
> ===
> Meritocracy
> --
> I'm very happy to move from a solo development model towards a
> collective one as more active developers are recruited.
> 
> Community
> --
> The RAT community needs to be developed. Having RAT here at Apache
> will hopefully encourage release managers to take a more active role
> in developing RAT.
> 
> Core Developers
> --
> It has been developed principally by myself but with significant
> contributions of small amounts of code from other Apache members and
> committers.
> 
> Alignment
> 
> RAT has found itself becoming a standard part of the Apache release
> infrastructure. The Incubator needs fully featured release tools. It
> makes sense to bring the project here.
> 
> Known Risks
> ==
> Orphaned Projects
> -
> This is a project with a set of definite goals aimed at serving the
> wider Apache community. There may well come a time when the coding is
> actually finished. It has a small set of developers who all have many
> other calls on their time. The target user audience is relatively
> small. So, this risk is real.
> 
> I think that it's clear that something similar to RAT is required. So,
> unless another better product is developed, time will be found to push
> RAT forward. Even if one day, RAT is orphaned then it will have done
> it's job.
> 
> Inexperience With Open Source
> -
> The contributors are Apache members or experienced Apache committers.
> 
> Reliance On Salaried Developers
> 
> I know of no one who's paid to work on RAT.
> 
> Relationships with Other Apache Products
> --
> RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting
> plugin. Analytic plugins for Ant and Maven will be developed. There
> are overlaps with Tika and there has been some talk of collaboration.
> The discordia lab will likely be used for license and artifact
> meta-data. RAT may integrate with Gump for continuous code scanning.
> 
> Initial Source
> 
> * [WWW] http://code.google.com/p/arat/source
> * [WWW] http://mojo.codehaus.org/rat-maven-plugin
> 
> External Dependencies
> -

Re: [VOTE] RAT to enter incubator

[Matthieu Riou]

On 10/30/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
>
> i'd like to propose that the IPMC sponsors the entry of RAT into the
> incubator


A huge +1.

Matthieu

Re: [VOTE] Accept project Buildr for incubation

[Brett Porter]

+1

On 30/10/2007, Matthieu Riou <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Following up on the proposal discussed at [1] I'd like to call for a vote to
> incubate Buildr. Buildr is a simple and intuitive build system for Java
> projects written in Ruby (and based on Rake), please see the complete
> proposal text at [2] or at the end of this e-mail.
>
> Also we're missing one more mentor so if someone could volunteer, that would
> really be great.
>
> Please vote on accepting Buildr into the Apache Incubator. This vote will
> run until Thursday November 1st at 3pm PST.
>
> [ ] +1 Accept Buildr project for incubation
> [ ] 0 Don't care
> [ ] -1 Reject for the following reason :
>
> Thanks!
> Matthieu
>
> [1] 
> http://mail-archives.apache.org/mod_mbox/incubator-general/200710.mbox/[EMAIL 
> PROTECTED]
>
> [2] http://wiki.apache.org/incubator/BuildrProposal
>
> ---
>
> = Abstract =
>
> Buildr is a simple and intuitive build system for Java projects.
>
> = Proposal =
>
> Buildr is a build system for Java applications. We wanted something that's
> simple and intuitive to use, so we only need to tell it what to do, and it
> takes care of the rest. But also something we can easily extend for those
> one-off tasks, with a language that's a joy to use. And of course, we wanted
> it to be fast, reliable and have outstanding dependency management.
>
> Here's what we got:
>
> * A simple way to specify projects, and build large projects out of
> smaller sub-projects.
> * Pre-canned tasks that require the least amount of configuration,
> keeping the build script DRY and simple.
> * Compiling, copying and filtering resources, JUnit/TestNG test cases,
> APT source code generation, Javadoc and more.
> * A dependency mechanism that only build that which changed since the
> last release.
> * Buildr uses the same file layout, artifact specifications, local and
> remote repositories as Maven 2.
> * All your Ant tasks belong to us! Anything you can do with Ant, you can
> do with Buildr.
> * Buildr is Ruby all the way down. No one-off task is too demanding when
> you write code using variables, functions and objects.
> * Simple way to upgrade to new versions.
> * Did we mention fast?
>
> = Background =
>
> Buildr is developed using the Ruby language and is layered on top of Rake, a
> popular build program for Ruby that provides all the task and task
> dependency infrastructure. It also relies on AntWrap to allow the reuse of
> all existing Ant tasks.
>
> = Rationale =
>
> Buildr's initial focus was to be layered on top of a powerful scripting
> language. It's an internal DSL and therefore enjoys a lot of ease of use and
> extensibility. It's also declarative, which gives scripts expressiveness
> (they're easy to read). And there's no XML!
>
> We believe bringing Buildr at Apache is a good way to expand even more the
> build tool space, attract more committers and users to Buildr and have
> people start playing with the Ruby language, both within and outside the
> foundation.
>
> = Current Status =
>
> == Meritocracy ==
>
> Buildr has been mostly developed by Assaf Arkin but others have contributed
> either directly or through patches. In addition to contributed patches, work
> on Scala and JRuby is done by community members, and we're working to
> cultivate that and add more committers.
>
> == Community ==
>
> A community of standard users but also power users is building around Buildr
> and several people are using it in all sort of different projects. Currently
> the discussion group has 86 members, more statistics available at
> http://groups.google.com/group/buildr-talk?lnk=srg
>
> == Core Developers ==
>
> Core developers are mostly from a single organization but more and more
> power users are contributing patches and trying to extend Buildr. Also
> current core developers are very experienced in open source and already
> follow the Apache ways.
>
> == Alignment ==
>
> Buildr is in line with the existing strong culture of build tools at Apache
> (Ant, Maven, Ivy, ...). It already relies on Maven2 repositories and follows
> most of its project structure conventions. It allows reuse of Ant tasks. Not
> to mention that other Apache projects could use it for their build (as ODE
> already does).
>
> = Known Risks =
>
> == Orphaned Projects ==
>
> Buildr core development is still very much dependent on Assaf but more and
> more people are getting familiar with the way Buildr works and its
> intricacies. So we're aware of the problem but also confident that we're on
> the right track as more and more people get involved.
>
> == Inexperience with Open Source ==
>
> Many committers have experience working on open source projects. Three of
> them are Apache committers.
>
> == Reliance on Salaried Developers ==
>
> Buildr is part of the committers job but is far from being the main company
> focus. So it's part working time and part personal ti

Re: [VOTE] RAT to enter incubator

[Brett Porter]

+1

On 31/10/2007, Luciano Resende <[EMAIL PROTECTED]> wrote:
> +1 (non-binding)
>
> On 10/30/07, Niklas Gustavsson <[EMAIL PROTECTED]> wrote:
> > +1 (non-binding)
> >
> > /niklas
> >
> > Robert Burrell Donkin wrote:
> > > i'd like to propose that the IPMC sponsors the entry of RAT into the 
> > > incubator
> > >
> > > - robert
> > >
> > > --8<-
> > > [ ] +1 Allow RAT to enter incubator, sponsored by IPMC
> > > [ ] +0
> > > [ ] -0
> > > [ ] -1 Do no allow RAT to enter incubator
> > > ---
> > >
> > > Rat Proposal
> > > ==
> > > Abstract
> > > 
> > > RAT is comprehension and auditing for distributions and source code.
> > >
> > > Proposal
> > > --
> > > RAT will provide a focus for components, applications and integration
> > > tools for the comprehension and audit of distributions and source
> > > code. It will collect data and meta-data as required. It will create
> > > suitable schemas for this data and meta-data as required.
> > >
> > > Background
> > > --
> > > RAT began as an attempt to automate the technical part of reviewing
> > > releases in the incubator. Following requests for access from release
> > > managers, RAT was developed as an open source project under the Apache
> > > License 2.0.
> > >
> > > Rationale
> > > ---
> > > Reviewing releases for compliance with Apache technical criteria and
> > > policies is time consuming. The Incubator requires that all releases
> > > are reviewed. Though small mistakes are common, this process typically
> > > adds only a little value. It is common for candidates to be presented
> > > with small but significant defects which then must be fixed and the
> > > candidate represented. Significant energy and good will is wasted by
> > > this process.
> > >
> > > This is unnecessary. Given effort, these technical criteria are
> > > capable of automation.
> > >
> > > Automated continuous checking of the source would allow the Incubator
> > > PMC to be alerted promptly to potential issues. Integration with build
> > > tools (such as Apache Ant and Apache Maven) would allow releases to be
> > > checked automatically and continuously.
> > >
> > > Initial Goals
> > > --
> > > * Read standard license meta-data for documents without license 
> > > headers
> > > * Improved RAT reporting
> > > * RAT source reporting for major build tools
> > > * Continuous RAT
> > > * RAT analytics: using meta-data to verify rules
> > >   o Apache third party documents policy analysis
> > >   o license compatibility analysis
> > > * Discordia integration to allow distributed binaries to be recognised
> > > * RAT analytic integration for major build tools
> > > * Improved recursive RAT scripts for better analysis of release
> > > with many distributables
> > >
> > > Current Status
> > > ===
> > > Meritocracy
> > > --
> > > I'm very happy to move from a solo development model towards a
> > > collective one as more active developers are recruited.
> > >
> > > Community
> > > --
> > > The RAT community needs to be developed. Having RAT here at Apache
> > > will hopefully encourage release managers to take a more active role
> > > in developing RAT.
> > >
> > > Core Developers
> > > --
> > > It has been developed principally by myself but with significant
> > > contributions of small amounts of code from other Apache members and
> > > committers.
> > >
> > > Alignment
> > > 
> > > RAT has found itself becoming a standard part of the Apache release
> > > infrastructure. The Incubator needs fully featured release tools. It
> > > makes sense to bring the project here.
> > >
> > > Known Risks
> > > ==
> > > Orphaned Projects
> > > -
> > > This is a project with a set of definite goals aimed at serving the
> > > wider Apache community. There may well come a time when the coding is
> > > actually finished. It has a small set of developers who all have many
> > > other calls on their time. The target user audience is relatively
> > > small. So, this risk is real.
> > >
> > > I think that it's clear that something similar to RAT is required. So,
> > > unless another better product is developed, time will be found to push
> > > RAT forward. Even if one day, RAT is orphaned then it will have done
> > > it's job.
> > >
> > > Inexperience With Open Source
> > > -
> > > The contributors are Apache members or experienced Apache committers.
> > >
> > > Reliance On Salaried Developers
> > > 
> > > I know of no one who's paid to work on RAT.
> > >
> > > Relationships with Other Apache Products

Re: [VOTE] RAT to enter incubator

[Luciano Resende]

+1 (non-binding)

On 10/30/07, Niklas Gustavsson <[EMAIL PROTECTED]> wrote:
> +1 (non-binding)
>
> /niklas
>
> Robert Burrell Donkin wrote:
> > i'd like to propose that the IPMC sponsors the entry of RAT into the 
> > incubator
> >
> > - robert
> >
> > --8<-
> > [ ] +1 Allow RAT to enter incubator, sponsored by IPMC
> > [ ] +0
> > [ ] -0
> > [ ] -1 Do no allow RAT to enter incubator
> > ---
> >
> > Rat Proposal
> > ==
> > Abstract
> > 
> > RAT is comprehension and auditing for distributions and source code.
> >
> > Proposal
> > --
> > RAT will provide a focus for components, applications and integration
> > tools for the comprehension and audit of distributions and source
> > code. It will collect data and meta-data as required. It will create
> > suitable schemas for this data and meta-data as required.
> >
> > Background
> > --
> > RAT began as an attempt to automate the technical part of reviewing
> > releases in the incubator. Following requests for access from release
> > managers, RAT was developed as an open source project under the Apache
> > License 2.0.
> >
> > Rationale
> > ---
> > Reviewing releases for compliance with Apache technical criteria and
> > policies is time consuming. The Incubator requires that all releases
> > are reviewed. Though small mistakes are common, this process typically
> > adds only a little value. It is common for candidates to be presented
> > with small but significant defects which then must be fixed and the
> > candidate represented. Significant energy and good will is wasted by
> > this process.
> >
> > This is unnecessary. Given effort, these technical criteria are
> > capable of automation.
> >
> > Automated continuous checking of the source would allow the Incubator
> > PMC to be alerted promptly to potential issues. Integration with build
> > tools (such as Apache Ant and Apache Maven) would allow releases to be
> > checked automatically and continuously.
> >
> > Initial Goals
> > --
> > * Read standard license meta-data for documents without license headers
> > * Improved RAT reporting
> > * RAT source reporting for major build tools
> > * Continuous RAT
> > * RAT analytics: using meta-data to verify rules
> >   o Apache third party documents policy analysis
> >   o license compatibility analysis
> > * Discordia integration to allow distributed binaries to be recognised
> > * RAT analytic integration for major build tools
> > * Improved recursive RAT scripts for better analysis of release
> > with many distributables
> >
> > Current Status
> > ===
> > Meritocracy
> > --
> > I'm very happy to move from a solo development model towards a
> > collective one as more active developers are recruited.
> >
> > Community
> > --
> > The RAT community needs to be developed. Having RAT here at Apache
> > will hopefully encourage release managers to take a more active role
> > in developing RAT.
> >
> > Core Developers
> > --
> > It has been developed principally by myself but with significant
> > contributions of small amounts of code from other Apache members and
> > committers.
> >
> > Alignment
> > 
> > RAT has found itself becoming a standard part of the Apache release
> > infrastructure. The Incubator needs fully featured release tools. It
> > makes sense to bring the project here.
> >
> > Known Risks
> > ==
> > Orphaned Projects
> > -
> > This is a project with a set of definite goals aimed at serving the
> > wider Apache community. There may well come a time when the coding is
> > actually finished. It has a small set of developers who all have many
> > other calls on their time. The target user audience is relatively
> > small. So, this risk is real.
> >
> > I think that it's clear that something similar to RAT is required. So,
> > unless another better product is developed, time will be found to push
> > RAT forward. Even if one day, RAT is orphaned then it will have done
> > it's job.
> >
> > Inexperience With Open Source
> > -
> > The contributors are Apache members or experienced Apache committers.
> >
> > Reliance On Salaried Developers
> > 
> > I know of no one who's paid to work on RAT.
> >
> > Relationships with Other Apache Products
> > --
> > RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting
> > plugin. Analytic plugins for Ant and Maven will be developed. There
> > are overlaps with Tika and there has been some talk of collaboration.
> > The discordia

Re: [VOTE] RAT to enter incubator

[Niklas Gustavsson]

+1 (non-binding)

/niklas

Robert Burrell Donkin wrote:

i'd like to propose that the IPMC sponsors the entry of RAT into the incubator

- robert

--8<-
[ ] +1 Allow RAT to enter incubator, sponsored by IPMC
[ ] +0
[ ] -0
[ ] -1 Do no allow RAT to enter incubator
---

Rat Proposal
==
Abstract

RAT is comprehension and auditing for distributions and source code.

Proposal
--
RAT will provide a focus for components, applications and integration
tools for the comprehension and audit of distributions and source
code. It will collect data and meta-data as required. It will create
suitable schemas for this data and meta-data as required.

Background
--
RAT began as an attempt to automate the technical part of reviewing
releases in the incubator. Following requests for access from release
managers, RAT was developed as an open source project under the Apache
License 2.0.

Rationale
---
Reviewing releases for compliance with Apache technical criteria and
policies is time consuming. The Incubator requires that all releases
are reviewed. Though small mistakes are common, this process typically
adds only a little value. It is common for candidates to be presented
with small but significant defects which then must be fixed and the
candidate represented. Significant energy and good will is wasted by
this process.

This is unnecessary. Given effort, these technical criteria are
capable of automation.

Automated continuous checking of the source would allow the Incubator
PMC to be alerted promptly to potential issues. Integration with build
tools (such as Apache Ant and Apache Maven) would allow releases to be
checked automatically and continuously.

Initial Goals
--
* Read standard license meta-data for documents without license headers
* Improved RAT reporting
* RAT source reporting for major build tools
* Continuous RAT
* RAT analytics: using meta-data to verify rules
  o Apache third party documents policy analysis
  o license compatibility analysis
* Discordia integration to allow distributed binaries to be recognised
* RAT analytic integration for major build tools
* Improved recursive RAT scripts for better analysis of release
with many distributables

Current Status
===
Meritocracy
--
I'm very happy to move from a solo development model towards a
collective one as more active developers are recruited.

Community
--
The RAT community needs to be developed. Having RAT here at Apache
will hopefully encourage release managers to take a more active role
in developing RAT.

Core Developers
--
It has been developed principally by myself but with significant
contributions of small amounts of code from other Apache members and
committers.

Alignment

RAT has found itself becoming a standard part of the Apache release
infrastructure. The Incubator needs fully featured release tools. It
makes sense to bring the project here.

Known Risks
==
Orphaned Projects
-
This is a project with a set of definite goals aimed at serving the
wider Apache community. There may well come a time when the coding is
actually finished. It has a small set of developers who all have many
other calls on their time. The target user audience is relatively
small. So, this risk is real.

I think that it's clear that something similar to RAT is required. So,
unless another better product is developed, time will be found to push
RAT forward. Even if one day, RAT is orphaned then it will have done
it's job.

Inexperience With Open Source
-
The contributors are Apache members or experienced Apache committers.

Reliance On Salaried Developers

I know of no one who's paid to work on RAT.

Relationships with Other Apache Products
--
RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting
plugin. Analytic plugins for Ant and Maven will be developed. There
are overlaps with Tika and there has been some talk of collaboration.
The discordia lab will likely be used for license and artifact
meta-data. RAT may integrate with Gump for continuous code scanning.

Initial Source

* [WWW] http://code.google.com/p/arat/source
* [WWW] http://mojo.codehaus.org/rat-maven-plugin

External Dependencies

Compliant with current Apache policy.

Cryptography
-
Required to check signatures.

Required Resources

Mailing lists:
* rat-private
* rat-dev
* rat-comm

Re: [VOTE] RAT to enter incubator

[Matthias Wessendorf]

+1 (non-binding)

On 10/30/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
> i'd like to propose that the IPMC sponsors the entry of RAT into the incubator
>
> - robert
>
> --8<-
> [ ] +1 Allow RAT to enter incubator, sponsored by IPMC
> [ ] +0
> [ ] -0
> [ ] -1 Do no allow RAT to enter incubator
> ---
>
> Rat Proposal
> ==
> Abstract
> 
> RAT is comprehension and auditing for distributions and source code.
>
> Proposal
> --
> RAT will provide a focus for components, applications and integration
> tools for the comprehension and audit of distributions and source
> code. It will collect data and meta-data as required. It will create
> suitable schemas for this data and meta-data as required.
>
> Background
> --
> RAT began as an attempt to automate the technical part of reviewing
> releases in the incubator. Following requests for access from release
> managers, RAT was developed as an open source project under the Apache
> License 2.0.
>
> Rationale
> ---
> Reviewing releases for compliance with Apache technical criteria and
> policies is time consuming. The Incubator requires that all releases
> are reviewed. Though small mistakes are common, this process typically
> adds only a little value. It is common for candidates to be presented
> with small but significant defects which then must be fixed and the
> candidate represented. Significant energy and good will is wasted by
> this process.
>
> This is unnecessary. Given effort, these technical criteria are
> capable of automation.
>
> Automated continuous checking of the source would allow the Incubator
> PMC to be alerted promptly to potential issues. Integration with build
> tools (such as Apache Ant and Apache Maven) would allow releases to be
> checked automatically and continuously.
>
> Initial Goals
> --
> * Read standard license meta-data for documents without license headers
> * Improved RAT reporting
> * RAT source reporting for major build tools
> * Continuous RAT
> * RAT analytics: using meta-data to verify rules
>   o Apache third party documents policy analysis
>   o license compatibility analysis
> * Discordia integration to allow distributed binaries to be recognised
> * RAT analytic integration for major build tools
> * Improved recursive RAT scripts for better analysis of release
> with many distributables
>
> Current Status
> ===
> Meritocracy
> --
> I'm very happy to move from a solo development model towards a
> collective one as more active developers are recruited.
>
> Community
> --
> The RAT community needs to be developed. Having RAT here at Apache
> will hopefully encourage release managers to take a more active role
> in developing RAT.
>
> Core Developers
> --
> It has been developed principally by myself but with significant
> contributions of small amounts of code from other Apache members and
> committers.
>
> Alignment
> 
> RAT has found itself becoming a standard part of the Apache release
> infrastructure. The Incubator needs fully featured release tools. It
> makes sense to bring the project here.
>
> Known Risks
> ==
> Orphaned Projects
> -
> This is a project with a set of definite goals aimed at serving the
> wider Apache community. There may well come a time when the coding is
> actually finished. It has a small set of developers who all have many
> other calls on their time. The target user audience is relatively
> small. So, this risk is real.
>
> I think that it's clear that something similar to RAT is required. So,
> unless another better product is developed, time will be found to push
> RAT forward. Even if one day, RAT is orphaned then it will have done
> it's job.
>
> Inexperience With Open Source
> -
> The contributors are Apache members or experienced Apache committers.
>
> Reliance On Salaried Developers
> 
> I know of no one who's paid to work on RAT.
>
> Relationships with Other Apache Products
> --
> RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting
> plugin. Analytic plugins for Ant and Maven will be developed. There
> are overlaps with Tika and there has been some talk of collaboration.
> The discordia lab will likely be used for license and artifact
> meta-data. RAT may integrate with Gump for continuous code scanning.
>
> Initial Source
> 
> * [WWW] http://code.google.com/p/arat/source
> * [WWW] http://mojo.codehaus.org/rat-maven-plugin
>
> External Dependencies
> -

[VOTE] RAT to enter incubator

[Robert Burrell Donkin]

i'd like to propose that the IPMC sponsors the entry of RAT into the incubator

- robert

--8<-
[ ] +1 Allow RAT to enter incubator, sponsored by IPMC
[ ] +0
[ ] -0
[ ] -1 Do no allow RAT to enter incubator
---

Rat Proposal
==
Abstract

RAT is comprehension and auditing for distributions and source code.

Proposal
--
RAT will provide a focus for components, applications and integration
tools for the comprehension and audit of distributions and source
code. It will collect data and meta-data as required. It will create
suitable schemas for this data and meta-data as required.

Background
--
RAT began as an attempt to automate the technical part of reviewing
releases in the incubator. Following requests for access from release
managers, RAT was developed as an open source project under the Apache
License 2.0.

Rationale
---
Reviewing releases for compliance with Apache technical criteria and
policies is time consuming. The Incubator requires that all releases
are reviewed. Though small mistakes are common, this process typically
adds only a little value. It is common for candidates to be presented
with small but significant defects which then must be fixed and the
candidate represented. Significant energy and good will is wasted by
this process.

This is unnecessary. Given effort, these technical criteria are
capable of automation.

Automated continuous checking of the source would allow the Incubator
PMC to be alerted promptly to potential issues. Integration with build
tools (such as Apache Ant and Apache Maven) would allow releases to be
checked automatically and continuously.

Initial Goals
--
* Read standard license meta-data for documents without license headers
* Improved RAT reporting
* RAT source reporting for major build tools
* Continuous RAT
* RAT analytics: using meta-data to verify rules
  o Apache third party documents policy analysis
  o license compatibility analysis
* Discordia integration to allow distributed binaries to be recognised
* RAT analytic integration for major build tools
* Improved recursive RAT scripts for better analysis of release
with many distributables

Current Status
===
Meritocracy
--
I'm very happy to move from a solo development model towards a
collective one as more active developers are recruited.

Community
--
The RAT community needs to be developed. Having RAT here at Apache
will hopefully encourage release managers to take a more active role
in developing RAT.

Core Developers
--
It has been developed principally by myself but with significant
contributions of small amounts of code from other Apache members and
committers.

Alignment

RAT has found itself becoming a standard part of the Apache release
infrastructure. The Incubator needs fully featured release tools. It
makes sense to bring the project here.

Known Risks
==
Orphaned Projects
-
This is a project with a set of definite goals aimed at serving the
wider Apache community. There may well come a time when the coding is
actually finished. It has a small set of developers who all have many
other calls on their time. The target user audience is relatively
small. So, this risk is real.

I think that it's clear that something similar to RAT is required. So,
unless another better product is developed, time will be found to push
RAT forward. Even if one day, RAT is orphaned then it will have done
it's job.

Inexperience With Open Source
-
The contributors are Apache members or experienced Apache committers.

Reliance On Salaried Developers

I know of no one who's paid to work on RAT.

Relationships with Other Apache Products
--
RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting
plugin. Analytic plugins for Ant and Maven will be developed. There
are overlaps with Tika and there has been some talk of collaboration.
The discordia lab will likely be used for license and artifact
meta-data. RAT may integrate with Gump for continuous code scanning.

Initial Source

* [WWW] http://code.google.com/p/arat/source
* [WWW] http://mojo.codehaus.org/rat-maven-plugin

External Dependencies

Compliant with current Apache policy.

Cryptography
-
Required to check signatures.

Required Resources

Mailing lists:
* rat-private
* rat-dev
* rat-commits
Subversion Directory: [WWW] https://svn.apache.org/rep

Re: [VOTE] Accept project Buildr for incubation

[ant elder]

+1

   ...ant

On 10/29/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Following up on the proposal discussed at [1] I'd like to call for a vote
> to
> incubate Buildr. Buildr is a simple and intuitive build system for Java
> projects written in Ruby (and based on Rake), please see the complete
> proposal text at [2] or at the end of this e-mail.
>
> Also we're missing one more mentor so if someone could volunteer, that
> would
> really be great.
>
> Please vote on accepting Buildr into the Apache Incubator. This vote will
> run until Thursday November 1st at 3pm PST.
>
> [ ] +1 Accept Buildr project for incubation
> [ ] 0 Don't care
> [ ] -1 Reject for the following reason :
>
> Thanks!
> Matthieu
>
> [1]
> http://mail-archives.apache.org/mod_mbox/incubator-general/200710.mbox/[EMAIL 
> PROTECTED]
>
> [2] http://wiki.apache.org/incubator/BuildrProposal
>
> ---
>
> = Abstract =
>
> Buildr is a simple and intuitive build system for Java projects.
>
> = Proposal =
>
> Buildr is a build system for Java applications. We wanted something that's
> simple and intuitive to use, so we only need to tell it what to do, and it
> takes care of the rest. But also something we can easily extend for those
> one-off tasks, with a language that's a joy to use. And of course, we
> wanted
> it to be fast, reliable and have outstanding dependency management.
>
> Here's what we got:
>
> * A simple way to specify projects, and build large projects out of
> smaller sub-projects.
> * Pre-canned tasks that require the least amount of configuration,
> keeping the build script DRY and simple.
> * Compiling, copying and filtering resources, JUnit/TestNG test cases,
> APT source code generation, Javadoc and more.
> * A dependency mechanism that only build that which changed since the
> last release.
> * Buildr uses the same file layout, artifact specifications, local and
> remote repositories as Maven 2.
> * All your Ant tasks belong to us! Anything you can do with Ant, you
> can
> do with Buildr.
> * Buildr is Ruby all the way down. No one-off task is too demanding
> when
> you write code using variables, functions and objects.
> * Simple way to upgrade to new versions.
> * Did we mention fast?
>
> = Background =
>
> Buildr is developed using the Ruby language and is layered on top of Rake,
> a
> popular build program for Ruby that provides all the task and task
> dependency infrastructure. It also relies on AntWrap to allow the reuse of
> all existing Ant tasks.
>
> = Rationale =
>
> Buildr's initial focus was to be layered on top of a powerful scripting
> language. It's an internal DSL and therefore enjoys a lot of ease of use
> and
> extensibility. It's also declarative, which gives scripts expressiveness
> (they're easy to read). And there's no XML!
>
> We believe bringing Buildr at Apache is a good way to expand even more the
> build tool space, attract more committers and users to Buildr and have
> people start playing with the Ruby language, both within and outside the
> foundation.
>
> = Current Status =
>
> == Meritocracy ==
>
> Buildr has been mostly developed by Assaf Arkin but others have
> contributed
> either directly or through patches. In addition to contributed patches,
> work
> on Scala and JRuby is done by community members, and we're working to
> cultivate that and add more committers.
>
> == Community ==
>
> A community of standard users but also power users is building around
> Buildr
> and several people are using it in all sort of different projects.
> Currently
> the discussion group has 86 members, more statistics available at
> http://groups.google.com/group/buildr-talk?lnk=srg
>
> == Core Developers ==
>
> Core developers are mostly from a single organization but more and more
> power users are contributing patches and trying to extend Buildr. Also
> current core developers are very experienced in open source and already
> follow the Apache ways.
>
> == Alignment ==
>
> Buildr is in line with the existing strong culture of build tools at
> Apache
> (Ant, Maven, Ivy, ...). It already relies on Maven2 repositories and
> follows
> most of its project structure conventions. It allows reuse of Ant tasks.
> Not
> to mention that other Apache projects could use it for their build (as ODE
> already does).
>
> = Known Risks =
>
> == Orphaned Projects ==
>
> Buildr core development is still very much dependent on Assaf but more and
> more people are getting familiar with the way Buildr works and its
> intricacies. So we're aware of the problem but also confident that we're
> on
> the right track as more and more people get involved.
>
> == Inexperience with Open Source ==
>
> Many committers have experience working on open source projects. Three of
> them are Apache committers.
>
> == Reliance on Salaried Developers ==
>
> Buildr is part of the committers job but is far from being the main
> company
> focus. So i

Re: [VOTE] Accept project Buildr for incubation

[Niklas Gustavsson]

+1, Buildr is excellent stuff.

/niklas

Matthieu Riou wrote:

Hi,

Following up on the proposal discussed at [1] I'd like to call for a vote to
incubate Buildr. Buildr is a simple and intuitive build system for Java
projects written in Ruby (and based on Rake), please see the complete
proposal text at [2] or at the end of this e-mail.

Also we're missing one more mentor so if someone could volunteer, that would
really be great.

Please vote on accepting Buildr into the Apache Incubator. This vote will
run until Thursday November 1st at 3pm PST.

[ ] +1 Accept Buildr project for incubation
[ ] 0 Don't care
[ ] -1 Reject for the following reason :

Thanks!
Matthieu

[1] 
http://mail-archives.apache.org/mod_mbox/incubator-general/200710.mbox/[EMAIL 
PROTECTED]

[2] http://wiki.apache.org/incubator/BuildrProposal

---

= Abstract =

Buildr is a simple and intuitive build system for Java projects.

= Proposal =

Buildr is a build system for Java applications. We wanted something that's
simple and intuitive to use, so we only need to tell it what to do, and it
takes care of the rest. But also something we can easily extend for those
one-off tasks, with a language that's a joy to use. And of course, we wanted
it to be fast, reliable and have outstanding dependency management.

Here's what we got:

* A simple way to specify projects, and build large projects out of
smaller sub-projects.
* Pre-canned tasks that require the least amount of configuration,
keeping the build script DRY and simple.
* Compiling, copying and filtering resources, JUnit/TestNG test cases,
APT source code generation, Javadoc and more.
* A dependency mechanism that only build that which changed since the
last release.
* Buildr uses the same file layout, artifact specifications, local and
remote repositories as Maven 2.
* All your Ant tasks belong to us! Anything you can do with Ant, you can
do with Buildr.
* Buildr is Ruby all the way down. No one-off task is too demanding when
you write code using variables, functions and objects.
* Simple way to upgrade to new versions.
* Did we mention fast?

= Background =

Buildr is developed using the Ruby language and is layered on top of Rake, a
popular build program for Ruby that provides all the task and task
dependency infrastructure. It also relies on AntWrap to allow the reuse of
all existing Ant tasks.

= Rationale =

Buildr's initial focus was to be layered on top of a powerful scripting
language. It's an internal DSL and therefore enjoys a lot of ease of use and
extensibility. It's also declarative, which gives scripts expressiveness
(they're easy to read). And there's no XML!

We believe bringing Buildr at Apache is a good way to expand even more the
build tool space, attract more committers and users to Buildr and have
people start playing with the Ruby language, both within and outside the
foundation.

= Current Status =

== Meritocracy ==

Buildr has been mostly developed by Assaf Arkin but others have contributed
either directly or through patches. In addition to contributed patches, work
on Scala and JRuby is done by community members, and we're working to
cultivate that and add more committers.

== Community ==

A community of standard users but also power users is building around Buildr
and several people are using it in all sort of different projects. Currently
the discussion group has 86 members, more statistics available at
http://groups.google.com/group/buildr-talk?lnk=srg

== Core Developers ==

Core developers are mostly from a single organization but more and more
power users are contributing patches and trying to extend Buildr. Also
current core developers are very experienced in open source and already
follow the Apache ways.

== Alignment ==

Buildr is in line with the existing strong culture of build tools at Apache
(Ant, Maven, Ivy, ...). It already relies on Maven2 repositories and follows
most of its project structure conventions. It allows reuse of Ant tasks. Not
to mention that other Apache projects could use it for their build (as ODE
already does).

= Known Risks =

== Orphaned Projects ==

Buildr core development is still very much dependent on Assaf but more and
more people are getting familiar with the way Buildr works and its
intricacies. So we're aware of the problem but also confident that we're on
the right track as more and more people get involved.

== Inexperience with Open Source ==

Many committers have experience working on open source projects. Three of
them are Apache committers.

== Reliance on Salaried Developers ==

Buildr is part of the committers job but is far from being the main company
focus. So it's part working time and part personal time.

== Relationships with Other Apache Products ==

As there aren't many Ruby projects in the ASF yet, there's less relationship
possible for the time being. But Apache ODE is already using Buildr as its
build tool

Re: [VOTE] Accept project Buildr for incubation

[Craig L Russell]

+1

It will be nice to see some Ruby development here.

Craig

On Oct 29, 2007, at 2:29 PM, Matthieu Riou wrote:


Hi,

Following up on the proposal discussed at [1] I'd like to call for  
a vote to
incubate Buildr. Buildr is a simple and intuitive build system for  
Java

projects written in Ruby (and based on Rake), please see the complete
proposal text at [2] or at the end of this e-mail.

Also we're missing one more mentor so if someone could volunteer,  
that would

really be great.

Please vote on accepting Buildr into the Apache Incubator. This  
vote will

run until Thursday November 1st at 3pm PST.

[ ] +1 Accept Buildr project for incubation
[ ] 0 Don't care
[ ] -1 Reject for the following reason :

Thanks!
Matthieu


Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!



smime.p7s
Description: S/MIME cryptographic signature

Re: Apache Composer - vote outcome

[Jim Jagielski]

On Oct 30, 2007, at 11:33 AM, Paul Hammant wrote:
  Jim Jagielski (with some comments about muck raking - hopefully  
allayed)


:)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Java Jabber Server

[Deepal jayasinghe]

Petar Tahchiev wrote:
> Hi guys,
>
> today I was looking for a Jabber server implemented entirely in Java,
> and the only results
> that I got was this:
>
> ---(free)---
> http://www.codecobra.com/chime/
> http://www.open-im.net/
> http://www.tigase.org/
> http://www.igniterealtime.org/projects/openfire/index.jsp
>
> (commercial)---
> http://www.adobe.com/special/antepo/?products.opnserver (no longer
> available - bought by Adobe)
>
> Does anyone (besides me) think that we can build something better?
>
> Waiting for your suggestions.
>   
I also like to contribute to this , if you are going to implement.
sometimes ago I wanted to build a Jabber (XMPP) implementation based
Stax implementation. May be this is a good chance for that.

Thanks
Deepal

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Java Jabber Server

[J Aaron Farr]

"Petar Tahchiev" <[EMAIL PROTECTED]> writes:

> Hi guys,
>
> today I was looking for a Jabber server implemented entirely in Java,
> and the only results
> that I got was this:
>
> ---(free)---
> http://www.codecobra.com/chime/
> http://www.open-im.net/

OpenIM was originally developed using Apache Avalon containers and now
uses Plexus (which is entering incubation).  The developer, alag, was
a regular on the mailing lists at the time.  I'm not sure how active
the project is today (looks like it's moved to Codehaus).  It's under
the MIT license.

And while I haven't used this particular feature of ActiveMQ, it does
advertise XMPP support:

  http://activemq.apache.org/xmpp.html

-- 
  J Aaron Farr jadetower.com[US] +1 724-964-4515 
馮傑仁  cubiclemuses.com [HK] +852 8123-7905  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Apache Composer - vote outcome

[Paul Hammant]

In Favor (+1)

  James Strachan
  Bertrand Delacretaz
  Jukka Zitting
  Martijn Dashorst
  Leo Simons
  Davanum Srinivas
  Robert Burrell Donkin
  Craig L Russell
  Eelco Hillenius
  Matt Hogstrom
  Justin Erenkrantz
  J Aaron Farr
  Kevan Miller (with come comments about off-list activity -  
hopefully allayed)


In Favor (non binding)

  Luciano Resende

Don't care (0)

  Jim Jagielski (with some comments about muck raking - hopefully  
allayed)
  Niclas Hedhman (with some concern that our beloved IntelliJ IDEA  
may suffer because of PicoContainer's move)


Thanks for the approval folks.

Stand back and watch for the diffs in coming weeks ;-)

- Paul

Re: Java Jabber Server

[Andrus Adamchik]

today I was looking for a Jabber server implemented entirely in Java,
and the only results
that I got was this:


Not like the list you've quoted indicates scarcity in the XMPP server  
space ;-)



Does anyone (besides me) think that we can build something better?


As always having an Apache-licensed alternative to a GPL'd versions  
is great, so good luck with this effort. Hopefully people who need to  
embed such server in their products would take note and join.


Andrus



On Oct 30, 2007, at 4:59 PM, Petar Tahchiev wrote:

Hi guys,

today I was looking for a Jabber server implemented entirely in Java,
and the only results
that I got was this:

---(free)---
http://www.codecobra.com/chime/
http://www.open-im.net/
http://www.tigase.org/
http://www.igniterealtime.org/projects/openfire/index.jsp

(commercial)---
http://www.adobe.com/special/antepo/?products.opnserver (no longer
available - bought by Adobe)

Does anyone (besides me) think that we can build something better?

Waiting for your suggestions.

--
Regards, Petar!
Karlovo, Bulgaria.

EOOXML objections
http://www.grokdoc.net/index.php/EOOXML_objections

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Java Jabber Server

[Petar Tahchiev]

Hi guys,

today I was looking for a Jabber server implemented entirely in Java,
and the only results
that I got was this:

---(free)---
http://www.codecobra.com/chime/
http://www.open-im.net/
http://www.tigase.org/
http://www.igniterealtime.org/projects/openfire/index.jsp

(commercial)---
http://www.adobe.com/special/antepo/?products.opnserver (no longer
available - bought by Adobe)

Does anyone (besides me) think that we can build something better?

Waiting for your suggestions.

-- 
Regards, Petar!
Karlovo, Bulgaria.

EOOXML objections
http://www.grokdoc.net/index.php/EOOXML_objections

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Accept project Buildr for incubation

[Matthieu Riou]

On 10/30/07, J Aaron Farr <[EMAIL PROTECTED]> wrote:
>
>
> Jim Jagielski <[EMAIL PROTECTED]> writes:
>
> > On Oct 29, 2007, at 5:29 PM, Matthieu Riou wrote:
> >
> >>
> >> Also we're missing one more mentor so if someone could volunteer,
> >> that would
> >> really be great.
> >>
> >
> > Count me in.
>
> Jim beat me to it. :-)
>
> I'll be keeping an eye on the project as well though.


Please do, we'll have quite a few issues to work on (especially licensing) .
And thanks for stepping up!

>> Please vote on accepting Buildr into the Apache Incubator. This
> >> vote will
> >> run until Thursday November 1st at 3pm PST.
> >>
> >> [X] +1 Accept Buildr project for incubation
> >> [ ] 0 Don't care
> >> [ ] -1 Reject for the following reason :
>
> +1
>
> Good to see some Ruby code coming into the foundation, even if it is
> for compiling Java.
>
> --
>   J Aaron Farr jadetower.com[US] +1 724-964-4515
> 馮傑仁  cubiclemuses.com [HK] +852 8123-7905
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [VOTE] Accept project Buildr for incubation

[Matthieu Riou]

On 10/30/07, Jim Jagielski <[EMAIL PROTECTED]> wrote:
>
>
> On Oct 29, 2007, at 5:29 PM, Matthieu Riou wrote:
>
> >
> > Also we're missing one more mentor so if someone could volunteer,
> > that would
> > really be great.
> >
>
> Count me in.


Thanks!

> Please vote on accepting Buildr into the Apache Incubator. This
> > vote will
> > run until Thursday November 1st at 3pm PST.
> >
> > [X] +1 Accept Buildr project for incubation
> > [ ] 0 Don't care
> > [ ] -1 Reject for the following reason :
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [apachecon eu'08] Guide to successful incubation at the ASF

[Martijn Dashorst]

Cool, thanks!

Now I need to get approved ;-)

Martijn

On 10/30/07, J Aaron Farr <[EMAIL PROTECTED]> wrote:
>
> "Martijn Dashorst" <[EMAIL PROTECTED]> writes:
>
> > I just sent a proposal to the apache con CFP for a presentation on
> > successful incubation.
> >
> > Unfortunately the title was submitted wrongly, and the apache con site
> > doesn't allow editing of the title of a submitted proposal.
>
> Cool.
>
> I did a couple of talks on open source communities and the incubator
> at OSCON and ApacheCon.  You can find the slides at:
>
>   http://www.cubiclemuses.com/cm/files/incubating_communities.pdf
>
>   http://www.cubiclemuses.com/cm/files/incubator.ppt
>
> Feel free to use anything that might help.
>
> --
>   J Aaron Farr jadetower.com[US] +1 724-964-4515
> 馮傑仁  cubiclemuses.com [HK] +852 8123-7905
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Accept project Buildr for incubation

[Erik Hatcher]

On Oct 30, 2007, at 9:23 AM, J Aaron Farr wrote:

Good to see some Ruby code coming into the foundation, even if it is
for compiling Java.


There's Ruby code under Solr:

* solr-ruby: Ruby API to Solr
* Flare: Ruby on Rails plugin using solr-ruby to present a faceted UI.

A couple of demos of Flare are here:

 - Blacklight (my baby, now evolving on its own without me): http:// 
blacklight.betech.virginia.edu
 - http://www.rondhuit-demo.com/yademo/ (appears to be down at the  
moment): a Japanese site with products from Yahoo, lots of  
screenshots blogged here 


 :)

  Erik



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [apachecon eu'08] Guide to successful incubation at the ASF

[J Aaron Farr]

"Martijn Dashorst" <[EMAIL PROTECTED]> writes:

> I just sent a proposal to the apache con CFP for a presentation on
> successful incubation.
>
> Unfortunately the title was submitted wrongly, and the apache con site
> doesn't allow editing of the title of a submitted proposal.

Cool.

I did a couple of talks on open source communities and the incubator
at OSCON and ApacheCon.  You can find the slides at:

  http://www.cubiclemuses.com/cm/files/incubating_communities.pdf

  http://www.cubiclemuses.com/cm/files/incubator.ppt

Feel free to use anything that might help.

-- 
  J Aaron Farr jadetower.com[US] +1 724-964-4515 
馮傑仁  cubiclemuses.com [HK] +852 8123-7905  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Accept project Buildr for incubation

[J Aaron Farr]

Jim Jagielski <[EMAIL PROTECTED]> writes:

> On Oct 29, 2007, at 5:29 PM, Matthieu Riou wrote:
>
>>
>> Also we're missing one more mentor so if someone could volunteer,
>> that would
>> really be great.
>>
>
> Count me in.

Jim beat me to it. :-)

I'll be keeping an eye on the project as well though.

>> Please vote on accepting Buildr into the Apache Incubator. This
>> vote will
>> run until Thursday November 1st at 3pm PST.
>>
>> [X] +1 Accept Buildr project for incubation
>> [ ] 0 Don't care
>> [ ] -1 Reject for the following reason :

+1

Good to see some Ruby code coming into the foundation, even if it is
for compiling Java.

-- 
  J Aaron Farr jadetower.com[US] +1 724-964-4515 
馮傑仁  cubiclemuses.com [HK] +852 8123-7905  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Accept project Buildr for incubation

[Paul Fremantle]

[ X] +1 Accept Buildr project for incubation
[ ] 0 Don't care
[ ] -1 Reject for the following reason :

I think this is a great idea. +1 from me.

Paul

On 10/30/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
>
> 
>
> On Oct 29, 2007 9:29 PM, Matthieu Riou <[EMAIL PROTECTED]> wrote:
>
> > [X] +1 Accept Buildr project for incubation
> > [ ] 0 Don't care
> > [ ] -1 Reject for the following reason :
>
> - robert
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

Re: [VOTE] Accept project Buildr for incubation

[Robert Burrell Donkin]

On Oct 29, 2007 9:29 PM, Matthieu Riou <[EMAIL PROTECTED]> wrote:

> [X] +1 Accept Buildr project for incubation
> [ ] 0 Don't care
> [ ] -1 Reject for the following reason :

- robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Accept project Buildr for incubation

[Jim Jagielski]

On Oct 29, 2007, at 5:29 PM, Matthieu Riou wrote:



Also we're missing one more mentor so if someone could volunteer,  
that would

really be great.



Count me in.

Please vote on accepting Buildr into the Apache Incubator. This  
vote will

run until Thursday November 1st at 3pm PST.

[X] +1 Accept Buildr project for incubation
[ ] 0 Don't care
[ ] -1 Reject for the following reason :




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Accept project Buildr for incubation

[Erik Hatcher]

To second a previous message.  JRuby is quite good already, and  
getting better every day.  Having JRuby tie to Ant's API through the  
elegance of Rake would be awesome.


Erik


On Oct 29, 2007, at 7:20 PM, Noel J. Bergman wrote:


+1

For what it is worth, I heard a lot of comments about buildr at a  
developer
conference last week, and the general consensus seemed to be that  
it should
ditch Ruby/Rake, and be rewritten to use Groovy.  Java developers,  
it was

widely claimed, don't want to have to install Ruby in order to do Java
development.

--- Noel



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Accept project Buildr for incubation

[Erik Hatcher]

+1

On Oct 29, 2007, at 5:29 PM, Matthieu Riou wrote:


Hi,

Following up on the proposal discussed at [1] I'd like to call for  
a vote to
incubate Buildr. Buildr is a simple and intuitive build system for  
Java

projects written in Ruby (and based on Rake), please see the complete
proposal text at [2] or at the end of this e-mail.

Also we're missing one more mentor so if someone could volunteer,  
that would

really be great.

Please vote on accepting Buildr into the Apache Incubator. This  
vote will

run until Thursday November 1st at 3pm PST.

[ ] +1 Accept Buildr project for incubation
[ ] 0 Don't care
[ ] -1 Reject for the following reason :

Thanks!
Matthieu

[1] http://mail-archives.apache.org/mod_mbox/incubator-general/ 
200710.mbox/% 
[EMAIL PROTECTED]


[2] http://wiki.apache.org/incubator/BuildrProposal

---

= Abstract =

Buildr is a simple and intuitive build system for Java projects.

= Proposal =

Buildr is a build system for Java applications. We wanted something  
that's
simple and intuitive to use, so we only need to tell it what to do,  
and it
takes care of the rest. But also something we can easily extend for  
those
one-off tasks, with a language that's a joy to use. And of course,  
we wanted

it to be fast, reliable and have outstanding dependency management.

Here's what we got:

* A simple way to specify projects, and build large projects  
out of

smaller sub-projects.
* Pre-canned tasks that require the least amount of configuration,
keeping the build script DRY and simple.
* Compiling, copying and filtering resources, JUnit/TestNG test  
cases,

APT source code generation, Javadoc and more.
* A dependency mechanism that only build that which changed  
since the

last release.
* Buildr uses the same file layout, artifact specifications,  
local and

remote repositories as Maven 2.
* All your Ant tasks belong to us! Anything you can do with  
Ant, you can

do with Buildr.
* Buildr is Ruby all the way down. No one-off task is too  
demanding when

you write code using variables, functions and objects.
* Simple way to upgrade to new versions.
* Did we mention fast?

= Background =

Buildr is developed using the Ruby language and is layered on top  
of Rake, a

popular build program for Ruby that provides all the task and task
dependency infrastructure. It also relies on AntWrap to allow the  
reuse of

all existing Ant tasks.

= Rationale =

Buildr's initial focus was to be layered on top of a powerful  
scripting
language. It's an internal DSL and therefore enjoys a lot of ease  
of use and
extensibility. It's also declarative, which gives scripts  
expressiveness

(they're easy to read). And there's no XML!

We believe bringing Buildr at Apache is a good way to expand even  
more the

build tool space, attract more committers and users to Buildr and have
people start playing with the Ruby language, both within and  
outside the

foundation.

= Current Status =

== Meritocracy ==

Buildr has been mostly developed by Assaf Arkin but others have  
contributed
either directly or through patches. In addition to contributed  
patches, work

on Scala and JRuby is done by community members, and we're working to
cultivate that and add more committers.

== Community ==

A community of standard users but also power users is building  
around Buildr
and several people are using it in all sort of different projects.  
Currently

the discussion group has 86 members, more statistics available at
http://groups.google.com/group/buildr-talk?lnk=srg

== Core Developers ==

Core developers are mostly from a single organization but more and  
more

power users are contributing patches and trying to extend Buildr. Also
current core developers are very experienced in open source and  
already

follow the Apache ways.

== Alignment ==

Buildr is in line with the existing strong culture of build tools  
at Apache
(Ant, Maven, Ivy, ...). It already relies on Maven2 repositories  
and follows
most of its project structure conventions. It allows reuse of Ant  
tasks. Not
to mention that other Apache projects could use it for their build  
(as ODE

already does).

= Known Risks =

== Orphaned Projects ==

Buildr core development is still very much dependent on Assaf but  
more and

more people are getting familiar with the way Buildr works and its
intricacies. So we're aware of the problem but also confident that  
we're on

the right track as more and more people get involved.

== Inexperience with Open Source ==

Many committers have experience working on open source projects.  
Three of

them are Apache committers.

== Reliance on Salaried Developers ==

Buildr is part of the committers job but is far from being the main  
company

focus. So it's part working time and part personal time.

== Relationships with Other Apache Products ==

As there aren't many Ruby projects in the ASF yet, there's less  
relat