The 'Low ~Profit' Model is interesting in this regard also
http://www.niemanlab.org/2009/08/whats-keeping-news-organizations-from-trying-the-low-profit-model/

Should apply to open-source software development even better in some ways.

Regards,
NMM


2009/8/20 Nico Morrison <[email protected]>

> Sorry tom Morris, I agree with you - I meant donation models are not
> counted in the academic paper by Dirk Riehle AFAIK.
>
> I personally think donations are the way to go and that small is beautiful.
> I LIKE the idea of people writing the Linux kernel code outside of company
> hours. I am appalled that a coder can approve his or her own patch.
> Interesting stuff.
>
> Regards,
> Nico Morrison
>
>
> 2009/8/20 Tom Morris <[email protected]>
>
> On Thu, Aug 20, 2009 at 07:28, Nico Morrison<[email protected]> wrote:
>> > MySQL since it's acquisition by Oracle/Sun  doesn't seem a good example.
>> I
>> > do not know the others listed in the academic article. Donation models
>> do
>> > not count.
>> >
>>
>> In the Ruby community, the core developers of JRuby were employed from
>> 2006 through 2009. Now they are employed by Engine Yard, a Ruby on
>> Rails hosting company. At least one IronRuby developer is employed by
>> Microsoft. Mono has been heavily supported by Novell, I think.
>>
>> This would seem to be the primary method of doing open source
>> commercially: large companies finding that having certain projects
>> mature and production-ready are beneficial to selling servers or
>> operating systems or IDEs or whatever it is they sell, so employ the
>> people who work on those projects to make them better. This is sort of
>> a 'donation model', but donation doesn't have quite the same
>> connotation as a full-time employed position.
>>
>> --
>> Tom Morris
>> http://tommorris.org/
>>
>> -
>> Sent via the backstage.bbc.co.uk discussion group.  To unsubscribe,
>> please visit
>> http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
>>  Unofficial list archive:
>> http://www.mail-archive.com/[email protected]/
>>
>
>

Reply via email to