Confirmed users
820
edits
Gaia/SMS/Scrum/2.2S13: Difference between revisions
What was bad in the last sprint
(→Demos) |
(What was bad in the last sprint) |
||
| Line 688: | Line 688: | ||
*** Will try to create bug with small but clear action item, that might be easier to see the progress | *** Will try to create bug with small but clear action item, that might be easier to see the progress | ||
*** I think that was the goal of my defining use cases yesterday -- and we can rediscuss about this during planning later. | *** I think that was the goal of my defining use cases yesterday -- and we can rediscuss about this during planning later. | ||
* One more related thing - I found etherpad isn't very good for "discussions distributed in time", I mean I don't know about updates right away | |||
** yeah I agree -- I think you prefer google docs ? | |||
** Yeah, but I don't know much alternatives - we can try anything else if you guys have in mind? | |||
** wondering if github could offer a platform for this -- we get notifications with comments in PR. | |||
** Will work too, we can have kind of README/Spec of service for example that we discuss. | |||
** yep for example, and we could merge the changes | |||
** Yeah sounds good, we should try - if we have it committed it would be great to have architecture/important things docs in tree. | |||
** should this be in gaia or in a separate repository ? | |||
** Actually if we talk about service architecture I even can imagine sms/services/activity_or_conversation/README.md for example.. | |||
** Do we need to have separate doc for services? | |||
** No preference, maybe one for all at first | |||
** No prefer +1, and having a doc should be a good start | |||
** So we can file a bug about landing a README (or other) with the spec, and this would be one bug to estimate later. Does this feel good? | |||
** "bug to estimate later." - you mean "create spec" bug that we'll estimate later today during planning? If so - then yep sounds good. This bug will block bug with actual service implementation. Yep estimate later in the meeting ;) Okay :) | |||
* Gecko regressions in graphics broke my usual workflow (flash the most recent gecko every day) | * Gecko regressions in graphics broke my usual workflow (flash the most recent gecko every day) | ||
** I stopped doing that ;) Now I ask somebody who flashes everyday (usually Alexandre Lissy) to know if I can flash ;) | ** I stopped doing that ;) Now I ask somebody who flashes everyday (usually Alexandre Lissy) to know if I can flash ;) | ||
** Ha-ha, good way of "safe" updates! | ** Ha-ha, good way of "safe" updates! | ||
* We didn't plan well for the services part that might need overall redesign our structure | * We didn't plan well for the services part that might need overall redesign our structure | ||
=== Any questions === | === Any questions === | ||