Oversight Board/2010/Meeting Log-2010-01-08


 *   hi sean
 *  hi rita
 *  happy new year :-)
 *   you are probably the right person to ask my question
 *   thank you, happy new year to you too!
 *   olpc Germany would like to produce german versions of soas and provide usb-sticks on events.
 *   but we don't know how to call this, as a projects and as branding for the usb sticks.
 *  great!
 *   would "Sugar on a Stick - auf Deutsch" (means "Sugar on a Stick - in German") be ok?
 *   is there any rule on how to do such local distributions?
 *  well, naming depends how similar or not to Blueberry
 *   if it would be a translated version of Blueberry?
 *  if straight translation, i don't see problem using Sugar on a Stick name
 *  but we haven't ironed out details yet... e.g., support
 *  there is a concept that the SoaS name means bug reports & support via the SoaS team
 *   I suspected that this would be not *that* easy.
 *   there is an education fair in Germany in March, and OLPC Germany would like to give out some sticks there. it would be great to know how to name it before that event.
 *  there is an soas meeting after the SLOBs meeting, perhaps we can discuss this with Sebastian?
 *   would that be in about 1 hour?
 *  yes
 *   I will see that either I can attend or find someone else, who is involved
 *   good morning/early afternoon everyone.
 *   anyone seen mchua_afk ?
 *   tomeu will not be able to join us
 *   is bernie awake?
 *   cjb, are you there?
 *   CanoeBerry_: ditto adam?
 *   SeanDaly: is it only you and me? (I guess people really need the reminder emails)
 *   listening
 *   SeanDaly: we'll have to wait for a quorum... but we can talk in the meanwhile
 *   morning
 *   hi chris... we just need one more for a quorum
 *  i'm back
 *  hi cjb happy new year
 *   you too :)
 *   I was remiss in sending out the reminder and it seems people forgot.
 *   this waking up in the morning thing is hard work for some of us :-)
 *   cjb: I am happy to meet later, but I don't know about our friends in Europe.
 *   yeah, I understand
 *  later is ok but not too late :-)
 *   adam, is that you?
 *  Hiya.
 *  Bernie up too late?
 *  hi CanoeBerry!
 *  "Morning"
 *   we have a quorum, so we should begin...
 * <CanoeBerry> May be tough for me to reschedule today.
 *   #startmeeting
 *   Meeting started at 10:11 UTC. The chair is walterbender.
 *   Commands Available: #TOPIC, #IDEA, #ACTION, #AGREED, #LINK
 *   #TOPIC TM policy
 *   We had made some changes to the TM policy last week but deferred a vote because we wanted to give people a chance to reflect
 *   I sent a note to the lists, but I don't think there was much discussion, if any.
 *   yeah, that's weird
 * <CanoeBerry> I assume we're talking about: http://wiki.sugarlabs.org/go/Talk:Sugar_Labs/Governance/Trademark#Sugar_Trademark_Policy
 *   I did create http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Trademark/Guidelines
 *   that did cause a little bit of a reaction
 * <SeanDaly> partly my fault, I had promised to write a mail explaining "sugarized" logo policy with examples
 *   CanoeBerry: yes. that is the page
 * <SeanDaly> Rita has asked me about how policy would be applied to German translation of SoaS
 *   CanoeBerry: with BOLD and STRIKE indicating changes
 *   SeanDaly: seems to be an example of 2a
 *   SeanDaly: but maybe we should be explicit about translation in that paragraph
 *   BTW, I also never heard any feedback from SFC :(
 * <SeanDaly> more like 5a, they want to hand out sticks
 *   Having slept on it, do people have any further thoughts?
 *   good idea, let's add ", including translations into other languages," into 2a text
 *   SeanDaly: hm, maybe they need to ask us, then
 *   so translations would be minor changes?
 *   yes, I'd vote for translations as minor changes
 *   rita, cjb: I agree


 * sdziallas	looks up
 * <CanoeBerry> Sounds reasonable.
 *   so I think the changes to the SL software do come under 2a
 *   FYI, I just added "translations into other languages," to the wiki page.
 *   but we have a specific mention of SoaS in 5a
 *   that says only Fedora-SoaS would be allowed to release SoaS products, without explicit permission
 *   there would be two ways around this:


 * SeanDaly	on phone....
 *   (a) you could argue that, since there are only minor changes, this *is* still Fedora-SoaS, and so there's already permission that way, or..
 *   (b) you could just ask for permission. :-)


 * sdziallas	would like to provide input on this topic.
 *   sdziallas: go for it
 *   First of all, I'll notice that bertf introduced me to somebody who said he was willing to do SoaS versions in German and asked for the way to do so.
 *   cjb, sdziallas what is the Fedora policy re translation? seems that for SoaS, it would have to pass both the SL and Fedora hurdles.
 *   I explained the procedure and also noted that there'll need to be some discussion on how it'll be named, since the project had been introduced to me, adding that it might also including new content.
 *   So I'm not opposed to translations. However, adding content is in my opinion something that needs approval.
 *   sdziallas: yes. let's separate those two issues.
 *   Additionally, I suggested that it'd be interesting to collaborate on the effort and to have the German version hosted in our GIT repo.
 *   walterbender: I'm done in a second, just explaining here.
 * <SeanDaly> agree translation not same as content change
 *   sdziallas: and that is a topic I want to discuss at the SoaS meeting too.
 *   walterbender: yes, but then here's the thing:
 *   but sdziallas, what is the Fedora policy re translations?
 *   originally, there was talk going on about SL granting the SoaS project the permission to use the Sugar name.
 *   walterbender: I don't know exactly. But I suspect that you can only call it Fedora in an unmodified form. (and not "substantially unmodified".)
 *   walterbender: however, if you don't add anything, this might be different.
 *   sdziallas: can you look into the translation question for us when you get a chance?
 *   walterbender: there are kickstart files in Fedora's GIT repo that just change the language and haven't gone through the approval process.
 *   walterbender: however, those don't get actively built, which makes things different.
 *   walterbender: I'd like to finish my point before and will do that then, if it's okay.
 *   sdziallas: please continue
 *   So if Sugar Labs decides to grant the SoaS project as it is a permission to use that name... I believe this thing becomes a SoaS issue.
 *   sdziallas: well, the permission is incumbent on playing by the rules, so it is not a unilateral SoaS issue.
 *   walterbender: agreed. but does this mean that SLOBs decides SoaS stuff? so who'd take care of an approval, in case it was inquired.
 *   s/./?
 *   I agree that it could be just a SoaS issue -- I think it's helpful to use as an example of making our trademark policy better, though.
 *   cjb: I agree there, too.
 *   So I guess something could happen like:
 *   sdziallas: SLOBS is trying to establish guidelines and as long as SoaS respects those guidelines, then it is cool to act unilaterally
 *   * someone brings the SoaS team a build they made and asks whether they need permission to distribute it:
 *   * if it's mostly unmodified, they don't need permission
 *   sdziallas: also the SL guidelines do not supersede Fedora (and vice versa)
 *   * if there are modifications, they do
 *   * if the SoaS team declines permission:
 *   walterbender: I didn't say they did?
 *   * the project should choose a new name, and then ask SLOBS for permission to use *that* name, if the naem has Sugar in it
 *   cjb: +1.
 *   those asterisks didn't work out very well :)
 *   (the +1 comes with my SoaS-hat on)
 *   Aren't we all in agreement here?
 *   walterbender: I'm basically asking who'd take care of things related to SoaS.
 * <SeanDaly> SLOBs decides use of SL trademarks

