Oversight Board/2009/Meeting Log-2009-12-11

From Sugar Labs
Jump to navigation Jump to search

Started logging meeting in #sugar-meeting, times are UTC.

<walterbender> Has everyone seen the agenda?
<bernie> mchua: I tried to make them help us test SoaS with actual children and provide feedback.
<bernie> walterbender: yes
<mchua> Yep.
<SeanDaly> walterbender: yes
<cjb> morning.
<bernie> cjb: ping
<walterbender> #TOPIC non-FOSS activities
<walterbender> Does anyone have further discussion/clarification regarding this topic?
<SeanDaly> just to be clear, we are talking about ASLO right?
<walterbender> SeanDaly: yes
<walterbender> SeanDaly: we probably need additional discussion about eBooks
<tomeu> I haven't heard any strong point in favour of non-foss stuff in aslo
<walterbender> SeanDaly: I never heard back from the SFC :(
<walterbender> tomeu: me neither.
<SeanDaly> I've been thinking since your mail about kids uploading their work
<SeanDaly> (your=wb)
<SeanDaly> perhaps we could make a distinction between
<walterbender> tomeu: I think the more controversial issues will be around censorship of content (e.g., violence)
<SeanDaly> ASLO activities in the search engine
<walterbender> SeanDaly: you me when kids upload their samples and code modifcations to a gallery?
<SeanDaly> and e-book bundles, and uploaded content - separate policies for each clearly marked?
<SeanDaly> walterbender: yes
<walterbender> SeanDaly: while the line between content and code is pretty blurry, let's stick to the latter for this particular discussion
<SeanDaly> e-book content, samples, Activities are similar (added to Sugar) but typology of content could be aligned with license policies
<SeanDaly> ok yes code
<walterbender> SeanDaly: a TA project would be kid's code... a hard line to draw there.
<cjb> walterbender: well, the discussion is on "what's allowed to be uploaded to ASLO"; I don't think we're limiting the question to just code
<cjb> but we could do
<bernie> so, what's the exact motion we're going to vote on?
<cjb> I made one last week
<mchua> Yeah, I was about to ask the same.
<tomeu> I actually thought we were discussing only respect to the floss-ness of code
<walterbender> cjb: let's see if we can reach consensus around code first and then see how far we can push it.
<mchua> Yeah, I thought we were going to do the "what are our acceptable licenses" motion
<walterbender> cjb: but you are right, the motion talks about content as well.
<cjb> MOTION: adopt http://opensource.org/docs/osd as a set of guidelines for what is permitted on ASLO, for both software and content, and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable
<bernie> personally, I'd like to say that all the licenses approved by fedora are also acceptable for aslo: http://fedoraproject.org/wiki/Licensing#Good_Licenses's
<walterbender> cjb: sorry to have confused things
<SeanDaly> I read the Fedora page and I very much appreciate its clarity
<bernie> cjb: I couldn't have said it better
<cjb> walterbender: it's okay. I think you're right that there are different feelings about content.
<SeanDaly> however, for legal matters, the SFC's input is vital
<bernie> SeanDaly: ++
<cjb> SeanDaly: for the purposes of this motion, there is no legal matter.
<bernie> SeanDaly: we may want to run that page through them...
<cjb> it's a philosophical question.
<walterbender> cjb: in part it is a matter of establishing licenses for the things that the kids create... I had a new feature proposal re CC in the journal, but it looks like there is a lot of push-back on that one still.
<bernie> SeanDaly: although RedHat legal has certainly already approved that, and they're license lawyers too
  • SeanDaly closet philosopher
<cjb> (of course I agree that if there was a legal matter, we should involve the SFLC.)
<cjb> walterbender: nod.
<SeanDaly> bernie: good point, hadn't realized
<walterbender> can we modify the motion to say it is pending final approval of the SFLA?
<cjb> Red Hat actually has more free software lawyers than any other company, that I know of
<cjb> walterbender: no
<cjb> oh
<cjb> I see why you say that now
<walterbender> since we are part of the SFC, we need to abide by their by-laws
<cjb> you mean that the link to the fedora page in particular in pending acceptance by the SFC
<cjb> I think I would rather say something like:
<walterbender> cjb: I mean whatever license policy we decide will probably need their ultimate approval
  • tomeu feels ready to vote
<cjb> MOTION: adopt http://opensource.org/docs/osd as a set of guidelines for what is permitted on ASLO, for both software and content, and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable, and always asking the SFC for advice when a particular license is under question.
<bernie> walterbender: since aslo is hosted by the FSF, we also need to respect their definition of what constitutes Free Software.
<bernie> walterbender: but I guess they won't have problems accepting whatever is acceptable for fedora. except for firmware, which we don't distribute on aslo anyway.
<bernie> cjb: yay
<walterbender> bernie: well, I agree in that we should let them know what we are doing and they may not like it... in which case we may get booted out...
<cjb> I'd like us to try and hold back from getting all the way down the legality and making everyone happy rathole
<cjb> this is a motion that's ostensibly about something else
<cjb> which is, what do *we* want to do?
<walterbender> bernie: but we are a part of the SFC, so it is a bit different.
<cjb> we can make it work with everyone else as soon as we've decided that we want to do it
<walterbender> cjb: I think we want ASLO software and content to be FOSS
<bernie> walterbender: our distribution of firmware blobs within SoaS is merely being tolerated, but I know the FSF is strongly opposed to it.
<cjb> walterbender: ok; maybe we can vote now
<SeanDaly> cjb: speaking philosophically :-) openness is central to Sugar's education mission
<cjb> bernie: that's extremely off-topic. please talk about it later.
<bernie> cjb: indeed
<walterbender> cjb, bernie that is related to Agenda Item #3...
<walterbender> ok. shall we vote on the amended motion?
<cjb> yes, please
  • mchua tries to patch together the amended motion
