Web   ·   Wiki   ·   Activities   ·   Blog   ·   Lists   ·   Chat   ·   Meeting   ·   Bugs   ·   Git   ·   Translate   ·   Archive   ·   People   ·   Donate

#sugar-meeting meeting, 2011-03-19 14:35:58

Minutes | Index | Today     Channels | Search | Join

All times shown according to UTC.

Time Nick Message
14:35 meeting Meeting started Sat Mar 19 14:35:58 2011 UTC. The chair is silbe. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:35 Useful Commands: #action #agreed #help #info #idea #link #topic #endmeeting
14:36 silbe #topic agenda
14:36 #info 1. Dextrose 2 bug fix release schedule
14:36 #info 2. Activity plans
14:36 #info 3. Dextrose 3 roadmap
14:36 #topic Dextrose 2 bug fix release schedule
14:37 m_anish: you have the stage :)
14:37 m_anish Ok, maybe i'll put it up on the roadmap page re: dx2... but I had a chat with pacita about the schedule for releasing updates...
14:37 we'd be releasing updated rpms on 1st April, 15th April, 1st May (and the first of every month from then on)
14:38 for 1st april, we'd be doing in-house testing like we have been till now, but starting from the 15th april release...
14:39 there would be a ~8 member team consisting of formadores, teachers and kids, who'd be given the updates a week before we release them to the world... and they'd test it for a week
14:40 we already have  dextrose-py-local and dextrose-py-local-testing repos setup with the latter being disabed for everyone
14:40 but we'll enable it for those select few team members...
14:40 icarito m_anish, how big is "world" in py? just would like to know
14:40 m_anish also since we'll have a predictable schedule, we can target what bugfixes to include in a particular update release and inform the testing-team of specific things to test before hand...
14:41 icarito, there are ~3700 laptops currently, with another 5000 arriving
14:41 they plan to start mass flashing starting monday and would probably take 3 weeks
14:41 nubae server wise, the schedule is not dated at all, I need help from Bernie for that
14:42 the road map I mean
14:42 m_anish ...continuing, for the 15th april release, we should release updates by 7th and probably inform them of what's getting fixed about 2-3 days before that
14:42 nubae, yep, i'm just talking about the dextrose-2 build that will be flashed on the laptops
14:43 does this all make sense? thoughts?
14:43 dirakx we should all be in sync with m_anish schedule.
14:43 nubae yah yah
14:43 dirakx m_anish: sounds good.
14:44 silbe m_anish: makes sense to me at any rate
14:44 icarito m_anish, i did not understand what is happening on the7th
14:45 you'll release updates on the 1st of every month starting may
14:45 in april twice
14:45 m_anish icarito, we'll push updated rpm's to the testing repo on 7th so that our testing-task force in py has a week to play with it
14:45 icarito, yep
14:45 icarito ok now i understand
14:46 dirakx, we should be prepared to release our modified activities in those dates
14:47 dirakx icarito: sure.
14:47 icarito m_anish, how can we make it easy for you to integrate updated activities, do you need us to release into ASLO every time?
14:47 m_anish icarito, nope, the updates are platform related ones...
14:47 icarito, we don't have automatic updating for activities
14:47 icarito interesting
14:47 m_anish icarito, if some activity blows up pretty seriously, we'd have to consider that, these are automatic platform updates...
14:47 silbe m_anish: I thought we have the shiny new microformat based activities updater?
14:48 m_anish silbe, we have, but it doesn't run 'automatically'
14:48 icarito does this auto updater fetch from ASLO?
14:48 m_anish FWIW, i don't expect major problem fixes or UI changes in these updates
14:48 icarito or where?
14:49 m_anish icarito, nope, we moved that to pyedu servers
14:49 nubae but originally
14:49 ?
14:49 m_anish http://activities.paraguayeduca.org/
14:49 nubae, originally it was from activities-testing.sl.o
14:49 nubae so that is a forwarder?
14:49 a mirror?
14:50 icarito 's internet connection hurts
14:50 m_anish nubae, nope, this isn't a mirror, this is a hard-coded path with fixed activity bundles linked to it
14:50 nubae the original file is uploaded to one location right?
14:50 m_anish nubae, icarito , we don't intend to change this page very often and atleast not via some online ASLO like tool
14:51 nubae, the activities will be uploaded to ASLO as always, we'd steal bundles from there as we see fit :)
14:51 icarito m_anish, maybe we could figure out a way to push updated activities at least with your ~8 ppl testing team
14:51 nubae fine gotcha
14:51 m_anish icarito, good idea!
14:51 dirakx m_anish: :).
14:52 nubae one thing that might be useful is telling ASLO NOT to automatically refuse caching agents
14:52 it really kills their server
14:52 m_anish #action figure out a way to push updated activities at least with our ~8 ppl testing team
14:52 silbe, is that how its supposed to be ^ :)
14:53 nubae there is a neat little tool that tells u how available content is from pages that owuld like to syndicte soem content
14:53 ASLo was voted really really restrictite
14:53 silbe m_anish: I think so. :)
14:53 dirakx m_anish: we could set up an http://activities-testing.paraguayeduca.org/ ?.
14:54 m_anish dirakx, yep, its an action item already :)
14:54 dirakx m_anish: great.
14:56 icarito nubae, aslo was voted? on a tool? i feel like i missed something
14:56 silbe nubae: yeah, quite a lot of our services just turn off all caching unconditionally. Most "web developers" are too lazy to figure out how to achieve consistency while still allowing a proxy to cache most stuff. Fixing them would be more work than we can handle at Sugar Labs. :-/
14:57 upstreams answer to this problem usually is to throw more hardware and/or server-side caching at it
14:58 (upstream = Mozilla, Trac, etc.)
14:58 ok, so are we done with the DX2 schedule?
14:58 m_anish silbe, yep, think so :)
14:58 silbe #topic Activity plans
14:59 icarito, dirakx: what exactly would you like to discuss?
14:59 icarito ok so i'd like to share with the team what we've been doing so far and also get some ideas from you no how to integrate better with the rest of AC workflow
15:00 as you know I started a couple of weeks ago, we are a new team, rafael started a bit earlier
15:00 what i've done so far is update the toolbars on several activities
15:01 help, typing turtle, words, maze, stopwatch, get books
15:01 we still have to push new bundles to ASLO but this involves pinging mantainers so could be a bottle neck as some are a bit orphaned
15:02 I also have been working in some plans for streaming content with gstreamer probably from a forked record activity for a documentary project in Peru
15:02 nubae silbe,  right, buts its pretty heavy on the server
15:02 icarito http://openetherpad.org/requer[…]neokinok-escuelab
15:02 nubae but nevertheless if it cant be done any other way, fine
15:03 just a shame to be fighint caching policy
15:03 icarito dirakx, this is what i've been doing, maybe you can share your part
15:04 and then we can discuss on ways we can make this better integrated with the rest of our plans
15:04 dirakx icarito: no special updates form my behalf. ;), the usual.
15:04 icarito dirakx, what is the usual, sorry, this is my first meeting
15:05 dirakx icarito: bug fixing, packaging and pootle admin.
15:06 among the dev stuff you metioned like toolbars and so on.
15:06 icarito: but mostly focused on developing specific requirements for activities.
15:07 icarito: that's the next part, you will be working on..after toolbars ;).
15:08 icarito ok then team, we'll share more as we go along then
15:08 silbe ok, sounds like you're humming along fine, except for getting blocked on releasing updated activities due to MIA maintainers?
15:08 dirakx silbe: +1.
15:09 icarito i'd like to have a plan for quality asurance of activities, this involves testing and deploying
15:09 but this is more long term
15:10 if the rest of team have ideas on the subject we can work over email
15:10 dirakx silbe: this is a problem, that we can fix in one way...having a super admin account on gitorious, like code-maint or so this user should have push rights to all activities. (but this proposal must be upstreamed ;))
15:10 silbe dirakx: can you make a list of activities you're currently blocked on, along with any maintainer information you have (from a.sl.o, wiki.l.o, wiki.sl.o, git)? I'll try to reach out to the maintainers then, like I already did with a few activities some weeks ago.
15:11 dirakx silbe: I preffer we follow the proposal i just mentioned..but dunno what you guys think ?.
15:11 silbe dirakx: the problem isn't a technical one (alsroot, bernie and I can easily hijack any repository on git.sl.o), but a social one (not offending the current maintainer who might not have done much work lately, but is still interested in the activity).
15:11 dirakx silbe: hmm ok.
15:11 nubae well obviouly quality assurance, but more importantly following policy
15:12 is really really KEY
15:12 dirakx silbe: I'll work on the list then..
15:12 nubae right now we dont have a policy reallly formalised
15:12 silbe dirakx: thanks!
15:12 nubae if we did, it would make life 100 times easier
15:12 dirakx silbe: i guess we can work together in pinging devs.
15:12 icarito nubae, +100 on policy
15:13 dirakx nubae: icarito we have a draft policy in wiki..editors policy for admins.
15:13 http://wiki.sugarlabs.org/go/A[…]ry/Editors/Policy
15:13 nubae not just tech, but marketing, logo usage, dress code, etc etc
15:13 dirakx we should complement it/improve it.
15:13 silbe FWIW, this topic has come up before (IIRC when wadeb was MIA); check out the sugar-devel archives.
15:14 nubae sounds almost schoool/uni like
15:14 but there is a reason they make u do that
15:14 silbe nubae: -1 for dress code :-P
15:14 icarito ok so then that's it from my side on activities team
15:14 dirakx with alsroot we think that this policy must be as transparent as possible and also low bar.
15:14 nubae hehehe
15:15 it was just an example
15:15 icarito dirakx, you're the man, you have the mic
15:15 :-)
15:15 m_anish this all makes sense :-)
15:15 nubae but its something that needs to be discussed overall with many folks
15:15 and then set in stone
15:15 think about lit like the decl. of independence
15:15 icarito nubae, policy might depend on deployments also, like m_anish is doing with activities.pyeduca
15:16 nubae, +1
15:16 dirakx icarito: no more to declare from my side. besides the Colombia-peru work we have been doing.
15:16 nubae sure thing...but first, we need our OWN policy
15:16 before started creating others
15:16 icarito hopes/wishes we had an apt-get like tool for activities
15:16 dirakx nubae: agree..at least an example..then deployments can make their own policies.
15:17 silbe icarito: check out alsroot's 0install work
15:17 still hasn't tried it - shame on him!
15:17 icarito i mean we could point say to AC's repo of activities
15:17 silbe, on my connection speed I need to throttle the amount of new stuff I try :-)
15:18 silbe, also I tried to get sweets to build but couldnt figure it out
15:18 silbe, atm i'm struggling with python-xpcom
15:18 dirakx, reg'd peru-colombia work, do you want to share something?
15:18 silbe icarito: there are several ways of doing that. A custom collection on a.sl.o, rpm packages for activities (like Fedora does), a microformat wiki page (like OLPC does), ...
15:19 icarito i'll say only we've begun approacing the Local Labs in Peru and Colombia to offer AC's services in tandem/conjunctino with SL Local Labs there
15:19 silbe, yes, too many ways
15:19 dirakx icarito: we can follow that by email @team we something happens.
15:19 when*
15:20 icarito dirakx, yes only since you mentioned it
15:20 dirakx icarito:  but yes! that's the resume of it.
15:20 silbe icarito: if we need to push out activity updates without waiting for the maintainers to merge our patches and release a new version, we can easily set that up. The "policy" we worked out the last time was: "Fork if you need".
15:21 icarito Sugar Co already had a meeting and the board agreed it was a good idea to offer AC's services
15:21 silbe icarito: interesting. I'm curious what will get out of it.
15:21 icarito and Escuelab in Lima too
15:22 dirakx hope it goes all well.
15:22 silbe crosses fingers
15:22 ok, anything else on activities?
15:22 dirakx silbe: :)
15:23 no more ;).
15:23 icarito puts the mic down and greets all around
15:24 silbe icarito: a warm "welcome to the team" from all of us, again. :)
15:24 m_anish claps :-)
15:24 silbe #topic DX3 roadmap
15:24 icarito silbe, thank you, m_anish  :-D
15:25 m_anish FWIW, an informal meeting happened yesterday with bernie, tch, dfarning http://meeting.sugarlabs.org/s[…]eeting/2011-03-18
15:25 tch <tch!~tch@190.52.131.169> has joined #sugar-meeting
15:25 silbe I've been working on DX3 builds this week. It takes me a lot of time, but we've even managed to get quite a few of our patches merged upstream (OLPC).
15:26 tch hello everyone, got stuck at some family issue
15:26 dirakx m_anish: thanks I was lurking and reading IRC at that time.
15:26 tch: hi!
15:26 silbe The first test image based on the new code base (we rebased on OLPC master) should be ready within the next few days.
15:26 tch current topic?
15:27 m_anish tch, dx3 roadmap (hope everything's fine)
15:27 silbe tch: "DX3 roadmap". I just started.
15:27 tch silbe: great :)
15:27 m_anish: yeah, not big issue i just couldn't leave
15:27 silbe #link http://meeting.sugarlabs.org/s[…]eeting/2011-03-18 informal meeting between bernie, dfarning, m_anish, tch
15:28 tch: hi, BTW :)
15:28 m_anish silbe, ah! meetbot should be smart enough to parse other links of meeting logs posted :-)
15:30 silbe that's quite a bit to read. I'd say we wrap up the official meeting and once I've read up on yesterdays meeting, we can continue discussing DX3 roadmap with everyone interested.
15:31 m_anish silbe, +1
15:31 silbe anything else someone would like to discuss?
15:32 dirakx something bad to share..SL was not accepted on GSOC :(.
15:32 but this is OT.
15:32 silbe dirakx: I noticed. :-/ Any idea why?
15:32 dirakx silbe: google doesn't says much about its disitions.
15:33 it seemed natural to get accepted..being successfull and all in the years we participated...but no luck this year.
15:33 silbe dirakx: IIRC they offered to explain on IRC. Guess we should accept that offer.
15:34 dirakx silbe: yep..I'll be on that meeting #gsoc
15:34 silbe dirakx: FWIW, another education related project (Tux4Kids) got rejected as well. Maybe they're setting a different focus this year.
15:34 dirakx: great, please keep up posted.
15:34 I guess that's it for the meeting?
15:35 dirakx silbe: i think this year is more focused to new orgs and investigation.
15:35 silbe 3
15:35 tch too bad,
15:35 silbe 2
15:35 1
15:35 #endmeeting
15:35 meeting Meeting ended Sat Mar 19 15:35:52 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot. (v 0.1.4)
15:35 Minutes: http://meeting.sugarlabs.org/s[…]-19T14:35:58.html
15:35 Log:     http://meeting.sugarlabs.org/s[…]11-03-19T14:35:58

Minutes | Index | Today     Channels | Search | Join

Powered by ilbot/Modified.
Webmaster