1,784
edits
Changes
Jump to navigation
Jump to search
New page: thumb|none|not really me I'm a volunteer member of the Sugarlabs team. Until February 2008, I was a full time volunteer developer at OLPC. My job was hacking X, the...
[[Image:Bernie.png|thumb|none|not really me]]
I'm a volunteer member of the Sugarlabs team.
Until February 2008, I was a full time volunteer developer at OLPC. My job was hacking X, the base Fedora OS, the Linux kernel, some i18n and input work. Later on, until April 2008, I was CTO of OLPC Europe and traveled around to present our project to government officials and dignitaries.
e-mail: bernie AT codewiz DOT org
Personal homepage: http://www.codewiz.org/
Old OLPC projects: http://www.codewiz.org/wiki/OneLaptopPerChild
== Why we should be more open ==
(I wrote the following note in 2007 while still working at 1cc)
Openness will be our greatest and most lasting strength. If we shy away
from it now it will never return.
-- [[User:SJ|Samuel Klein]]
"We should be more open" may strike many as a surprising suggestion
for OLPC, since it's already supposed to be one of the most open
projects out there.
But opening just the source without opening the rest of the
development process is a recurring pitfall in which even
large corporates such as RedHat and Sun all fell, initially.
I see us likely to fall into the same circular thinking that
"trying to involve external contributors does not pay off
because so far we've got so little external contributions".
And I've heard the argument that "working on our platform would
be too hard for outside contributors". This can't possibly be
true: projects like OpenWRT and the Linux kernel and dozens of
RTOS projects out there regularly attract flocks of hackers who
are very capable of working on all kinds of fancy and undocumented
hardware and exotic OSes, with great results.
My access point can now play MP3s :-)
I'm a volunteer member of the Sugarlabs team.
Until February 2008, I was a full time volunteer developer at OLPC. My job was hacking X, the base Fedora OS, the Linux kernel, some i18n and input work. Later on, until April 2008, I was CTO of OLPC Europe and traveled around to present our project to government officials and dignitaries.
e-mail: bernie AT codewiz DOT org
Personal homepage: http://www.codewiz.org/
Old OLPC projects: http://www.codewiz.org/wiki/OneLaptopPerChild
== Why we should be more open ==
(I wrote the following note in 2007 while still working at 1cc)
Openness will be our greatest and most lasting strength. If we shy away
from it now it will never return.
-- [[User:SJ|Samuel Klein]]
"We should be more open" may strike many as a surprising suggestion
for OLPC, since it's already supposed to be one of the most open
projects out there.
But opening just the source without opening the rest of the
development process is a recurring pitfall in which even
large corporates such as RedHat and Sun all fell, initially.
I see us likely to fall into the same circular thinking that
"trying to involve external contributors does not pay off
because so far we've got so little external contributions".
And I've heard the argument that "working on our platform would
be too hard for outside contributors". This can't possibly be
true: projects like OpenWRT and the Linux kernel and dozens of
RTOS projects out there regularly attract flocks of hackers who
are very capable of working on all kinds of fancy and undocumented
hardware and exotic OSes, with great results.
My access point can now play MP3s :-)