Content meetings: Difference between revisions

From OLPC
Jump to navigation Jump to search
(..)
(..)
 
(20 intermediate revisions by 4 users not shown)
Line 1: Line 1:
''see also [[talk:library]], [[game development meetings]], [[software meetings]]''
''see also [[talk:library]], [[game development meetings]], [[software meetings]], [http://laptop.org/teamwiki/index.php/Team:Content_meetings Team:Content meetings], and [[support meetings]]''


: '''Archives''': [[Content meetings/Summer 2007]]
== 7 Aug 2007 ==


== February 12, 2008 ==
Tues Aug 7, 2007, 2pm EST, on #olpc-content. add to agenda.
''1615''
to be present: paur, lauren, sj, mel, (kim?)


Agenda
* next meeting
# Image customization : autoinstalling keys, bundles, and more via USB / via network
* report from Wikimania - wiki, community, loc updates
#: variation in danger based on method
* check-in on Activity & Library grid, XO and server collections
# Topical focus : Health, Math, Images, Literature
* reconnect re hiring (specifically re repository/server dev, PM, wiki farmer)
#: sidebars and other highlights from main pages
*: Renaud Gaudin, Mali (offline editing/synch internship)
# Contributor focus : postering, poster design, campus events
*: fourkitchens
#: PBHA, social benefit groups; via chapters and regional SIGs
* bundles
# XO lib testing : final review before tomorrow's goals
*: collection sizes & C drop
#: dev key placement. link checking. strange character checks. (using trac)
* l10n priorities
# Requests/offers; RT
#: large collections; cc-DVD and asheesh; flickr and commons and archive and bigU
# Shared presentations and event outreach
#: MFA, MOMA, AIA meeting
#: GDC, EDC, CC@SXSW
# Annotations : stamping, ccLearn, textbookrevolution




== 30 July 2007 ==


Monday July 31, 2007, 2pm EST, 2AM Taipei, on #olpc-content. add to agenda.
to be present: paur, lauren, sj, mel, (kim?)


* setting a time for regular meetings
* quick report on Wikimania; any requests from SJ and Mel (who will not be sleeping, apparently)
* check-in to make sure we have an easy place for Taipei Jam contributors (& others) to upload content - Library Grid not the most friendly thing in the world at present
* touch base re hiring (specifically re PM and server developer)


== [[school server]]s ==
''have a lot of disk space; useful as supernodes; shouldn't be required in general for services to work''
* weekly discussions of implementation
* currently: no readily accessibly crypto signing
* libraries: preshipped, modular components added by hand


== [[content stamping]] ==
''working on this: Adir Abraham''
* use cases: world at large


== [[data store]] ==
== February 5, 2008 ==
''mako, sethwoodworth, sj, arjs, lauren, andri, anna b, [manu]''


<pre>
=== July 5 ===
* Health
'''Who gets to write to the data store?'''
Anna B: talking about setting up a system
-- > mail will o to content.laptop.org and it will go into rt
people on rt will decide whether and how to get back to them.


question about peer review. in this context, it should be thought of in the sense of : is it just for wiki pages, hardware or software, or what?
Some of this is still up in the air. Interesting use cases:
* an activity wants to store something to the data store that is public and sharable. How can the store something in the data store and tag it as sharable?
* There's currently a "share activity" / "collaborate" button that shares a current document. Implications need to be worked out.
* We need an indicator of 'state' -- whether one is working in a shared or private state at a given moment.


when peer review happens on wp, whathappesn and what is reviewd.
Use cases:
perhaps this is done now
* [[mesh board]] (distributed craigslist) -- as soon as you 'share' or 'publish' a new announcment, it is stored as something shared.
* Can something on the level of the [[presence]] service offer distributed content or other pervasive services that store data using the tag and permission features of the data store? should there be something similar but separat with different security implications for scratch-type store and forwarding? (see below)


advisory group : a meta group, a health group of 6-7. talk with ken shan, nate ackermann, eli l about math and music groups. most advisors are busy. if we ask them to join the library list they will be inundated. thought : have a wiki portal with advisory requests : there people/students/volunteers can put up a list of requests... who, what they are working on, and places they need help.
'''Store and forward ''': Whether or not you use store and forward, there are times when you want to communicate with someone who isn't online.
* Imagine sharing distributed content across a loosely connected network.
* Can this use scratch storage on the laptops? Or another 'directory' in the data store?


seth : PATH has operations in 16 countries. they want 6 xo's to look into the whole concept and adopt it as one of their projects.
'''Asynchronous notification''': We need a style guideline for notifying someone that things are happening related to their interests outside the scope of the current full-frame activity
|
* notify people when they get responses to their efforts in a particular arena (say, board postings, or shared items further edited by collaborators)
\---> sj : moving up a level, we should define how a large org can 'look into OLPC' above and beyond an intro to a single laptop. Hewl. has asked something similar.
* this can also be useful for doing semi-persistent sharing of files and other assets across the mesh.

hopefully all 3 can join at 1300 sunday EST for a call. (sj - with irc too for minutes; later move to irc in general)

advisors would go through the page periodically and adopt a request, or get them in touch with someone else. this is in addition to being present @ monthly conf calls and discussing those issues.

seth - exactly how the health pages are structured... could write this up in the doc' of health projects. [we now have tasks such as 'health professional' or 'photographer' which asks that sort of person to help that way.] with similar wording on that project page.

running through the agenda:
• health
[see above]

• seeding open communities
there could definitely be a good tagging community on flickr. there's an existing olpc group with contributors who could help in this; mostly it's about photos of xo's, from meetups, &c. the dialogue area of that would be a bad place to start

just got some scripts from cc folks for their autocuration db. they went into the flickr api to pull out photos based on license, while keeping the attribution/licenses correct [we should do that for wm commons]

asking people to get involved? what's the background of how people start working; need a doc page on olpc for how to use our tools.
sj : ask wikipedia.

• format conversion toolchain
librivox and audio conversion : some nice scripts for that. u.1 doesn't support the right mime types. ask archive.org to process on update? librivox uploads to a.o --

how do we add this as server functionality? we won't be able to do this easily on laptops.
--- mesh solutions (share conversion as activity)
--- server solutions (host @ XS, on web)
: ffmpeg and ffmpeg2theora for videos
:: add support for speex to it -- file a bug [against jay].
:: get all the codecs from Real and others for this
:: talk to them and AMD about mp3 stuff.
: find people to ask for docs
: image conversion : imagemagik on the server.
:: consider openstreetmap.
: theora + speex in ogg wrapper ...

• ebook readers
browser is too slow to run html/js reader.
evince is slow for pdf; but now runs djvu.
annotation.
: in evince? annoying: pdf has an annotation standard
:: see gnuPDF ... who is supporting this? not evince codebases
parallels with sharing. anontation for anything that lets you 'read' -- have writers/users rather than readers.
someone should just create an activity that allows commenting. if that's especially important, we should pay someone to do it -- don't know about the evince community; but it's that simple. it's not necessarily fun or someone would have done it.
even if we're writing to a pdf annotation format, we could also create a common interface to that, an annotation library that happens to be able to talk to evince to read/write pdf annotations. and could potentially do others as well. no problem there. maybe find someone in that community, ask around @ redhat, who would be a good candidate. then -- just do it.
annotate the web browser : js extensions -- look into greasemonkey and other. get basic annotations in place.

• community/content updates -- dailies, featured projects?
Waiting for mburns to finish drupal install; using that for a 1.0 version. |.. = ..| Send something out each day.

• lifecycles for the library

1: implement a share activity : pick anything, zip it and bundle it and share it with anyone else?
we have the ability to share sessions. not activities and collections and more. along the way, asnwer some important questions : how do you want to share things with people you konw. how important is it you know things are one and not another thing (mime-type or session-type equivs at different scales)

2. define use cases for MikMik for the future, along with the above.

3. finishing use cases for webservers for a dynamic content library. there are solutions that don't involve this; but it is simplest.

• new business: levelled readers. seth and colleagues.
What format to produce for them? html + css.

• game development : food force meetings (2-3x a week, manu's contacts in india)
</pre>


== January 23, 2008 ==
'''school and larger-scale use cases'''

current school needs (Bryan Berry)
visualization and interface. (Eben)
specific uses : Moodle (Martin Langhoff, Moodle)
Fedora-Repository and Exhibit.
'''internet use cases'''
integration with Wikimedia, Curriki, the Internet Archive, &c. (Josh Marks)
Regional mirrors.
'''wrapup, q&a.'''
Outreach to other groups for feedback
Case studies from trials (Arjun & Manu)
'''creator networks'''
School projects to create and share : connecting them with other schools
Community and Library groups for sharing ideas and knowledge
Educational consortium : inspiring an anthology of culture
what does this look like in different regions, communities, fields?
OLPC chapters : universities, cities, countries
contributors program & reviewing projects
'''global canvas'''
p2p networks and local filesharing : searching and publishing
how do you 'publish' something in a lasting local way?
selection : featured lists, exhibits, shows, competitions.
reviewing, judging and standards
how does olpc choose its best works for distribution?
newsletters, reports, and aggregates : editors and distribution channels
'''curation and coordination'''
current and future groups, and some case studies (biology, music, video)
Library of Congress, World Digital Library
high school & educator networks
'''review''': scheduling the Feb. meeting, mesh w/ Feb 1x learning workshop

== general discussions ==

=== metadata ===
In some countries, you have strict metadata based on ministry needs; but want to bring in material from repos that aren't so formal. See [[Talk:Library/Metadata]] and contrast with [[bundle metadata]].

=== libraries and repositories ===
1) working with partner repositories - good interfaces for curriki and
the internet archive, et al. that hide the complexities of their
system and make it easy to upload things "for OLPC" and to find/tag
related material

2) use of Wikimedia projects, Fedora and like repositories to organize
both physical and digital materials -- books, media, library records,
XO bundles, [other] web learning activities.