<bernie> walterbender: ok, let's postpone it. I'm sorry I've derailed the aslo licenses motion with this unrelated topic
<walterbender> cjb> MOTION: adopt http://opensource.org/docs/osd as a set of guidelines for what is permitted on ASLO, for both software and content, and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable, and always asking the SFC for advice when a particular license is under question.
<mchua> seconded
<bernie> walterbender: yay
<cjb> bernie: it's fine, it's not derailed, just trying to keep us moving quickly
<cjb> (I guess grammatically that should be s/asking/ask/, but everyone gets the idea.)
<tomeu> bernie is yayish today... ;)
<mchua> yea
<cjb> yea
<SeanDaly> yea
<tomeu> aye
<walterbender> yea
<bernie> yep
<walterbender> Adam?
<bernie> CanoeBerry__: ?
<cjb> hm, guess he isn't here
  • SeanDaly thinks CanoeBerry timed out but didn't come back
<bernie> he's double underscore today... must have had much networking trouble :)
<walterbender> Seems the motion will pass... we can let Adam cogitate...
<CanoeBerry__> Sorry, distracted.
<walterbender> shall we move on to the DP topic?
<CanoeBerry__> Yes.
  • mchua nods
<cjb> ok
<walterbender> the motion passes.
<walterbender> #ACTION walter will inform the community
<walterbender> could someone volunteer to update the ASLO policy pages?
<walterbender> or volunteer to find a volunteer?
<cjb> the DP work was actually extremely good, even though incomplete; we should thank them
<cjb> walterbender: I think we can follow up to your announce mail asking dfarning or alsroot
<walterbender> #TOPIC SoaS DP
<cjb> they seem like the best candidates
<walterbender> cjb: +1
<bernie> alsroot: ping ^^^
<walterbender> cjb: I think their report is pretty comprehensive. Just don't understand why they never submitted it to SLOBs...
<cjb> yeah, I got the same impression
<walterbender> shall we walk through the three subtopics?
<cjb> good idea
<bernie> cjb: can you point us at the wiki page where all the DP opinions were summarized? I can't remember the url
<tomeu> I think mtd is pretty busy these days?
<cjb> http://wiki.sugarlabs.org/go/Decision_panels/SOAS
  • alsroot the quesion is what should be updated on ASLO policy pages
