Confirmed users
525
edits
Gaia/Dialer/Restructure: Difference between revisions
Jump to navigation
Jump to search
→Etienne
| Line 146: | Line 146: | ||
===Etienne=== | ===Etienne=== | ||
* General | |||
** Agrees there's a problem within dialer | |||
** Optimistic about these plans in general and that people are looking into ways to restructure | |||
* Daily meetings | |||
** Ok with coming to daily meetings, not super enthusiastic though | |||
** Would like for it to be over IRC | |||
** Worried when he sees people saying standups help them get unblocked | |||
*** Thinks people should be using needinfos/IRC instead | |||
*** Likes having time to think before responding | |||
*** (drs/note) I mentioned that we'll be getting more people soon and not everyone is as familiar with the dialer as him, and he agreed that there's value for us there | |||
* Vision for his role | |||
** Work mostly on blockers | |||
** Likes working on stuff he actually uses | |||
** Feels a bit like dialer is mostly done | |||
** Always worked on other stuff, didn't just suddenly decide to move out of dialer | |||
** There was an idea within the comms team of people rotating around inside the team but it never happened, he liked this idea | |||
** Was owner once most of the features were already done, module ownership came relatively late | |||
* Estimations (bugs) | |||
** Bugs take constant time for him (cool!) so he doesn't think they're worth estimating | |||
*** Only takes bugs he can repro locally | |||
*** debug/console.log a bit | |||
*** make a dirty fix, make a test, make a clean fix | |||
* Estimations (features) | |||
** More valuable to do estimations here than for bugs | |||
** We don’t have a lot of practice | |||
** No strong opinion | |||
** Doesn't believe that feature work can be constant time | |||
** Would support it if we did it | |||
* Wiki articles | |||
** management likes having this | |||
** Not sure how he would use them | |||
** Workflow is very Bugzilla-driven | |||
** Would start contributing to dialer docs, has wanted to for a while | |||
* Sprint planning | |||
** Last one went pretty well | |||
** Not sure about sprints themselves, planned items are not the majority of his work | |||
** Likes treating blockers differently, likes the way contacts team is run | |||
* Planning | |||
** Anthony and Etienne talk about the CSS and how to organize it | |||
** Not much planning on other things | |||
** The last year, biggest change was DSDS, rushed last minute | |||
** No strong opinion on this stuff yet (such as anticipating changes) | |||
** Now is first time we got the opportunity to fix stuff properly | |||
* Long term project ideas | |||
** Integration testing | |||
*** If we get better integration testing, refactors will be easier | |||
**** ex: if we had tools, we could cover all of CDMA fairly quickly | |||
*** Mulet (b2g desktop on firefox) inject chrome scripts to mock the telephony api | |||
**** Implement RIL daemon in JS | |||
**** Been discouraged on doing this because emulator coming (but waiting a while) | |||
**** Compromise: stub the ril.js | |||
* People | |||
** No opinion | |||
** The way the contacts team is working sounds good | |||
* UX relations | |||
** Getting better | |||
** Doesn't need to contact UX a lot for his work | |||
** Progress-based meetings would be good instead of scheduled | |||
*** In system, they have a meeting with UX designer rob where they go through everything they need to talk about | |||
**** Once every 3 weeks during feature dev, once every week during bug fixing | |||
* Comms meeting | |||
** Getting worse | |||
** Wasting time | |||
** Wants to kill it | |||
===Anthony=== | ===Anthony=== | ||