I think it's worth noting that with the announcement of the new 2.0 spec on the hardware, you're going to get even more backlash of current G1G1 participants feeling like they helped to fund and purchase a system that is basically really a serious work in progress and test bed for the new system. Again, impression counts.<br>
<br>Todd<br><br><div class="gmail_quote">On Thu, May 22, 2008 at 9:25 AM, C. Scott Ananian <<a href="mailto:cscott@cscott.net">cscott@cscott.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 5/21/08, Kim Quirk <<a href="mailto:kim@laptop.org">kim@laptop.org</a>> wrote:<br>
> I have been trying to understand it, explain it, live with it ,<br>
> and improve it for a year now. What I think is going on is a unique<br>
> and somewhat chaotic (perfect storm?) intersection of non-profit, open<br>
> source, research lab cultures with the need to ship a real product.<br>
</div>[...]<br>
> Can we use help? Absolutely. Lots of it! The hardest thing for us to figure<br>
> out is how to let people help us.<br>
<br>
OLPC is not so unique and special that we can't learn from our<br>
predecessors. OLPC is not the first research lab which morphed into a<br>
non-profit with a product. I'm sure others can contribute examples,<br>
but Firefox and Debian leap to mind.<br>
<br>
That said, I don't think that we can (or should) point our finger at<br>
any single person and say that we don't communicate as well as we<br>
could because of that scapegoat. Rather, I'd like to suggest that we<br>
point to a person who *doesn't yet exist*: a community liason.<br>
<br>
Fedora and Firefox both have (many!) designated 'ambassadors' whose<br>
job it is to keep the community in the loop. Debian has a 'Project<br>
Leader' with similar charge.<br>
<br>
I would like to nominate SJ and Adam for the role of interim community<br>
liason, as they've done a fantastic job to date building and<br>
nourishing their respective content and support communities. What we<br>
need is to broaden that task and embody and formally recognize it. A<br>
liason will be privy to inside information and continually ask "is<br>
this public? can it be?" and conversely, keep in touch with the<br>
broader community and bring to internal attention worthwhile efforts<br>
outside. By naming and recognizing a liason (even an interim one), we<br>
would all have a single point of contact: cc '<a href="mailto:liason@laptop.org">liason@laptop.org</a>' to<br>
ensure broad distribution.<br>
<br>
This job is likely to be a bit overwhelming, and I suggest actively<br>
seeking to hire proven community builders who have worked with other<br>
projects to take the burden off our interim liason(s). Liasons<br>
should, of course, work with the community to build a broader base of<br>
OLPC ambassadors who can share the local work.<br>
<br>
Concrete things I'd like to see a liason take charge of:<br>
<br>
a) monthly tech "mini-conferences" to present current work and wild ideas<br>
<br>
b) the same for deployments, to exchange success stories, challenges,<br>
and curricula<br>
<br>
c) organizing local OLPC chapters, with their own charges, projects,<br>
& focus. Providing resources to same: <a href="http://alabama.laptop.org" target="_blank">http://alabama.laptop.org</a> could<br>
be a focus for OLPC volunteers in Alabama, for example. (See<br>
<a href="http://freesklyarov.org/local-howto.html" target="_blank">http://freesklyarov.org/local-howto.html</a> for inspiration.)<br>
<br>
d) collecting and archiving talks and press releases for reference<br>
and to ensure broad distribution. (both 1cc-created content, and<br>
locally-created content)<br>
<br>
e) A more broadly-focused "community news", agressively seeking out<br>
and incorporating local as well as "offical OLPC" content<br>
<br>
f) coordinating blogging efforts: a weekdaily blog post by a<br>
different OLPC developer each day, say.<br>
<br>
g) coordinating news releases to community sources like OLPCNews as<br>
well as traditional press sources. Providing access to traditional<br>
press for noteworthly community work.<br>
<br>
h) To some degree involving local communities with local i18n and<br>
support work for pilots and deployments.<br>
<br>
i) Hosting regular "open houses", both at 1cc and at local OLPC groups.<br>
<br>
j) Faciliating travel to allow different groups to interact: having<br>
1cc developers give talks at local OLPC groups and vice-versa.<br>
<br>
I'm sure folks here can contribute more ideas. Note that some of<br>
these tasks are made much easier if there is an OLPC employee<br>
involved, while others (c, d, e, h) are good task which interested<br>
members of the community can take the lead on w/o waiting for us. In<br>
fact, if there are passionate community members, I'd suggest viewing<br>
the entire list as within your scope: I think that OLPC employees are<br>
very amenable to badgering by the community if (for example) someone<br>
has set up a mini-conference elsewhere and wants to get someone from<br>
1cc to attend.<br>
--scott<br>
<br>
ps. Since I personally have a technology focus, I can suggest several<br>
interesting 'research projects' I'd love to see a local group really<br>
take charge of. Some ideas: care & nourishment of the<br>
Debian/Ubuntu/Fedora packaging of Sugar; maintaining a Sugar live cd<br>
and/or maintaining a one-click-install Windows emulator of Sugar for<br>
groups interesting in exploring Sugar or teacher training; a research<br>
fork investigating gestures for Sugar; a research group to tackle the<br>
best approaches for emulating keyboards on a touchscreen; research<br>
projects in collaboration or mesh technologies (<a href="http://open80211s.org/" target="_blank">http://open80211s.org/</a><br>
and <a href="http://wiki.funkfeuer.at/" target="_blank">http://wiki.funkfeuer.at/</a> are good focal points for such work);<br>
someone to revive/review alternate flash filesystems for the XO; care<br>
& feeding of adobe flash bundles for the XO; care and feeding of gnash<br>
on the XO (keeping us up to date, liasoning between community content<br>
and gnash developers); similar work for patent-encumbered codecs<br>
(helps if you're outside the US); care & feeding of Ogg and media on<br>
the XO (assembling good demos, optimizing encoder/decoder<br>
performance); a research group on sound/video editing for kids; a<br>
research group to improve interoperability with non-Sugarized<br>
applications; someone to investigate alternate window managers for<br>
Sugar; someone to investigate Xinerama suport in Sugar, in<br>
anticipation of eventually running Sugar across two displays in Gen 2;<br>
a research group developing software for school management (Uruguay<br>
demonstrated a very nice database application tracking kids, XOs,<br>
theft reports, and repair history, but they had it developed under<br>
contract and the result is closed source; it would be nice to provide<br>
an OSS alternative for other deployments). That's just off the top of<br>
my head. I hope a liason would be able to nuture such local projects.<br>
<font color="#888888"><br>
--<br>
( <a href="http://cscott.net/" target="_blank">http://cscott.net/</a> )<br>
</font><div><div></div><div class="Wj3C7c">_______________________________________________<br>
Sugar mailing list<br>
<a href="mailto:Sugar@lists.laptop.org">Sugar@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/sugar" target="_blank">http://lists.laptop.org/listinfo/sugar</a><br>
</div></div></blockquote></div><br>