<alsroot> ..and ASLO draft policy pages
<alsroot> s/and/on/
<walterbender> Q1: OS distributor v. upstream
<cjb> alsroot: text similar to "anything you upload must be under a free software license that meets the Open Source Definition's criteria at http://opensource.org/docs/osd"
<cjb> Q1: SL is already being a Linux distributor. It seems to be working out pretty well, and SoaS is something SL spends most of its effort on
<cjb> so I can't imagine answering no to this question
<bernie> alsroot: and http://fedoraproject.org/wiki/Licensing#Good_Licenses is being used to disambiguate weird licenses.
<alsroot> or maybe just FSF list
<cjb> alsroot: I don't think they have one
<cjb> in any case, no big different, let's use the Fedora one
<cjb> let's stay on topic on DP now, pls
<bernie> cjb: personally I'd answer no to maintain distro neutrality, but this time I prefer to second the DP decision with my vote rather than my personal opinion
<tomeu> hmm
<tomeu> how does SLs spend most of its efforts in soas?
<SeanDaly> cjb; SoaS central marketing pillar of SoaS, but not sure correct to say developers spend most time on it
<cjb> SeanDaly: yeah, didn't mean just developers
<tomeu> and translators, etc
<tomeu> they work upstream
<bernie> alsroot: the fsf has a list of licenses with a discussions of their pros/cons... it's not really a list of acceptable free licenses.
<cjb> true. sorry, didn't realize I was saying something contentious.
<cjb> maybe to put it another way: if you ask people what Sugar Labs does, lots of people will say that it makes Sugar on a Stick
<walterbender> I think that the SoaS effort as with all our packaging efforts are almost all upstream...
<tomeu> that point isn't in the DP wiki page, right?
<alsroot> bernie: maybe http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses GPL compat. list
<mchua> I'd say SoaS is SL's primary deployment mechanism for Sugar.
<SeanDaly> cjb: not really contentious, but SoaS is a downstream of Sugar proper, and associates one distro in particular
<bernie> cjb: I'd rather not give this impression if possible
<cjb> tomeu: yes, I'm just quizzing Bernie on why he doesn't think that SL should distribute Linux
<cjb> because it seems to conflict massively with the reality of what we're actually doing
<tomeu> mchua: then we get to if SLs should do deployments itself ;)
<bernie> cjb: I'd like to say that we also do Trisquel Sugar and the XO builds... or none at all.
<bernie> cjb: "endorse" rather than "do"
<cjb> bernie: Sugar Labs do not distribute the XO builds.
<bernie> cjb: distributing soas is ok. I'm not saying we shouldn't distribute it. we may even distribute ubuntu and fedora... that's not the point.
<cjb> ok
<walterbender> Personally, I think SL should would with GNU/Linux distros and groups such as OLPC to distribute Sugar
<tomeu> cjb: but we have soas-xo :p
<cjb> tomeu: true :)
<SeanDaly> tomeu: not for Blueberry yet though
<walterbender> cjb: in fact, SL cannot sign builds for OLPC
<cjb> also true
<cjb> walterbender: should it only do that, or is that just one of the things it should do?
<cjb> (I mean.. "should it only work like that, or should it also distribute Sugar itself?"
<cjb> )
<walterbender> cjb: we should nurture projects like SoaS
<bernie> cjb: my point is that Sugar Labs does Sugar. SoaS is done by Sugar Labs people the same way the XO builds are being done by Sugar Labs people too (you and dsd)
<tomeu> as I have said since long ago, I tihnk that SLs should try to keep being just an upstream, which is Sugar. and soas should get its own organization. but in the short/medium term, I agree with soas staying in SLs if that helps them
<cjb> bernie: ok
<bernie> tomeu: +1
<cjb> bernie: I guess I disagree
<walterbender> tomeu: but SL will promote any and all good uses of Sugar...
<cjb> SL clearly makes press releases and talks about SoaS as if it's a product we distribute
<walterbender> of which SoaS is a prime example
<SeanDaly> tomeu: makes sense from development POV, but only when there are enough hands to go around... from marketing POV, different
<walterbender> and Sugar on OLPC another
<bernie> cjb: anyay, the DP wants us to say that we're a distributor in the Fedora Project sense, and as I said I'm going to second their decision.
<cjb> bernie: and I think this is a good thing, because it's good to have products that everyone knows you care about
<cjb> bernie: ok
<cjb> shall we vote on answering the first question, then?
<cjb> since I don't know of anyone who's arguing we should vote noj
<cjb> *no
<walterbender> SeanDaly: I think SL can market and promote SoaS even if it is not a SL "product"
<bernie> cjb: it's not that I don't want us to care about SoaS. Of course I do. But I don't wanna make it look like we compete against Trisquel Sugar or other distros containing Sugar.
<cjb> bernie: do you write press releases about those other distros too?
<SeanDaly> walterbender: yes... depends on trademark issues, branding
<cjb> if not, you're competing with them.
<tomeu> SeanDaly: yes, I agree the longer term goal depends on having enough resources
<walterbender> SeanDaly: the trademark and branding are of course our responsibility... but we can license our mark to non-SL products
<SeanDaly> cjb: when I draft the SL PR, I'm competing with the OSes preinstalled on computers in schools
<walterbender> cjb: we have promoted Triquel, for example
<SeanDaly> walterbender: yes of course
<tomeu> cjb: don't think we are competing with them, but we are discriminating them, sure
<tomeu> but I don't see how it can be otherwise
<cjb> tomeu: I agree
<walterbender> cjb: and I mention many distros whenever I talk publicly about SL
<cjb> tomeu: but Bernie doesn't
<cjb> walterbender: makes sense
<bernie> cjb: what we do today does not necessarily reflect what we'd do if 3 equally good live USB distros with Sugar existed.
<cjb> bernie: oh, that's true
<walterbender> cjb: and that day will come (or is almost here already)
<cjb> bernie: so your reading of "should we be neutral about distros" is "in an ideal world, should we be neutral about distros?" rather than "today, should we be neutral about distros?"
<SeanDaly> bernie: a very good point. Put another way, if teachers could easily overcome installation barrier, we wouldn't have to put in so much effort promoting Sugar in a form which lowers that barrier
<walterbender> trisquel and openSUSE have pretty solid products.
<cjb> Any seconds for voting and moving on past question 1?
<bernie> tomeu, cjb: Can we agree that we'd happlily distribute Trisquel Sugar from our servers and advertise it in our wiki? I actually offered them this option.
<walterbender> cjb: we can be neutral and still work closely with specific distros that want to work with us
<SeanDaly> I'd like SL brandbuilding to lift all Sugar boats including Trisquel and openSUSE
<mchua> Do we have a motion?
<walterbender> mchua: not yet :(
<cjb> MOTION: Question 1: Yes, SL is and should be a GNU/Linux distributor.
<bernie> cjb: yes
<walterbender> bernie: is that a vote on the motion? we need to second it and call the vote
<cjb> shall we vote on that?
<walterbender> can someone second it?
<SeanDaly> seconded
<tomeu> I would have to vote yes and no on that question, as I said before
<walterbender> ok. let's vote
<bernie> walterbender: no, I was just answering cjb... but I'd vote yes also on the motion so it doesn't matter :)
<cjb> tomeu: then you could abstain, I suppose
  • cjb votes aye
