Difference between revisions of "User:Bernie"
| Line 13: | Line 13: | ||
== Why we should be more open == | == Why we should be more open == | ||
| − | (I wrote the following note in 2007 while still working at 1cc) | + | (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 | Openness will be our greatest and most lasting strength. If we shy away | ||
| Line 23: | Line 23: | ||
projects out there. | projects out there. | ||
| − | But opening just the source without opening the rest of the | + | But opening just the source code without opening the rest of the |
| − | development process is a recurring pitfall in which even | + | development process to the community is a recurring pitfall in which |
| − | large corporates such as RedHat and Sun all fell, initially. | + | even large corporates such as RedHat and Sun all fell, initially. |
I see us likely to fall into the same circular thinking that | I see us likely to fall into the same circular thinking that | ||
"trying to involve external contributors does not pay off | "trying to involve external contributors does not pay off | ||
| − | because so far we've got so little external contributions". | + | because, so far, we've got so little external contributions". |
| − | + | I've heard the argument that "working on our platform would | |
be too hard for outside contributors". This can't possibly be | be too hard for outside contributors". This can't possibly be | ||
true: projects like OpenWRT and the Linux kernel and dozens of | true: projects like OpenWRT and the Linux kernel and dozens of | ||
Revision as of 08:41, 19 August 2008
- Personal homepage: http://www.codewiz.org/
- e-mail: bernie AT codewiz DOT org
- IRC: _bernie, hanging on #sugar on FreeNet
- Old OLPC projects: http://www.codewiz.org/wiki/OneLaptopPerChild
I'm a volunteer working for the Sugar Labs 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. Curremtly, I'm a volunteer at | OLE Nepal in Kathmandu, Nepal.
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. -- 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 code without opening the rest of the development process to the community 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".
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 :-)