Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
MIME-Version: 1.0
In-Reply-To: <op.yt9mp1w14ntv07@desktop-v42f38k>
References: <op.yt9kfpca4ntv07@desktop-v42f38k> <CAEWfVJmEh3=jeNFN79QP2Nq02XB3dd0AHfXNR9sLpXOruShDnA@mail.gmail.com>
 <op.yt9mp1w14ntv07@desktop-v42f38k>
From: David Nalley <david@gnsa.us>
Date: Wed, 18 Jan 2017 18:01:39 -0500
Message-ID: <CAKprHVYu_xNnQU9pKUBDvtzug_HHt+wqBQwngRYgKHiAUAQSmQ@mail.gmail.com>
Subject: Re: Working Ecosystems at ASF
To: dev@community.apache.org
Content-Type: text/plain; charset=UTF-8
archived-at: Wed, 18 Jan 2017 23:02:06 -0000

On Wed, Jan 18, 2017 at 9:33 AM, Raphael Bircher
<rbircherapache@gmail.com> wrote:
> Hi Bertrand
>
> Am .01.2017, 15:03 Uhr, schrieb Bertrand Delacretaz
> <bdelacretaz@apache.org>:
>
>> Hi Raphael,
>>
>> On Wed, Jan 18, 2017 at 2:44 PM, Raphael Bircher
>> <rbircherapache@gmail.com> wrote:
>>>
>>> ...Has anybody ever used crowd funding to cover development costs?...
>>
>>
>> I know of one documented case,
>> http://community.apache.org/committers/funding-disclaimer.html but I
>> don't have info on how well it went.
>>
>> The disclaimer was important to properly dissociate such initiatives
>> form the ASF, which does not fund software development.
>
>
> Thanks for the link. This rise a question, i got never a real answer for it.
> Why ASF dosen't found Developers?. Some people say, because to non-profit
> status. Others say, this are our rules. But what are the reasons behind. It
> would be nice, if someone take the time to explain this.
>

Resources and positions are always limited.
Hiring a developer and deciding what they are going to work on means
you are essentially picking what is important to the Foundation. The
ASF has long said that it is happy to pick runners not winners. That
means that we are happy for projects, even projects that compete with
each other, to call the ASF home. We hope they are all successful, but
we are essentially letting the community decide where to allocate its
time. When you pay people, you have to decide what they are going to
work on, and even what specific aspects of that project that they are
going to work on. This means someone who controls the payroll can
decide which of two competing projects gets more resources, and
potentially even effect the direction that they are headed in
technically.

It also has the side effect of creating a division between the
developers paid by the ASF and those who aren't. (Read that as the
privileged developers, and the the unprivileged developers.) Today,
everyone (in the eyes of the ASF) is on equal footing because no
developer is employed by the ASF to work on code at the ASF.

Finally - we frankly don't have the money to do so.


--David

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org