<tomeu> well, actually can vote no
  • tomeu votes no
  • mchua votes no
<SeanDaly> yea
<walterbender> walter votes no
<CanoeBerry__> Abstain
  • bernie votes aye
<cjb> huh, no has it
<cjb> apparently we're not a Linux distributor anymore :)
<walterbender> seems we are 3 aye, 3 no, 1 abstain
<walterbender> so the motion does not pass.
<cjb> oh, yes, I misread
<SeanDaly> now I'm confused :-)
<cjb> so, I think the right process is:
<cjb> * talk about why that just happened
<cjb> * come up with another motion
<cjb> agreed?
<bernie> CanoeBerry__: ouch you created ambiguity :-)
<CanoeBerry__> Sorry
<walterbender> cjb: feel free to come up with a new motion...
<tomeu> cjb: what if we phrased the motion "SLs should aim not to be a GNU/Linux distributor but will host SoaS as an strategic step"?
<bernie> cjb: agreed
<bernie> tomeu: I would agree to this one too
<walterbender> tomeu: I think we could host many distros
<walterbender> tomeu: I think we should say something stronger than just be upstream
<tomeu> walterbender: or that, though some distros cannot be hosted in SLs
<walterbender> I think we should say that we will actively seek out and work with distros interested in Sugar
<tomeu> well, that all upstreams should do
<bernie> SeanDaly: answering to your last message to me, I agree that SL *marketing* can be biased towards one particular distro or another
<walterbender> and help host and promote those efforts
<tomeu> ok, that's something else
<walterbender> tomeu: should do is one thing, but to say explicitly it is our policy is another
<bernie> SeanDaly: I understand the need to give one clear message such as "Download SoaS, it's great" rather than "find a distro you like and see if you can get it to boot with Sugar"
<SeanDaly> Proposal for motion: "SL wishes to spread the use of Sugar on all distros, and in so doing is and will be offering downloadable versions which may include one or more distros"
<walterbender> SeanDaly: can we add something about working with distros to create downloadable versions?
<bernie> SeanDaly: s/offering/produce and offer/
<SeanDaly> s/is and will be/offers (more concise)
<SeanDaly> bernie: yes more clear yours
<bernie> walterbender: +1
<tomeu> well, offering downloadable versions means just having links?
<SeanDaly> walterbender: +1
  • mchua is liking this
