Difference between revisions of "User:Bernie"

From Sugar Labs
Jump to navigation Jump to search
Line 1: Line 1:
 +
= Bernie Innocenti =
 +
 
[[Image:Bernie.png|thumb|none|not really me]]
 
[[Image:Bernie.png|thumb|none|not really me]]
  
:Personal homepage: http://www.codewiz.org/
 
 
:e-mail: bernie AT codewiz DOT org
 
:e-mail: bernie AT codewiz DOT org
 
:IRC: _bernie, hanging on #sugar on FreeNet
 
:IRC: _bernie, hanging on #sugar on FreeNet
:Old OLPC projects: http://www.codewiz.org/wiki/OneLaptopPerChild
+
:Jabber: bernie AT codewiz DOT org (yes, I run my own Jabber server ;-)
 +
:Contact info: http://www.codewiz.org/ContactInformation
 +
 
 +
:Personal homepage: http://www.codewiz.org/
 +
:Blog: http://www.codewiz.org/wiki/
 +
:Resume: http://www.codewiz.org/wiki/CurriculumVitae (somewhat outdated)
 +
:LinkedIn profile: http://www.linkedin.com/profile?viewProfile=&key=5159373
 +
:Old OLPC projects: http://www.codewiz.org/wiki/OneLaptopPerChild
  
I'm a volunteer working for the Sugar Labs team.
+
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 [http://www.olenepal.org/ | OLE Nepal] in Kathmandu, Nepal.
 
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 [http://www.olenepal.org/ | OLE Nepal] in Kathmandu, Nepal.
  
 +
== Platform ==
 +
 +
To position itself as THE educational environment of the future, Sugar needs
 +
to grow a larger user and developer base.  This is only possible by
 +
transforming Sugar into a truly community-driven project with its own
 +
independent identity.
 +
 +
=== Goals for Sugar Labs ===
 +
 +
1. Enhance our public-facing web presence and development infrastructure;
 +
 +
2. Attract contribution from multiple hardware and OS vendors;
 +
 +
3. Foster the creation of companies and groups offering professional Sugar
 +
consulting and outsourcing.
 +
 +
4. Raise funding to sponsor developer meetings and our presence at major
 +
international events
 +
 +
 +
=== Anti-goals for Sugar Labs ===
 +
 +
1. Hire a large team of software developers -- This would end up discouraging
 +
outside contributors;
 +
 +
2. Brew a custom OS platform -- We work with distributors, not compete against
 +
them;
 +
 +
3. Let Sugar Labs become unfairly biased towards specific partners --
 +
that would undermine our relationships with other partners;
  
== Why we should be more open ==
+
4. Trade project autonomy for funding or support -- we're glad to offer our
 +
services, not our souls.
  
(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
+
=== Personal agenda ===
from it now it will never return.
 
  -- [[User:Sj|Samuel Klein]]
 
  
"We should be more open" may strike many as a surprising suggestion
+
I'm exploring the possibility to build a small team of Sugar hackers that
for OLPC, since it's already supposed to be one of the most open
+
would offer consulting services such as porting to specific hardware
projects out there.
+
platforms or development of features.  Internet would be our office.
  
But opening just the source code without opening the rest of the
+
Over the next few years, computers will become central in world education.
development process to the community is a recurring pitfall in which
+
This will in turn stimulate the creation of a florid industry offering
even large corporates such as RedHat and Sun all fell, initially.
+
hardware, software and contents for the specific needs of schools.
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
+
Sugar has a large competitive advantage over any other proprietary
be too hard for outside contributors".  This can't possibly be
+
offering on the horizon, and a huge momentum.  This is why I also see
true: projects like OpenWRT and the Linux kernel and dozens of
+
Sugar as a rewarding business opportunity to invest in.
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 :-)
+
See also [Why open]

Revision as of 11:59, 19 August 2008

Bernie Innocenti

not really me
e-mail: bernie AT codewiz DOT org
IRC: _bernie, hanging on #sugar on FreeNet
Jabber: bernie AT codewiz DOT org (yes, I run my own Jabber server ;-)
Contact info: http://www.codewiz.org/ContactInformation
Personal homepage: http://www.codewiz.org/
Blog: http://www.codewiz.org/wiki/
Resume: http://www.codewiz.org/wiki/CurriculumVitae (somewhat outdated)
LinkedIn profile: http://www.linkedin.com/profile?viewProfile=&key=5159373
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.

Platform

To position itself as THE educational environment of the future, Sugar needs to grow a larger user and developer base. This is only possible by transforming Sugar into a truly community-driven project with its own independent identity.

Goals for Sugar Labs

1. Enhance our public-facing web presence and development infrastructure;

2. Attract contribution from multiple hardware and OS vendors;

3. Foster the creation of companies and groups offering professional Sugar consulting and outsourcing.

4. Raise funding to sponsor developer meetings and our presence at major international events


Anti-goals for Sugar Labs

1. Hire a large team of software developers -- This would end up discouraging outside contributors;

2. Brew a custom OS platform -- We work with distributors, not compete against them;

3. Let Sugar Labs become unfairly biased towards specific partners -- that would undermine our relationships with other partners;

4. Trade project autonomy for funding or support -- we're glad to offer our services, not our souls.


Personal agenda

I'm exploring the possibility to build a small team of Sugar hackers that would offer consulting services such as porting to specific hardware platforms or development of features. Internet would be our office.

Over the next few years, computers will become central in world education. This will in turn stimulate the creation of a florid industry offering hardware, software and contents for the specific needs of schools.

Sugar has a large competitive advantage over any other proprietary offering on the horizon, and a huge momentum. This is why I also see Sugar as a rewarding business opportunity to invest in.

See also [Why open]