Oversight Board/2009/Log-2009-08-28

Oversight Board meeting log 2009-08-28

 *   Can I call the SLOBS meeting to order?
 *   its now?
 *   I think it's supposed to be now
 *   caroline: I believe so.
 *   let's get started.
 *   hmm, no meeting bot
 *   I'll just grab the log by hand :(
 *   so, as far as an agenda, I have a few topics; others may as well
 *   (1) QT
 *   (2) $
 *   (3) Interns
 *   (all three are related, actually)
 *   heh, soudns good
 *   (4) 0.86++
 *   Re #1, Bernie and I continue to dialog with Nokia re their interest in Sugar/QT
 *   they would like us to explore it for them and have some funding for some interns this fall
 *   I want to make sure that it is OK to accept this funding and put a program together
 *   there has been some discussion about how this is a distraction, but I see it as an opportunity
 *   I guess all opportunities are a distraction as well ;)
 *   the basic plan would be to:
 *   but are all distractions opportunities :)
 *   1. Bundle some existing Qt/KDE educational software for the Sugar
 *   Learning Platform.
 *   2. Design an equivalent of the sugar-toolkit bindings for Qt-based activities.
 *   3. Sugarize an existing Qt/KDE application (such as KStars) with full
 *   Journal, collaboration, and Activity toolbar support.
 *   So, unless there is strong opposition from SLOBs, I'd like to proceed
 *   Walter, can you give us a statement of what you hope for and draw the picture of how this work leads to kids learning with Sugar (I'm not doubting, I just want a clearer understanding).
 *   I would personally start with 3
 *   caroline++
 *   caroline: sure
 *   1. it (potentially) broadens the platform base, the contributor base, and the available set of Suagr activities
 *   2. it is a major player interested in getting Sugar onto their platform
 *   3. it forces us to be more dilligent about being toolkit agnostic the way we are already trying to be hardware and OS agnostic
 *   #3 could be a distraction
 *   but I cannot see any reason why we wouldn't pursue #1 and #2
 *   and #3 is good, but may be more trouble than it is worh
 *   caroline: does that explain it or should I drill deeper
 *   Good!
 *   can you go a bit deeper in terms of software we will get?
 *   Kstars, what else?
 *   ok, what about: 1. we put this concrete question on iaep (accepting the funding), 2. SLOBS vote by email if no consensus
 *   google kde education for a start


 * tomeu	doesn't like voting in irc
 *   tomeu: I am not sure this is a matter of voting.
 *   it is a matter of discussion and reaching consensus


 * sdziallas	is here, lurking for the meeting, too
 *   we've had a lot of discussion of the topic on iaep and dev (and irc) already
 *   walterbender: ok, it's just a pity there isn't more people here
 *   Great thanks
 *   walterbender: yeah, but I'm not sure if it was as well framed as you put the question now
 *   do you have any details on how much it will expand our platform base? or is that unknowable at this point.
 *   caroline: I think it is unknowable at this point.
 *   yeah, we would need to know how many developers with gtk or qt knowledge exist
 *   Will we be able to write a press release about this?
 *   but I think we can say there's lots of them in both fields
 *   tomeu: I think this falls under the category of something that a group of people what to do and it is more a matter of whether SL endorses it or just lets it happen
 *   walterbender: sounds good
 *   Walter, I'm all for it, I just want to understand it and have us think together about how to make it the most positive it can be.
 *   tomeu: I would argue that Nokia, in investing in Trolltech and with their recent announcements, is going to contnue to promote and develop the Qt world.
 *   tomeu: they would like to explore with us being part of that world
 *   walterbender: totally, this week they released new python bindings for qt, btw
 *   I frankly cannot see how we could turn away such an opportunity
 *   tomeu: and announced two new hardware platforms that are Sugar targets
 *   yes, I thnk that is imporatnt
 *   two? I only knew of one
 *   tomeu: a netbook and a new maemo device
 *   wow, didn't knew about the netbook


 * tomeu	googles
 *   to suceed we need to not only be technically successful, but be percieved as successful. this could be a huge opportunity to work on both of these.
 *   I am concerned that we are getting ahead of ours selves. At this point we are only talking about funding intern with money we would not other wise recieve to to preliminary feasibility work not making a commitment to support qt
 *   dfarning: we are not getting ahead of ourselves exactly because this is a feasiblity study, not a commitment to support
 *   nod to Dave, clearly we should do this. The interesting question is what should we say about doing it.
 *   walterbender: sorry, that is what tried to say:(
 *   which perhaps should be tabled till Sean gets back. But it sounds like a great opportunity to expand the perception of Sugar as well.
 *   caroline: I think we should talk with Nokia about how to talk about this publicly
 *   dfarning: I think part of the confusion is that some people thought we were thinking of adding qt to the platform or using qt on sucrose
 *   dfarning: while none of those have been put on the table as of yet
 *   so we were discussing about ghosts in the ml, IMO
 *   tomeu: I agree. I think there was that confusion
 *   tomeu: agreed
 *   we may get there one day, but we are quite far from it right now
 *   so, I'd like to say to Nokia, yes wearing a SL hat
 *   but this leads to a second topic: interns
 *   walterbender: +1
 *   dfarning and jelkner set up a mechanism for interns
 *   modeled after GSOC
 *   any reason not to continue to leverage that mechanism?
 *   now that we talk about interns, I would like to see their work more exposed to the community
 *   like have them sending emails to iaep presenting themselves, their work, giving progress reports, etc
 *   tomeu: some of them blogged to the planet
 *   tomeu: but most of them hung out in #sugar and the devel list
 *   yeah, thinking about something more formal
 *   tomeu: so I agree, it would be good to broaden the exposure
 *   I'm not sure it's clear for iaep readers which interns we have and on what they work
 *   also would like to know exactly how many people read the planet ;)
 *   so I know how worth it's writing there
 *   tomeu: in my blog this week, I only mentioned GSOC... next week, when I get all the reports in, I plan more detail about what they did
 *   I have had to refer to my posts several times from sugar-devel
 *   so have the impression that not many sugar people read my blog
 *   Blog posts can be confusing because they assume you have the history of previous posts.
 *   tomeu: I spend a few minutes each week posting to the blog, community news, and the wiki...
 *   I assume people are not annoyed at the redundancy
 *   but I have no idea which one people actually read
 *   I tend to get more feedback from the email, but that may be because it is easy to hit reply
 *   yeah, may be useful to know, but I guess we are digressing now
 *   we can pas this issue to the marketing team
 *   back on topic: any reason not to use the intern mechanism for the Qt project as well?
 *   with mentors from the community identified for each intern?
 *   sounds good to me
 *   and good communication to the community :)
 *   which brings me to the $ question.
 *   I can arrange for the $ to get to the SFC, but I am still unclear on how one spends money...
 *   (or rather, how one gets reimbursed for money spent)
 *   +1, after watching how GSOC went, we will model future intern/co-op programs similarly.
 *   I assume each project has a manager who approves expenditures (Caroline in the case of the GPA project, for example)
 *   but how do I get reimbursed for the USB keys I bought for GPA, for example?
 *   dfarning ?
 *   the is no formal program yet.
 *   dfarning: can we task you with working out a mechanism with SFC?
 *   so far I have been asking for approval on slob for each expenditure.
 *   dfarning: seems tedious. I would think we would have SLOBs apprve a project/budget and then let the project manager approve the expenses
 *   yes
 *   and report back to SLOBs periodically
 *   Agreed, would it be possiable to assign me, or some else as, treasurer?
 *   the lack of treasurer makes this murky
 *   dfarning: I thought you were the treasurer
 *   or chair of the finance committee
 *   or CFO
 *   or some such title
 *   our Scrooge McDuck :)
 *   no, i just started doing it to help keep you from getting frustrated with dealing with money:)
 *   can we (SLOBs) appoint dfarning to this role?
 *   before he gets cold feet :)
 *   sounds good to me
 *   heh, mcduck
 *   (webbed feet in the case of Scrooge McDuck)
 *   shall we put it to a vote? (SLOB members only)
 *   all in favor of appointing dfarning as treasure (AKA McDuck)?


 * walterbender	votes yeah :)
 * lfaraone	must have came in late.
 * tomeu	also votes yes
 *   lfaraone: yup, want me to paste the backlog?
 *   tomeu: sure.
 *   Let's re ask on slob mailing list to insure more complete consensus. Money can be a sticky issue on oss projects.
 *   lfaraone: http://pastebin.be/20581
 *   ml++
 *   dfarning: OK. But let's consider provisional approval
 *   ok, i'll start moving forward
 *   specially considering that no one will volunteer ;)
 *   that exhausts my topics.
 *   there's SLOBs elections, any news on that
 *   lfaraone has stood up to update the membership roles and run the election.
 *   lfaraone and sdziallas are the new membership committee
 *   maybe they can report
 *   it seem to be moving forward
 *   walterbender: Well, we've received 5 requests so far. All have been approved. (and are viewable at http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List )
 *   so we aren't going to have automatic expiration of membership?
 *   lfaraone: maybe you can ask people in#sugar to join... many are not members.
 *   walterbender: it's posted in the topic, but I'll mention it agian.
 *   tomeu: as far as I recall from the list, we're going to send out reminders to folks asking them if they still want to be a member
 *   lfaraone: (is this true or is my mind playing tricks on me?)
 *   sdziallas: this is actually something we hadn't worked out, but yes.
 *   sdziallas: this is actually something we hadn't worked out, but yes.


 * sdziallas	nods.
 *   sdziallas: I'm not sure how we'd manage all the replies. know of a free tool we can use to automate the verification?
 *   wonder if automatic expiration doesn't make more sense in very big communities like ubuntu or sugarlabs2011
 *   lfaraone: hrm, that's something to think about... not directly off my head, but we might find one.
 *   tomeu: well, in launchpad they have functionality to ask members to renew.
 *   lfaraone: and if nothing else works, a google spreadsheet form could do the trick for now.
 *   lfaraone: right, they had to setup tools because they were a lot of people
 *   walterbender: can you get me the address list from last year?
 *   lfaraone: will do
 *   but we aren't so many, wonder what's the problem with having some people on the list that have lost interest
 *   maybe you lose your membership if you don't vote?
 *   walterbender: hm. seems sensible. what if I don't like any of the candidates?
 *   send it none of the above?
 *   write in?
 *   caroline: hehe.
 *   walterbender: I mean, we could hack up a little script that generates emails from a list in tandem with a CGI script server-side.
 *   I defer to the membership committee to work this out
 *   Good call. /me moves this into either PM or #sugar :)
 *   you are expelled from sugarland :p
 *   tomeu: no, anything but that!
 *   I personally don't see much of a point right now, but as I'm not going to be doing the work...
 *   we should wrap up soon
 *   it has been an hour
 *   any other pressing topics?
 *   +1 to defering to membership commettee -- this is a great learning opportunity for lfaraone and sdziallas
 *   dfarning: the intelligence is in the leaves :)
 *   walterbender: even if the leaves don't realize it yet:)


 * lfaraone	accidentally set a fire and burned the whole branch down.
 *   hopefully we'll try to keep a gardner around to make sure things don't get out of hand.
 *   well, as we digress, I would propose we end the meeting
 *   +1 to adjourn
 *   #end-meeting
 *   I'll post the log
 *   Thanks everyone