3) organizing community review and assessment : good and brilliant
packages and bundles; content stamping.
: Re: [[Content stamping]] - is active development on this still needed? If it's urgent, we can write up a spec/job-descript and post it to our soon-to-be-pretty [[Internships]] (unpaid... and intended for local groups to post opportunities and help-wanteds) page. I can also talk to the folks at OpenPlans next month to see if they are still interested. [[User:Mchua|Mchua]] 02:08, 25 January 2008 (EST)

=== supporting new projects ===
1) [Southern] Summer of Content - we have some interested sponsors
who want to make sure SoCon happens again this month / next, and a
potential co-announcement this summer. how to propagate successes from the Aug/Septemer SoCon? &c.
: Now that I'm back in the continent and will be in a stable home with equally stable wireless, I can actually jump back in on this. I've been focusing on building a back-end Mediawiki site with semantic capabilities that will make submitting, reviewing, processing, and keeping track of applications and projects much more sane than last time; it can be ready to go the second week of Feb, possibly earlier if we need it then. Need to catch up with SJ, Wayne, and whoever else is interested - please ping me. [[User:Mchua|Mchua]] 02:16, 25 January 2008 (EST)
:: Great to have you back. let's track down wayne early this week and talk with him before synch'ing with other interested groups. --[[User:Sj|Sj]]&nbsp;[[User talk:Sj|<font color="fc9" style="font-size:70%">leave me a message</font>]]

