On Fri, Sep 26, 2008 at 5:58 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 26, 2008 at 6:23 AM, Jim Jagielski <[EMAIL PROTECTED]> wrote: > > > > On Sep 23, 2008, at 9:50 PM, Assaf Arkin wrote: > > > >> > >> On Sep 23, 2008, at 6:17 PM, "Tal Rotbart" <[EMAIL PROTECTED]> wrote: > >> > >>> "... that the Apache Buildr project be responsible for the creation > >>> and maintenance of a scripting-based build system based on the > >>> principles of DRY, DIY and doesn't make you cry." > >>> > >>> :-P > >> > >> +1 > >> > > > > We can't really be serious about that, right? > > I don't have a problem injecting a bit of humor. Software should be, > besides all the other boring requirements, also fun to use, enjoyable, > something you look forward to on a Monday morning. > I'm fine with humor too but the charter will stick around for quite a while (as long as possible actually) and there are some jokes that tend to grow old. So I liked the first version better: "... that the Apache Buildr project be responsible for the creation and maintenance of a scripting-based build system based on the principles of DRY (Don't Repeat Yourself), convenience and flexibility." Maybe the "convenience and flexibility" could be replaced by something a bit more focused but until that I like it. Is "agile" too overloaded? Matthieu > It should also have a philosophy, and a good charter would focus on > what the software is, rather than what it does. BTW right now > Buildr's tagline is "a build system that doesn't suck". > > Assaf > > > > > In general, the charter should not be recursive, but also > > not so detailed that the project can't grow. > > > > How about: > > > > a scripting-based build system for applications with > > sophisticated dependency management. > > > > ?? > > > > >