<SeanDaly> tomeu: I recently learned fedora downloadable in several different versions. But first contact I really liked pancake button and easy installation path
<SeanDaly> same for ubuntu netbook remix (but haven't installed yet)
<mchua> I imagine something like http://spins.fedoraproject.org/
<mchua> Instead of "based on Fedora" they'd be "runs Sugar"
<mchua> it's clear that Fedora itself isn't responsible for those spins
<mchua> and that they're done by the individual groups behind those spins
<walterbender> Motion: SL wishes to spread the use of Sugar and consequently works with GNU/Linux distros to produce and offer downloadable versions.
<mchua> but there's a trademark approval process to go through to be able to call yourself a "Fedora Spin" so the quality of the brand association is preserved.
<cjb> walterbender: hm, it's not clear who's doing the production or offering there
<SeanDaly> walterbender: true, but some people had issues with the "preferential" treatment of SoaS
<cjb> do we do it or does the distro? should make that explicit.
<bernie> SeanDaly: I agree, SL marketing should be left free to bias towards one particular distro if it helps promoting sugar better.
<walterbender> cjb: we help the distro (or anyone else) do it
<walterbender> cjb: I am trying to add a proactive element to our mission.
<cjb> but in the soas case, we actively host it
<SeanDaly> bernie: in fact, marketing as policy excludes distro promoting, but only because distro brands are weak
<bernie> SeanDaly: and I think the marketing team should be empowered to make such strategic decisions without interference from other teams.
<cjb> so we aren't merely working with a distro; that's why I think the motion is a bit unclear
<walterbender> cjb: I don't see why that is contradictory
<SeanDaly> bernie: no argument from me there, but I prefer the community understanding & approving since decisions are rational and not capricious :D
<walterbender> cjb: please help clarify the language
<cjb> walterbender: It's not contradictory, it just doesn't directly provide an answer to the question, because it leaves the main point "should SL be doing the distributing?" unclear/unanswered.
<bernie> cjb: yeah, at this time we're very biased towards SoaS, I admit it. I think we should just make it clear that it is a matter of fact and not a policy or a goal.
  • cjb will try to help
<walterbender> cjb: working with could include helping to promote and host
<cjb> walterbender: ok, let's add that for clarity
<SeanDaly> bernie: what's a policy is, I'd like to choose the best distro for the job to promote Sugar.
<SeanDaly> and that could change.
<cjb> walterbender: Motion: SL wishes to spread the use of Sugar and consequently works with GNU/Linux distros to produce and offer downloadable versions. This work can include helping to promote distros, and hosting them.
<mchua> Choose once for each release, perhaps?
<SeanDaly> and, I'd like to support all distros with Sugar
<mchua> +1
<walterbender> cjb: seconded
<CanoeBerry> +1
<SeanDaly> mchua: no, more like which one should be in SoaS?
<cjb> shall we vote now?
<mchua> SeanDaly: right, I mean make that choice once every release cycle, so we know how often the issue will come up
<walterbender> I think we are getting ahead of our selves...
<cjb> SeanDaly: we're having enough trouble moving past the easy question :)
<cjb> yeah. please stick to the question under debate only for now.
<bernie> cjb: yea
<walterbender> let's stick to Q1, which is the subject of the motion
<cjb> we'll get to the question that encompasses all this stuff later.
  • cjb votes aye.
<walterbender> walter: aye
<SeanDaly> mchua: (I had suggested once per year on conditions)
<SeanDaly> yea
<tomeu> yes
<mchua> yea
<cjb> CanoeBerry: ?
<cjb> (passes, in any case)
<cjb> question 2 is:
<cjb> Question 2: "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
<walterbender> well, seems we have a resolution of Q1 :) :)
<tomeu> success!
<cjb> I can't possibly answer yes to this, because we already act in a way that is preferential to SoaS, and I don't think that's a bad thing
<cjb> so I feel like I either have to answer no, or encode why we treat SoaS differently in the answer
<cjb> what do others think?
<walterbender> cjb: well, the question is about distros in general, not Live images
<tomeu> hmm
<CanoeBerry> SJ writes: "SL should support effective distros; this can be done neutrally"
<cjb> walterbender: I wasn't aware of that
<cjb> walterbender: I think live images are distros.
<walterbender> I think we treat distros with neutrality and think about the specific cases of their product offerings
<mchua> I think SL can provide identical infrastructure offerings to all interested distros, at the very least.
<mchua> Give them an equal playing field in that respect.
<bernie> CanoeBerry: as long as we maintain a shim of neutrality, I'm with SJ
<mchua> Marketing is the tough part, I think - SeanDaly?
<tomeu> what if someone asked "SL should be neutral about programming languages and shouldn't endorse one over another?" after all, there are communities around languages, same as around distros
<bernie> mchua: +1
<SeanDaly> Well... if distro A offers Sugar as install and makes it easy to switch, and distro B makes it difficult to obtain & install & configure Sugar, do we have to be neutral?
<cjb> CanoeBerry: oh, I see. so SJ's answer might be "SL should pick a distro that it judges to be the most effective, and then support that extremely strongly, but it chooses that distro neutrally, based purely on grounds like technical ability and maintainer activity"
<tomeu> the answer seems to be: the development team focuses on whatever they need to focus on, but everybody is welcome to bring more resources and work on whatever they feel like within the SLs goals
<walterbender> tomeu: if someone wants to do the work of refactoring Sugar in Java... more power to them
<bernie> tomeu: I'd actually agree to this one too. We do not endorse any one language, do we?
<tomeu> walterbender: right, so we could say that the marketing team is focusing on soas, but if someone else would like to do marketing for another one...
<cjb> (I guess I like the SJ answer, as long as we make it clear which distro we currently endorse.)
<tomeu> bernie: no, but I use to mention the pedagogic advantages of python in those cases
<bernie> tomeu: we choose languages based on technical merits, we don't have a policy that everything should be written in, say, Python or SmallTalk or C++.
<bernie> (the three main languages we use in our codebase)
<mchua> +1 to that; need to be clear what distro we endorse and what mechanism we use for choosing it.
<bernie> oh, and C
<tomeu> bernie: not only technical merits
<tomeu> actually, I don't want to enter into a discussion of what is better
<bernie> tomeu: well, consistency is a technical merit
<bernie> tomeu: we also ship LOGO... 2 different LOGOs :-)
<tomeu> ok, we engineers see everything as technical problems :p
<bernie> tomeu: yes, you're right. let's postpone
<SeanDaly> mchua: by not promoting underlying distro, I am supporting neutrality - I'd like Sugar on ALL distros, and i feel the way to get there is to promote a good one, and right now & foreseeable future SoaS is a really good one
  • cjb agrees strongly with SeanDaly
