community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hadrian Zbarcea <hzbar...@gmail.com>
Subject Re: Working Ecosystems at ASF
Date Thu, 19 Jan 2017 02:48:07 GMT
David, your answer gets 5 stars from me.

On the funding piece we didn't even try because we don't want to go 
there. It's not really a cause, more like an effect.

Cheers,
Hadrian


On 01/18/2017 06:01 PM, David Nalley wrote:
> 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
>

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


Mime
View raw message