2) task boards for sharing needs and offers. social network by talent
and passion. bounty and job boards for partners who need to find help
on short notice (ex: UNICEF is always short of python programmers in
non-english speaking countries. this is a plum job. they have a hard
time getting the word out...)
: [[Internships]] might be turning into something like this - [[Help wanted]] and [[Job wanted]], perhaps? There might be less clunky ways of doing it than on a manually-updated-and-pruned mediawiki page, though - perhaps something in one of the new forums? Another idea: "helpwanted" mailing list for OLPC-related "job" postings. In general, way too many grassroots people have been asking me about this, so I'm very interested (for the sake of my own sanity) in finding a good next-generation solution. Definitely want to be updated; not sure how much time I can spend helping with this (esp. if I'm doing SoCon again). [[User:Mchua|Mchua]] 02:16, 25 January 2008 (EST)
:: Yes, the wanted / bounty board dichotomy... perhaps two sections on the same page. A mailing list would be a fine thing as well. --[[User:Sj|Sj]]&nbsp;[[User talk:Sj|<font color="fc9" style="font-size:70%">leave me a message</font>]]

=== outreach ===
1) university connections : a consortium of faculty advisors and
coordinators, with student curators and creators, in touch with /
maintaining connections with thousands of archives, museums,
publishing channels, classes, and individual authors
: Already nucleating university chapters, primarily in the Chicago area for now. Will see if we can get more helpful resources for starting chapters out there. In general, nucleating university (and grassroots) groups seems to work best when already-active OLPC volunteers go out and run an intensive boot-camp intro kickoff/projects session at the location for at least a full day... most of the groups I've run into so far need connections and the knowledge of where to find information more than anything else to help them really get going. Btw, a university chapter is just a specialized form of grassroots group, imo. [[User:Mchua|Mchua]] 02:24, 25 January 2008 (EST)