<walterbender> I think we will chose what to do on technical merits but we should endorse all efforts that advance our mission
<bernie> SeanDaly: +1
<tomeu> bernie: no need to postpone, we could rephrase as "SLs should only discriminate a distro because of availability of resources"
<bernie> walterbender: +1
<bernie> (which is education, not OSes or programming languages)
<walterbender> so how do we turn Sean's statement into a motion?
<cjb> walterbender: I think it's compatible with the SJ argument I mentioned
<cjb> I mean, I think it's a rewording of it
<cjb> Motion: "SL should pick a distro that it judges to be the most effective, and then support that extremely strongly, but it chooses that distro neutrally, based purely on grounds like technical ability and maintainer activity"
<walterbender> cjb: we just need it in the form of a motion
<cjb> how's that?
<bernie> tomeu: hmm... I think it's better to put it in the positive way: "SL endorses distributions based on availability of volunteer resources to support them"
<walterbender> OK
<bernie> cjb: nay
<walterbender> cjb: maybe plural? picks distros...
<tomeu> cjb: well, I think it's the marketing team which picks distros, not SLs
<walterbender> tomeu: I am not sure about that...
<tomeu> does SLs need to pick one distro for anything other than marketing?
<CanoeBerry> Time Check: 11am
<bernie> cjb: put this way, the motion contradicts sean's original proposal
<SeanDaly> cjb: i would go for even more flexibility. What if openSUSE got a huge education contract? In such a scenario I wouldn't pick, I would have my cake & eat it too: "Sugar is part of openSUSE blah blah, and can be tried on any PC, Mac, or netbook with Sugar on a Stick"
<cjb> tomeu: I think the marketing team *is* SL..
<walterbender> can people hang in a bit longer?
<cjb> yes, I can stay
<tomeu> cjb: ok, but not otherwise
<bernie> walterbender: I can
<bernie> which was: Proposal for motion: "SL wishes to spread the use of Sugar on all distros, and in so doing is and will be offering downloadable versions which may include one or more distros"
<SeanDaly> I can
<tomeu> I can about 20 mins more
<cjb> bernie: um
<cjb> bernie: wasn't that question 1?
<walterbender> OK. let's try to get this one sorted out.
<SeanDaly> it's the "refuse to endorse" part of the question I don't like.
<walterbender> I think we have to allocate our limited resources efficiently but we will do it in a neutral way
<cjb> bernie: I don't see the contridiction; we can host other distros at the same time that we're endorsing one main one more than others
<cjb> SeanDaly: okay, will try to reord
<cjb> reword
<bernie> cjb: oops sorry... I quoted the wrong one. The DP quesiton was different though.
<SeanDaly> kind of like saying I refuse to endorse 220 volts over 110 volts
<bernie> Q2: "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
<bernie> and the DP consensus was YES
<cjb> Motion: Q2: "SL should pick a distro that it judges to be the most effective, and endorse that distro more strongly than it endorses other distros, but it chooses that distro neutrally, based purely on grounds like technical ability and maintainer activity"
<cjb> anyone willing to second?
<walterbender> second
<SeanDaly> cjb: again, no need to say we pick one
<tomeu> I don't like that either
<cjb> hm
<SeanDaly> it's a policy question for me, not a one-distro-over-another question
<cjb> oh
<bernie> cjb: nay
<tomeu> I see value in making explicit that only the marketing need has a strong need of picking one distro or another
<cjb> could we pick more than one?
<bernie> tomeu: +1
<SeanDaly> and in our marketing we don't endorse Fedora at all
<cjb> Q2: "SL should pick distribution(s) that it judges to be the most effective, and endorse that distro more strongly than it endorses other distros, but it chooses that distro neutrally, based purely on grounds like technical ability and maintainer activity"
<cjb> is that good?
<bernie> cjb: could we not even say that we pick one distro at the SL level?
<tomeu> SeanDaly: we are referring to soas as a distro
<SeanDaly> because we know smart journalists will ask the question and answer it themselves
<bernie> cjb: I'd stick to Q2 the way the DP discussed it
<cjb> bernie: we good, but then we would be failing to encode our preferential treatment of SoaS
<cjb> s/good/could/
<bernie> cjb: which, I think, is solely a marketing decision
<bernie> cjb: justified by availability of resources
<bernie> cjb: and quality
<SeanDaly> tomeu: ok... but then it needs to be explicit that SoaS is a distro
<walterbender> ok. how about SL will endorse distros purely on grounds like technical ability and maintainer acitvity... skip the who first part of the motion?
<tomeu> SeanDaly: what else could it be?
<cjb> SoaS is certainly a distro.
<bernie> it's a remix :)
<cjb> it's based on a distro, which means it is one too. :)
<SeanDaly> again... SoaS pillar od marketing strategy because of market situation... will evolve when market evolves
<tomeu> and a remix isn't a distro?
<cjb> walterbender: sure, I'll try that:
<cjb> "Question 2: No, SL should not be completely neutral about endorsing distros, but it should only choose to more strongly endorse a distro based on technical merit and maintainer activity.
<cjb> walterbender: how does that work for you?
<mchua> add "And clearly publish the criteria under which that decisoin was made?"
<mchua> ...except with proper spelling
<walterbender> Not sure why "No," is that the beginning...
<SeanDaly> cjb: no i prefer another formula
<cjb> walterbender: because it's the answer to the question!
<bernie> cjb: I'd still vote nay on this one
<cjb> Question 2: "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
<cjb> we have to answer yes or no
<walterbender> cjb: gotcha.
<SeanDaly> No, SL should not be completely neutral about endorsing distros, but it should only choose to more strongly endorse a distro to further its education mission
<cjb> SeanDaly: that's too vague for me, I think
<cjb> although I understand the idea
<bernie> cjb: The DP answered yes. I'd tend to respect their decision.
<SeanDaly> No, SL should not be completely neutral about endorsing distros, but it should only choose to more strongly endorse a distro to better spread the use of Sugar on all distros
<cjb> bernie: no, the DP answered timeout.
<SeanDaly> bernie: I was on the DP and did not answer yes!
<bernie> cjb: ok, but their consensus was yes.
<tomeu> bernie: being neutral seems like a good idea to everybody except to those who need to make a choice ;)
<walterbender> I think we all agree that, yes, we should be neutral as far as distros go and what we should endorse their products based on technical and educational merits.
<cjb> bernie: I don't find that compelling enough to move me away from what seems like a very common sense answer that describes how we do behave already, with no argument given for why we shouldn't be behaving that way.
<cjb> bernie: so I can't vote yes.
<bernie> SeanDaly: well, the way the quesiton is posed, I would say no too.
  • mchua trying to rephrase = "SL should be neutral about providing *infrastructure* to Distros, but should not be neutral in our marketing/endorsement of them."
