Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of roberto.galoppini@gmail.com
 designates 209.85.192.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <520DF1D0.30606@cord.dk>
References: <520D17A6.2080603@rcbowen.com>
	<520DF1D0.30606@cord.dk>
Date: Fri, 16 Aug 2013 14:22:01 +0200
Message-ID: 
 <CAGNcyf_T7HdxR0XhDm-KBSxUKEfPq6rw_=yk4JRBd0vavkej1A@mail.gmail.com>
Subject: Re: Contacting other Apache projects
From: Roberto Galoppini <roberto.galoppini@gmail.com>
To: allura-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b6d7a1048d07804e40fa3de

--047d7b6d7a1048d07804e40fa3de
Content-Type: text/plain; charset=ISO-8859-1

2013/8/16 Daniel Gruno <rumble@cord.dk>

> 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.
>

Daniel would you be open to draft a message in this sense? Given your
experience with Apache projects and your knowledge of Allura I believe
you'd be able to capture the essence of what matters most to Apache folks.

On a separate line of thoughts I'd be interested in learning your ideas
about how heatbeats and allura could be integrated.

Roberto


>
> 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.
>

--047d7b6d7a1048d07804e40fa3de--