Oversight Board/2009/Log-2009-02-02


 *  	shall we get started?
 *  	Marco is at the dentist.
 *  	Does anyone know if Dfarning will be joining us?
 *  	where's dfarning?
 *  	he was taking some time off, right?
 *  	not sure if he's back or not
 *  	yeah
 *  	how about cjb?
 *  	What, is Marco getting every tooth pulled? Every time I turn around, he's at the dentist.
 *  	too mcuh sugar in his life
 *  	clearly
 *  	I would like to focus on a few issues today:
 *  	walterbender: I "called" him
 *  	(1) status of the new release
 *  	mchua|zzz: zzz?
 *  	(2) what we want to ask of OLPC going forward
 *  	(3) the slobs email controversy and community relations in general
 *  	(4) FOSDEM
 *  	(5) finances and prospects
 *  	Anything else on people's minds?
 *  	Well, chime in as we get going.
 *  	nope
 *  	Is erikos here?
 *  	nope
 *  	haven't seen him today
 * '' gregdek	is lurking while he handles flight details on phone.
 *  	about the new release, I'm a bit concerned that we are landing big user experience changes and I'm not sure we have gotten enough feedback
 *  	maybe we should leave #1 to the end then in case he shows up (and marco may be able to join us towards the end as welll)
 *  	makes sense
 *  	Topic: OLPC
 *  	I spoke with Chuck and Ed after the OLPC announcement and they asked me to make a proposal from SL about what we would want from them going forward...
 *  	A few ideas have been floated: a server (bernie), support for a few important changes to Write (gregdek),
 *  	hmm, what OLPC needs that we can help with?
 *  	clarity about who is still at OLPC and with whom we should be interfacing (walter)
 *  	(specifically, solving the collaboration crash issues in Write)
 *  	also, some clarity around support and RT
 *  	For example, it is still not clear to me if there is still a support gang at OLPC
 *  	and testing...
 *  	anything else we should ask them for?
 *  	from NN's announcement, I have trouble making myself an idea of what OLPC cares about now
 *  	so I don't really know what we can ask them that makes sense to them
 *  	Maybe we should be talking to Adam Holt directly about Support Gang?
 *  	If anyone will know, he will.
 * 	the support gang is still very active at OLPC - at the moment that is but who knows for how much longer
 *  	gregdek++
 *  	It is a bit strange... on the one hand, they have said some very positive things about Sugar; on the other, still talk about how we are about of fundamentalist, shooting ourselves in the foot...
 *  	but the bottom line is that theya re still our biggest deployment and we should help them any way we can
 *  	General coordination of incoming volunteers
 *  	I think that OLPC would like to feed their volunteers to us...
 *  	yes, I think so too.
 *  	should we ask them to fund a volunteer coordinator at SL?
 *  	Is that the impression you get?
 *  	but is OLPC a deployment? or deployments are uruguay, nepal, peru, etc?
 *  	Have they actually *said* that?
 *  	Yes. In so many words.
 *  	They have a lot of universities pledging people...
 *  	Then yes, we should ask them to fund a volunteer coordinator.
 *  	and need help coordinating them.
 *  	lots of work to do in that area
 *  	So we are prepared to take the step of hiring prof. management...
 *  	walterbender: what about the PM who was going to join us some time ago?
 *  	prime minister?
 *  	Bernie: please refresh my memory...
 *  	I have a small cache and no diskspace
 *  	walterbender: I don't think he wanted his name to go public yet
 *  	now they will accuse us of conspiracy :-/
 * edmcnierney	tunes in due to request from bernie - hi there.
 *  	no need for a name, but the idea?
 *  	hi ed... timely entry
 *  	I think I'm just reiterating walterbender's point that Chuck and I would like to hear a proposal on SL support from OLPC.
 * |	unmadindu (n=sayamind@gnu-india/admin/unmadindu) has joined #sugar-meeting
 *  	We haven't had a chance to gather as a group for a while, hence our delay getting back to you.
 *  	That's definitely something we're still interested in doing, but it would really help to get a coordinated, comprehensive proposal rather than an assortment of individual requests.
 *  	+1
 *  	what means "SL support" here?
 *  	That is why we are discussing it here--to get everyone's ideas on the table.
 *  	walterbender: Yes, I realize you've been busy :)
 *  	yeah, coding
 *  	edmcnierney: do you have the log from the last 10 minutes?
 *  	yes
 * |	cwhii (n=cwhii@adsl-69-227-95-58.dsl.sndg02.pacbell.net) has joined #sugar-meeting
 *  	I think we are goign to be in a situation where prospective deployments are decidign between XOs, netbooks of various brands and SoaS. Can we do anything to reduce the potentail awkwardness of such a situation?
 *  	Other than a few details: a server, triage in on important area, it is about support and coordination that we are interested in help.
 * cwhii is now known as cwhii_
 *  	@caroline: we cannot get in the middle of the hardware discussions... we would need to build a wholly different organization.
 *  	What we can do is make sure Sugar is the right choice regardless of what decision is reached.
 *  	or work together with the organizations that decide the hw, so sugar runs well there
 * |	befana (n=befana@190.158.124.131) has joined #sugar-meeting
 *  	in case we cannot make sugar run well everywhere ;)
 *  	back to OLPC for a moment...
 *  	Ed: is there still a support gang at OLPC?
 *  	befana: aren't you a member of the support gang?
 *  	whether there is or not in the long run, we should work on a way to coordinate efforts...
 *  	in many companies, the point of contact between support and R&D is the bug tracker
 *  	the gang is still ongoing ;)
 *  	they can file requests there
 *  	bernie: hi, i'm not
 *  	btw, in the absence of a PM, do we want/need a bugmaster who would prioritize bugs, assign them, etc?
 *  	I expect that we're going to have to do some of that in the engineering meetings.
 *  	So we need to make sure that the RT system remains intact and ideally is in service of OLPC, OLPC deployments, Sugar, and Sugar deployments as they begin to diverge...
 *  	In my limited time, as we near release, that's probably what I'll spend most of my time doing.
 *  	this is what Pia has been thinking about.
 *  	bernie: that would the bugsquad erikos has been working on
 * |	erikos (n=erikos@e178222092.adsl.alicedsl.de) has joined #sugar-meeting
 *  	gregdek: yes, our trac will soon start to bitrot without some love
 *  	Engineering meetings at release time should be: "which bugs are hot, and what's our status on them?"
 *  	But honestly, it's a full-time job.
 *  	gregdek: but we cannot deal with many bugs in a meeting
 * '' walterbender	aaaaargh. too many windows open
 *  	tomeu: You'd be surprised how many bugs you can discuss in a two-hour meeting.
 *  	gregdek: a team of people could work together async with a bugtracker
 *  	True.
 *  	I remember the triaging sessions at olpc
 *  	We probably need to do both.
 *  	OK. We need to stay focused.
 *  	What else should be part of the "ask" from OLPC?
 *  	Can I gist from your discussion that we need a concrete plan for coordinating bugtracking as well as for RT?
 *  	We have one, of sorts, but we should tighten it up.
 *  	gregdek: can you point us at where it is written down?
 *  	i.e. we have agreement that Sugar bugs that end up in OLPC trac will be placed into Sugar Trac, and then closed in the OLPC trac with an id pointing to the Sugar trac id.
 *  	It's in email right now. We can get it into engineering docs somewhere.
 *  	And a reciprocity?
 * |	eric_the_sad (n=joe@joenet.demon.co.uk) has joined #sugar-meeting
 *  	We'll send them OLPC bugs?
 *  	i.e. Sugar bugs that are actually OLPC-related will be moved to olpc trac in the same way?
 *  	walterbender: a server for pootle and builds would be nice
 *  	Make sense t ome.
 *  	yeah, we have some bugs in dev.s.o that are XO specific
 *  	What about Fedora bugs?
 *  	We didn't discuss it, actually, but it certainly makes sense.
 *  	Q: we would need also to separate SL's RT from OLPC's RT ?
 *  	The actual policy is simple. It's moving the bugs that's expensive.
 * |	hpachas-PE (n=hpachas@200.37.120.18) has joined #sugar-meeting
 *  	we need to add an xmlrpc plugin on both tracs to make moving bugs possible
 *  	I was counting on coderanger to help me with that
 *  	dirakx: I think we'd want a similar mechanism for RT, but as I understand it, what Pia proposed is one point of entry...
 *  	walterbender: ok.
 *  	Sugar lives in a certain part of the complete software stack, I guess we shouldn't have open bugs in the Sugar trac that lie in other parts of the stack? like those battery bugs we have now?
 *  	and then the tickets get distributed to the various concerned parties.
 *  	but I guess what I am asking of OLPC is if they are in agreement with such schemas and what resources they'd be able to bring to the table.
 *  	To be clear: Fedora, Ubuntu, and GNOME all have tons of issues keeping track of these kinds of problems.
 *  	I understand RT as closer to the user than trac, if SL isn't going to be in the business of directly deploying, why should it have an RT instance?
 *  	why not deployers move tickets from their RTs to our trac?
 *  	So we can state a simple policy -- "always move bugs to the proper upstream" -- but that policy will get messy very quickly.
 *  	(sorry, got interrupted - I'm catching up)
 *  	tomeu: that seems plausible.
 *  	tomeu: +1, i never understood rt from a developers point of view
 *  	I think Tomeu's proposal makes sense for Sugar, but perhaps not for Activities?
 *  	Activities are what end users interactive with...
 *  	hmm
 *  	But if there are good people manning the RT systems, it would probably work.
 *  	So SL would be trac only and we'd have a good outreach to the various RT/support teams
 *  	including whatever OLPC and the OLPC deployments use...
 *  	I guess RT places a focus on tickets being properly followed so the user is happy because sees their issues being addressed, while trac or bugzilla try rather that developers are happy by knowing that their software is less buggy
 *  	RT is about customer service.
 *  	ideally there would be a single system that achieves both, but in practice that's not feasible
 *  	I agree: SL should be trac-only.
 *  	other way could be creating a sugar category on OLPC's RT..and having the SG's resolving the issues there.
 *  	tomeu: That seems to be my impression, too.
 *  	SGs?
 *  	oh, support gang
 *  	tomeu: ;)
 *  	One way or another, someone has to ensure that there is a support gang (SG) out there
 *  	and that someone is manning an RT system.
 *  	right
 *  	walterbender: I can help install RT on one of our machines, but only if there is a real group of support people behind it
 *  	So back to the question of what OLPC's plans are in that regard?
 *  	I personally think end-user support is better done locally in the field
 *  	bernie: the way that the conversation is heading, not sure that this is SL server issue...
 *  	also because of language and cultural barriers
 *  	But if the deployments cannot do it on their own, we could pitch in to help...
 *  	walterbender: We don't have any plans to switch from using trac for bug-management and RT for "service" issues.
 *  	So there are plans to maintain the RT system and the support gang?
 *  	walterbender: I think we have a reasonable understanding in place on how to manage trac bugs moving to SL and vice-versa, we'll just need to keep an eye on how it plays out in practice.
 *  	walterbender: Yes, no change there. SG has continued to be active and meeting regularly, and RT's in use for a number of things here and won't change.
 *  	that is very good news.
 *  	Just got a "welcome" email for a new support-gang volunteer from yesterday :)
 *  	Shall we move on to the next topic then?
 *  	(I'll try to summarize the discuss into an email to Chuck and Ed)
 *  	walterbender: Thanks - that would be a big help.
 *  	(3) slobs email controversy?
 *  	I have to admit I am not quite sure what the controversy is, but there is an impression of a lack of transparency from slobs...
 *  	There is always that impression, and you have to fight it tooth and nail.
 *  	the government is always bad
 *  	:_
 *  	Are there specific complaints we can address?
 *  	i don't see the lack of transparency..but i would like to see the ”thread” ;).
 *  	btw, I had a similar discussion in #sugar about it just before the SugarCamp
 *  	I didn't hear back from Michael yet about my suggestion that he monitor slobs mail for things that should be public...
 *  	gregdek: the specific issue was brought up by m_stone, who seems to be afk now
 *  	but having someone who's job it is to ensure we are as transparent as possible seems a good thing...
 *  	some people feel trouble in getting integrated into SLs, and I don't see how we can improve there
 *  	Is this an issue from anyone other than m_stone?
 *  	dirakx: we're missing dfarning's consent before we can "declassify" it :-)
 *  	walterbender: ivan pointed out that the thread happened out of the slobs ml
 *  	bernie: ok.np.
 *  	yeah, dfarning said he would be away the weekend and part of the week
 *  	but he seems to be occasional email access
 *  	s/be/have
 *  	I agree with dfarning regarding the merit of discussing some ideas with peers before entering into a public discussion: I am a big believer in editing.
 *  	gregdek: cjb also said he was mad for that, but he might have been joking
 *  	My quick take: (1) slobs ml archive should be open unless there's a compelling reason not to open it; (2) slobs ml should be invite-only even if the archive is available.
 *  	something related, anybody has already thought about declassifying a month worth of slobs mail after some months/years?
 *  	Limited, but transparent.
 *  	gregdek: but where we'll discuss issues that involve partners that demand privacy?
 *  	I thought that was the only purpose of the slobs ml
 *  	The reason for a private list is to have a place to discuss things that others have asked us to keep private.
 *  	tomeu: good point.
 *  	not of the slobs in itself, just the ml
 *  	I don't think we ever (purposefully) discuss SL business in private.
 *  	slobs issues that don't demand privacy should be discussed in iaep
 *  	walterbender: But everyone assumes that you do.
 *  	that is why I'd like a 3rd party to monitor the list...
 *  	The existence of a private email list *always* makes people assume that you are discussing Serious Business there.
 *  	some 3rd party business is serious
 *  	gregdek: we publish all our code so people can check that we don't have time to discuss stuff in private :p
 *  	tomeu: ideally, one of the observers should be doing the name blanketing
 *  	ok, then +1 to have a transparency cop in the slobs ml
 *  	Make m_stone that guy.
 *  	maybe that is all we can do at the moment...
 *  	gregdek: also, michael came in at an extraordinary time where 12 emails were sent the same day. usually it's 2-3 per day.
 *  	I've asked him.
 *  	the results of these kinds of discussions come out in the weekly news, right?
 *  	Good. :)
 *  	shenki: yes
 *  	next topic then?
 *  	shenki: not always, especially negotiations with hw companies
 *  	(4) FOSDEM
 *  	shenki: oh, you mean the present discussion? yes
 *  	bernie: well, but those discussions must go public at some point
 *  	bernie: or they fail
 *  	bernie: i ment in general
 *  	tomeu: yes
 *  	ok next topic
 *  	yep
 *  	When they don't go public, it is an example of a failure.
 *  	we are going to have much bigger activity in this year's fosdem
 *  	We're gathering on Friday for a pre-meeting in a hacker room kindly offered by the FOSDEM organizers
 *  	lots of important meetings of the mind there too
 *  	http://hsb.wikidot.com/
 *  	Can we plan to keep an IRC channel open during the meetings?
 *  	gregdek, bernie, ChristophD: anything will happen in fosdem that is not here? http://sugarlabs.org/go/MarketingTeam/Events/FOSDEM_2009
 *  	walterbender: the problem we have about that right now is that we only have one meeting with time assigned and none with an agenda
 * 	tomeu, not anything that I'm aware of ;)
 *  	walterbender: I'm going to send reminders today
 *  	we should schedule the unofficial events too, such as the code sprint with Rob Savoye
 *  	yeah, rob also needs to say what time works for him
 *  	when we get meeting times nailed down, it would be good to send a heads up.
 * '' erikos	will meet with sdzillas to talk about SoaS
 *  	tomeu: I will review and add anything necessary.
 *  	erikos: Great!
 *  	tomeu: yes. we'll get drunk on friday night
 * 	gregdek, will you join us on Friday?
 *  	ChristophD: Unclear. I'm spending part of the day in an open source education conference with Mozilla.
 *  	erikos: who's sdzilla?
 *  	bernie: sebastian dzillas
 *  	or what is it?
 * 	gregdek, ah, okay, well, that shall be interesting as well!
 *  	bernie: Fedora volunteer who is maintaining a Sugar spin for Fedora that is *very* similar to SoaS.
 *  	bernie: sebastian dziallas
 *  	Looking to cut down on duplication of effort, I presume.
 *  	yeah. sebastian has brought up a lot of interesting strategic points we should discuss.
 *  	gregdek: we *must* throw SoaS on his shoulders
 *  	bernie: yup - he offered kindly some help and we wish to coordinate a bit
 *  	Yep. :)
 *  	He's a 17 year old kid with huge enthusiasm and capacity.
 *  	bernie: will he need access to SLs infrastructure?
 *  	one issue dfarning brought up in the sekret thread was that we're dispersing too much energy in supporting disparate distros.
 *  	there is a plan to have a SoaS stand somewhere?
 *  	developers should develop
 *  	gregdek: oh wow - awesome
 *  	walterbender: We will be making SoaS on demand at the Fedora booth.
 *  	I gather someone will be handing out USB keys at the meeting...
 *  	bernie: sure, i think there is always a long term and short term goal
 *  	bernie: we just help to get the ball rolling
 *  	gregdek: great
 *  	"Bring your USB key, get SoaS!"
 *  	erikos: sure, now it is maybe the time to spend some energies to widen our user base.
 *  	when you see companies giving out USB sticks see if they want to give us some to give to kids.
 *  	bernie: yes - and i really think soas is a good tool for that
 *  	if we keep in mind we should hand off these things to local maintainers so we don't stay busy with the packaging and distro work
 *  	bernie: sure
 *  	If and when we have some money, we can make branded sticks (2 gig) for ~$5-10 depending on quantity
 *  	You should have lollipops at the booth too :)
 *  	2 color printing.
 *  	caroline: indeed
 *  	And I am still chasing after Belkin
 *  	mchua is printing business cards
 *  	she's sweet
 *  	btw, we may need to start thinking about our presence in the next conferences, etc
 * 	walterbender, excellent idea selling the SugarLabs SoaS sticks!
 * 	bernie, mchua will be at FOSDEM???
 *  	ChristophD: no :-(
 *  	ChristophD: but her soul will be
 *  	bernie: oh right - does she need some details from us?
 * 	bernie, hehe, okay... too bad she wont be there!
 *  	ChristophD: andriani will get us business cards designed, organized and paid for by mel
 *  	where in the world is Mel today?
 *  	zzz i guess
 *  	I thought boston?
 *  	jetlagged?
 *  	i guess so
 *  	Anything else re FOSDEM
 *  	do we have more companies to approach?
 *  	collabora will be there too
 *  	of course
 *  	Any and all hardware folks who will be there... and distros, and the edu spins
 *  	I have a meeting with a TI guy
 *  	they have a nice ARM laptop, apparently
 *  	sorry, I never mentioned before... you know, it's a cabal
 *  	as long as you don't disclose your talks with microsoft, we are good
 * 	bernie, I wanna see that laptop as I'm very excited about the low-cost ARM netbooks!
 *  	there are a lot of new laptops coming out: gdium and the one from India...
 *  	the mobilis I guess, not the $10 one :p
 *  	ChristophD: yeah, it's very likely that the future of the industry is arm-only
 *  	don't discount mips
 * 	good point
 *  	yeah, mips is cheaply done in china
 * 	but I think for 2009-2010 ARM will be kind, esp. in Europe and North America
 *  	and italy
 *  	do we meet with anyone from mandriva?
 *  	and opensuse?
 *  	opensuse is also strong on some netbooks
 *  	walterbender: although alsroot is doing nice work on sugar on mandriva 2009.1, we don't know yet how sugar can get into the mandriva versions that run on arm and mips
 * |	aa (n=aa@r190-135-151-45.dialup.adsl.anteldata.net.uy) has joined #sugar-meeting
 *  	walterbender: mandriva standard doesn't build for those architectures, they seem to have something internal
 *  	tomeu: I think the gdium team may have some ideas there...
 * |	neuralis (n=krstic@solarsail.media.mit.edu) has joined #sugar-meeting
 *  	walterbender: so would be good to keep them in sync
 *  	the openmoko guys will be there -- naa, I don't think we care
 *  	they will be at FOSDEM
 *  	yeah, they must know about mandriva+mips
 * 	could someone take http://sugarlabs.org/go/MarketingTeam/Events/FOSDEM_2009#Goals_.7C_Community_Meetup and turn it into a real agenda with attached schedule so we dont go off on a tangent?
 *  	apparently they have many improvements over the core
 *  	one theme I think a lot of people are interested in is how to integrate their widgets with Sugar
 *  	walterbender: I guess we have lots to discuss about that, I'm not sure what that would mean right now
 *  	me neither.
 *  	but a lot of h'ware folks do some unique things to give them some differentiation...
 *  	how that would integrate with Sugar is important.
 *  	ChristophD: will think of some proposals there
 * 	tomeu, thanks :)
 *  	what hw do we expose at the booth?
 *  	hopefully some concrete discussions will happen at FOSDEM
 *  	I have an EEE-PC, and an XO
 * 	classmate
 *  	bernie: do we have a booth? ;)
 * 	bernie, what about the Beagle board?
 *  	All that we can...
 *  	ChristophD: do you have soas running on it already?
 *  	ChristophD: nubae also has one apparently
 *  	I printed a big Sugar Labs banner I used at LCA.
 *  	ChristophD: yes I was planning to get it there
 * 	bernie, nubae has aaron's classmate
 *  	Anyone going to FOSDEM from Boston?
 *  	but it requires a display
 * 	and I think its currently a vanilla ubuntu install with sugar on top of it
 *  	who could bring an LCD panel?
 * <ChristophD>	bernie, you are the ones going by car ;)
 *  	walterbender: maybe gregdek knows someone from RH who travels there from boston?
 *  	Oh, btw: robsavoye will be there too. we'd like to hack together a gnash activity
 *  	tomeu: Nope.
 *  	Maybe just shout out to the list?
 *  	ChristophD: not any more. we were 6, costs went up... and planes were €10...
 *  	bernie: have some ideas about that
 *  	tomeu: cool, it shouldn't be hard with bertf's wrapper script
 *  	there was a gnash developer at the olpc-[hilippines meeting
 *  	tomeu: or with proper fallbacks in sugar for native applications
 * <ChristophD>	bernie, ah, okay, when will you be arriving at BRU?
 *  	bernie: oh, I thought we were going to be a bit ambitious, but let's talk about it in #sugar
 *  	ChristophD: thursday evening
 * <ChristophD>	okay, great
 *  	caroline: do you know if that gnash dev in in sugar-devel?
 *  	s/in/is
 *  	no clue sorry
 *  	anything else abut FOSDEM to discuss here?
 *  	we should talk about (5) Finances as we are getting late
 *  	We have a little money and a few expenses...
 *  	I have a big stack of grant rejections...
 *  	and a few more birds in the bush...
 *  	I need some help identifying opportunities
 *  	I've just exchanged a few words with rob.
 *  	he'll be in brussels friday evening, too late for the hack room.
 *  	particularly outside of the US usual gang of suspects
 *  	bernie: whereas you added finances to the agenda, anything you wanted to discuss?
 *  	walterbender: OSL did a lot of good work for us. I was thinking of rewarding them with a small donation
 *  	some $200-300 just to show our gratitude
 *  	they have discretely asked for donations to the lab a few times
 *  	then, the FSF still isn't asking us money
 *  	but they should :-)
 *  	their server has been in production for a while now
 *  	GA
 *  	maybe a token gesture to OSL until we have surer footing...
 *  	I don't want us in a position where we are operating in the red...
 *  	maybe a more detailed financial report from dfarning next week?
 *  	with a budget?
 *  	then we would be in a better position to make decisions.
 *  	ok
 *  	we don't have the meetingbot on to record AI?
 *  	no hurry
 *  	crap we forgot
 *  	I'll just trasnscribe by hand
 *  	so, what else before we can get back to code?
 *  	final topic: 0.84?
 *  	Erikos: can yo give a quick update?
 *  	walterbender: so we hope to get a god understanding what is broken what needs fixed
 *  	and how the new design changes work out
 *  	with the testing we get from the soas
 *  	walterbender: so i don't think we are to bad
 *  	we don't know if we are too bad :p
 *  	tomeu: yeah ;)
 *  	so we need more testing
 *  	walterbender: the main issue in general is distraction
 *  	I did some informal testing
 *  	walterbender: from the actual coding
 *  	tomeu: yup
 *  	on the EEE, we have a few problems with the smaller display size
 *  	but have enough tickets to fix right now
 *  	bernie: cool
 *  	and supposedly the classmate will be the same
 *  	bernie: yes - this is one item that needs to be addressed
 *  	How can we make sure that the various testing teams (e.g., Wellington) try the new code?
 *  	on F11, we have a few dead activities due to 2.5 ->''' 2.6
 *  	are they listed in the wiki?
 *  	apart from this, 0.83 looks very polished to me
 *  	bernie: that is ok i presume - we only want to have the fructose ones packaged
 *  	bernie: that i did already
 *  	joyride does not seem to boot on my xo
 *  	is it broken?
 * '''<--|	eric_the_sad has left #sugar-meeting
 *  	bernie: don't worry about joyride
 *  	walterbender: announce the soas on the list and on the blog
 *  	walterbender: i want to have a FOSDEM spin
 *  	walterbender: with the latest fixes in
 *  	erikos: then it's ok
 *  	walterbender: that we cna announce widely again
 *  	walterbender: turtleart also has issues with the eee display
 *  	yes... tell me exactly what to announce.
 *  	@bernie: which version?
 *  	walterbender: what went on SoaS?
 *  	bernie: also, what resolution?
 *  	from the activity dev. POV, it is really hard to test everything everywhere
 *  	walterbender: that is the latest working one http://erikos.sweettimez.de/?p=332
 *  	and old builds too.
 *  	walterbender: i will update you with newer versions
 *  	erikos: I have a disruptive proposal: why don't we change the default screen size of sugar-emulator to the same of the EEEPC for a while?
 *  	erikos: so developers see these bugs on their computers
 *  	bernie: you can set screen size for the emulator easily
 *  	I run jhbuild at various resolutions...
 *  	erikos: yeah, but who does? :)
 *  	bernie: -i
 *  	erikos: -1?
 *  	ah!
 *  	bernie: heh
 *  	but for instance, making sure an activity still runs on 656 or 703 or even 767?
 *  	and making sure it runs on Fedora and Debian...
 *  	it is difficult.
 *  	bernie: i am ok - to change the default - but maybe more 1024x748
 *  	erikos: I mean, it's a psychological trick to shake bugs easily. the weirdest and more restrictive the default, the better
 *  	bernie: ok with me - tomeu?
 *  	erikos: ok for 1024x768, it also fits better in people's displays
 *  	One other thing to keep in mind is that there are scaling issues in Pango between the XO and other displays...
 *  	bernie: yeah 768 i meant ;p
 *  	I had to introduce a scaling factor in TAPortfolio because the fonts will all wrong on the XO
 *  	walterbender: oh yes. dpi really need some work. I asked unmadindu to have a look if he has time
 *  	walterbender: yeah :/
 *  	fine with me, but won't other users feel bugged by that
 *  	I think it is an XO-spefici issue...
 *  	we should also have a smaller cursor for lower DPI displays
 *  	walterbender: it may be a high resolution issue, so would be present in other machines
 *  	Is there a page in the wiki with the list things to look for in making an activity cross-platform?
 *  	benzea has some ideas about that, need to talk with him
 *  	walterbender: don't think so
 *  	For example, I discovered that the reason TA wouldn't launch in 703 was that I was checking the version number of the activity, which is not an environment variable set in 703... I had to add an exception
 *  	Erikos, if you tell me where to put the page, I'll start adding the gotchas I have encountered...
 * '' unmadindu	plans on looking at gnome-settings daemon to figure out dpi stuff.
 * '' unmadindu	has chewed g-s-d before
 *  	walterbender: perhaps inside the Activity Team wiki area?
 *  	walterbender: sorry, which page?
 *  	unmadindu: that would be awesome
 *  	tomeu: +1
 *  	walterbender: what version works with which release?
 *  	I think it uses xsettings for handling dpi stuff, but I'll have to check
 *  	erikos: a page for activity developers to consult re cross platform and corss version compatibility
 *  	(and testing tips)
 *  	unmadindu: I think it uses the value that gets set in the gnome "appearance" control panel
 *  	walterbender: oh ok - yeah i agree with toeu to put it in the Activity Team namespace
 *  	unmadindu: not sure if it lives in xsettings or in gconf
 *  	we degenerated into heavily technical discussion for a slobs meeting, but I like it
 *  	maybe we bring the meeting to a close and move back to #sugar?
 *  	yup sounds good
 *  	OK. See you on #sugar
 *  	thanks
 *  	meeting adjourned
 * <ChristophD>	Isnt this cross-platform compatibility issue something that should also be considered for the Remora project?
 *  	ChristophD: yeah, remora already allows us to tag a bundle with a sugar version and a platform
 *  	ChristophD: I don't think that we have any portability issue''' that mozilla don't have as well in their addons
 * <ChristophD>	tomeu, ah, good to know, thanks :)
 *  	duh adjourned just now that I'm arrived!
 *  	ChristophD: I don't think that we have any portability issue''' that mozilla don't have as well in their addons
 * <ChristophD>	tomeu, ah, good to know, thanks :)
 *  	duh adjourned just now that I'm arrived!