From general-return-16338-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org Tue Oct 30 22:17:39 2007 Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 8975 invoked from network); 30 Oct 2007 22:17:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Oct 2007 22:17:38 -0000 Received: (qmail 96311 invoked by uid 500); 30 Oct 2007 22:17:24 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 96162 invoked by uid 500); 30 Oct 2007 22:17:23 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 96151 invoked by uid 99); 30 Oct 2007 22:17:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2007 15:17:23 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of brett.porter@gmail.com designates 209.85.198.187 as permitted sender) Received: from [209.85.198.187] (HELO rv-out-0910.google.com) (209.85.198.187) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2007 22:17:24 +0000 Received: by rv-out-0910.google.com with SMTP id k20so2045053rvb for ; Tue, 30 Oct 2007 15:17:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=BtgdMb/nm0THxm/cnlSB1nOyMwJpdTpzQqfHgqZu52c=; b=oO4ah2e1tKcR/J7r3I/P9vnGqmcyYIZJ9D5h+BPX0fL3Gt/FyaMhzEnT89tr/Uto4lIT2ODN5ARirGTwmiNjuVaR+MHpp80NSi/Yhug6nJvvcsXPH9vO2bl9sr3WRTxE/JRdkVGU5QTvsAm0vFW69xgFCemcwAByYomJuhqX9B0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EWGuU4dlffozN7Yb8iz/RQ204qCGn7iaolB0jhwUDrxhyNaGOqfLTCM13e+M/1/4IkwbVKZdpOCo6TM8kCwhjO4HYvNXsdgCFyqu8eYzWOunwWzmLnQGA1284mY2EVJlOQ/EQPHsYyegcyq6D6p9fyteFOGXzaPYNDuEI+d5VfM= Received: by 10.141.205.10 with SMTP id h10mr3633298rvq.1193782621986; Tue, 30 Oct 2007 15:17:01 -0700 (PDT) Received: by 10.141.5.21 with HTTP; Tue, 30 Oct 2007 15:17:01 -0700 (PDT) Message-ID: <9e3862d80710301517l312887d7m5aee827b9672f15e@mail.gmail.com> Date: Wed, 31 Oct 2007 09:17:01 +1100 From: "Brett Porter" To: general@incubator.apache.org Subject: Re: [VOTE] Accept project Buildr for incubation In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org +1 On 30/10/2007, 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 > * Yoav Shapira > > = 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