[IAEP] Working with a commercial entity.
Tomeu Vizoso
tomeu at tomeuvizoso.net
Wed May 19 04:42:23 EDT 2010
On Wed, May 19, 2010 at 09:12, Jonas Smedegaard <dr at jones.dk> wrote:
> On Tue, May 18, 2010 at 02:13:34AM -0400, Bernie Innocenti wrote:
>>
>> El Mon, 17-05-2010 a las 18:19 -0400, Martin Langhoff escribió:
>>>
>>> On Mon, May 17, 2010 at 6:04 PM, Christoph Derndorfer
>>> <e0425826 at student.tuwien.ac.at> wrote:
>>> > "Done critically, creatively, and transparently, voluntary free >
>>> > software projects
>>>
>>> There is a bit of misdirection in there. Projects are rarely defined as a
>>> "voluntary free software project". IMHE successful long term projects have
>>> diverse group of developers with diverse driving forces.
>>
>> +1024.
>>
>> Kernel development was once led entirely by volunteers and is now largely
>> accomplished by employees of large corporates.
>>
>> What did never change throughout 15 years of successful kernel development
>> is that developers come from a variety of industries, bringing wildly
>> different ideas while trying to reach the most disparate objectives. No
>> single entity controls Linux development exclusively, making it the de-facto
>> industry standard for almost any new device being engineered.
>>
>> Before, the idea of a single kernel which could run on thousands of
>> architectures ranging from tiny access points to supercomputers was simply
>> unthinkable.
>>
>> Sugar needs to do the same: diversify its contributors by engaging
>> volunteers, commercial entities, governments, non-profits, academic
>> institutions... and of course deployments.
>>
>> Giving up centralized control is key to success in distributed
>> development.
>
> I wholeheartedly agree with all of above.
>
> My concern was one of transparency. Noone else has a concern about that
> apparently, which is (hopefully) comforting...
I don't think we can expect that everybody will talk about Sugar only
in the designated public spaces, so maybe the best we can do is to
have processes that give everybody a chance to be informed of changes
in advanced, allow everybody to participate in the discussion, etc.
The problem is that having those processes requires that people
understand why they have to follow them instead of holding ad-hoc
discussions and also that somebody manage it. For example, now we have
the release manager role vacant.
Regards,
Tomeu
>
> - Jonas
>
> --
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136 Website: http://dr.jones.dk/
>
> [x] quote me freely [ ] ask before reusing [ ] keep private
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQIcBAEBCgAGBQJL849vAAoJECx8MUbBoAEhs0sP/A8yAveWd7D4tHgTuFno8zj2
> AuCBIiecuN9FRLxyQI4TqppCP5zpggYTaeFiU26yNWQN2Y0L4borrl7C79C8S1x6
> i5MyaTJWdoPC5k3d7bKSfHQO131etT5Iz9Zuy+PVuhbTyzGZrG4qWjVWPlqU9JOp
> e1drvu9Dilw05mr3gGuqGt3chq0SIJlczr2fXc6NUVmw4t4ue3bpZrkZZKD6pGVZ
> BwMX0AQkLhtKYvDzBriG1AuSfP5AmkSz79vI47GGCDHy2MY7bq66Z4MzF9uVVMUY
> 0Wwwb21j2I+iMSuLSLNKb4+QileeEL359rbY4R/ZjWtzpVJ5cJXadHDUOEkQHkI6
> 3GQP7dDeIu9Vjwd6/Thmuo3UBWQAgDJY5E36jEjngARDNYIbUOCFNzD9pE+lgRYd
> sQPUAgAtD+RSblPR7DC6UuKS9W3LaEVjjdfA+vS1gBkeYQ9gJGkpJ9fboRZPtAj5
> tQ6gCruvugwdKi4WWebx2kqSmPSSgOBSO6kBqL6kpyPoRGI1hJYDVxK2tGl11wuP
> ThExZxC3dJYy5jRQl6XV5JM7PFPfy5O6C16/CHB2jcpZciMnFajueVrh7tgzZAlC
> eFA49MP9JtCyfovhuo2a5PNZs3iiL+f9RDnmfMIUSt5XJN/tcuFGUAtBnhKGajD9
> D6Zotr0IUeVlncfaC6pk
> =T5rM
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
More information about the IAEP
mailing list