<walterbender> and as cjb added early, we should be public and clear about our rationale
<cjb> will add that now
<walterbender> mchua: that is good.
<tomeu> walterbender: I still don't understand why anything other than the marketing team needs to pick one or another distro
<walterbender> endorse is the broken word.
<cjb> "Question 2: No, SL should not be completely neutral about endorsing distros, but it should only choose to more strongly endorse a distro based on technical merit and maintainer activity, and should publish the criteria it uses for making that decision."
<SeanDaly> mchua: yes, and whatever choices are made are in order to better spread Sugar use
<bernie> cjb: if we can only vote to ratify the status quo, then we're useless.
<SeanDaly> walterbender: yes I was against it from the start
<cjb> bernie: I didn't say that
<cjb> I said I'm not going to vote *against* reality when no-one is persuading me why that reality is bad and should be avoided
<walterbender> seandaly: promote?
<mchua> how about this?
<mchua> "Question 2: SL should not be completely neutral about endorsing distros, but it should only choose to more strongly endorse a distro based on technical merit and maintainer activity, and should publish the criteria it uses for making that decision. Furthermore, SL should be neutral about providing infrastructure resources (hosting, etc) to distros."
<tomeu> walterbender: promote sounds good to me, because promoting is a task of the marketing team
<cjb> mchua: very good point
  • mchua just added the infra bit in, so that the separation of infra and mktg is clear.
