Oversight Board/2008/Log-2008-08-01


 * Now talking on #sugar-meeting
 * Topic for #sugar-meeting is: The meeting channel for the sugar developers (sugarlabs.org) | see also #sugar | meeting time: thursdays 17.00 UTC
 * Topic for #sugar-meeting set by erikos at Wed Jun 4 07:36:15 2008
 *   i am here
 * morgs too
 *   me too.
 *   shall we get started?
 *   marcopg, ?
 *   hey
 *   cjb around?
 *   bemasc doesn't seem to be around
 *   yeah he is neither in #sugar
 *   and tomeu is already on his way to inner portugal
 *   Land of the Classmate II
 *   yeah :)
 *   Let's start with a review of outstanding issues from last time.
 *   the minutes are in the wiki: http://sugarlabs.org/go/Sugar_Labs/OversightBoard/Minutes
 *   ok
 *   As I recall, I was suppose to ask the infrastructure committee to report back.
 *   They did. I included their report in last weekend's Sugar Digest
 *   The gist is Solarsail is up and running
 *   yeah we are good there
 *   we just need to figure out the second box
 *   I have a call with AMD after this meeting to ask them about that
 *   oh nice
 *   cool
 *   what about SFC?
 *   If they cannot provide a server in a timely fashion, I'll ask one more time at OLPC
 *   did they give feedback=
 *   That is the second topic I was to follow up on
 *   I have had some email back and forth with Karen
 *   She apologized that she has been slow getting back to us
 *   She'll have something early next week.
 *   Also, some feedback regarding trademarks
 *   I worry a little that SFC is not going to be able to as responsive as we need them to be in the early days of the program
 *   But I think we need to stay the course
 *   yeah :/
 *   ok
 *   what about election process?
 *   The other thing I did was to follow up with Mako regarding the election software
 *   I started putting together a ballot, but realized I need a list of candidates first
 *   I plan to solicit them from the community this week and hold the election beginning next week.
 *   Sound OK?
 *   Or is one week too short of a window?
 *   the list for the people of the commitee right?
 *   maybe a couple weeks
 *   the list of nominees for the oversight committee
 *   Morning all.
 *   Hi Chris.
 *   hey cjb
 *   Maybe two weeks, then?
 *   Should I solicit nominees for all the committees at once? Or leave that for later?
 *   I don't recall: do we elect the other committees or appoint them?
 *   Let me check in the wiki...
 *   There was consensus that we begin with just Oversight and Members committees.
 *   Yes. But it is ambiguous as to whether or not the Members committee is elected or appointed.
 *   I cannot tell from the wording in the wiki: The Oversight Board is responsible for establishing committees as necessary.
 *   i think we said appointed
 *   I'm fine with that. Makes things simpler.
 *   Is an announcement in the wiki and to the initial members list adequate notice for candidate nominations?
 *   I would think so.
 *   I only worry one week may be tight as many people are on vacation/traveling this time of year.
 *   sure - you can as well leave a note in the digest
 *   it sounds fine to me, but one week seems too short yeah
 *   How about nominations close on the 16th and the election begins on the 17th and runs until the 30th?
 *   that sounds good
 *   that should be enough
 *   OK. If people have further thoughts on this, just let me know.
 *   I'll get the word out and we can get past this hurdle.
 *   I think that was all the business from last time.
 *   Are those who were here OK with the minutes?
 *   I included the transcript of the chat, or at least all that I managed to capture, so I think we are pretty complete
 *   Yup.
 *   what about the logo?
 *   there has been any movement on it=?
 *   Good question.
 *   I had given some feedback to Luca and Franco; they were going to work on the fonts
 *   But I haven't seen an update.
 *   I think that we are pretty close.
 *   We do need to move quickly, as OLPC has asked that we remove our current logo
 *   Their lawyers say we are infringing on their trademark
 *   huh
 *   http://sugarlabs.org/go/DesignTeam/Logo-ideas#Designs_by_Luca_Ferrari_and_Franco_Lodato
 *   they know we plan to change it, so they aren't being too aggressive about it
 *   there have been some edits it looks like
 *   (I guess our current logo has an XO and "Sugar". Are they claiming ownership of both at once, or one or the other?)
 *   I don't think we have any problem using XO in the interface, just the logo for Sugar Labs
 *   cool, okay
 * erikos likes this one http://sugarlabs.org/go/Image:Luca-logo-3.jpg
 *   Erikos: I didn't see any new edits to the logos. Just the changes I made as feedback to Luca.
 *   walter, could be that i did not see them all last time
 *   I think we have reasonable consensus on the overall direction and we should leave the final details to the pros.
 *   I have to say their space-age typography has grown on me somewhat.
 *   I thought the little color gimmick I did with fructose and sucrose was cute, but I don't know their thoughts.
 *   So, I think we are ready to jump in to the more meaty topics?
 *   yup
 *   yeah
 *   walter, you said you made some progress on trademarks?
 *   The topics that are really pressing I think are the relationship between the engineering needs of OLPC and the long-term goals
 *   and the relationship to the learning community
 *   They are all somewhat related in my mind, even though they are different agenda items.
 *   Let me explain:
 *   OLPC has immediate needs regarding the 500K machines in the field; Sugar Labs of course should be responsive to these needs since OLPC is the only deployment of Sugar of any significance
 *   That said, the learning community as a whole currently has little access to XOs, so if they are going to have a chance to explore Sugar, it is likely to be on off-the-shelf hardware
 *   Old machines in the classroom or an old laptop at home
 *   I think it is really important that we make it easy for teachers et al. to try out Sugar
 *   there is also the problem of who move forward sugar development
 *   walter, focusing on getting packages in ubuntu/fedora should be a good start or?
 *   implementing new features for example
 *   I don't think the current live CD /USB options are mature enough to the casual user
 *   because OLPC is busy with much more critical problems at the moment
 *   and has no resource, say, to implement the full Journal vision
 *   All of this is at odds with the long-term development goals in terms of our limited resources
 *   I agree about live cd...
 *   To my mind, getting something simple and stable into a package that is easy to explore on a trial basis in a conventional laptop is critical to the growth of Sugar
 *   how do we resource that work though?
 *   we need someone focused on it, if we want it to get mature enough
 * bemasc (n=bens@c-24-62-4-169.hsd1.ma.comcast.net) has joined #sugar-meeting
 *   I'm not even sure that resourcing is as much the problem as knowing what we want
 *   I don't get the feeling OLPC is interested in this direction.
 *   We made a pretty big push for Sugar packages in distros, and it has happened -- volunteers worked on Debian, Ubuntu and Fedora packages
 *   The recent edict to make a "dual-boot" KDE/Sugar machine is some of my evidence.
 *   The Ubuntu/Debian/Fedora push is very important
 *   i think people in 1cc think that sugar is doing ok
 *   and that we don't need more ressources
 * bemasc is sorry to be late; has to borrow neighbor's wireless until Wednesday
 *   erikos: didn't you interview a new Sugar developer this morning? :)
 *   cjb, i would probably have not if i would get all the private messages :/
 *   cjb, but details are not subject here - sorry should not have started
 *   cjb: hiring a Sugar developer is something OLPC wants to do, but clearly not a top priority
 *   which I suppose means we need to find ways to resource the work OLPC is unable to
 *   marcopg, thanks for putting it in better words
 *   marcopg: I think we can say definitively that there will be work Sugar Labs wants that OLPC won't be willing to resource, and we should talk about how to handle that. I'm not convinced yet that it's fair to say that OLPC doesn't want to give any more resources to Sugar.
 *   We're clearly trying to hire, it's just been very slow. We put an offer out to W, but he didn't accept.
 *   cjb: I didn't say that. Just that it's not top prio
 *   marcopg: erikos did
 *   cjb, i meant to say that it is not top prio
 *   (probably he didn't mean to, he is just a little pissed off :P)
 *   and well this KDE thing pisses off quite a bit
 *   So, the bigger question is divergent priorities between Sugar Labs and OLPC.
 *   mainly because we are not informed about it
 *   and we get to know by external people
 *   (but this is an OLPC discussion, so I stop it)
 *   marcopg: It was in a techteam thread yesterday
 *   marcopg: This is a Sugar Labs discussion.
 *   cjb: which one?
 *   marcopg, about double boot
 *   q
 *   marcopg: from Kim, buried in the SW-ECO thread last night
 *   I suspect that the people talking about this don't particularly mean "KDE" and would be just as happy with XFCE.
 *   I will read it
 *   is this about G1G1 or about schools too?
 *   Let's not dwell on the KDE details. I only bring it up to suggest that the changing priorities of OLPC make it difficult for us to make long-term plans
 *   marcopg: also, we shouldn't think of Walter as an "external person". He's trusted by OLPC to hear their long-term plans, which is why they tell him stuff like this, and it's not the same as having broadcasted it to the world.
 *   bemasc: agreed
 *   marcopg: G1G1
 *   marcopg: it's to reduce G1G1 support queries by people who aren't patient enough to work with Sugar
 *   happy to know that olpc still consider walter an internal person :)
 *   I still think we need to "contract" some architectural work in several areas to address the reasons why Sugar "sucks"
 *   I've been advocating for some time that, rather than attempt to make Sugar run all legacy applications, we should provide a separate legacy environment
 *   cjb: ok that's good to know
 *   bemasc: you and everyone else. But the that is not the point here
 *   someone needs to do that work
 *   being it design or just implementation
 *   Can we agree to disagree about the need to architect our software goals?
 *   of course
 *   Is there a concrete decision we are trying to make? Perhaps I missed it.
 *   I don't know how we make progress on, for example collaboration, without an agreed upon framework. The disconnect between Scott's piece in the wiki and Greg's document from a couple of days ago is dramatic.
 *   I think we probably just mean different things by architect. At the moment everyone's just fire-fighting, so there are many aspects of architecture (blue-sky design, seeing changes through from design to implementation, ..) missing.
 *   and collabora plans too, likely
 *   I would like to have someone write down the goals--a la the bitfrost document--and they we can have the community fire away
 *   But it is a rudderless exercise right now.
 *   the bitfrost document remains essentially unimplemented
 *   As someone -- was it Poly -- pointed out, there is no decisionmaking process.
 *   also, while I have high regard for the Bitfrost design, it is essentially a listing of how to do secure containerization using vserver
 *   Bitfrost is largely unimplemented, but we aren't spinning our wheels deciding what are goals are.
 *   bemasc: -EOFFTOPIC :)
 *   Is the word vserver even mentioned in the Bitfrost spec?
 *   If we could agree on the high-level goals, we could have a better chance of unleashing the community to take action.
 *   what I'm trying to say is, Bitfrost is a helpful guideline, but it's not a brand-new blueprint for security architecture
 *   it's just a thin metaphor over vserver
 *   we might want to go back o the topic: how do we implement the parts not interested by OLPC
 *   I'm skeptical the community will take action on the base of a spec
 *   erikos: step 1: by specifying what they are and why they're important
 *   we need someone to lead the implementation of these components
 *   Bitfrost is not a spec, true. That is fine in my book
 *   and do it in a way that the community can be involved in
 *   Yes. Yes.
 *   +1 to what marco said
 *   If we agree to the goals, then, for example, we can say to Poly: if there are so many superior algorithms that meet these goals, then put one forward.
 *   I agree. The only way to pick winners in an open project is to pick the spec that has been implemented
 *   But without an agreed upon goal, we cannot measure results
 * unmadindu (n=sayamind@gnu-india/admin/unmadindu) has joined #sugar-meeting
 *   So maybe it is a matter of semantics, our disagreement.
 *   I think we were very close to finalizing a set of goals and overarching designs for the Journal/datastore in January.
 *   cool!
 *   what's happening in January?
 *   cjb: no, January 2008
 *   oops
 *   I thought s/were/are/
 *   the Datastore Summit
 *   Yes, the Datastore Summit
 *   I guess my point is that even once the requirements are clear, you still need someone to take care of doing most of the implementation
 *   that didn't go very well, because there were only a few people there and the discussion remained private
 *   If Scott had time to come up for air, he could probably pull all the pieces together quickly for the community to take over (with help from Tomeu, ofcourse)
 *   Ivan was apparently tasked with drawing up a detailed design document, and then everything fell apart
 *   I don't think Scott was *at* the datastore summit
 *   we can't hope the community will step up to implement complex components like the datastore
 *   I don'
 *   he was not
 *   I don't think a private planning meeting is a bad thing. It is fine if the results are made public for vetting. If wasn'
 *   Ivan was supposed to spec what we agreed at that summit
 *   marcopg: depends how you look at it. I'd claim that Federico is working on doing it :)
 *   t an edict, like KDE
 *   and get larger feedback
 *   marcopg, i guess the community can do the 'simpler tasks' to free the other devs from doing them
 *   but it didn't happen
 *   heh
 *   It is that things like that slip between the cracks that is the problem.
 *   http://www.gnome.org/~federico/news-2008-07.html
 *   GNOME's thinking about a document-centric desktop
 *   The day-to-day firefights tend to dominate people's time; hence my proposal to dedicate some people to wrapping these things up.
 *   something we could do is try to make sure we can influence their thinking so that the result could be used by sugar too
 *   that would have some great benefits; we'd get compatibility with GNOME without even trying. :)
 *   My feeling on the datastore is maybe a good example of why I'm resisting the push for an architecture document. I think it would be better to implement a simple versioning datastore that's backwards-compatible with the current API.  That seems quite easy to me.  We can move incrementally from there.
 *   cjb: yeah we should try to get involved in that
 *   (we're == OLPC)
 *   I agree that most of Sugar's technologies (isolation, central document store, versioning, pervasive collaboration) are a natural fit for a next-gen Gnome.
 *   I think that if we had a document, then we could assess your proposal and perhaps quickly agree to it.
 *   I think if we had a set of clear goals, we could quickly assess your assertion and probably agree to it.
 *   here's some of the stuff people have been doing in GNOME:
 *   http://www.iola.dk/nemo/blog/?p=3
 *   so, time-centric rather than folder-centric, has labels/categories, things like that.
 *   For what it is worth, when I spoke to Stormy yesterday from the Gnome foundation, she promised whatever cooperation she could muster.
 *   maybe we should take an action item for someone (maybe dfarning?) to make contact with the people who've expressed interest in the GNOME datastore work
 *   If we could agree on what we are looking for, we could probably leverage their work.
 *   right
 * morgs concludes first meeting of #ubuntu-sugarteam
 *   and I think the work's happening right now, so it would be a good time to introduce ourselves and share ideas
 *   I'm not sure what you would like to see in such document yet
 *   morgs: wow!
 *   morgs, congrats!
 *   I asked the GVFS people, and it sounds like GVFS is very focused on the standard filesystem approach, and so not of much use to us in its current form.
 *   morgs: cool
 *   the requirements? or the implementation details for these components?
 *   The meta issue again is how to get the resources pulled together to be able to define and agree upon these questions
 *   ok
 *   I'm beginning to understand this discussion correctly.
 *   So the obvious thing that can happen is: someone with an architecture plan can write it up on the wiki and solicit improvements. Once it's ready, they can post it to the mailing list and say "who wants to help work on this".  A bunch of people can get together, open a repository, and start coding.  After it's working, they can ask the gatekeepers (marcopg, tomeu?) to include it.
 *   The question is: is there something we should do to help this process along, such as blessing a particular proposal or directing specific developers to work on specific tasks?
 *   bemasc, i think that you have to guide it a bit
 *   My feeling is that Sugar Labs doesn't have any resources (e.g. $$) that allow us to make people do things they don't want to do.
 *   and how do we encourage the community to do the architecture work?
 * mtd proposes walter as BDFL and then we could move on :).
 *   bemasc, unless the interests are overlapping greatly - someone will not jump up and code soemthing like the datastore
 *   marcopg: we say "Hey you! _You_ can write designs for Sugar. _Anyone_ can make designs for Sugar.  Try it!  We'll keep our criticism friendly."
 *   bemasc: I think in the case of design work, it's not even that we don't want to do it, it's just that we're busy with an OLPC release for the next month.
 *   specing things might help to show what we are interested in - and if there are overlaps yuo can work together
 *   cscott stepped up to do that work on both the datastore and network
 *   I don't think we need to resolve anything more than "if you have an idea, write a spec on the wiki, and e-mail it out to sugar@"
 *   but it didn't produce anything useful yet
 *   why it didn't work?
 *   marcopg: the network part didn't work because there are lots of people working on the network, and cscott is not their boss
 *   hmm i can tell you
 *   marcopg: I'm not sure.
 *   bemasc: what about ds?
 *   yeah, the networking thing is a disaster. no surprises there.  olpcfs seemed to be going well, though.
 *   marcopg, you can not only start - you need to follow up as well
 *   also, I contest that olpcfs hasn't produced anything useful. It's usable today, just not as a journal backend.
 *   my feeling is that until you have an implementation and a maintainer
 *   the spec is not very compelling to the community that needs to accept it
 *   This is the open source world. Ultimately, what matters is the code.
 *   cjb: what I mean, is that we are far from an agreement on olpcfs technical merits, let alone on a concrete plan to land it
 *   yeah. the more I think about the datastore, the more I realize that the !olpc sugar developer community is still small, and the best shot for the moment is to latch on to the GNOME people who are currently very excited about it and make sure they're working on the same goals
 *   marcopg: right. so, maybe that's the problem -- cscott presented it and didn't really get strong feedback saying he should land it next release, so he left it alone
 *   cjb: that's really the same approach we're taking with networking. I think the next Gnome will use Telepathy+Empathy as its default IM client.
 *   (that's a guess, I don't know if it's actually what happened)
 *   I think the need is both a olpcfs spec and a connection to the various components that need building
 *   (also, some other examples of versioned filesystems have come along since olpcfs)
 *   Maybe we should move on for now?
 *   so what's the next step here? should we encourage people to work on the designs for both ds and network?
 *   and participate actively to the discussion about this on the mailing lists?
 *   I guess I don't see other ways to reach an agreement...
 *   I think we need to be more focused than jut ask people to jump in
 *   I'm fine with moving on, but I'd like to at least reach an agreement on an action item to move this a little forward
 *   and probably try to make it as public as possible to get feedback from other communities
 *   or at least that they are aware of
 *   marcopg: my suggestion is the GNOME contact
 *   I don't think we need a network rearchitecture. Collabora is very much on the case, and Telepathy seems like the right solution to me.
 *   cjb: yeah but even in that case we need to come up with a good description of our goals
 *   Anyone here friends with lots of Gnome devs?
 *   yeah. J5
 *   (I guess the GNOME is lacking versioning btw, which is fundamental in our design)
 *   We can organize a "user-friendly storage" IRC meeting with all the people working on these problems.
 *   sounds good!
 *   even just letting them know that we want to use their code and are happy to show them ours would be a fine outcome of such a meeting
 *   How about setting a tentative date/time, publicizing it on sugar@ and devel@ and gnome lists and freedesktop.org lists and ...?
 *   and also specfically inviting people we know to be working on such projects?
 *   maybe stormy can help publicizing inside gnome
 *   I think tomeu's on vacation for two weeks or so?
 *   it could be after he gets back
 *   yeah, one week
 *   cjb: that would be fine with me
 *   we could do it in a couple weeks
 *   okay, so tentatively mid-August
 *   since it would be good to let OLPC's 8.2 work cool off a little too
 *   how can we note this so as not to forget about it?
 *   minutes? :)
 *   action item in the minutes I guess
 *   hmm guys the emperor has no clothes: you really expect to get a new DS from this process in the next year? via an IRC meeting?
 *   ...with no hiring?
 *   not in the next year for sure
 *   oh ok
 *   mtd: well, this is my point too. we don't, which is why we latch onto GNOME, which has a much larger community base
 *   mtd: the point is that the Gnome people are thinking about the same problems, as are the developers of Btrfs and Tux3 and ...
 *   even with GNOME, it's likely to take years
 *   if we want immediate action, there is no other way then hiring imo
 *   of course.
 *   right, ok. So basically we should stop worrying about it (besides agitating for upstream) and focus on other stuff?  So no more "the DS sucks" distractions?
 *   I'll go with that.
 *   mtd: I disagree. I think we also need a simple, short-term DS replacement.
 *   sorry... I was on the phone with AMD and only half in the discussion
 *   They'll try to get us a server.
 *   That was actually scheduled for 8.2, and then dropped.
 *   yeah agree with bemasc
 *   I need to send them a spec
 *   we should incrementally improve the DS
 *   while a better system is being cooked, hopefully with the larger GNOME community
 *   marcopg: I guess I'm saying that I don't think it'll take much for a GNOME ds to become better than our current one.
 *   and that we're at a critical point in our opportunity to shape their work so that we can use it.
 *   oh, I found the incomplete datastore redesign stuff: http://wiki.laptop.org/go/Category:DatastoreRedesign
 *   I don't remember why we dropped DS refresh from 8.2
 *   cjb: I should look more into what they have right now to say that
 *   cjb: in particular I'm not sure about versioning
 *   was it because we didn't think we could complete it in time (and test it)
 *   I think it just fell off the stack
 *   we could punt on versioning until it can be done as part of the GNOME thing, I guess
 *   (we didn't do that, though)
 * bemasc still doesn't like olpcfs
 *   It would be helpful if the OLPC devs kept an explicit public work-queue, but that would also be tremendously invasive.
 *   my suspect is that the GNOME thing is just based on a normal filesystem
 *   which gives great compatibility
 *   bemasc: I think it would too depressing to see "June: Firefighting.  July:  Firefighting."
 * dirakx (n=rafael@190.156.106.187) has joined #sugar-meeting
 *   but also limits quite a bit the features you can get
 *   cjb: true
 *   marcopg: well, we have the chance to tell them to use a db instead
 *   it's an enanched file manager, not an enanched file store
 *   We shouldn't debate the details here, but what is the agreed upon action plan?
 *   yeah
 *   And for the network?
 *   the initial code for nautilus seems to be at http://gitorious.org/projects/nautilus/repos/mainline
 *   And for our LiveCD strategy?
 *   walter: we'll pick a date to hold an IRC meeting about document-centric storage. We'll ask you to use your contact with Stormy to publicize it to the GNOME community at-large, and we'll invite some key people by hand.
 *   for the datastore I think we should take the time to look into nemo
 *   and try to organize an irc meeting with all the people interested
 *   I guess I'm about to say something controversial: I don't think networking has much to do with Sugar
 *   I'd certainly put telepathy outside the Sugar stack
 *   cjb: I agree with you, but the fact that collaboration is so important to Sugar...
 *   that doesn't mean Sugar shouldn't have networking APIs -- the presence service is a good example of one, it says "once you know how you want to communicate presence, you call this add_buddy function and I'll show it on the screen"
 *   perhaps, but we need to ensure Sugar has a good collab framework it can use
 *   and the fact that it is so unstable and unpredictable...
 *   but it does mean that the primary problems with networking right now aren't really Sugar's fault, or Sugar's area to fix
 *   personally I'm fine with collabora keeping to cook it
 *   and confident they will slowly get there...
 *   means that we cannot rely on it
 *   cjb: this is a taxonomy problem, of course.
 *   collabora is also working with GNOME a lot
 *   I agree that power management is not a Sugar problem...
 *   which bring us in the same good direction as trying to coordinate with them about the ds
 *   power management is not a Sugar Labs problem, at least not a big one.
 *   cjb: you're right. I think what's just been argued about the DS could be argued about collab.
 *   well, I suppose if there is nothing we can do, we should focus on what we can fix: DS, tc.
 *   tc?
 *   etc.
 *   oh :)
 *   I cannot seem to type today :(
 *   yeah I'd say to start from the DS
 *   I want to return to the boot image question for a moment
 *   good
 *   I think there's great potential for working on DS with the GNOME community. It'll introduce us to them, could engage a lot of their developers with Sugar.
 *   it is critical to getting people to try Sugar in the field
 *   apt-get sugar (or yum install sugar) is great, but not good enough yet for those not on the bleeding edge
 *   do we have agreement on what we need there?
 *   morgs: ubuntu seems like a great platform for Sugar LiveCDs. Are there people on your team interested in producing them?
 *   did you see the appliance someone at rh is working on?
 *   bemasc: so is Fedora :P
 *   marcopg: I could not figure out what "appliance" means in this context. It seems to be a Fedora-specific term.
 *   morgs: I agree, but for example, I have a friend in Kenya right now, running ubuntu in schools, and he cannot get Sugar to install...
 *   he needs to upgrade too much stuff for his network capacity
 *   bemasc, heh have problems with it as well
 *   bemasc: http://www.vmware.com/appliances/
 *   yuck, vmware
 *   oh it doesn't use vmware
 *   was just an example of the same concept outside Fedora :)
 *   I am still intrigued with the possibility of using Ubuntu's Wubi with an Ubuntu Sugar livecd
 *   It seems we are close along any number of fronts. This may be a place where the community could jump in, perhaps the ubuntu-sugarteam could take a leadership role
 *   I am not familiar with Wubi
 *   Wubi runs a complete linux VM under Windows
 *   the Fedora/OLPC interest group seem to be working well
 *   perhaps we could get quite a bit of help from them on this one
 *   but anyway
 *   Between the two, if we could really make it plug and play...
 *   Wubi would be great for getting Sugar onto existing Windows-based desktops in schools
 *   I would like to understand what we are aiming to
 *   walter: the idea would be that rebooting into a livecd is a lot of disruption, and popping up a Sugar window on their Windows machine would make it a lot easier.
 *   the other question is configuration of these machines.
 *   is a well working livecd what we need here?
 *   the network for sharing, etc.
 *   marcopg: yes, that would be great
 *   or liveusb, which gives you rw
 *   marcopg: that would also be great
 *   we really need all these things, and we need them kept automatically up to date
 *   I have that working for Fedora...
 *   Liveusb is attractive: we could give them away at education summits
 *   the thing is that we need someone with enough time to make it work well
 *   well, there's the fedora-olpc-list now
 *   I think this is a matter of being organized more than anything else...
 *   and to ensure it always have the latest versions etc
 *   the community can do this!!
 *   sure
 *   here the community can really be a lot of help
 *   if you look at the applicance thread
 *   Would Dennis be the lead in the Fedora community?
 *   there are people already that are trying to make it work
 *   This is a great task for new arrivals from the outside world. I'm perfectly happy to push parallel Fedora- and Ubuntu- based efforts
 *   not that with the same config as the appliance
 *   you can also generate liveusb and livecd
 *   s/not/note
 *   cool
 *   walter: I think Greg DeKoeningsberg would do a great job, actually
 *   yeah
 *   So how do we push this?
 *   Maybe I should contact Greg DeK.?
 *   (in case people didn't know, Dennis is moving from OLPC to Red Hat. He'll still be around a bit.)
 *   walter: yup, sounds great
 *   perhaps we ask gdk to push it in fedora
 *   walter: he'll be in Cambridge next week or the week after next or so
 *   and morgs can help out on the ubuntu side
 *   I didn't know Dennis was leaving. He's been a great help.
 *   walter: you should get on his timetable :)
 *   walter, yeah sadly he is - but he has suggested a replacement already
 *   and Red Hat's particularly friendly to OLPC at the moment :)
 *   that is a good change in the wind
 *   so it seems we have a plan for liveCD/liveusb/appliance etc.
 *   this will help with our outreach efforts
 *   other topics for today?
 *   yeah
 *   I wonder if we should talk about Portugal at all
 *   I pinged Intel on this.
 *   They said they'd get back to me.
 *   But who knows.
 *   *nod*
 *   Anyway, isn't Tomeu handling this while he is on holiday :)
 *   hehe
 *   ah, infiltrating from within, cunning.
 *   I think Intel (like OLPC) is taking an attitude that they'll give the customer whatever they want
 *   Windows, Linux, KDE, Sugar, etc.
 *   so we just need to convince their customers that Sugar is better :)
 *   But we need to make sure Sugar is on the list at a minimum
 *   The trick with Intel is the incentive to their Sales force.
 *   the award winning UI! :)
 *   deploying Sugar on a non-XO device is going to be fairly tricky
 *   walter, i only hope - that this means as well that they keep on supporting sugar
 *   walter, and not just outsource that whole part
 *   bemasc: we need to exactly how so
 *   at a minimum, Networkmanager will have to be reconfigured substantially, the power management stuff will probably have to be removed... and I'm not even talking about resolution independence.
 *   also, OLPC has little incentive to support this sort of work
 *   bemasc: s/little/no/
 *   bemasc: what probs do you expect with NM?
 *   marcopg: mesh
 *   but that's okay, because the work isn't that hard.
 *   I mean the current nm supports normal access points just fine
 *   mesh on the Intel platform is Intel's problem, but collaboration through AP works out of the box
 *   and works in a way that is compatible with the XO
 *   bemasc: install Fedora 9, yum install sugar, run it, fix bug, repeat.
 *   marcopg: the question is whether NM will correctly recognize that there is no mesh device, and if that recognition will propagate correctly up through the UI
 *   bemasc: it clearly does so on Fedora 9.
 *   bemasc: yeah
 *   I think most of the resolution issues are covered at this point
 *   oh, you're worried about spurious mesh circles in the UI. Well, that might happen.
 *   but it's not like it crashes :)
 *   resolution is some tricky/not fun work, but should not take too much
 *   not sure which pm stuff you are referring to
 *   I notice few if any anomalies when I run on my non-XO
 *   bemasc: to elaborate on s/little/no/, I think after an OLPC-Sugar Labs split, porting to new platforms is one of Sugar Labs' main purposes, and becomes not part of OLPC's purpose at all.
 *   but well that guy is picky :P
 *   cjb: certainly
 *   cjb: right. Ideally, Intel would fund the port.
 *   I don't mean that OLPC doesn't gain anything from it, though. It's in everyone's interest for more people using Sugar and writing activities.
 *   I think they (Intel) and others need to kick in.
 *   there are several little things which are XO specific
 *   but in general I expect it to not be a bunch of work
 *   (it also mentioned Windows)
 *   oh yeah seen that one
 *   Where was it published?
 *   the bid?
 *   I've never seen it.
 *   It was linked from olpcnews, will find a URL
 *   We should probably wrap up soon.
 *   http://www.latu.org.uy/portal/page?_pageid=514,1&_dad=portal&_schema=PORTAL
 *   http://www.olpcnews.com/countries/uruguay/ceibal_project_progress.html
 *   I'll write up the notes
 *   cjb: thanks.
 *   thanks!
 *   the bottom link on the latu page is the Sugar job, and there are two PDFs, the particulares PDF:
 *   thanks
 *   >''' Se verificará que la interfaz desarrollada pueda ser instalada y correr al menos sobre las
 *   variantes del sistema operativo Linux DEBIAN y FEDORA.
 *   >''' Se verificará que la interfaz desarrollada pueda ser instalada y correr al menos sobre los
 *   equipos XO, Classmate PC, Asus eee.
 *   I think the action items are the (1) election; (2) the server; (3) the logo; (4) gnome outreach for the DS; (5) outreacht o ubunutu and fedora re liveCD
 *   anything I missed?
 *   sounds good.
 *   good
 *   it really would be excellent to Sugar on Portugal's laptops, although there's no specific action item :) It'd be worth e.g. a plane ride to show them what we can do.
 *   s/to/to get/
 *   yeah
 *   sounds like we should try to be active on that front :)
 *   We need to find out who are the decision-makers. I don't know if Intel will invite us...
 *   I'll push for it.
 *   Thanks everyone for participating today.
 *   thanks!
 *   Please make suggestions for new topics in the wiki.
 *   ok thanks!
 *   Have a good weekend
 *   Chris, get to the Go Club!!
 *   ok thanks!
 *   Have a good weekend
 *   Chris, get to the Go Club!!