Haven’t blogged for a while on MeeGo related stuff, probably because GNOME was way more crucial in the last weeks.
- Wrote a proposal for allowing 3rd party products to be listed in bugs.meego.com – see this bug report for the discussion. Still need to get into the loop with the rest of the folks doing the planning on this, like repositories etc.
- Worked on a document to make the Downstream-Upstream relation a bit easier to understand for MeeGo developers that might be new to working in open source / free software environments (and the corresponding expectations on collaboration).
- The meego-qa mailing list, probably not the only place for this observation: It sometimes feels like there is not much feedback on issues that get brought up and should be discussed and that people work in their chambers without any note to the public or early codedrop of what they are doing (like a one sentence email to drop on a public mailing list that might take you less than a minute but avoids duplicated work and opens up contribution opportunities). Sure, sometimes I feel like it’s getting better; still printing this and taping it onto your computer screen to learn it by heart might help you.
- Looks like our talk proposals (Bug’s Life, presentation of the bug’s life cycle and BoF Improving MeeGo Error Management Process and Practices) have been accepted for the MeeGo Conference which will take place in one month. Plus looking forward to yet another talk by the MeeGo EM crew.
And on an unrelated note: The MeeGo QA Dashboard beta looks pretty neat.