2) by chapter : local and national chapter development, policies, &c.
: Wait... policies? ([[[OLPC Chicago]] has "we are... we are not..." guidelines inspired by [[OLPC Europe]] - are you thinking of something like this, or more rule-like policies that all chapters must follow? [[User:Mchua|Mchua]] 02:24, 25 January 2008 (EST)
:: These sorts of guidelines are just what I mean.

3) by creative community : via [[curators|curators and coordinators]], through subprojects within Flickr, Youtube, Wikimedia Commons, Wikipedia, and the like
: What happened to [[Curators]]? [[User:Mchua|Mchua]] 02:24, 25 January 2008 (EST)
:: They need help from new fields and communities; currently at ~20% coverage.

4) by major educational project : subgroups within UNICEF, WHO and the
like coordinating sharing of works in child-friendly and XO-friendly
formats.
: Can these be grouped with #3? Can they use the same infrastructures/tools in terms of ways (not necessarily technological) of interfacing their stuff with OLPC? (This is badly phrased, I know; can't think of a way to reword it more coherently atm.) [[User:Mchua|Mchua]] 02:24, 25 January 2008 (EST)
:: Perhaps. the infrastructure, and the methods of interacting with these groups, are quite different; it takes time to become skilled in each mode of interaction.

5) by tool/activity : blogging, music sharing, programming... forming
networks, organizing local and regional competitions, topical
newsletters to highlight good work. Examples from primary and
secondary networks elsewhere
: Example: [[Art]] - it seems like a lot of communities of this sort are just missing critical mass and a willing maintainer. [[User:Mchua|Mchua]] 02:24, 25 January 2008 (EST)

6) by language; What sorts of partnerships this opens up with local groups
: What has grassroots activity been like in the target countries? Is there a possibility that they might be willing to host volunteers from overseas (who would pay their own way, or find funding to do such - no financial burden imposed upon host institutions) who can speak the local language and have relevant experience? [[User:Mchua|Mchua]] 02:24, 25 January 2008 (EST)
:: A number of countries explicitly offer housing for volunteers.

A discussion page for library software and content delivery. Older discussion first.
: See also [[content meetings]].

== December 1, 2007 ==
Rough agenda:
0. Infrastructure
- Adding bundle-installation to the [[smoke test]]
- moving journal patches (simon) to olpc-config (scott)
- finishing a dynamic library spec - mail to ian b (mako), findbundles/makecache
: main page ---> page of icons / mouseover thumbnails
- writing build-scripts : .info, linkcheck, thumbnailer, registry
: install on crank for folks to upload a .zip and --> xo[l]

