On Sun, Jul 19, 2009 at 9:35 PM, Alex Boisvert <[email protected]> wrote:
> Yes, some of this could be reused and reformulated for the FAQ, although > the > intent here is to focus on the core ideas behind Buildr. FAQs tend to > address questions over a wider range of importance. This list is also > different from a marketing feature list where you're selling the software, > so I would leave out smart defaults and support for multiple languages from > the list, unless there's something fundamental about them that would help > people better reason about how Buildr works. Speaking of FAQ: http://inquiryapp.com/ Assaf > > > alex > > > On Sun, Jul 19, 2009 at 12:02 PM, Daniel Spiewak <[email protected] > >wrote: > > > Cool! I think this should be fleshed out slightly and turned into a part > > of > > the yet-to-be-realized FAQ. Two items I would like to see in the list > are > > "Buildr is Smart", meaning that it has a set of sensible defaults; and > > something about its first-class support for more than one language. I'm > > still firmly of the opinion that Buildr is the best build system for > Scala, > > and I think we need to advertise that a bit. :-) > > > > Daniel > > > > On Fri, Jul 17, 2009 at 9:28 PM, Alex Boisvert <[email protected]> > > wrote: > > > > > Inspired by our recent discussions about documentation, FAQ and Scott > > > Adams' > > > Rule of Twelve <http://www.dilbert.com/blog/entry/rule_of_twelve>, I > > > decided > > > to draft a list of 12 Things to Know About > > > Buildr< > > > > > > http://cwiki.apache.org/confluence/display/BUILDR/12+Things+to+Know+About+Buildr > > > >. > > > > > > > > > The last few ones are sort of fillers for the time being... Can you > > think > > > of better or additional important things to know? > > > > > > alex > > > > > >
