Oversight Board/2008/Log-2008-07-18

irc.freenode.net #sugar-meeting

2008.07.18 17:00UTC
(Alas, I managed to lose the very beginning of the log file... --Walter 20:19, 18 July 2008 (UTC))


 *   cjb is on the board for olpc right?
 *   so the members are finalized?
 *   I haven't heard back from Karen if she agrees to represent SFC
 *   The document is on the wiki now:
 *   http://wiki.sugarlabs.org/go/SFC-SugarLabs_Agreement
 *   CJB is the OLPC rep.
 *   cjb is traveling to 1cc
 *   I compiled an initial membership list so that we can hold an election.
 *   he wanted to make to this meeting
 *   I tried to be inclusive of all the Sugar contributors and anyone who spoke up recently.
 *   I think it is fair and reasonable place to start from
 *   I'd like to use Mako's tool (http://selectricity.media.mit.edu/) to hold an election...
 *   we don't have SJ; I suppose he is still in Egypt
 *   Hello! Sorry I'm late.
 *   We can let any member nominate candidates for the various committees and then vote for up to n people, where n is the size of the committee
 *   (reading)
 *   (SJ had a number of distinctive things to say about the voting/committee system)
 *   I've not heard any of them, nor seen any comments posted in the governance pages...
 *   Can you talk him into sharing his ideas more publicly?
 *   (We don't bite)
 *   I will try
 *   can't see anything bad in the agreement, but I'm not a lawyer :)
 *   I trust Mako's judgment in process...
 *   marcopg, you are the representative of us devs?
 *   not sure actually, I guess
 *   erikos: not that this board is only temporary
 *   one will be elected
 *   (when?)
 *   Re the agreement, the concern I had was pretty simple: it is an agreement about being an ope-source project, which is fine, but Sugar Labs is really about a different set of goals, of which FOSS is a principle means
 *   I hope we can hold the election in August
 *   walter: we may not be able to do all we want to do in one single organization
 *   marcopg, don't really understood your comment
 *   erikos: I mean the current members of the board are temporary
 *   erikos: the real board will be elected, hopefully in August
 *   marcopg, ok
 *   dfarning: !
 *   Simon, please nominate lots of developers!!
 *   dfarning, hello!
 *   Hello all
 *   Dave, I'll be posing the log of what you've missed so far...
 *   walter, that could be elected you mean?
 *   walter, i guess that was the list you talked about earlier
 *   I hope we get a good set of nominations that represent all aspects of the community.... then we will elect from there...
 *   walter: are you trying to address that concern with Karen?
 *   walter: "any software distributed by the Project will be distributed solely as Free Software" is certainly a striking statement, but given the makeup of the Sugar Labs community I don't think it represents a meaningful restriction
 *   walter, sounds good
 *   I think the FOSS nature of the Conservancy is not an issue for us...
 *   We won't restrict, but rather will encourage other organizations to grow up around us
 *   They can build upon Sugar in different ways...
 *   sounds good
 *   ok, any other issue people can think of?
 *   walter: so you are basically happy with the document you posted? Just waiting for Karen to signoff?
 *   We should decide on initial committees before the election
 *   I think the basic relationship with SFC and the governance model are in reasonably good shape
 *   Is there any (personal) financial liability we should be worried about, or anything like that?
 *   I think we are cool re liability, but I will check with Karen. (I think this is one way we are immediately helped by the SFC)
 *   (It doesn't sound like it, but it's my first time on a board, not sure what our responsibilities are.)
 *   We aren't really the "board" since there will be a board for the SFC.
 *   I see.
 *   We are an advisory group.
 *   But I will check with Karen whether we need some liability insurance of some sort...
 *   Something to add to the budget if necessary
 *   She told me that she'd be back with any final edits sooner than later...
 *   As you may recall, we already have provisional acceptance into the conservancy
 *   And I haven't heard any negative feedback from the community.
 *   I don't think I have any comments on the free software clause. Most of Sugar (the parts that might be extended) is LGPL, so it's legal for someone else to link e.g. a proprietary activity to it.  I'm happy with the statement that Sugar Labs won't do that, though.
 *   I agree.
 *   yeah +1
 *   it all sounds like it's going well
 *   (Even if I did have comments, maybe I'd have to run them by OLPC to check they reflected OLPC's opinion first ;-)
 *   I am only concerned that the project not be seen so narrowly as just a FOSS project.
 *   *nod* It sounds like the biggest problem, then, is "A":
 *   > The purpose of the Project is to produce and distribute and support the use of software [..]
 *   Please do make sure that the OLPC crowd is comfortable with what we are doing
 *   right
 *   can we think of a redefinition to suggest?
 *   are we allowed to change it?
 *   "support" makes it quite broad
 *   bemasc: we should certainly be allowed to propose a change.
 *   cjb: true
 *   I added the support the use of language...
 *   my view is that this line is in fact a true statement. It just places the emphasis in a slightly wrong way.
 *   not usually part of their agreements...
 *   walter: oh, that's very good
 *   walter: I'll either write a individual report for OLPC, or make sure the minutes get seen with some commentary if any is necessary.
 *   So, everyone OK with this? We can await final feedback from Karen and OLPC?
 *   I am ok
 *   I don't think we should worry about people getting the wrong idea about Sugar labs from reading our Sponsorship Agreement
 *   What sort of activities can Sugar Labs do that aren't based around producing software?
 *   if the software is towards education, support is *really* broad
 *   cjb: curricula
 *   bemasc: Ah! Maybe "content" is a missing word?
 *   e.g. "The purpose of the Project is to produce and distribute and support the use of software and content"
 *   that may work quite well
 *   Personally, I think Sugar Labs itself is not doing the content distribution and support, but it is hard to draw a line between software and content these days.
 *   I don't really care how accurate this document is. No one who wants to know what we're all about is going to look for the answer here.
 *   sound like with content it would cover pretty much everything we can do
 *   walter: right
 *   That would be an example of an affiliated effort.
 *   bemasc: I'm asking partly because I don't already know the answer to "What does Sugar Labs want to do?".
 *   Like OLPC Nepal'
 *   And while it's not necessary to agree in a legal document, it's at least a good idea to make sure we all understand.
 *   I can hardly see any disagreement between the SFC and us, philosophically, regardless of how we phrase this, so I am not concerned.
 *   I think Sugar Labs wants to support the engineering and learning communities
 *   again, FOSS is an important (and non-controversial) means
 *   bemasc: the question I'd ask is, can you see disagreement between us and us?
 *   well, we can support the software by producing content
 *   cjb: certainly, I can disagreement within myself about what Sugar Labs should be... and that's fine. We're friendly people around here, so disagreements of this sort do not worry me either.
 *   walter: do we support member of the community which does closed content?
 *   Or support the meta process of developing content.
 *   I think we only support non-FOSS in being a project in which people and draw from for their own purposes
 *   bemasc: sure. but that disagreement means this conversation is worth having even if the piece of paper it ultimately produces is not particularly.
 *   ok
 *   But I cannot imagine a scenario where we'd directly support a non-FOSS effort
 *   walter: that sounds good
 *   marcopg: a very interesting question. How about "we will take efforts to assist creators of non-free content only to the degree that those efforts seem likely to assist creators of free content".
 *   If that were to be the case, we'd have to leave the Conservancy
 *   I think it is an unlikely scenario, so we should probably cross that bridge only when we come to it.
 *   yeah
 *   Yeah. I don't think any of this needs to go into the document.
 *   but then, probably should be a partner organization to do that
 *   Can we think of other things Sugar Labs might want to do that aren't directly creating software or content?
 *   For example, do we want to.. fly educators in to hold workshops, things like that?
 *   I see that clearly in support
 *   cjb: that's supporting learning right? so I'd say yet
 *   yes
 *   Maybe we should jump to Topic 3 for a moment
 *   Righto.
 *   there are a lot of things that we may want to do, such as provide professional support to people deploying Sugar, but many of these things may end up easiest to do outside Sugar Labs itself.
 *   I think Sugar Labs is about bringing the best of engineering and learning together
 *   fostering that community around a vision
 *   I hope lots of "for profit" enterprise grows up around Sugar
 *   but Sugar Labs is the glue that keeps these efforts working towards the same goal
 *   ok, we can push those conflicts out from sugar labs, is that?
 *   the same people can be involved, it just doesn't need to happen inside the sugar labs umbrella
 *   Not sure what conflicts you are referring to
 *   walter: in case we want to do something not in the stated goals of the project
 *   but yes, just as there can be multiple licenses for code, people can have multiple goals and affilations
 *   But the Sugar Labs focus must stay clear or we'll never get anything done
 *   speaking of which, I think we're happy enough with this document to move on.
 *   +1
 *   So...
 *   Any concerns re membership except the ones we hope to hear from SJ?
 *   only concern is that i can not access the page
 *   I don't think we have much representation from educators yet, but there is some...
 *   (Mako's page is down, but the list in the wiki should be accessible)
 *   walter, where is the list again?
 *   uy teachers look quite active in the sur ml
 *   cjl: selectricity.org is up
 *   http://wiki.sugarlabs.org/go/Sugar_Labs/initial_members_list
 *   thanks!
 *   the link in Mako's blog was wrong.... I've updated the link to .org
 *   yup have it now
 *   I'll take a first pass at creating the vote structure and report back
 *   ok
 *   so... committees?
 *   walter: do we need to setup a way for people to request membership?
 *   I don't think it needs to be too complicated
 *   before the elections that would be
 *   otherwise it seems like *we* designated the members
 *   (in GNOME it works that way)
 *   The membership committee can handle members, but we had to start somewhere.
 *   Gentoo accomplishes something like this by requiring that new developers be sponsored by existing developers.
 *   I've been soliciting on the lists for members and got quite a few that way, so I think the word is out
 *   but yes, the solution is to create membership committee so we don't have to think about it
 *   +1
 *   if you all think this is fine for the first election I'm ok
 *   bemasc, the membership committee?
 *   well, once the SFC deal goes through a big announcement will be in order
 *   erikos: http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Committees
 *   I've tried to have a very public discussion about it, so I think we are OK to get started
 *   ok with me
 *   bemasc, ok thanks
 *   Again, my concern is not developers, whom I think are so far pretty well represented
 *   But there are few educators... this is how we differ from other projects
 *   sure that's great...
 *   my concern was mostly political
 *   i.e. people might not see the election as completely impartial
 *   it seems to me that it would be nice to have an elections committee prior to the elections. Anyone want to be on the membership+elections committee?
 *   I think we should be OK... people have had lots of opportunity to speak up...
 *   because someone designated the electors
 *   and there is no real exchange between educators and devs i think
 *   I am working on locating a few people to bridge the developer/educator gap
 *   Yes. and a few others are as well.
 *   Reaching out particularly to teachers in the large deployments
 *   One thing we can do, and that I have started doing, is saying to educators "If you have an idea, we can build it", a little like the Linux Drivers Project. Perhaps we can make that more official.
 *   I don't know how closely you follow the olpc-sur discussion, but it is pretty good
 *   not official; public
 *   should we finish up on the committees?
 *   do we have a list of those? I thought we had
 *   marcopg: http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Committees
 *   ok membership is clearly needed
 *   finance seems also clear
 *   community seem important to me
 *   infrastructure seems necessary
 *   someone to organize the events etc
 *   bemasc: what's the role of the infra one?
 *   I mean
 *   marcopg: to manage sugarlabs.org
 *   how is it different from sysadmin
 *   marcopg: it's not
 *   committees are elected? I forgot
 *   I actually argued at one point for a Treasurer to head the finance committee and a Sysadmin to head the infrastructure committee
 *   I have those roles, but not in the committee list
 *   marcopg: currently, they are. I'm not sure that elections are the best way for committees, but I don't know what the best way is.
 *   it's a little weird to have an elected or even designated sysadmin team
 *   shouldn't that work like the developers team?
 *   http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Oversight_Board
 *   or is the committee to decide which servers to buy for example?
 *   I am not sure every committee member has to be elected
 *   but the heads of the committees should be elected
 *   they set policy as much as implement
 *   walter: yeah I'm just not sure if the sysadmin team should be related to the board at all
 *   marcopg: to decide what servers to buy, to decide to switch from mediawiki to texwiki, to decide that we will run our own Jabber server, etc.
 *   it seem like a technical thing
 *   but yeah since we are going to spend the foundation money on it, it might make sense
 *   I think sysadmin and treasurer are working on behalf of the committees
 *   not sure if it's large enough to require a committee though
 *   or if the board could handle directly
 *   What about setting policy at bcrat level on wiki, etc. stuff that needs an arbitration mechanism, it if comes to it.
 *   the treasurer I think we get from the SF Conservancy, so it is really just sysadmin
 *   many people told us we have too many committees there
 *   marcopg, the committee should probably get technical opinions from the devs and admins and then decide
 *   erikos: yeah but the same can do the board directly
 *   just trying to see if we can reduce the number of committees a bit I guess
 *   marcopg: we used to have too many committees. Also, I see the education committee as a trick to lure in more educators.
 *   and create them on demand
 *   marcopg, committee in general sounds scary to me :)
 *   oh we already reduced them
 *   I don't know which committees to eliminate, but we need not launch them all at once
 *   marcopg: that page is called "bootstrapping", with the idea that once things are running, we can change committees as needed
 *   But we should take care, because disbanding a committee is probably difficult
 *   walter: ok, so which ones we need right away?
 *   Infrastructure not needed day one oversight will handle it.
 *   oversight will handle any details that nobody else is handling
 *   also maybe finance can lean on the SFC in the beginning
 *   Membership, finance needed day one, community on day two.
 *   membership is the obvious one
 *   maybe that is all we elect at the start
 *   walter: I like that.
 *   finance somewhat optional, nice to have out of hands of oversight for trust reasons.
 *   walter: make sense
 *   committees may help with people feeling more responsible of their areas of contribution?
 *   cjl: that sounds backwards :)
 *   we can elect the membership and elections committee, who then get to figure out how to proceed.
 *   We have the SFC to handle the money (of which we have none) to start
 *   (what greg dek said about having tons of VPs)
 *   I don't recall... sounds like a Dilbert
 *   tomeu: I think that's on the technical side mostly
 *   like the bug triage team lead
 *   hmm, sure?
 *   cjb it is a two-man segregation of duties thing. I deal with Sarbanes-Oxley compliance at a public company :-(
 *   or the documentation team lead
 *   I think what dfarning set up goes very much in that direction
 *   we have these teams people can feel part of
 *   or even lead
 *   walter: when edward cherlin became our VP of localization
 *   I'm not sure exactly what the VP thing is all about... heads of our working groups/task forces??
 *   walter: of our teams I think, yeah
 *   One question is who gets a beautiful Sugar Labs business card?
 *   Any member?
 *   anyone?
 *   creative commons!
 *   And then we can have some means of assigning titles?
 *   sounds good
 *   any member I'd say
 *   anyway
 *   Then many the head of each task force (as designated by the taxonomy that Dave set up) becomes a VP?
 *   People tend to be encouraged towards volunteerism by having their role made public and obvious, so all sounds good.
 *   do we agree about setting up membership and do the others on demand?
 *   are you suggesting that Sugar Labs will have VP posts?
 *   I'm still pretty confused about why non-educators volunteer for Sugar. It's not scratching an itch.  :)
 *   I don't see that anywhere in the governance document...
 *   Probably a detail we need not sort out now, but anything that encourages participation is goodness.
 *   bemasc: I didn't mean to suggest that, just that business cards and titles may help volunteerism.
 *   cjb: some people have itches in strange places ;)
 *   It has been a mystery from the very beginning... not the norm for a FOSS project
 *   I'm not wild about VP this and that as a title... seems too corporate...
 *   hmm, every project can be very different in that regard
 *   And, the best people just like solving interesting and challenging problems:)
 *   So, anything we can do to provide extra motivation given that the itch won't be there sounds good. Webspace, mail address, so on?
 *   Proposal: once the SFC deal is complete, we send out an e-mail to all member asking them to nominate themselves for the Membership and Elections committee, with instructions on how to add their name to the list on selectricity. We announce an election date (perhaps a week hence), and then elect that committee.
 *   yes, VP is an odd title for us. There may be better titles.
 *   cjb++
 *   cjb++
 *   +1; Well, shall we move on?
 *   yeah, I thought it would be more normal for people from the US ;)
 *   I like "Activist", but that's just me ;-)
 *   don't know who like it, then
 *   this raises a question: how do we e-mail all members?
 *   I have an email list I compiled for all the members
 *   oh damn
 *   yueah
 *   ah nice!
 *   great.
 *   mass wiki-mail? IAEP
 *   I haven't put it anywhere yet---I'll make a list on the mailman server...
 *   hmm, shouldn't we communicate with the members through the main mailing list?
 *   Is it mailman or the host you don't like? or email in general?
 *   I don't see a need for a members-only list
 *   tomeu: we can't assume they are subscribed I think
 *   at least during the bootstrapping process, so we are more open
 *   that's an issue, yeah
 *   I need to send ballots out somehow
 *   walter: just the host having no obvious connection to sugarlabs
 *   bemasc: we are fixing
 *   marcopg: great
 *   walter: maybe mako would be willing to run the electionN?
 *   infra is on the agenda
 *   (not so great, it's being painful!)
 *   It'll get better
 *   walter: maybe it might be a good idea to reuse the gnome foundation election infrastructure ?
 *   walter: I don't know quite what you mean by ballots
 *   walter: ok, I see
 *   selectricity requires that each user be provided with a distinct secret string that enables them to vote
 *   so what we are describing is a list of e-mails, but not a "mailing list". Each user receives a different e-mail.
 *   bemasc: yes
 *   I have the list of emails.... most, but not all are either on sugar or education
 *   also "its.an.education.project" is beginning to seem a bit petulant to me
 *   well, more outdated, since we're no longer about compelling OLPC to do things.
 *   the name was chosen to emphasize that we are the bearers of the true and great Sugar tradition, not the new false religion, or something.
 *   Really? I think the education debate has been getting more substance (and Albert is being reasonable in his language)
 *   walter: oh, I think he just means the name
 *   The posts themselves are fine with me.
 *   yeah, just the name
 *   should be just Education maybe
 *   I don't know, it's not terrible
 *   yeah, albert looks to be making a big effort
 *   we already changed the title
 *   gmane has it as "sugar-discuss"
 *   marcopg: oh, what to?
 *   cjb: interesting
 *   Oh. Well, I like the idea of a list for technical details and a list for education discussions,
 *   heh
 *   As has been pointed out on the OLPC-sur list, combining the two is off-putting to non-geeks
 *   cjb: Education
 *   it's a tricky political issue though. Presently, we have IAEP and sugar@lists.laptop.org
 *   "Education" :,
 *   neither are hosted at a sugarlabs domain, and both have lots of subscribers
 *   not sure if it has always been like that actually :)
 *   let's move on with the organization, we'll be able to tackle this issues better later
 *   +1
 *   Just quickly: Luca is working up some new sketches for us for a "corporate identity"
 *   I think the basic graphic is very appealing
 *   walter: we need to get him more feedback about the logo I think
 *   walter: he has been asking me about it
 *   I'm not sure what to make of it. It looks like a lower-case o, and some pretty deformed hooklike hands
 *   bemasc: did you see all of them?
 *   Maybe the "hands" are too hook-like...
 *   marcopg: no
 *   http://wiki.sugarlabs.org/go/DesignTeam/Logo-ideas#Designs_by_Luca_Ferrari_and_Franco_Lodato
 *   I think they look better in 2D.
 *   anyway I guess my question is how do we go about choosing one
 *   art is subjective :P
 *   Luca is working on better typography
 *   Bernie seem to dislike all of them for example
 *   http://wiki.sugarlabs.org/go/Image:Sugarlabs2.png :)
 *   I like lots of these!
 *   (all of those designed by Luca, that is)
 *   I like a bunch of them
 *   I'm sure we can find something
 *   I think they look very amateurish (the sugar bowls)
 *   this seems like exactly the sort of thing that we don't have to decide here
 *   thankfully
 *   +1
 *   heh
 *   yeah though we need to move forward on it in some way :)
 *   we can do a voting :)
 *   guess we can discuss later on iaep
 *   yeah :) I don't think we need to vote or anything; a simple show of hands on the mailing list once we think we have everything up there would be fine.
 *   erikos: yeah but using Luca ones means we also get a website :)
 *   marcopg, aha i see :p
 *   anyway
 *   let's use the education list for this
 *   I agree that handing this off to some willing pros is not a bad strategy
 *   but we can get a show of hands on the list
 *   if I had energy to discuss about the logos, we'd have composition in 8.2.0
 *   hehe
 *   but this is something that can be left entirely to the rest of the community
 *   I someaht disagree about doing this by e-mail list, I think you use the list to move the discussion to the wiki. Just my thoughts.
 *   I'll ask people to make comments in the wiki... we have some, but not many to date.
 *   anyway, next topic?
 *   yeah
 *   Budget
 *   We have a few expenses that are going to come up.
 *   One is getting international trademarks (for Sugar Labs and our beautiful logo to be)
 *   the SFLA will handle the legal aspects for us pro bono, but not the filing fees.
 *   oh in which category we are for fees?
 *   Apparently this will cost real money--several tens of thousands of dollars
 *   huh
 *   eeh for once?
 *   the problem is we are a global project
 *   hmm
 *   we need to file in lots of different places
 *   who could sponsor that?
 *   Is there a mechanism to accept funds (before SFC)?
 *   cjl: nope
 *   walter: it seems hard to find someone to sponsor this
 *   I think that once we have Sugar Labs up and running, I need to switch mostly into fundraising mode.
 *   is this trademark thing really necessary?
 *   walter: what's the motivation for getting the trademarks?
 *   sorry, need to leave for 5 minutes
 *   I was told by Eben Moglen that we really should trademark...
 *   it might be easier to change name every year and spend the several tens of thousands of dollars paying developer and educators, sponsoring conferences, etc.
 *   It is standard for FOSS projects and it is a potential point of leverage.
 *   what could possibly happen if we don't trademark?
 *   I wonder how GNOME did it
 *   Something to discuss. But we need to establish a strong identity.
 *   walter: this is certainly surprising. There are a lot of famous FOSS projects out there with budgets that don't even remotely compare
 *   I guess Firefox and Openoffice are trademarked. Can't think of any others off-hand.
 *   cjb: GNOME is apparently
 *   I think most of them are... but not necessarily everywhere.
 *   marcopg: GNOME has an awful lot of money, I've never worked out why :)
 *   KDE too
 *   ie. >$100k.
 *   Maybe that is the piece we can debate.
 *   cjb: they have very low membership, don't get where they get those from
 *   Most of the GNOME budget goes to organizing meetings.
 *   marcopg: I think their corporate sponsors give a lot. They just hired an Executive Director full-time, even.
 *   the money comes from corporate memberships
 *   yeah
 *   cjb: I guess the advisory board pays significatly
 *   yeah. we may have to do the same thing
 *   walter, the trademark is a thing per country http://www.uspto.gov/main/trademarks.htm or can you get a global one ?
 *   (Trademarks are generally country by country)
 *   cjb:    * Small company: 1-49 employees. $5,000 / year
 *      * Medium and large company: 50 or more employees. $10,000 / year
 *   I guess it all depends on much we can raise anyway :)
 *   http://foundation.gnome.org/about/
 *   So, a better question: firefox, openoffice, gnome and kde represent software projects whose codebases have existed for over ten years each.  Why are we like them with regard to trademarks?
 *   walter: what the trademark status of "Sugar"?
 *   The other way to do things is get attached to venues like linuxfoundation
 *   (Sugar is not trademarked--I checked several months ago with Robert Fadel at OLPC)
 *   they have offered to help us participate in their spring conference in SF
 *   cjb: some troll might decide to trademark sugar instead and then sue us.. it happened in the case of "Linux"
 *   unmadindu: and Linus won.
 *   As some of us have discussed in the past, I'd like a Sugar Labs presence at a section of Linux and Learning conferences around the world
 *   yeah - but that was additional headache to handle ;)
 *   bemasc, he had probably the money to defend himself :/
 *   it's certainly a fight we'd like to avoid
 *   that'll take some money... not just once as in the trademark, but every year
 *   (Let's agree to get advice from the SFLA re the trademark issue)
 *   unmadindu, your numbers were per year no?
 *   walter: +1
 *   walter, sure - i know nothing in that area
 *   erikos: yep
 *   I don't think we need to decide now, but making some decisions soon on what conferences are important to the Sugar community is important
 *   walter: would you like to have someone from SugarLabs in all the important confs?
 *   so we can plan resources and calendars
 *   that could cost quite a bit of moneys, I guess
 *   It'd be great if there was some representation in each continent at least once per year...
 *   but we can leverage the local Sugar teams too
 *   we don't all have to travel all the time
 *   yeah leveraging local make sense...
 *   we won't be able to make all that travelling :)
 *   makes sense in terms of time, money and the environment
 *   Sugar Labs has a certain egalitarian philosophy, so asking any local members to represent us seems in the spirit of the thing.
 *   I'd rather have all the Sugar developers at one conference than a Sugar developer at each, I think.
 *   cjb++, but we need to do both
 *   yeah having all Sugar devs at a conf a couple of times per year would be great
 *   but not both at every conference
 *   marcopg: does it need to be a conference?
 *   bemasc: no, not necessarily
 *   maybe a rich online forum.
 *   (it's cheaper if you don't have to pay conference fees for everyone)
 *   I could ask CISCO to help
 *   yeah, conference fees suck
 *   Ubuntu seems to be pretty heavily into online meetings (IRC, gobby, voip). Dunno how successful they are, though.
 *   mako might know?
 *   I've had some good discussions with CISCO re Sugar Labs
 *   Sugar devel does a good job already with online tools
 *   But the learning community is way behind on this
 *   that is the bigger challenge
 *   I put a link to education meetings too
 *   well, we're talking about how to spend money we don't have
 *   yeah, that one sounds tricky
 *   I need to get a feel for how much money I need to try to raise...
 *   and for what purposes
 *   Then it will be easier for me to make a plan
 *   it depends what Sugar Labs is... but what Sugar Labs is depends on how much money we have
 *   chicken - egg
 *   I had an interesting conversation with Chuck about this yesterday
 *   if it's a few thousand dollars a year, then it goes toward conference fees
 *   if it's 50,000 a year then maybe it can go towards airfare too
 *   I think we will need to raise a lot more than a few thousand, but not the tens of millions that OLPC raises
 *   if it's $100,000 a year then maybe Sugar Labs can start contracting people to do more software work, or curriculum material writing
 *   I'd like to help people raise money for such efforts, but not raise it for them
 *   (subject to Mako's warning about paying people when others are volunteer)
 *   I'm trying to get a universtiy network going
 *   I like that idea
 *   yeah
 *   walter: what Chuck thinking about this?
 *   I think a lot of Sugar Labs stuff would be great undergrad projects and even postdoc projects
 *   I spoke, for example, with the University of Tampere (where I have a visiting appointment), about raising money from TEKES, the Finnish science foundation to support their Suagr-related efforts
 *   that is easier than getting TEKES money to Sugar Labs itself.
 *   Chuck and I talked about corporate money
 *   He thinks I am not being aggressive enough
 *   I'm perfectly happy with the idea that all the sugar developers would work for interested universities and corporations
 *   We plan to revisit the topic in the coming weeks
 *   ok, anything else we need to cover about funding?
 *   who to talk to and what types of relationships to establish
 *   walter: perhaps we could ask everyone with a stake in Sugar to contribute a person/funding for a "Sugar Labs developer"?
 *   Gnome, somewhat unexpectedly, has found themselves with a lot of money, and decided to hire a full time project manager
 *   I'm not good with this sort of strategy, happy to leave it to Walter :)
 *   The model I proposed to Chuck was that industry give engineers, not money
 *   cjb: I think companies will be much more willing to donate $10,000 a year as writeoff than to designate an engineer as working on Sugar
 *   engineers, remember, cost $200,000 a year, even though they're paid much less
 *   Hopefully we'll start to get both
 *   bemasc: there was someone earlier as well - Tim Ney
 *   walter: That would work. I was just imagining the edge case of an organization that doesn't employ Python programmers.
 *   bemasc: I had the opposite intuition, actually.
 *   bemasc: Companies aren't rational; they might prefer to reassign someone to a task than to "spend money".
 *   I think any company that is interested in Sugar enough to contribute to Sugar Labs is already going to have lots of people working on Sugar-related stuff
 *   cjb: charitable donations are unusually cheap for corporations due to tax law
 *   That's true.
 *   Why are corporations going to be interested in Sugar, I get it for the distros, but Sugar?
 *   cjl: there's a company right now working on deploying an XO-based online tutoring system (something about No Child Left Behind...)
 *   their current plan is to deploy a dedicated tutoring system OS that, at the end of the self-guided course, unlocks and reveals Sugar underneath
 *   that's just a specific example I am aware of
 *   bemasc: huh. who's that?
 *   there is lots of non-education interest in Sugar too
 *   hm, point of order: coming up on 3pm here.  Anything else on the agenda?
 *   cjb: I don't know... the developer shows up in #olpc-devel occasionally
 *   (If the answeris "nothing else on the agenda, but let's keep chatting for a while", that's fine too.)
 *   the agenda is very long still
 *   walter: Waht to talk a little about the non-education interest?
 *   but I'm not sure we will have energy to cover all
 *   cjb: http://wiki.sugarlabs.org/go/Sugar_Labs/OversightBoard/Minutes#Friday_July_18_2008_-_17.00_.28UTC.29
 *   that's the agenda
 *   We should just talk about infrustructure briefly and then perhaps call the meeting to an end?
 *   yeah maybe we can cover some points next week
 *  oh man
 *   I think we can continue next week...
 *   Sounds good. People here are heading off for a football match soon.
 *   What's the current situation with infrastructure?
 *   Just quickly on infrastructure
 *   neuralis offered solarsail?
 *   and Chuck offered Antenna
 *   I am still going back and forth with MIT on a server room
 *   the one they are currently proposing is not ideal
 *   walter: but it's ok as temporary one?
 *   I hope we can sort this out and get our servers running by the end of next week
 *   What's Antenna?
 *   Antenna is a server that OLPC owns that was never turned on... It was sitting at the Media Lab, waiting for Henry to pick it up
 *   The server room is OK, but it is messy and lacks decent AC
 *   Oh, heh.  Okay.
 *   No UPS?
 *   I think UPS, just poorly maintained as a room
 *   we was planning to move services on solarsail this morning
 *   (solarsail is also at MIT)
 *   wiki, mailing list etc
 *   I guess solarsail is going to move to this server room too?
 *   cjb: it's there
 *   the main problem we have is how to do backups right now
 *   I think the real issues are not these...
 *   it is what services we run as Sugar Labs vs elsewjhere...
 *   yeah those are harder
 *   but having good server in a good location with good backups is also essential :)
 *   until we have the hardware running, we can hardly make that call
 *   marcopg, is the backups a space problem or a technical one?
 *   erikos: well, we need a machine to backup on
 *   Maybe we should see what happens Monday and pick up the thread next week?
 *   with lots of space
 *   to do full backups
 *   ok
 *   Bernie argues that we need full backups *now*
 *   sounds like the solution is solarsail _and_ antenna
 *   and on the other two machines we already run different services as i understood
 *   bemasc: Ivan and Bernie discusses splitting the services between the two machine
 *   so antenna can not be a backup of solarsail
 *   bemasc: for security reasons
 *   Well, we can rsync-backup the machines to each other, or use MIT TSM. Seems like this is a sysadmin decision?
 *   yeah technical decision
 *   marcopg: well, encrypt the backups, then?
 *   I guess I don't really see why sugar labs' server would need to have anything srcure on it. :)
 *   we should probably let Bernie and Ivan sort it out
 *   yeah, sure
 *   cjb: I think Ivan would like to put shells on a different machine
 *   cjb: so that it's harder to compromise the services
 *   Let's call it a day...and pick up here next Friday.
 *   not sure exactly now, /me not a sysadmin type
 *   day!
 *   yeah
 *   We can ask for a report from the ad hoc committee on infra.
 *   ok!
 *   thanks all!
 *   thanks to everyone for hanging in there
 *   (meaning bernie and ivan)
 *   ok, nice to talk with you all
 *   cjb, thanks for joining in!
 *   I'll post the log and minutes later today
 *   thanks!
 *   thanks to everyone
 *   ciao
 *   thanks to everyone
 *   ciao