maemo-meeting-2009-06-18

* Jaffa just doing some last minute paper work.15:32
JaffaWelcome all to the June (*cough*) sprint maemo.org sprint meeting15:32
JaffaThe agenda is as follows:15:32
Jaffa1) Discussion of status reports sent to maemo-community on the final statuses of last sprint's tasks: http://wiki.maemo.org/Maemo.org_Sprints/May_09#Tasks15:33
Jaffa2) Discussion on new sprint process15:33
Jaffa3) Agreement on next sprint tasks15:33
Jaffa4) AOB15:33
JaffaFirst off, review of the last sprint items.15:35
JaffaDoes anyone have anything to add to the items which are already reported as "done"?15:35
JaffaFor reference 9.03-01, 9.05-03, 9.05-04, 9.05-06, 9.055-07, 9.05-11, 9.05-12 (belonging to qgil, dneary, dneary, X-Fade, X-Fade, qole and jeremiah respectively)15:36
X-FadeFor me those were pretty clear tasks.15:37
JaffaAre any of the other tasks completed, but not marked as such? (qgil, andre, ferenc, GeneralAnitilles, indeyets, jeremiah, daniel, jeremiah, ferenc, feenc, GeneralAntilles, GeneralAnitilles, qole, qole)15:38
qolenot mine :(15:38
sopiferenc: none from my side.15:38
andre__nope, not at all :-(15:38
jeremiahKinda.15:38
jeremiahI just want some feedback on how to finish the task that is an 90%15:39
jeremiahThat is why it is at 90%15:39
Jaffajeremiah: The ITP workflow got to 90%... yeah.15:39
* JimiDini = indeyets15:39
JaffaWhat *is* ITP?15:39
JimiDininope. app-karma is still not ready15:39
jeremiahITP == Intend to Package15:39
jeremiahThis allows people to pick up some software and package it for maemo15:40
jeremiahOften this is a good way to get involved if you don't write software15:40
sopiJeremiah: mark it done, and tell people to file bug reports if they have a problem.15:40
Jaffajeremiah: Ah, right. I suppose the outstanding bit is deciding on workflow, a beta test period and then production?15:40
jeremiahsopi: Well, I wanted some feedback from the council.15:40
jeremiahThat is: Should I only allow an ITP to be filed if we have a valid email or garage user id?15:41
sopijeremiah: ok, i see. maybe you can mark it done after this meeting then.15:41
jeremiah:)15:41
Jaffajeremiah: Sounds like it might need to be discussed on maemo-developers; so the last 10% can be a task for this next (shorter) sprint.15:41
Jaffa*** BTW, apologies for the tardiness of this meeting.15:42
jeremiahSounds good. That works well for me. :)15:42
* Jaffa would like to address the "must" tasks which didn't get done. Probably for good reasons, but the idea of a must task only taking up 60% of the available project time is that it's the SHOULD & COULDs which get pushed out when unexpected things happen.15:43
Jaffasopi: 9.04-02 "Git for Garage" is at 90% concludes "no time".15:44
sopiyes, that's correct.15:44
sopiit is a cosmetic work, the name of the task is misleading.15:44
X-FadeThat task needs to spit up.15:45
X-FadeSo one part can be closed.15:45
X-FadeAnd one part can be set at 0%.15:45
X-FadeOr whatever status it really is at.15:45
JaffaAgreed. It was already split up into "garage integration" and "UI", but that sounds like it wasn't discrete enough.15:45
sopigit for garage has / had these activities:15:46
sopi1. enable git on got.maemo.org15:46
sopi2. setup gitweb15:46
sopi3. skin gitweb15:46
sopi4. allow garage projects to pick git as SCM15:46
sopi5. offer svn->git migration via garage UI15:47
sopi1, 2, 4 are done.15:47
sopi3: 0%15:47
JaffaAnd 5 is 9.05-01?15:48
sopi5: 99%  see 9.05-01 15:48
sopiyes.15:48
sopii just did not want to update the task table before this review meeting.15:48
JaffaOK, so we should have 3 in the backlog (and perhaps pushed in this sprint)15:48
qoleI see why you've left the cosmetic stuff to the end.15:48
Jaffasopi: that's good - the group is supposed to have ownership of the plan, so changing the agreed plan without consensus would be bad ;-)15:49
sopiJaffa: yes, i thought so too.15:49
Jaffasopi: What's needed to get 5 from 99% to 100%? Is it just time, or do you need assistance/15:50
sopiI need time, a few days at most.15:50
sopiand then I will contact those projects who helped me so far.15:51
JaffaOK, so 3 & 5 go into the backlog; possibly for this 2-week sprint.15:51
Jaffasopi: thanks15:51
sopiJaffa: no probs, you are welcome.15:51
Jaffaandre__: GeneralAntilles isn't here, but he had a must in 9.04-05: newstyle for Bugzilla. Status at 80%: "sent to andre, wiating on progress there"15:52
JaffaAnything to add? (Again, perhaps develop & deploy should've been two separate tasks)15:52
andre__Jaffa, i am right now on it15:52
andre__hacking testzilla...15:52
X-Fadeandre__: breaking testzilla ;)15:52
andre__yeah. X-Fade is more correct :-P15:52
Jaffaandre__: OK, cool. Does it look close enough to be considered as just bugs/business-as-usual; and should be closed?15:53
andre__don't close yet15:53
andre__can't say yet, must test a bit more15:54
X-Fadedeploy skin: this 2 week sprint?15:54
X-FadeThen you can close GA's task?15:54
* Jaffa nods15:54
andre__yupp15:54
JaffaOK cool.15:54
Jaffadaniel here? 9.04-09 "Setup SSO testing environment" - "must" - no updates since the task was added15:55
-!- etrunko [n=edulima@200.184.118.130] has joined #maemo-meeting15:55
X-FadeDaniel is in south america atm.15:55
X-Fade3 week holiday.15:55
JaffaOK. No more info there then.15:55
JimiDiniI believe daniel posted progress-report in some other place..15:56
Jaffajeremiah: 9.04-10 test build of diablo on fremantle. 75%? "Still some packages needed to build"15:56
JaffaJimiDini: There was an update on tmo a while ago, but I'm not going hunting for it.15:57
jeremiahYeah. This too needs to be broken down into more discreet elements since there is so much involved.15:57
jeremiahBut a lot of the packages have been built, more remain.15:57
JaffaCool.15:58
jeremiahWhen one hits a stopper, say a missing lib, one has to track that down, etc.15:58
jeremiahWhat do you think the best way to handle this is?15:58
jeremiahJust keep forging ahead?15:58
jeremiahI think it can get to 100% at the end of this sprint.15:58
JaffaAt work, we've had something like "must do $X packages", "should do $X*2 packages", "could do $X*3 packages"15:59
jeremiahOr should we atomize it and attack it with a finer grain.15:59
jeremiahJaffa: Ah - that is actually a good idea.15:59
jeremiahI'll follow that approach.15:59
jeremiahHow about I say that 20 more diablo packages will be built and their depends and build problems tracked down15:59
jeremiahas a 'MUST'?15:59
Jaffajeremiah: Cool. Anything else, or is all the infrastructure in place, and it's just a case of plodding through them now?16:00
jeremiahJaffa: If I had too, I could send them all to the autobuilder16:00
X-FadeBonus points for this tedious task btw :)16:00
jeremiahBut that is messy and rude to the others who want to build16:00
JaffaHow many are remaining? And how many have been done? (So we can get an idea of how big a job is "20" is ;-))16:00
jeremiahX-Fade: Well thank you for your help!16:00
jeremiahYou did all the libs!16:00
jeremiahthat was huge.16:00
jeremiahJaffa: We have lots of packages - 2,000 or so (help me out here X-Fade) :)16:01
jeremiahBut lots are already built16:01
X-FadeI'd guess there are about 200 useful packages to be added still.16:01
jeremiahSo maybe 20 is too low.16:01
jeremiahShall I say 50?16:02
JaffaUp to you; you're the one committing to it ;-)16:02
X-FadeBut we'd need to so some sorting/unique to determine the total.16:02
qolehm, keep 20 as must, if you want 50 put it as should?16:02
jeremiahqole: Yeah, I think something like that might be good.16:02
jeremiahI can commit to 25 - which includes contacting Nokia if there are build issues in the builder, contacting devs if they are missing libs or have perms wrong, etc.16:03
qoleremember this is a short sprint, too.16:03
Jaffaqole: good point16:03
jeremiahSometimes building one package means building all its depends too so . . .16:03
jeremiah20!16:04
Jaffajeremiah: excellent. And 40 as a should?16:04
jeremiahRight.16:04
jeremiah:)16:04
jeremiahBut, one caveat.16:04
jeremiahThe 'reduce number of private repos' backlog task is still important16:04
jeremiahPeople feel that this is still a problem16:05
jeremiahAnd it is only going to get worse16:05
jeremiahAnd we can do something about it 16:05
jeremiahI feel more ambivalent.16:05
jeremiahBut maybe I should save all this for when we discuss next sprint?16:05
* Jaffa nods.16:05
JaffaOnly other unfinished must is 9.05-05 which is GeneralAntille's newstyle for mxr. Explanation seems obvious "VCS issues and no time to resolve with work". I'll take an action to ask if there's anything anyone can do to help with the VCS issues.16:06
JaffaAnybody anything else to add on the last sprint?16:07
Jaffa(35 minutes rather than 25; but not bad)16:07
JimiDiniwell.. would be good to know what kind of issues are those? ;)16:07
JaffaJimiDini: Indeed, but he's not here :-(16:07
JaffaHence my action :)16:07
Jaffa+++ #2 Discussion on sprint process16:08
JaffaI've changed this from "agreement" as we've had some good stuff come out on -community about it; and don't think we'll do it justice online here in the time available.16:08
JaffaI'll also note, for the record, that I've certainly appreciated the level of info available going into the sprint meeting with the wiki updates and mailing list posts.16:09
JaffaAlthough, it's the wiki I've referred to during the meeting; but I think the mailing list posts have acted as a good reminder16:09
* jeremiah concurs16:09
* qole does too16:10
-!- VDVsx [n=valerio@bl5-137-103.dsl.telepac.pt] has quit ["fui :P"]16:13
JaffaBut I think we've missed a trick in keeping track of MUSTs (in particular) slipping16:13
JaffaAnd perhaps the more visibility on the status reporting/making it easier would've helped identify blockages earlier?16:14
X-FadeSo it might be good to either get automatic warnings, or somebody to follow up on those at set intervals during the sprint?16:14
jeremiahWhile I agree, I think part of it can be attributed to the newness of the adoption of the Moscow plan.16:14
jeremiahMUSTs are bit a harder to calculate accurately.16:15
Jaffajeremiah: a good point16:15
qole(I think you should leave my little coulds out of the next sprint, they're kinda cluttering the page...)16:15
jeremiahHopefully we'll get better at this and therefor better at managing expectations.16:15
Jaffajeremiah: indeed; already we can see we're better at splitting things up into discrete things at different levels.16:16
jeremiahJaffa: Yeah, that has been my problem. I haven't done that well.16:16
JaffaI'll update my proposal on -community: status reports still on the wiki, but (personalised) reminders every week to anyone who has a task not at 100% (bit of screenscraping or manual secretarial work)16:17
X-Fadescrum master? :)16:17
JaffaHell, it's probably even possible to screenscrape the "activity log" to an RSS feed. I admit I'm useless at checking it16:17
JaffaX-Fade: :)16:17
JaffaANything else on process? Have we got a consensus on why we want it?16:20
Jaffa(I really liked that 'managing expectations' article I found; going to use it at work ;-))16:20
jeremiahI think, to some degree, consensus is going to be hard to come by.16:21
jeremiahBut it appears we have a working one at the moment.16:22
JaffaPragmatism always wins over idealism in these things :)16:22
jeremiahIndeed.16:22
JaffaTry to minimise the overhead of process so that it's not resented too much, but is still actually useful to some person for some task.16:22
X-FadeAnd we need to see if we can still stay ..... agile ;)16:22
bergiewe could also use Qaiku or Twitter16:23
jeremiahYeah, agile seems well suited for software development, less good for system administration and operating system development.16:23
jeremiahbergie: Yeah, I might experiment with Qaiku16:23
JaffaIf nothing else, good progress reports ahead of the meeting reduces the length of a meeting in the middle of a working day16:24
qolejeremiah: 20 minutes ago you mentioned that reducing external repos is still an important task. I think I'd like to discuss this publicly somewhere, I don't think there's a clear consensus about it...16:24
sopibergie: yes, a qaiku channel for each "major" task. not a bad idea. i would actually prefer that over the wiki.16:24
Jaffabergie: hash tag or something per task ID - easy updates16:24
bergieor maybe even just a thread per task16:24
sopibergie: i wonder if mediawiki could integrate snippets from a channel.16:24
jeremiahqole: Yeah, that sounds good. Should we do that on Talk.m.o?16:24
bergieand we could use even "qaikudata" for additional metadata, see http://www.qaiku.com/channels/show/Qaiku-api/view/1de5bfa5c5c83a65bfa11dea402d97edb6074ee74ee/16:25
jeremiahYeah, a #maemo.task tag or something16:25
bergiesopi: I think that would be a simple MediaWiki extension (or use an RSS importer extension that probably exists)16:25
qolejeremiah: tmo sounds like a good place for it... 16:25
jeremiah:)16:26
sopiwhat if we try both (qaiku and tmo) approach in this short sprint?16:27
jeremiahI'm all for it.16:28
sopiok, it would be double "reporting" effort from all, but we could then easier decide what to do in July.16:28
X-Fadesopi: I think they were talking about discussing the repositories task ;)16:28
qolemy time is running out... 16:28
qolejust leave me off the next sprint for now...16:29
jeremiahqole: If you have to go you and I can catch up in the t.m.o thread. 16:29
Jaffaqgil suggested the tmo approach a while ago on -community, and the only feedback I got on it as an idea was "hmm, now we're updating at least three places: wiki, task page/Bugzilla, tmo"16:31
JaffaI suggest we take it to the mailing list. The wiki page is master; and I'll send some reminders out via email during the sprint. The "activity log" is one of three suggested approaches for logging activity; the others being tmo & qaiku.16:33
X-FadeFor what I do, I think the wiki is just fine. But if you want to change that, no problem.16:33
Jaffas/the wiki page/the tasks table on the wiki page/16:33
Jaffa+++ 3) June mini-sprint tasks16:34
JaffaSuggested so far:16:34
Jaffadneary: MUST Set up environment for library.maemo.org API tasks; SHOULD Modify library.gnome.org to use .debs of docs rather than building .tar.gzs; COULD Proof-read HIG; ensure updating library happens on releases16:35
Jaffaqgil: MUST texts for maemo.nokia.com; SHOULD Maemo Summit rough budget; COULD Plan for the OMAP2 acceleration drivers16:35
Jaffasopi: MUST Gitweb skin; SHOULD Conversion UI16:36
Jaffajeremiah: MUST 20 more packages from diablo -> fremantle; SHOULD 40 more packages16:36
Jaffaandre: ??? Complete bugzilla newstyle16:36
X-FadeMUST: Work on package promotion/repository management/community qa interface. SHOULD and COULD too. 16:36
X-FadeAnd MUST finish that thing for the next sprint.16:37
andre__Jaffa: we had that one already a few minutes ago. right now working on it :)16:37
andre__yepp. i agree. MUST.16:37
Jaffaandre__: I'm summarising in this section what we said earlier so it's easier for me to do the table ;-)16:37
JaffaX-Fade: Sorry, the same task is SHOULD & COULD?16:37
andre__okay. i should up and should not multitask in that case :-P16:37
andre__er shut16:37
X-FadeBecause it is more than 2 weeks.16:37
X-FadeJaffa: Yeah, fremantle is coming and we really need to get this done.16:38
JaffaX-Fade: OK. Bit of a process breakage, but what you're saying is that this is priority #1 and it's a *proper* MUST16:38
X-FadeSo 100% priority for me.16:38
JaffaAs in, late nights if it's not done ;-)16:38
X-FadeJaffa: I already started on it 100% this week..16:39
X-FadeQuite an amount of code already..16:39
JaffaAnyone want to carry over their tasks from the last sprint? Probably things like patchsets (andre), karma for apps (JimiDini) need splitting up?16:40
andre__yes, i want16:40
JaffaOh, I also missed jeremiah's COULD(?) Complete ITP process16:40
JimiDiniJaffa: well yes. we can split up app-karma into 1) getting stats (done) 2) implementing karma-formula (not done)16:41
jeremiahYeah, that sounds good. I suspect that will be done by the next sprint without problem.16:42
JaffaJimiDini: Is there a decision on what the karma-formula *is*?16:42
Jaffajeremiah: cool16:42
JaffaJimiDini: If not, that sounds like a different task (at a higher priority than implementing it ;-))16:42
JimiDiniJaffa: not yet. there's my proposal and then we need to test it and fine-tune until we like it16:42
JaffaKarma for apps has been kicking around for a couple of sprints, so it suggests it needs restructuring slightly.16:43
X-FadeJaffa: But now there was actual code progress on it.16:43
X-FadeJaffa: As the gathering of stats for this karma was the major part.16:43
JimiDini"implementation" itself would be trivial, and fine-tuning formula would take some time16:43
JaffaX-Fade: ok16:43
JaffaSo is it still one task? Is it in the sprint? At what priority (given the 2 weeks available)?16:44
JimiDiniX-Fade: did the cron start working properly? (app-karma stats)16:45
X-FadeJimiDini: No.16:45
JimiDiniok...16:45
JimiDiniJaffa: let's try it with "should" marker16:46
JaffaJimiDini: OK16:47
JaffaAnyone else anything they want to push?16:47
qoleok going now... as I said, leave me off the next sprint16:47
-!- qole [n=qole@d207-6-250-238.bchsia.telus.net] has quit ["Leaving"]16:47
Jaffaqole: thanks for your input16:47
Stskeepsfrom mer: http://wiki.maemo.org/Mer/Proposals/Vendor_Hardware_Repositories16:48
Stskeepsbasically implementing the flowchart16:48
Stskeepsin order to push being able to properly support nokia hw - as per long discussions as well as at cph meet16:49
JaffaStskeeps: is it a task for this 2-week sprint to liaise with the appropriate people (e.g. X-Fade) on the maemo.org specifics of it? So that a series of concrete tasks can be put into the next sprint?16:49
Stskeepsyes, i think so16:50
X-FadeJaffa: We've discussed this at the Danish weekend.16:51
X-FadeAnd got preliminary OKs, but now it has to be done ;)16:51
JaffaIndeed, but that flowchart looks a little big to be done in a single task when it has interdependencies between people16:51
X-FadeYes, there are multiple parties in this.16:53
JaffaHence the suggestion of a task to identify all the sub-tasks :)16:53
X-FadeWell, I can't commit on carrying it. But will help where I can.16:54
Stskeepsit's mostly a matter of web implementation - what needs to work is basically the serial/MAC check -> EULA check -> show a unique token and a list of downloads you now can do16:54
Stskeeps*nod*16:54
X-FadeStskeeps: That code is available.16:54
JaffaStskeeps: are you going to own it?16:54
Stskeepsi can commit to working with people to get this divided up into bite size chunks i guess16:54
StskeepsX-Fade: k - then that's a matter of adapting it to mer in general then. anything open (excepting the wlan mac dbs)16:55
Stskeeps?16:55
Stskeepsbecause then i can help modifying it to fit our purposes 16:55
X-FadeStskeeps: Doesn't have to be open, as it will run on Nokia's part?16:55
X-FadeStskeeps: But anyway, the code is only a few lines.16:55
X-FadeStskeeps: So I can get that setup for you.16:56
StskeepsX-Fade: yeah - that's a discussion of who delegates the tokens and so on, we just need to get a demo up and running so we can show to nokia this is how it would be handled :)16:56
Stskeepsk16:56
X-FadeStskeeps: When Marcell is back, we can get this in place.16:56
Stskeeps*nod*16:56
JaffaCool.16:56
JaffaAnything else from anyone?16:56
X-FadeStskeeps: But that leaves the acual packages of course ;)16:56
Jaffa+++ 4) AOB16:57
JaffaAnything? Nothing from me.16:57
JaffaStill a long meeting, but feels a bit more concrete than previous ones.16:57
JaffaSo thank you, all.16:57
StskeepsX-Fade: yeah, we'll deal with that over the summer i guess :)16:57
jeremiahCheers!16:58
sopithank you. bye!16:59
JaffaThanks all.16:59
JaffaHas someone a log they can send me, asap?16:59
JaffaIf not, I'll do a copy & paste marathon from irssi16:59
X-FadeJaffa: I'll upload it.17:00
X-FadeIn the regular place.17:00
JaffaX-Fade: ta muchly17:00
JaffaThanks all!17:00

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!