1. Libraries
- [[Manual]] : where to insert this in the process?
: find name for manual/guide package by Friday6
: convert to convenient html ebook -- set style for "1 page" of text
: art requests to [[Art Team]] and [[User:Nlee]]/[[User:Leejc]]
: add/update bundle / adding,removing packaging
: connect AG and Adam with Felicity
- XO library : process and testing
: [[style guide]]; add update/removal notes to manual
- XS library : (schoolserver) activities for teachers; making large bundles
: Add note about this to the manual
2. Style
- Creator guidelines : how-tos in the simplified manual, scripts,
style guidelines (writing for translators, for children)
- Reviewer guidelines : copyright, trademark, photo releases
3. Testing
- Library testing -- how to emulate and review bundles
- Library process -- style for bundles, reviewing steps and groups
- Status levels for bundles : community curation of "stable" bundles
4. Community content projects
- Our Stories launch, country connections
- Report update, Knight grant, Uguruay/Brasil input
- [[AMADIS]] reuse
- sugarize Xword, Xmame, nes em.
5. Winter projects
- [[SoCon]], bundle wishlists; iCommons update
- December gathering; DC meetup;
- [[Community]] outreach : G1G1 project via OSU
- Language : simpler localization; visit, get a few words each time

6. Media status
- [[Flash]] and [[Gnash]]
- [[Audio]], ogg and mp3 and wav; using Record
- [[Video]], ogg and other; using Record
- [[Etoys]] projects
- [[Books]]: pdf and html, outstanding issues


'''Activity-level daemons''' : There's no spec yet for defining user-level activity daemons, for something persistent.
* Does a data sharing service need to be at the presence level? If so, we may need to provide a UI for turning this on and off.
* Do we need sth like a python libevent dbus loop to allow cheap addition of persistent service daemons?


[[Category:Content]]
[[Category:Content]]

Latest revision as of 21:42, 12 February 2008

see also talk:library, game development meetings, software meetings, Team:Content meetings, and support meetings

Archives: Content meetings/Summer 2007

February 12, 2008

1615

Agenda

  1. Image customization : autoinstalling keys, bundles, and more via USB / via network
    variation in danger based on method
  2. Topical focus : Health, Math, Images, Literature
    sidebars and other highlights from main pages
  3. Contributor focus : postering, poster design, campus events
    PBHA, social benefit groups; via chapters and regional SIGs
  4. XO lib testing : final review before tomorrow's goals
    dev key placement. link checking. strange character checks. (using trac)
  5. Requests/offers; RT
    large collections; cc-DVD and asheesh; flickr and commons and archive and bigU
  6. Shared presentations and event outreach
    MFA, MOMA, AIA meeting
    GDC, EDC, CC@SXSW
  7. Annotations : stamping, ccLearn, textbookrevolution




February 5, 2008

mako, sethwoodworth, sj, arjs, lauren, andri, anna b, [manu]
* Health
Anna B: talking about setting up a system
 -- > mail will o to content.laptop.org and it will go into rt
 people on rt will decide whether and how to get back to them.

question about peer review.  in this context, it should be thought of in the sense of : is it just for wiki pages, hardware or software, or what?  

when peer review happens on wp, whathappesn and what is reviewd.
perhaps this is done now

advisory group : a meta group, a health group of 6-7.  talk with ken shan, nate ackermann, eli l about math and music groups.  most advisors are busy.   if we ask them to join the library list they will be inundated.    thought : have a wiki portal with advisory requests : there people/students/volunteers can put up a list of requests... who, what they are working on, and places they need help.  

seth : PATH has operations in 16 countries.  they want 6 xo's to look into the whole concept and adopt it as one of their projects.  
|
\---> sj : moving up a level, we should define how a large org can 'look into OLPC' above and beyond an intro to a single laptop.  Hewl. has asked something similar.

