MozillaWiki

Firefox OS/Comms/Dialer/Restructure/Proposal: Difference between revisions

Page Discussion

Firefox OS/Comms/Dialer/Restructure/Proposal (view source)

Revision as of 13:26, 1 February 2015

966 bytes added ,  1 February 2015
m
Lakrits moved page FirefoxOS/Comms/Dialer/Restructure/Proposal to Firefox OS/Comms/Dialer/Restructure/Proposal: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's easier to find a page if the spelling o...
(Initial page)
m (Lakrits moved page FirefoxOS/Comms/Dialer/Restructure/Proposal to Firefox OS/Comms/Dialer/Restructure/Proposal: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's easier to find a page if the spelling o...)
 
(19 intermediate revisions by one other user not shown)
Line 72: Line 72:


==Dialer Team==
==Dialer Team==
I don't believe that we should necessarily take everything that the other teams are doing and use them verbatim. Our team isn't structure the same way and has somewhat different people. In particular, I think it would be helpful to define our identity now and my vision for what it will be.
I don't believe that we should necessarily take everything that the other teams are doing and use them verbatim. Our team isn't structured the same way (such as different timezones) and has somewhat different people. In particular, I think it would be helpful to define our identity now and my vision for what it will be.


===Our Identity===
===Our Identity===
Line 84: Line 84:
I see a team that is well organized while not hoisting too much burden onto any team members, so they're able to get work done but the team can scale to include more developers. We don't know how many people will be joining from partners, so we should prepare for many.
I see a team that is well organized while not hoisting too much burden onto any team members, so they're able to get work done but the team can scale to include more developers. We don't know how many people will be joining from partners, so we should prepare for many.


I like our background in UX, and I believe that one of our greatest problems is that, due to our lack of organization, we're not able to make use of these skills. We aren't able to push forward long-term projects which would use this part of us. For this reason, I think that we need to free up time to work on these long-term projects.  
I like our background in UX, and I believe that one of our greatest problems is that, due to our lack of organization, we're not able to make use of these skills. We aren't able to push forward long-term projects which would use this part of us. For this reason, I think that we need to free up time to work on these long-term projects.


==Action Items==
==Action Items==
Line 97: Line 97:


===Phases===
===Phases===
✔ = done, ? = in progress, - = not started<br>
<onlyinclude>
We're currently in [[FirefoxOS/Comms/Dialer/Sprint/1|Sprint 1]], though we only started documenting it half-way through, didn't do estimations, etc.
✔ = done, ? = in progress, - = not started, x = failed/punted<br>


====Phase 1 (now until sprint 2)====
====Phase 1 (sprint v2.0-S5 / aka "1" until sprint v2.0-S6)====
* ✔ Make and use a new #fxos-dialer channel on IRC.
* ✔ Make and use a new #fxos-dialer channel on IRC.
* ✔ Start having daily meetings. I think we can do this over IRC for a start, but be flexible with it.
* ✔ Start having daily meetings. I think we can do this over IRC for a start, but be flexible with it.
* ✔ Improve cross-team communication and sharing of ideas.
* ✔ Improve cross-team communication and sharing of ideas.
** I've spoken with Francisco who is very interested in sharing ideas and talking about ways to organize ourselves, and I will be talking with Julien soon. I have spoken with the other messaging team members in the interim.
** I've spoken with Francisco who is very interested in sharing ideas and talking about ways to organize ourselves, and I will be talking with Julien soon. I have spoken with the other messaging team members in the interim.
*? Track planning, progress, and discussions on wiki articles.
* ✔ Get UX and VD specs all in one place.
* ✔ Track planning, progress, and discussions on wiki articles.
** See https://wiki.mozilla.org/FirefoxOS/Comms/Dialer/Sprint/1
** See https://wiki.mozilla.org/FirefoxOS/Comms/Dialer/Sprint/1
*? Clean up general docs on dialer.
* ✔ Clean up general docs on dialer.
** See https://wiki.mozilla.org/FirefoxOS/Comms/Dialer
** See https://wiki.mozilla.org/FirefoxOS/Comms/Dialer
*? Start estimating during sprint planning.
* ✔ Catalog long-term projects that we can work on, encourage brainstorming and feedback.
*? Catalog long-term projects that we can work on, encourage brainstorming and feedback.
** Since we're still in damage-control mode, I don't believe that it's a good idea to put serious thought into implementation of these yet. We have to get ourselves under control, and then start on these when we can.
** Since we're still in damage-control mode, I don't believe that it's a good idea to put serious thought into implementation of these yet. We have to get ourselves under control, and then start on these when we can.
*? Get UX/VD specs all in one place.
* ✔ Kill the comms meeting.
** I have emailed Carrie and Vicky and will discuss ways we can do this if they've stopped using box.com.
* - Kill the comms meeting.
** This isn't really in our scope but it's partly our fault that it still happens.
** This isn't really in our scope but it's partly our fault that it still happens.
** This isn't done but is effectively out of our hands.
* ✔ Get the UX and VD people on Vidyo/Skype and IRC.
** I've contacted Vicky and she's looking into how to get on IRC with the Telefonica firewall in place (she's going to ask Arnau).


====Phase 2 (sprint 2 to sprint 3)====
====Phase 2 (sprint v2.0-S6 to sprint v2.1-S1)====
*? Begin cross-collaboration and sharing of ideas with other teams. Ask them for feedback and help where necessary.
* ✔ Switch to the people rotation system that the contacts team uses. (see "Differences Between Teams" / "Contacts" / "People")
* - Decide on which long-term projects we will be prioritizing.
* ✔ Begin setting aside time for long-term projects.
* - Begin actual planning of long-term projects, discussing architecture, designs, etc.
* ✔ Gather feedback from the changes previously implemented, iterate where necessary.
* ✔ Begin cross-collaboration and sharing of ideas with other teams. Ask them for feedback and help where necessary.
* ✔ Decide on which long-term projects we will be prioritizing.
* ✔ Begin actual planning of long-term projects, discussing architecture, designs, etc.
** We will be careful to include every team member in these discussions.
** We will be careful to include every team member in these discussions.
* - Switch to the people rotation system that the contacts team uses. (see "Differences Between Teams" / "Contacts" / "People")
* ✔ Establish better relations with UX and VD, consider setting up progress-based meetings for when we need to discuss many things with them.
* - Begin setting aside time for long-term projects.
** This is sort of covered by the weekly comms meeting, but there might still be work here to be done.
* - Establish better relations with UX and VD, consider setting up progress-based meetings for when we need to discuss many things with them.
** Anthony has been doing a great job talking with UX and VD and I don't think there's a problem here.
** Push to get them on Vidyo/Skype and IRC as well.
* x Continue to improve technical documentation.
* - Gather feedback from the changes previously implemented, iterate where necessary.
* x Start estimating during sprint planning.
* - Continue to improve technical documentation.
** We decided to delay this until next sprint due to lack of features to estimate.


====Phase 3 (sprint 3 onward)====
====Phase 3 (sprint v2.1-S1 onward)====
* - Actually set time aside and work on long-term projects.
*✔ Actually set time aside and work on long-term projects.
* - Prepare for new team members from partners.
*✔ Prepare for new team members from partners.
** This is a very loose objective. I think we should start thinking about this here, but I don't have any specifics.
** This is a very loose objective. I think we should start thinking about this here, but I don't have any specifics.
** We have absorbed a couple of new team members fairly well, been able to deal with Etienne participating more on other teams, and we have more infrastructure in place to support more new people. I think this is resolved.
*✔ Start estimating during sprint planning.
*✔ Start doing demos of new features/big fixes.
*✔ Continue to improve technical documentation.
** We decided to not commit seriously to this and instead improve documentation as we go along. Reviewers are expected to request inline docs/comments for new commits and wiki articles for more complicated things.
</onlyinclude>
Lakrits
3,860

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/992973...1052003"