Hey Paul, Sounds like Buildr sparked an impassioned reaction in you :)
I agree there's a whole lot of software around build, continuous integration, configuration/lifecycle management that could suck less. We're not "stopping here" but Buildr's scope is relatively well defined at the moment, although as an Apache TLP, we can certainly grow in any of the different directions you mentioned. I probably don't need to tell you this but what's needed, beyond vision, is typically one (sometimes two) very motivated individual to lay the foundation for that expansion in such a way that will incite other people to join. There needs to be a critical mass of software written up-front to kick-start things. No roadmap or vision can replace that. And it's not a sufficient condition to guarantee traction -- merely a necessary one. The good news is there's a good likelihood you'll find interested people and, perhaps, some who share your passion and ambitions in this community. With some luck, they might even have a lot of free time too :) I certainly encourage you to pursue this. If something comes out of it and the conditions are right, I believe Buildr would be a great community to host the project(s). Just be prepared for what sounds like a fairly engaged and arduous journey. Bootstrapping open-source projects can require a lot of effort and dedication; even more so for projects not directly tied to developer's itch. cheers and welcome! alex On Thu, Jun 10, 2010 at 9:07 PM, Paul Kramer <[email protected]> wrote: > Hey Folks, > > You are doing something I think is great work in Buildr. But why stop so > short. > > I'm my mind, all of the infrastructure should be developed with rapid > development in mind. To me that equates to Python/Django and Ruby/Rails, and > not only that. There is HUGE opportunity in the embedded space. Look at the > rapid growth of the mobile market. The folks in this space are looking > around and what do they see. Lots of Java based tools (cruise-control, > hudson, teamcity, and on and on). That java stuff does not fit into that > space at all. > > So why stop short with Buildr. Buildr could easily be extended to provide > its own continuous integration, done in ruby/rails of course. > > Consider the following: http://qbal.mozdev.org/ circa 1999-2000 > http://qbal.mozdev.org/oldQbal.jpeg This was a proof of concept based on > earlier work I've done. It was 100% javascript. I'm going to ramp this stuff > up again, but this time I want to use ruby/rails/javascript > > Here is the thing. I've been doing this stuff for a long long time. You can > take a moment to look at www.qbalsoftware.com to get an idea of my > background. I'd like to start collaborating on some solutions that turn > things upside down and produce some results that help teams fly! > > Let me know if you are interested in talking further. > > Regards -- Kramer > > I live in Mt View (silicon valley) and this is my wing-man Cosmo. > > > > > > > > > > > > > >