hopefully all 3 can join at 1300 sunday EST for a call.  (sj - with irc too for minutes; later move to irc in general) 

advisors would go through the page periodically and adopt a request, or get them in  touch with someone else.  this is in addition to being present @ monthly conf calls and discussing those issues. 

seth - exactly how the health pages are structured... could write this up in the doc' of health projects.   [we now have tasks such as 'health professional' or 'photographer' which asks that sort of person to help that way.]  with similar wording on that project page.  

running through the agenda:
• health
[see above]

• seeding open communities
there could definitely be a good tagging community on flickr.  there's an existing olpc group with contributors who could help in this; mostly it's about photos of xo's, from meetups, &c.  the dialogue area of that would be a bad place to start

just got some scripts from cc folks for their autocuration db.  they went into the flickr api to pull out photos based on license, while keeping the attribution/licenses correct   [we should do that for wm commons]

asking people to get involved?  what's the background of how people start working; need a doc page on olpc for how to use our tools.  
sj : ask wikipedia.   

• format conversion toolchain 
librivox and audio conversion : some nice scripts for that.  u.1 doesn't support the right mime types.  ask archive.org to process on update?  librivox uploads to a.o -- 

how do we add this as server functionality?   we won't be able to do this easily on laptops.  
 --- mesh solutions (share conversion as activity)
 --- server solutions (host @ XS, on web)
   : ffmpeg and ffmpeg2theora for videos
   :: add support for speex to it -- file a bug [against jay].
   :: get all the codecs from Real and others for this
   :: talk to them and AMD about mp3 stuff.  
   : find people to ask for docs
   : image conversion : imagemagik on the server.  
   :: consider openstreetmap.   
   : theora + speex in ogg wrapper ...    

• ebook readers
browser is too slow to run html/js reader.
evince is slow for pdf; but now runs djvu.
annotation.  
  : in evince?  annoying: pdf has an annotation standard
  :: see gnuPDF ... who is supporting this?  not evince codebases
  
parallels with sharing.  anontation for anything that lets you 'read'  -- have writers/users rather than readers.    
someone should just create an activity that allows commenting.  if that's especially important, we should pay someone to do it -- don't know about the evince community; but it's that simple.  it's not necessarily fun or someone would have done it.  
     even if we're writing to a pdf annotation format, we could also create a common interface to that, an annotation library that happens to be able to talk to evince to read/write pdf annotations.  and could potentially do others as well.    no problem there.  maybe find someone in that community, ask around @ redhat, who would be a good candidate.  then -- just do it.  
     
     annotate the web browser : js extensions -- look into greasemonkey and other.  get basic annotations in place.  

• community/content updates -- dailies, featured projects?
Waiting for mburns to finish drupal install; using that for a 1.0 version.  |.. = ..|   Send something out each day. 

• lifecycles for the library

1: implement a share activity : pick anything, zip it and bundle it and share it with anyone else?   
we have the ability to share sessions.  not activities and collections and more.  along the way, asnwer some important questions : how do you want to share things with people you konw.  how important is it you know things are one and not another thing (mime-type or session-type equivs at different scales)

2. define use cases for MikMik for the future, along with the above.

3. finishing use cases for webservers for a dynamic content library.  there are solutions that don't involve this; but it is simplest.

• new business: levelled readers.  seth and colleagues.
What format to produce for them?   html + css.  