|<--	CanoeBerry has left freenode (Read error: 60 (Operation timed out))
 *   walterbender: it looked like SLOBs would be approved SoaS remixes.
 *   sdziallas: SoaS takes care of SoaS...
 *   s/approved/approving
 *   sdziallas: and the more clarity SL can bring, the easier your job will be.
 *   walterbender: thanks for clarifying it :)
 *   walterbender: I agree.
 *   sdziallas: what I would like to discuss are other types of changes we may want to implicitly approve.
 *   sdziallas: for example, if someone wanted to add an ebook collection to their SoaS
 * <SeanDaly> sdziallas: for example i suggested to rita she participate in SSoaS meeting re german version
 *   I asked on the german list and got confirmation that Raffael will participate in the meetng.
 *   SeanDaly: I saw that some minute ago. But making clear whether SLOBs decides on SoaS things or not is a SLOBs matter.
 *   rita: cool!
 *   walterbender: *nod*
 *   walterbender: I've some opinion on that, but dunno whether we shouldn't defer that to the SoaS meeting
 *   Argh, my window didn't ping - I'm sorry about that, folks


 * mchua	reads up
 * <SeanDaly> sdziallas: SLOBs are implicated on trademark level for sure
 *   mchua: glad to have you join us :)
 *   SeanDaly: I don't see why that has to be the case


 * SeanDaly	greets mchua
 *   SeanDaly: so somebody can approach SLOBs, ask for trademark permission and SLOBs approves something which is named "Sugar on a Stick $FOO"?
 * <SeanDaly> cjb: SL has to manage SL trademarks
 *   SeanDaly: is this an appropriate description of how the process should work?
 *   SeanDaly: we don't know anything about SoaS; if someone shows up with their custom SoaS build, we aren't going to be the people to examine it, the SoaS team is. I think it makes sense for them to make the call.
 * <SeanDaly> sdziallas: i wouldn't recommend that. What about support, bug filing etc.?
 *   SeanDaly: the SoaS team is part of SL, though.
 *   SeanDaly: for example, right.
 *   I might pull up the Fedora example again.
 *   We've the Spins SIG there, which handles "technical approval".
 *   Once that is given, one may approach the Board for "trademark approval".
 * <SeanDaly> there is technical aspect, content aspect, trademark aspect
 *   Not receiving "technical approval" can be escalated to the board.
 *   cjb, SeanDaly It is our responsibility to set guidelines for the people who use our TM and we need to at some level make sure that they follow our guidelines... that doesn't mean we do their decision-making for them, but we need some sort of auditing process
 *   cjb, SeanDaly: maybe we need to ask for an annual report from our TM users?
 * <SeanDaly> walterbender: yes my feelings exactly... my hope is that policy will be clear enough to avoid having to decide every case
 *   cjb, SeanDaly: something we can review to ensure that things are on track...
 *   that sounds good
 * <SeanDaly> walterbender: in previous meetings I mentioned that there should be conditions attached to tm use
 *   back to rita's question, from the SL POV, translation is fine. But SoaS needs to make sure that fits the Fedora rules too.
 * <SeanDaly> one of those conditions should be I think informing us periodically of how tms are used


 * mchua	caught up now. sounds like the question is "does exclusive right to use a trademark imply delegation of the decision of that trademark usage?"
 * <SeanDaly> mchua: i disagree, SL doesn't delegate any tm decision at all, it's still SFC with final say
 *   mchua: I think it can within the context of our guidelines... but it cannot carve out new ground...
 *   Well, only decision-powers that a group has can be delegated
 *   SeanDaly: maybe we are disagreeing about what "decision of that TM usage" means
 *   walterbender: thanks for the clarification! so the other aspect will be talked abput in the soas meeting?
 *   and override privs from the folks who did the delegating could be implied
 *   mchua: that is what I said with regard to Fedora's process.

