You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Matthieu Riou <ma...@offthelip.org> on 2007/10/29 22:29:34 UTC

[VOTE] Accept project Buildr for incubation

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/%3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e

[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.

= Documentation & Intial Sources =

The current Buildr website is at: http://buildr.rubyforge.org
The Buildr sources are available at: http://www.intalio.org/buildr

== External Dependencies ==

External dependencies are one of the main concerns that will need to be
addressed. Buildr relies on several packages that are licensed under the
Ruby License, which hasn't been categorized yet as okay or not. We've
already mentioned this on legal-discuss@a.o (see [1]). There are a few
subtleties as well as the Ruby packaging system, RubyGems, doesn't require
you to distribute any dependencies as it handles them for you. So we will
have to figure out what the options are before the first incubator release
and graduation.

[1]
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200708.mbox/%3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e

= Required Resources =

 * buildr-private
 * buildr-dev
 * buildr-user

Subversion Directory: [WWW]
https://svn.apache.org/repos/asf/incubator/buildr
Issue Tracking: JIRA

= Initial Committers =

 * Assaf Arkin (Intalio)
 * Alex Boisvert (Intalio)
 * Matthieu Riou (Intalio)

== Champion ==

Matthieu Riou

== Mentors ==

Volunteers please:

 * Matthieu Riou <mriou AT apache.org>
 * Yoav Shapira <yoavs at the usual for this wiki>

= Sponsoring Entity =

The final destination is still uncertain. If Buildr is successful, a TLP
could make sense. So right now we would like to ask the Incubator PMC to
sponsor Buildr.

Re: [VOTE] Accept project Buildr for incubation

Posted by Eelco Hillenius <ee...@gmail.com>.
 [ x ] +1 Accept Buildr project for incubation
 [ ] 0 Don't care
 [ ] -1 Reject for the following reason :

Eelco

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


Re: [VOTE] Accept project Buildr for incubation

Posted by ant elder <an...@gmail.com>.
+1

   ...ant

On 10/29/07, Matthieu Riou <ma...@offthelip.org> 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/%3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e
>
> [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.
>
> = Documentation & Intial Sources =
>
> The current Buildr website is at: http://buildr.rubyforge.org
> The Buildr sources are available at: http://www.intalio.org/buildr
>
> == External Dependencies ==
>
> External dependencies are one of the main concerns that will need to be
> addressed. Buildr relies on several packages that are licensed under the
> Ruby License, which hasn't been categorized yet as okay or not. We've
> already mentioned this on legal-discuss@a.o (see [1]). There are a few
> subtleties as well as the Ruby packaging system, RubyGems, doesn't require
> you to distribute any dependencies as it handles them for you. So we will
> have to figure out what the options are before the first incubator release
> and graduation.
>
> [1]
>
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200708.mbox/%3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e
>
> = Required Resources =
>
> * buildr-private
> * buildr-dev
> * buildr-user
>
> Subversion Directory: [WWW]
> https://svn.apache.org/repos/asf/incubator/buildr
> Issue Tracking: JIRA
>
> = Initial Committers =
>
> * Assaf Arkin (Intalio)
> * Alex Boisvert (Intalio)
> * Matthieu Riou (Intalio)
>
> == Champion ==
>
> Matthieu Riou
>
> == Mentors ==
>
> Volunteers please:
>
> * Matthieu Riou <mriou AT apache.org>
> * Yoav Shapira <yoavs at the usual for this wiki>
>
> = Sponsoring Entity =
>
> The final destination is still uncertain. If Buildr is successful, a TLP
> could make sense. So right now we would like to ask the Incubator PMC to
> sponsor Buildr.
>

Re: [VOTE] Accept project Buildr for incubation

Posted by Martijn Dashorst <ma...@gmail.com>.
+1

Martijn

(I'm eyeing this project for future assimilation in my build procedures)

On 10/29/07, Matthieu Riou <ma...@offthelip.org> 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/%3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e
>
> [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.
>
> = Documentation & Intial Sources =
>
> The current Buildr website is at: http://buildr.rubyforge.org
> The Buildr sources are available at: http://www.intalio.org/buildr
>
> == External Dependencies ==
>
> External dependencies are one of the main concerns that will need to be
> addressed. Buildr relies on several packages that are licensed under the
> Ruby License, which hasn't been categorized yet as okay or not. We've
> already mentioned this on legal-discuss@a.o (see [1]). There are a few
> subtleties as well as the Ruby packaging system, RubyGems, doesn't require
> you to distribute any dependencies as it handles them for you. So we will
> have to figure out what the options are before the first incubator release
> and graduation.
>
> [1]
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200708.mbox/%3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e
>
> = Required Resources =
>
>  * buildr-private
>  * buildr-dev
>  * buildr-user
>
> Subversion Directory: [WWW]
> https://svn.apache.org/repos/asf/incubator/buildr
> Issue Tracking: JIRA
>
> = Initial Committers =
>
>  * Assaf Arkin (Intalio)
>  * Alex Boisvert (Intalio)
>  * Matthieu Riou (Intalio)
>
> == Champion ==
>
> Matthieu Riou
>
> == Mentors ==
>
> Volunteers please:
>
>  * Matthieu Riou <mriou AT apache.org>
>  * Yoav Shapira <yoavs at the usual for this wiki>
>
> = Sponsoring Entity =
>
> The final destination is still uncertain. If Buildr is successful, a TLP
> could make sense. So right now we would like to ask the Incubator PMC to
> sponsor Buildr.
>


-- 
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: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [VOTE] Accept project Buildr for incubation

Posted by Doug Cutting <cu...@apache.org>.
Matthieu Riou wrote:
> Following up on the proposal discussed at [1] I'd like to call for a vote to
> incubate Buildr.

+1

Doug

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


Re: [VOTE] Accept project Buildr for incubation

Posted by Bruce Snyder <br...@gmail.com>.
On 10/29/07, Assaf Arkin <ar...@intalio.com> wrote:
> On 10/29/07, Bruce Snyder <br...@gmail.com> wrote:
> >
> > This sounds like Rake (http://rake.rubyforge.org/) to me. Is Buildr
> > just a customized Rake? How is Buildr any different than Rake?
>
>
> Buildr is Rake underneath, we started with Rake to handle all the task and
> dependency management, works very well and no point re-inventing the wheel.
>
> But using just Rake leads to a lot of boilerplate code.  Feeding classpath
> dependencie to javac, downloading and installing artifacts, running JUnit
> and producing test reports, packaging JARs and WARs, etc.
>
> Instead you get a high level abstraction based on projects, pre-configured
> tasks (like compile, test, package), and ad hoc tasks.  So Buildr takes care
> of all the detail work that's identical across projects, and also adds a
> large library of easy to use tasks.

Thanks for the information, Assaf :-).

Bruce
-- 
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Castor - http://castor.org/

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


Re: [VOTE] Accept project Buildr for incubation

Posted by Assaf Arkin <ar...@intalio.com>.
On 10/29/07, Bruce Snyder <br...@gmail.com> wrote:
>
> This sounds like Rake (http://rake.rubyforge.org/) to me. Is Buildr
> just a customized Rake? How is Buildr any different than Rake?


Buildr is Rake underneath, we started with Rake to handle all the task and
dependency management, works very well and no point re-inventing the wheel.

But using just Rake leads to a lot of boilerplate code.  Feeding classpath
dependencie to javac, downloading and installing artifacts, running JUnit
and producing test reports, packaging JARs and WARs, etc.

Instead you get a high level abstraction based on projects, pre-configured
tasks (like compile, test, package), and ad hoc tasks.  So Buildr takes care
of all the detail work that's identical across projects, and also adds a
large library of easy to use tasks.

Assaf

BTW, these are innocent questions for my own education. Please don't
> read anything into them.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache ServiceMix - http://servicemix.org/
> Apache Geronimo - http://geronimo.apache.org/
> Castor - http://castor.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [VOTE] Accept project Buildr for incubation

Posted by Bruce Snyder <br...@gmail.com>.
On 10/29/07, Matthieu Riou <ma...@offthelip.org> 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/%3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e
>
> [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.
>
> = Documentation & Intial Sources =
>
> The current Buildr website is at: http://buildr.rubyforge.org
> The Buildr sources are available at: http://www.intalio.org/buildr
>
> == External Dependencies ==
>
> External dependencies are one of the main concerns that will need to be
> addressed. Buildr relies on several packages that are licensed under the
> Ruby License, which hasn't been categorized yet as okay or not. We've
> already mentioned this on legal-discuss@a.o (see [1]). There are a few
> subtleties as well as the Ruby packaging system, RubyGems, doesn't require
> you to distribute any dependencies as it handles them for you. So we will
> have to figure out what the options are before the first incubator release
> and graduation.
>
> [1]
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200708.mbox/%3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e
>
> = Required Resources =
>
>  * buildr-private
>  * buildr-dev
>  * buildr-user
>
> Subversion Directory: [WWW]
> https://svn.apache.org/repos/asf/incubator/buildr
> Issue Tracking: JIRA
>
> = Initial Committers =
>
>  * Assaf Arkin (Intalio)
>  * Alex Boisvert (Intalio)
>  * Matthieu Riou (Intalio)
>
> == Champion ==
>
> Matthieu Riou
>
> == Mentors ==
>
> Volunteers please:
>
>  * Matthieu Riou <mriou AT apache.org>
>  * Yoav Shapira <yoavs at the usual for this wiki>
>
> = Sponsoring Entity =
>
> The final destination is still uncertain. If Buildr is successful, a TLP
> could make sense. So right now we would like to ask the Incubator PMC to
> sponsor Buildr.
>

This sounds like Rake (http://rake.rubyforge.org/) to me. Is Buildr
just a customized Rake? How is Buildr any different than Rake?

BTW, these are innocent questions for my own education. Please don't
read anything into them.

Bruce
-- 
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Castor - http://castor.org/

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


Re: [VOTE] Accept project Buildr for incubation

Posted by Craig L Russell <Cr...@Sun.COM>.
+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:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


Re: [VOTE] Accept project Buildr for incubation

Posted by Paul Fremantle <pz...@gmail.com>.
[ 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 <ro...@gmail.com> wrote:
>
> <snip>
>
> On Oct 29, 2007 9:29 PM, Matthieu Riou <ma...@offthelip.org> wrote:
>
> > [X] +1 Accept Buildr project for incubation
> > [ ] 0 Don't care
> > [ ] -1 Reject for the following reason :
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


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

blog: http://pzf.fremantle.org
paul@wso2.com

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

Re: [VOTE] Accept project Buildr for incubation

Posted by Robert Burrell Donkin <ro...@gmail.com>.
<snip>

On Oct 29, 2007 9:29 PM, Matthieu Riou <ma...@offthelip.org> wrote:

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

- robert

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


Re: [VOTE] Accept project Buildr for incubation

Posted by Bertrand Delacretaz <bd...@apache.org>.
On 10/29/07, Matthieu Riou <ma...@offthelip.org> wrote:

> ...Following up on the proposal discussed at [1] I'd like to call for a vote to
> incubate Buildr...

+1

-Bertrand

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


Re: [VOTE] Accept project Buildr for incubation

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Tuesday 30 October 2007 05:29, Matthieu Riou wrote:

> Please vote on accepting Buildr into the Apache Incubator. 
>
[x] +1 Accept Buildr project for incubation
[ ] 0 Don't care
[ ] -1 Reject for the following reason :

Cheers
Niclas

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


Re: [VOTE] Accept project Buildr for incubation

Posted by Erik Hatcher <er...@ehatchersolutions.com>.
+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/% 
> 3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e
>
> [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.
>
> = Documentation & Intial Sources =
>
> The current Buildr website is at: http://buildr.rubyforge.org
> The Buildr sources are available at: http://www.intalio.org/buildr
>
> == External Dependencies ==
>
> External dependencies are one of the main concerns that will need  
> to be
> addressed. Buildr relies on several packages that are licensed  
> under the
> Ruby License, which hasn't been categorized yet as okay or not. We've
> already mentioned this on legal-discuss@a.o (see [1]). There are a few
> subtleties as well as the Ruby packaging system, RubyGems, doesn't  
> require
> you to distribute any dependencies as it handles them for you. So  
> we will
> have to figure out what the options are before the first incubator  
> release
> and graduation.
>
> [1]
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/ 
> 200708.mbox/% 
> 3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e
>
> = Required Resources =
>
>  * buildr-private
>  * buildr-dev
>  * buildr-user
>
> Subversion Directory: [WWW]
> https://svn.apache.org/repos/asf/incubator/buildr
> Issue Tracking: JIRA
>
> = Initial Committers =
>
>  * Assaf Arkin (Intalio)
>  * Alex Boisvert (Intalio)
>  * Matthieu Riou (Intalio)
>
> == Champion ==
>
> Matthieu Riou
>
> == Mentors ==
>
> Volunteers please:
>
>  * Matthieu Riou <mriou AT apache.org>
>  * Yoav Shapira <yoavs at the usual for this wiki>
>
> = Sponsoring Entity =
>
> The final destination is still uncertain. If Buildr is successful,  
> a TLP
> could make sense. So right now we would like to ask the Incubator  
> PMC to
> sponsor Buildr.


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


Re: [VOTE] Accept project Buildr for incubation

Posted by Brett Porter <br...@gmail.com>.
+1

On 30/10/2007, Matthieu Riou <ma...@offthelip.org> 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/%3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e
>
> [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.
>
> = Documentation & Intial Sources =
>
> The current Buildr website is at: http://buildr.rubyforge.org
> The Buildr sources are available at: http://www.intalio.org/buildr
>
> == External Dependencies ==
>
> External dependencies are one of the main concerns that will need to be
> addressed. Buildr relies on several packages that are licensed under the
> Ruby License, which hasn't been categorized yet as okay or not. We've
> already mentioned this on legal-discuss@a.o (see [1]). There are a few
> subtleties as well as the Ruby packaging system, RubyGems, doesn't require
> you to distribute any dependencies as it handles them for you. So we will
> have to figure out what the options are before the first incubator release
> and graduation.
>
> [1]
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200708.mbox/%3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e
>
> = Required Resources =
>
>  * buildr-private
>  * buildr-dev
>  * buildr-user
>
> Subversion Directory: [WWW]
> https://svn.apache.org/repos/asf/incubator/buildr
> Issue Tracking: JIRA
>
> = Initial Committers =
>
>  * Assaf Arkin (Intalio)
>  * Alex Boisvert (Intalio)
>  * Matthieu Riou (Intalio)
>
> == Champion ==
>
> Matthieu Riou
>
> == Mentors ==
>
> Volunteers please:
>
>  * Matthieu Riou <mriou AT apache.org>
>  * Yoav Shapira <yoavs at the usual for this wiki>
>
> = Sponsoring Entity =
>
> The final destination is still uncertain. If Buildr is successful, a TLP
> could make sense. So right now we would like to ask the Incubator PMC to
> sponsor Buildr.
>


-- 
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/

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


Re: [VOTE] Accept project Buildr for incubation

Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 29 Oct 2007, Matthieu Riou <ma...@offthelip.org> wrote:

> Following up on the proposal discussed at [1] I'd like to call for a
> vote to incubate Buildr.

+1

Stefan

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


Re: [VOTE] Accept project Buildr for incubation

Posted by Yoav Shapira <yo...@apache.org>.
Hey,

On Oct 29, 2007 5:29 PM, Matthieu Riou <ma...@offthelip.org> wrote:
> 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 :

Yoav

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


Re: [VOTE] Accept project Buildr for incubation

Posted by Niklas Gustavsson <ni...@protocol7.com>.
+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/%3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e
> 
> [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.
> 
> = Documentation & Intial Sources =
> 
> The current Buildr website is at: http://buildr.rubyforge.org
> The Buildr sources are available at: http://www.intalio.org/buildr
> 
> == External Dependencies ==
> 
> External dependencies are one of the main concerns that will need to be
> addressed. Buildr relies on several packages that are licensed under the
> Ruby License, which hasn't been categorized yet as okay or not. We've
> already mentioned this on legal-discuss@a.o (see [1]). There are a few
> subtleties as well as the Ruby packaging system, RubyGems, doesn't require
> you to distribute any dependencies as it handles them for you. So we will
> have to figure out what the options are before the first incubator release
> and graduation.
> 
> [1]
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200708.mbox/%3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e
> 
> = Required Resources =
> 
>  * buildr-private
>  * buildr-dev
>  * buildr-user
> 
> Subversion Directory: [WWW]
> https://svn.apache.org/repos/asf/incubator/buildr
> Issue Tracking: JIRA
> 
> = Initial Committers =
> 
>  * Assaf Arkin (Intalio)
>  * Alex Boisvert (Intalio)
>  * Matthieu Riou (Intalio)
> 
> == Champion ==
> 
> Matthieu Riou
> 
> == Mentors ==
> 
> Volunteers please:
> 
>  * Matthieu Riou <mriou AT apache.org>
>  * Yoav Shapira <yoavs at the usual for this wiki>
> 
> = Sponsoring Entity =
> 
> The final destination is still uncertain. If Buildr is successful, a TLP
> could make sense. So right now we would like to ask the Incubator PMC to
> sponsor Buildr.
> 


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


[RESULT] [VOTE] Accept project Buildr for incubation

Posted by Matthieu Riou <ma...@offthelip.org>.
Forgot to change the mail subject to [RESULT], posting again for the benefit
of filters and archives.

Thanks,
Matthieu

On Nov 1, 2007 1:17 PM, Matthieu Riou <ma...@offthelip.org> wrote:

> Hi,
>
> With 18 positive votes including 14 binding votes and no -1, Buildr is
> accepted as an Incubator project. +1 votes were registered from:
>
> Martijn Dashorst
> Eelco Hillenius
> Noel J. Bergman
> Niclas Hedhman
> Yoav Shapira
> Stefan Bodewig
> Bertrand Delacretaz
> Gilles Scokart
> Erik Hatcher
> Jim Jagielski
> Robert Burrel Donkin
> Paul Fremantle
> J. Aaron Farr
> Craig L. Russel
> Niklas Gustavsson
> Ant Elder
> Brett Porter
> Doug Cutting
>
> I'll start working with the other mentors, the committers and infra to get
> things going.
>
> Thanks for all your votes!
> Matthieu
>
>
> On Oct 29, 2007 2:29 PM, Matthieu Riou < matthieu@offthelip.org> 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/%3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e
> >
> > [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.
> >
> > = Documentation & Intial Sources =
> >
> > The current Buildr website is at: http://buildr.rubyforge.org
> > The Buildr sources are available at: http://www.intalio.org/buildr
> >
> > == External Dependencies ==
> >
> > External dependencies are one of the main concerns that will need to be
> > addressed. Buildr relies on several packages that are licensed under the
> > Ruby License, which hasn't been categorized yet as okay or not. We've
> > already mentioned this on legal-discuss@a.o (see [1]). There are a few
> > subtleties as well as the Ruby packaging system, RubyGems, doesn't require
> > you to distribute any dependencies as it handles them for you. So we will
> > have to figure out what the options are before the first incubator release
> > and graduation.
> >
> > [1] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200708.mbox/%3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e
> >
> >
> > = Required Resources =
> >
> >  * buildr-private
> >  * buildr-dev
> >  * buildr-user
> >
> > Subversion Directory: [WWW] https://svn.apache.org/repos/asf/incubator/buildr
> >
> > Issue Tracking: JIRA
> >
> > = Initial Committers =
> >
> >  * Assaf Arkin (Intalio)
> >  * Alex Boisvert (Intalio)
> >  * Matthieu Riou (Intalio)
> >
> > == Champion ==
> >
> > Matthieu Riou
> >
> > == Mentors ==
> >
> > Volunteers please:
> >
> >  * Matthieu Riou <mriou AT apache.org>
> >  * Yoav Shapira <yoavs at the usual for this wiki>
> >
> > = Sponsoring Entity =
> >
> > The final destination is still uncertain. If Buildr is successful, a TLP
> > could make sense. So right now we would like to ask the Incubator PMC to
> > sponsor Buildr.
> >
> >
> >
>

Re: [VOTE] Accept project Buildr for incubation

Posted by Matthieu Riou <ma...@offthelip.org>.
Hi,

With 18 positive votes including 14 binding votes and no -1, Buildr is
accepted as an Incubator project. +1 votes were registered from:

Martijn Dashorst
Eelco Hillenius
Noel J. Bergman
Niclas Hedhman
Yoav Shapira
Stefan Bodewig
Bertrand Delacretaz
Gilles Scokart
Erik Hatcher
Jim Jagielski
Robert Burrel Donkin
Paul Fremantle
J. Aaron Farr
Craig L. Russel
Niklas Gustavsson
Ant Elder
Brett Porter
Doug Cutting

I'll start working with the other mentors, the committers and infra to get
things going.

Thanks for all your votes!
Matthieu

On Oct 29, 2007 2:29 PM, Matthieu Riou < matthieu@offthelip.org> 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/%3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e
>
> [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.
>
> = Documentation & Intial Sources =
>
> The current Buildr website is at: http://buildr.rubyforge.org
> The Buildr sources are available at: http://www.intalio.org/buildr
>
> == External Dependencies ==
>
> External dependencies are one of the main concerns that will need to be
> addressed. Buildr relies on several packages that are licensed under the
> Ruby License, which hasn't been categorized yet as okay or not. We've
> already mentioned this on legal-discuss@a.o (see [1]). There are a few
> subtleties as well as the Ruby packaging system, RubyGems, doesn't require
> you to distribute any dependencies as it handles them for you. So we will
> have to figure out what the options are before the first incubator release
> and graduation.
>
> [1] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200708.mbox/%3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e
>
>
> = Required Resources =
>
>  * buildr-private
>  * buildr-dev
>  * buildr-user
>
> Subversion Directory: [WWW] https://svn.apache.org/repos/asf/incubator/buildr
>
> Issue Tracking: JIRA
>
> = Initial Committers =
>
>  * Assaf Arkin (Intalio)
>  * Alex Boisvert (Intalio)
>  * Matthieu Riou (Intalio)
>
> == Champion ==
>
> Matthieu Riou
>
> == Mentors ==
>
> Volunteers please:
>
>  * Matthieu Riou <mriou AT apache.org>
>  * Yoav Shapira <yoavs at the usual for this wiki>
>
> = Sponsoring Entity =
>
> The final destination is still uncertain. If Buildr is successful, a TLP
> could make sense. So right now we would like to ask the Incubator PMC to
> sponsor Buildr.
>
>
>

Re: [VOTE] Accept project Buildr for incubation

Posted by Erik Hatcher <er...@ehatchersolutions.com>.
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 <http://lucene.jugem.jp/?cid=15>

      :)

   Erik



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


Re: [VOTE] Accept project Buildr for incubation

Posted by Matthieu Riou <ma...@offthelip.org>.
On 10/30/07, J Aaron Farr <fa...@apache.org> wrote:
>
>
> Jim Jagielski <ji...@jaguNET.com> 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: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [VOTE] Accept project Buildr for incubation

Posted by J Aaron Farr <fa...@apache.org>.
Jim Jagielski <ji...@jaguNET.com> 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: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [VOTE] Accept project Buildr for incubation

Posted by Matthieu Riou <ma...@offthelip.org>.
On 10/30/07, Jim Jagielski <ji...@jagunet.com> 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: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [VOTE] Accept project Buildr for incubation

Posted by Jim Jagielski <ji...@jaguNET.com>.
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: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [VOTE] Accept project Buildr for incubation

Posted by Matthieu Riou <ma...@offthelip.org>.
On 10/29/07, Noel J. Bergman <no...@devtech.com> 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.


For the Java runtime aspect of it, we've been thinking of JRuby. There are
still a couple of hurdles but JRuby is maturing quickly and it should very
soon be good enough to run Buildr (for the curious, the problem is actually
needles). But performance is still and I think will remain an issue: when
you've experienced the instantaneous startup of CRuby, the JVM feels pretty
slow to load. But that's a trade-off and JRuby support will probably make a
lot of people happy.

As for Groovy vs. JRuby, language wars... :)

Matthieu


        --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

RE: [VOTE] Accept project Buildr for incubation

Posted by Gilles Scokart <gs...@gmail.com>.
+1 (non-binding)

Gilles

> -----Original Message-----
> From: matthieu.riou@gmail.com [mailto:matthieu.riou@gmail.com] On Behalf Of Matthieu Riou
> Sent: lundi 29 octobre 2007 22:30
> To: general@incubator.apache.org
> Subject: [VOTE] Accept project Buildr for incubation
> 
> 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/%3cfbdc6a970710231604k2740d83ap50d913927c858da1@mail.gmail.com%3e
> 
> [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.
> 
> = Documentation & Intial Sources =
> 
> The current Buildr website is at: http://buildr.rubyforge.org
> The Buildr sources are available at: http://www.intalio.org/buildr
> 
> == External Dependencies ==
> 
> External dependencies are one of the main concerns that will need to be
> addressed. Buildr relies on several packages that are licensed under the
> Ruby License, which hasn't been categorized yet as okay or not. We've
> already mentioned this on legal-discuss@a.o (see [1]). There are a few
> subtleties as well as the Ruby packaging system, RubyGems, doesn't require
> you to distribute any dependencies as it handles them for you. So we will
> have to figure out what the options are before the first incubator release
> and graduation.
> 
> [1]
> http://mail-archives.apache.org/mod_mbox/www-legal-
> discuss/200708.mbox/%3cfbdc6a970708291553r5a654ceald71212750e8aeaf7@mail.gmail.com%3e
> 
> = Required Resources =
> 
>  * buildr-private
>  * buildr-dev
>  * buildr-user
> 
> Subversion Directory: [WWW]
> https://svn.apache.org/repos/asf/incubator/buildr
> Issue Tracking: JIRA
> 
> = Initial Committers =
> 
>  * Assaf Arkin (Intalio)
>  * Alex Boisvert (Intalio)
>  * Matthieu Riou (Intalio)
> 
> == Champion ==
> 
> Matthieu Riou
> 
> == Mentors ==
> 
> Volunteers please:
> 
>  * Matthieu Riou <mriou AT apache.org>
>  * Yoav Shapira <yoavs at the usual for this wiki>
> 
> = Sponsoring Entity =
> 
> The final destination is still uncertain. If Buildr is successful, a TLP
> could make sense. So right now we would like to ask the Incubator PMC to
> sponsor Buildr.


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


Re: [VOTE] Accept project Buildr for incubation

Posted by Erik Hatcher <er...@ehatchersolutions.com>.
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: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org


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


RE: [VOTE] Accept project Buildr for incubation

Posted by "Noel J. Bergman" <no...@devtech.com>.
+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: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org