+dev-b2g to a broader audience

Great idea!

I’m adding Kevin Hu to facilitate this team work on the EPM side so that the 
"polish bugs” can have better visibility.

--
James Ho
Senior Director of Mobile Devices
Mozilla Corporation

On Dec 12, 2014, at 2:25 AM, Christopher Lord <cl...@mozilla.com> wrote:

> Hello everyone,
> 
> This is a long mail, so I'm going to stick headers to aid anyone that just 
> wants to skim it.
> 
> 
> Pre-amble
> 
> Something I think most would agree with, especially those who are 
> dog-fooding, is that FirefoxOS lacks 'polish'. It's pretty hard to define 
> exactly, but it's what makes a product feel satisfying to use. That ethereal 
> quality that makes something more than just the sum of its parts.
> 
> I'd like to think that polish really comes down to attention to detail. All 
> the small things that you might take for granted, but when they aren't there, 
> you subconsciously (or consciously) miss them. With this in mind, I've 
> proposed that we form a team to tackle polish-related bugs. This is not to 
> encourage that features land unpolished, but to make sure that there are 
> people actively taking care of this so that issues don't fall through the 
> cracks and get de-prioritised as deadlines loom.
> 
> 
> What is Polish Team?
> 
> We have performance teams at Mozilla; in my eyes, this is a logical extension 
> of that. A multi-functional team with the remit of improving the feel of 
> polish of FirefoxOS.
> 
> Polish Team is a secondary team for people who want to help make FirefoxOS a 
> more polished product. That is, a team you are in, in addition to your 
> regular team. There will be (at least) a monthly meeting to triage issues, 
> and weekly update meetings to keep track of work. If you have polish bugs 
> assigned to you, two days of your week should be dedicated to working for 
> polish team. Polish team has the backing of managers and UX, so polish bugs 
> will be on an even keel with other non-polish bugs. *This is not extra work*.
> 
> 2.2 has had various features de-scoped, making this the perfect time to focus 
> on producing a really accomplished release. Polish team's primary objective 
> will be to markedly improve the feeling of polish in the upcoming 2.2 release.
> 
> 
> Sounds great! How do I join?
> 
> I'd tentatively suggest that we meet after next week's Vidyo stand-up to 
> perform our first polish triage and decide what our first actions will be. If 
> you could also reply to me and/or the list to express any interest, 
> suggestions or concerns you have, I'd love to hear from you.
> 
> I'm all for people bringing their pet polish peeves (PPPs), but if you'd like 
> more focus, I would also suggest that we first look at the consistency and 
> performance of state transitions (app launching, navigating through panels in 
> apps, bringing up menus, etc.).
> 
> 
> All the best,
> 
> --Chris
> 
> p.s. I'll be bringing this up again in the Gaia meeting on Tuesday, for 
> maximum exposure.
> _______________________________________________
> dev-gaia mailing list
> dev-g...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-gaia

_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to