-->|	CanoeBerry (n=Canoe@c-98-216-65-79.hsd1.ma.comcast.net) has joined #sugar-meeting
 *   SeanDaly: we are giving the "licensee" a sandbox to play in and within that sandbox, they can make decisions
 *   SeanDaly: but we define the sandbox
 * <SeanDaly> walterbender: sure, but we need to be able to protect the marks
 *   (or we could talk about basis functions)
 * <CanoeBerry> Internet problems hopefully overcome-- I'm back after 10min of outage.
 *   SeanDaly: Is Sugar Labs protecting the Sugar mark and asking for approval for all "$DISTRO Sugar Spin" versions?
 *   SeanDaly: would an override function on the stuff that happens in the sandbox work?
 *   SeanDaly: the sandbox we define with our guidelines is exactly for that protection.
 *   sdziallas: you haven't quite got the 2a wording, but you're right -- we don't police those. We've explicitly said they aren't covered by our trademark policy.
 *   cjb: I'm aware of the 2a wording.
 * <SeanDaly> sdziallas: the idea is a policy which easily grants a logo label within guidelines, but requires explicit decision in others; with SL/SFC reserving final tm rights
 *   (which is a bit different from saying that they're protected and someone else is going to handle protecting them for us, but maybe not that different.)
 * <SeanDaly> mchua: yes there has to be an override
 *   cjb: so if I went ahead and created a Fedora Sugar Spin, nobody would mind?
 *   SeanDaly: then I would like that override to have a timeout - maybe the override has to happen within 2 weeks of the sandbox event SLOBs wants to revert
 *   cjb: replace Fedora with Ubuntu and Spin with Remix, if you want. Or OpenSUSE. Or whatever.
 *   sdziallas: we might mind, but we would not be able to do anything about the fact that we mind.
 *   at least, using trademark law, with the current trademark policy, etc etc
 *   cjb: "do they require approval?"
 *   sdziallas: no
 * <SeanDaly> cjb: that doesn't work I'm afraid
 *   cjb: and if they don't, what happened if I did Sugar on a Stick outside of Sugar Labs?
 *   cjb: that'd be an equivalent case.
 *   sdziallas: it's not equivalent
 * <SeanDaly> cjb: SL needs to manage its marks
 *   Fedora Sugar Remix is a clear case of 2b
 *   SeanDaly: you keep repeating that as if we don't all agree. :/
 *   cjb: it isn't.
 * <SeanDaly> "Sugar Spin" won't be the name of anything
 *   cjb: "Ubuntu, joined with Sugar" is.
 * <SeanDaly> the phrase is not chosen yet
 *   Or I'm reading it wrong (which might be well possible).
 *   sdziallas: ok. I don't see why you chose a non-2b wording.
 * <SeanDaly> it's a marketing issue
 *   I have to leave, thanks!
 *   SeanDaly: so the argument is that you don't consider the trademark policy finished, so we shouldn't trust anything it says?
 * <SeanDaly> i'm late on starting that thread in the list, but again the idea is to start a logo label program
 * <SeanDaly> cjb: certainly not finished, no
 *   SeanDaly: but then why did you vote to adopt it?
 * '''<--|	rita has left #sugar-meeting
 *   cjb: I think you are using hyperbole...
 * <SeanDaly> cjb: it's a draft
 *   walterbender: ok. sorry, I'll take a step back.
 *   cjb: we had agreed that the example in 2a and 2b would be replaced by Marketing after a discussion, but otherwise we were happy with the document...
 * <SeanDaly> what I'm interested in doing is building Sugar awareness, but in a scalable way from quality associated with the brand
 *   so to say we cannot trust *anything* it says is a bit extreme...
 *   walterbender: oh! ok.
 *   SeanDaly: but we all agree that having brand dilution would be a bad thing, marketing wise, right?
 * <SeanDaly> our granting tm use is to assure no confusion
 * <SeanDaly> sdziallas: yes of course
 *   SeanDaly: and at the same time, we want new people to come up with their work and to contribute, too...
 * <SeanDaly> sdziallas: yes exactly
 *   SeanDaly: (I'm trying to understand everything we want to accomplish better)
 * <SeanDaly> we are breaking new ground with this


 * sdziallas	nods
 * <SeanDaly> historically distros & projects have treated the problem only from tech perspective
 *   but we want to put a strong marketing perspective on there, too.
 * <SeanDaly> and desktops too... who probably should have done the most marketing
 * <SeanDaly> sdziallas: yes... a strong brand stands for something, people know what it means


 * walterbender	would like to interject
 * <SeanDaly> And,


 * sdziallas	nods again.
 *   so I guess we would want to have *both* aspects.


 * sdziallas	listens
 * <SeanDaly> sdziallas: yes both
 *   maybe we should defer the final vote on the TM policy until after Marketing comes up with the final wording for 2a and 2b.
 *   and we can take this interesting discussion to the lists???
 * <SeanDaly> walterbender: yes i would hope so


 * sdziallas	nods (or for those who are able to, in the next hour)
 *   we only have a few more minutes today. can we quickly switch topics?
 * <SeanDaly> yes, as I say I had previously promised to start thread, been swamped
 *   #topic guidelines for interacting with the SFC
 *   I am bringing this up more for informational sake... nothing to vote on, but I would like feedback on http://wiki.sugarlabs.org/go/User_talk:Walter#notes_re_administrative_transactions_with_the_SFC
 *   There are a few more details I am trying to work out with them so as to make things more transparent and predicatble
 *   so when you get a chance, please look at that page and comment...
 *   #topic infrastucture
 *   Bernie is not here to argue for his new server... but maybe we do this one by email?
 *   I have looked into the finances and the money is there if we decide to spend it
 *   #topic finances
 *   Is there a finances update? I'm curious how much would be left after the new server if we say yes, and what else we might have to spend it on
 *   I have been talking with Bradley about a few minor anomalies that had me confused... I think by next week I can give a coherent report.
 * <SeanDaly> I need to break out the 2009 marketing expenses
 *   re mchua's question: we have lots of potential things to spend money on... marketing, deployments, etc.
 * <SeanDaly> it would be helpful for me if at least press releases could be covered...
 *   mchua: but infrastructure is also important...
 *   SeanDaly: can you put together a budget for the marketing team for 2010?
 * <SeanDaly> at SugarCamp Paris we studied budgeting approaches if you remember
 *   we should have budgets for all the teams and use them to set some goals for fundraising
 * <SeanDaly> walterbender: sure
 * <CanoeBerry> 10:59AM aside, before we end: did I miss a vote when I lost Internet for 10-15min in the middle?
 *   CanoeBerry: no, no motions were proposed
 *   CanoeBerry: no vote yet...
 *   Meet again next week???
 * <CanoeBerry> Yes
 *   sure
 * <SeanDaly> OK for me
 *   SeanDaly: would a bit later work for you?
 * <SeanDaly> walterbender: yes
 *   16UTC (to let cjb sleep a bit longer?)
 * <SeanDaly> fine with me
 *   worksforme
 *   Can we come with motions?
 *   OK. let me sum up with some actions then.


 * SeanDaly	not sure I could get up early for such a meeting :D
 *   mchua: no motions yet, I am afraid
 *   #action sean and the marketing team will lead the discussion about the final phrasing of 2a and 2b
 * <CanoeBerry> FYI bernie will be move 1 time-zone East, so will have even less excuses for sleeping in :)
 *   from that action, we'll be able to make a motion re TM policy :)
 * <SeanDaly> yes
 *   #action walter will finish up the budget discussion with SFC and present next week
 *   #action team leaders will be asked to submit budget proposals for 2010
 *   (I'll send that request)
 *   #action we'll discuss bernie's request by email and (perhaps) vote on it before the next meeting
 *   #action we will meet at 16UTC on 15 January 2010
 *   Anything I missed?
 * <SeanDaly> looks good
 *   SeanDaly: could you come with a motion on the final phrasing of 2a and 2b?
 * <SeanDaly> mchua: no
 *   thanks everyone... I'll end meeting and then we'll get going on the SoaS meeting.
 * <SeanDaly> needs to be discussed by marketing team
 *   or a series of concrete examples/proposals
 *   #endmeeting
 *   Meeting finished at 11:04.
 *   Logs available at http://meeting.olpcorps.net/sugar-meeting/