• game development : food force meetings (2-3x a week, manu's contacts in india) 


January 23, 2008

school and larger-scale use cases

 current school needs  (Bryan Berry)
 visualization and interface.  (Eben)
 specific uses : Moodle    (Martin Langhoff, Moodle)
    Fedora-Repository and Exhibit.

internet use cases
  integration with Wikimedia, Curriki, the Internet Archive, &c.  (Josh Marks)
  Regional mirrors.

wrapup, q&a.
  Outreach to other groups for feedback
  Case studies from trials  (Arjun & Manu)

creator networks
   School projects to create and share : connecting them with other schools
   Community and Library groups for sharing ideas and knowledge
   Educational consortium : inspiring an anthology of culture
         what does this look like in different regions, communities, fields?
   OLPC chapters : universities, cities, countries
   contributors program & reviewing projects

global canvas
    p2p networks and local filesharing : searching and publishing
        how do you 'publish' something in a lasting local way?
    selection : featured lists, exhibits, shows, competitions.
    reviewing, judging and standards
        how does olpc choose its best works for distribution?
    newsletters, reports, and aggregates : editors and distribution channels

curation and coordination
    current and future groups, and some case studies (biology, music, video)
    Library of Congress, World Digital Library
    high school & educator networks

review: scheduling the Feb. meeting, mesh w/ Feb 1x learning workshop

general discussions

metadata

In some countries, you have strict metadata based on ministry needs; but want to bring in material from repos that aren't so formal. See Talk:Library/Metadata and contrast with bundle metadata.

libraries and repositories

1) working with partner repositories - good interfaces for curriki and the internet archive, et al. that hide the complexities of their system and make it easy to upload things "for OLPC" and to find/tag related material

2) use of Wikimedia projects, Fedora and like repositories to organize both physical and digital materials -- books, media, library records, XO bundles, [other] web learning activities.

3) organizing community review and assessment : good and brilliant packages and bundles; content stamping.

Re: Content stamping - is active development on this still needed? If it's urgent, we can write up a spec/job-descript and post it to our soon-to-be-pretty Internships (unpaid... and intended for local groups to post opportunities and help-wanteds) page. I can also talk to the folks at OpenPlans next month to see if they are still interested. Mchua 02:08, 25 January 2008 (EST)

supporting new projects

1) [Southern] Summer of Content - we have some interested sponsors who want to make sure SoCon happens again this month / next, and a potential co-announcement this summer. how to propagate successes from the Aug/Septemer SoCon? &c.

Now that I'm back in the continent and will be in a stable home with equally stable wireless, I can actually jump back in on this. I've been focusing on building a back-end Mediawiki site with semantic capabilities that will make submitting, reviewing, processing, and keeping track of applications and projects much more sane than last time; it can be ready to go the second week of Feb, possibly earlier if we need it then. Need to catch up with SJ, Wayne, and whoever else is interested - please ping me. Mchua 02:16, 25 January 2008 (EST)
Great to have you back. let's track down wayne early this week and talk with him before synch'ing with other interested groups. --Sj leave me a message

2) task boards for sharing needs and offers. social network by talent and passion. bounty and job boards for partners who need to find help on short notice (ex: UNICEF is always short of python programmers in non-english speaking countries. this is a plum job. they have a hard time getting the word out...)

Internships might be turning into something like this - Help wanted and Job wanted, perhaps? There might be less clunky ways of doing it than on a manually-updated-and-pruned mediawiki page, though - perhaps something in one of the new forums? Another idea: "helpwanted" mailing list for OLPC-related "job" postings. In general, way too many grassroots people have been asking me about this, so I'm very interested (for the sake of my own sanity) in finding a good next-generation solution. Definitely want to be updated; not sure how much time I can spend helping with this (esp. if I'm doing SoCon again). Mchua 02:16, 25 January 2008 (EST)
Yes, the wanted / bounty board dichotomy... perhaps two sections on the same page. A mailing list would be a fine thing as well. --Sj leave me a message

outreach

1) university connections : a consortium of faculty advisors and coordinators, with student curators and creators, in touch with / maintaining connections with thousands of archives, museums, publishing channels, classes, and individual authors

Already nucleating university chapters, primarily in the Chicago area for now. Will see if we can get more helpful resources for starting chapters out there. In general, nucleating university (and grassroots) groups seems to work best when already-active OLPC volunteers go out and run an intensive boot-camp intro kickoff/projects session at the location for at least a full day... most of the groups I've run into so far need connections and the knowledge of where to find information more than anything else to help them really get going. Btw, a university chapter is just a specialized form of grassroots group, imo. Mchua 02:24, 25 January 2008 (EST)

