Confirmed users
525
edits
Firefox OS/Comms/Dialer/Sprint/v2.1-S5: Difference between revisions
Jump to navigation
Jump to search
m
Firefox OS/Comms/Dialer/Sprint/v2.1-S5 (view source)
Revision as of 04:27, 16 September 2014
, 16 September 2014→Retrospective
(Created page with "=Bugs= <onlyinclude> ====Status==== File:Dialer_v2.1-S5_burndown_chart.png * 0,0,0,0,0,0,0,0,0,0 ====Bugs Taken in Planning==== <bugzilla> { "component": "Gaia::Dialer...") |
m (→Retrospective) |
||
| Line 78: | Line 78: | ||
==Things we did well== | ==Things we did well== | ||
* <drs> This was a nice and relaxed sprint, and we didn't get many blockers. | |||
* <davidg> Managed to get bugs on time | |||
==Things we could do better== | ==Things we could do better== | ||
* <drs> Dialer has ~550 bugs open at any given time: https://bugzilla.mozilla.org/buglist.cgi?component=Gaia%3A%3ADialer&list_id=11111500&product=Firefox%20OS&query_format=advanced&resolution=---&order=bug_id&limit=0 | |||
** <drs> Thoughts on doing a bug bash? I know it's not fun, but a lot of these bugs are ancient and it will probably be as simple as resolving them or duping them. | |||
** <thills> I would like to do it. Would be good to set aside a time where we can all work on it at the same time. | |||
* <drs> We didn't do any demos this last sprint. I'm wondering if anyone sees any value in them. We asked this last time but maybe the answer has changed. If we decide to get back to doing them, I will really start pushing it this sprint for anything demoable. | |||
** <thills> do we have a blog to go along with this? I'm not sure it's for us directly, but others outside the team. | |||
** <drs> Anthony was going to, but I don't know if we got enough demos, or if he had time. | |||
* <davidg> A bug that was late-l10n was just landed at the very last moment, but it was ready much before. | |||
** <drs> Suggestions? | |||
** <davidg> When the bug get blocked by a deadlock discussion, just try to unlock it. Pretty much what we did at the end but earlier. | |||
** <drs> Yeah, sometimes it's hard to know the state of everything. I noticed that this was blocked a bit later because it didn't seem blocked on the surface a few days before. It would help if this was mentioned in daily meetings and notes. | |||
** <davidg> I should probably tried to propose a solution instead of just watch them argue :) | |||
** <drs> It's ok, it's hard to know what to do all the time. Just mention it in the daily. Either way it was ok, it would have just been nice to be unblocked sooner. | |||
==Action items== | ==Action items== | ||
* <drs> We have not been doing enough to get contributors engaged. I've talked with Francisco who actively sets himself as a mentor on many bugs and provides and plan and support for contributors. I'm going to begin doing this and I suggest that others do the same as well. | |||
** <gsvelto> I've set myself up as a mentor on a number of bugs but none dialer-related IIRC. Most of those are code cleanup & factoring out shared pieces as those are easy for new contributors and not high priority. We could start by filing some of those as there's many parts of the dialer that could use some love. Additionally if a bug needs an easy follow up it's always best to set it as a mentored one (e.g. remove a workaround, polish some unit-tests, etc...). | |||
** <davidg> Maybe we should invite Jorge and Francisco to join dailys | |||
*** <drs> I did I think. I should double-check that. | |||
* <drs> Do a bug bash. | |||
** <drs> Have a 2.2 phone and 2.0 or 2.1 ready to test bugs. | |||
* <drs> Really push for demos and do a blog post. | |||
* <drs> Continue doing office hours. | |||
=Demos= | =Demos= | ||