On 08/15/2013 08:02 PM, Rich Bowen wrote: > Oone of the compelling things about the Allura project is that it > provides a unified software forge, while Apache projects tend to operate > with a loosely coupled (or completely uncoupled) set of tools to develop > their code. > > While one is usually reluctant to spam the entire committer@ list with > ... well, with anything ... It's been done before (I did it once, not too long ago) and with great success. People tend to be positive towards receiving such mails, if they are well crafted and explain exactly _why_ projects would benefit from using this software.
> it may be useful to send a (well written) > message to committers@ that says: > > 1) Here's what Allura does. If you're going to send to committers@, I'd put emphasis on what it does _for projects such as Apache projects_, and not so much on _everything it does_. So emphasis on collaboration (and exactly how this is achieved, 'cause we know Allura is kind'a good at that ;) ) would be a good thing. As you said in the beginning, it's a unified software forge, which means people won't have to ask infra for 17378 different tools every time they set up a new project or migrate from podling to TLP, so maybe but some of that in as a compelling argument. > > 2) Here's the kind of things we hope Allura does in the coming N months. > > 3) What kinds of tools would you, as a committer on the Apache Foo > project, like to see in a forge style tool, or are you completely > content with the status quo in Apache development tools? > > > Thoughts? > > With regards, Daniel.