2) by chapter : local and national chapter development, policies, &c.

Wait... policies? ([[[OLPC Chicago]] has "we are... we are not..." guidelines inspired by OLPC Europe - are you thinking of something like this, or more rule-like policies that all chapters must follow? Mchua 02:24, 25 January 2008 (EST)
These sorts of guidelines are just what I mean.

3) by creative community : via curators and coordinators, through subprojects within Flickr, Youtube, Wikimedia Commons, Wikipedia, and the like

What happened to Curators? Mchua 02:24, 25 January 2008 (EST)
They need help from new fields and communities; currently at ~20% coverage.

4) by major educational project : subgroups within UNICEF, WHO and the like coordinating sharing of works in child-friendly and XO-friendly formats.

Can these be grouped with #3? Can they use the same infrastructures/tools in terms of ways (not necessarily technological) of interfacing their stuff with OLPC? (This is badly phrased, I know; can't think of a way to reword it more coherently atm.) Mchua 02:24, 25 January 2008 (EST)
Perhaps. the infrastructure, and the methods of interacting with these groups, are quite different; it takes time to become skilled in each mode of interaction.

5) by tool/activity : blogging, music sharing, programming... forming networks, organizing local and regional competitions, topical newsletters to highlight good work. Examples from primary and secondary networks elsewhere

Example: Art - it seems like a lot of communities of this sort are just missing critical mass and a willing maintainer. Mchua 02:24, 25 January 2008 (EST)

6) by language; What sorts of partnerships this opens up with local groups

What has grassroots activity been like in the target countries? Is there a possibility that they might be willing to host volunteers from overseas (who would pay their own way, or find funding to do such - no financial burden imposed upon host institutions) who can speak the local language and have relevant experience? Mchua 02:24, 25 January 2008 (EST)
A number of countries explicitly offer housing for volunteers.

A discussion page for library software and content delivery. Older discussion first.

See also content meetings.

December 1, 2007

Rough agenda:

0. Infrastructure
 - Adding bundle-installation to the smoke test
 - moving journal patches (simon) to olpc-config (scott)
 - finishing a dynamic library spec - mail to ian b (mako), findbundles/makecache
   : main page ---> page of icons / mouseover thumbnails
 - writing build-scripts : .info, linkcheck, thumbnailer, registry
   : install on crank for folks to upload a .zip and --> xo[l]
1. Libraries
 - Manual : where to insert this in the process?
   : find name for manual/guide package by Friday6
   : convert to convenient html ebook -- set style for "1 page" of text
   : art requests to Art Team and User:Nlee/User:Leejc 
   : add/update bundle / adding,removing packaging
   : connect AG and Adam with Felicity 
 - XO library : process and testing
   : style guide; add update/removal notes to manual
 - XS library : (schoolserver) activities for teachers; making large bundles
   : Add note about this to the manual 

2. Style
 - Creator guidelines : how-tos in the simplified manual, scripts,
           style guidelines (writing for translators, for children)
 - Reviewer guidelines : copyright, trademark, photo releases
 
3. Testing
 - Library testing -- how to emulate and review bundles
 - Library process -- style for bundles, reviewing steps and groups
 - Status levels for bundles : community curation of "stable" bundles

4. Community content projects
 - Our Stories launch, country connections
 - Report update, Knight grant, Uguruay/Brasil input
 - AMADIS reuse
 - sugarize Xword, Xmame, nes em.
          
5. Winter projects
 - SoCon, bundle wishlists; iCommons update
 - December gathering; DC meetup;
 - Community outreach : G1G1 project via OSU
 - Language : simpler localization; visit, get a few words each time 
6. Media status
 - Flash and Gnash
 - Audio, ogg and mp3 and wav; using Record
 - Video, ogg and other; using Record
 - Etoys projects
 - Books: pdf and html, outstanding issues