<SeanDaly> walterbender: "endorse"... since our policy is not to endorse any distros at this time. But... as I said above, that could change based on market conditions
<bernie> cjb: so, even if our past actions seem to suggest that we only endorse one distro, we may decide today that we're going to be neutral and endorse distros based on availability of resources and marketing strategy.
<cjb> bernie: that's what the motion says, IMO
<cjb> bernie: it doesn't limit us to one distro
<SeanDaly> I ratther never use "endorse" :-(
<bernie> cjb: which, in practice, may not have any visible effect for a long time.
  • mchua has to leave now, but will read backlog later
  • mchua already squishing things in overtime
<cjb> mchua: are you comfortable voting on that motion?
<cjb> I think it's the best one we've had yet, even if it's not what we end at
<walterbender> could we vote on mel's motion with ^endorse^promote^
<SeanDaly> as i said, not contradictory to market several Sugars: OLPC, SoaS, hypothetical large distro deployment
<cjb> walterbender: good idea
<tomeu> walterbender: +1
<bernie> cjb: I guess you're right, more or less. I'd rephrase it, though.
<walterbender> let's vote and then tackle Q3 next week?
<cjb> MOTION: "Question 2: SL should not be completely neutral about promoting distros, but it should only choose to more strongly promote a distro based on technical merit and maintainer activity, and should publish the criteria it uses for making that decision. Furthermore, SL should be neutral about providing infrastructure resources (hosting, etc) to distros."
<walterbender> seconf
<bernie> cjb: the way it's phrased now suggests that we do not want to be neutral.
<walterbender> ^f^d
<cjb> bernie: feel free to attempt a reword
<cjb> although walter has seconded this one
<cjb> so we should vote on it first
  • cjb votes yes
<walterbender> bernie: neutral about distros, but not neutral about the efforts that are being put into them
<tomeu> I vote yes
  • walterbender votes yes
<SeanDaly> votes yes
  • cjb cheers :)
<cjb> CanoeBerry: mchua: still around for the vote?
<walterbender> I think we lost mel, but we can record her vote later
<bernie> nay
<SeanDaly> all criteria concerning SoaS marketing is totally public :-)
<cjb> ok, we should get votes from CanoeBerry/mchua for completeness
<bernie> I'm rewording the motion, please give me one minute
<cjb> but the motion passes, if I can count today
<walterbender> cjb: yes. I'll ask by email
<walterbender> Let's finish Q3 next week? Same time? Same channel?
<cjb> walterbender: ok
<walterbender> and then get into the remix topic?
<SeanDaly> walterbender: ok
<walterbender> thanks everyone. I think we got a lot done today :)
<cjb> bernie: you could provide an amendment to the decision next week, when we discuss q3
<walterbender> bernie: yes. please circulate a revised wording by email
<SeanDaly> cjb: there are possible scenarios in which technical + maintainer outweighed by other factors...
<walterbender> ok. we are almost 20+ so let's wrap up.
<walterbender> SeanDaly: did we lose educational? :(
<SeanDaly> cjb: for example, a distro which would bring $20m USD in TV advertising campaigns :D
<SeanDaly> yes, would have liked to see educational in there...
<bernie> MOTION: "Question 2: SL endorses Sugar distributions based on availability of resources (i.e. volunteers) and technical merits. Hosting and infrastructure will be offered neutrally. SL marketing may choose to bias promotion resources towards strategically important distros.
  • tomeu tries to imagine how a distro could impact education over the others
<cjb> SeanDaly: true enough. I don't think it's necessary to encode every use case, but we can provide an amendment for that too.
<bernie> walterbender, cjb: oops, ok
<cjb> tomeu: yeah, that's why I felt it was too vague to add
<bernie> I'll send this by email.
<SeanDaly> tomeu: if a government chooses e.g. openSUSE over Windows for 150,000 Classmates
<walterbender> ok. let's formally close the meeting...
<cjb> bernie: I don't see that your motion does anything different to the one we passed, except for refuse to answer the question directly :)
<SeanDaly> running Sugar
<walterbender> #endmeeting