Fair enough. You make a good argument in regards to the features set itself and getting a better sample data of what end users want instead of just concentrating on the foxfooding group which is what the list somewhat represents.
There are also backend changes that need to take place for Development to become easier as well. Your footnote is also touching upon something that needs to be addressed. I also believe that there are certain apps that are not available on the Firefox OS that prevents certain people from switching. It would be great if the work week could address these very issues. On Tue, Dec 1, 2015 at 8:45 PM, Marcus Cavanaugh <[email protected]> wrote: > On Tue, Dec 1, 2015 at 5:50 PM, Naoki Hirata <[email protected]> wrote: > >> I think we really need to go back to the roots of Mozilla and help cater >> to the features that people are requesting : >> http://foxfooding.github.io/dashboard/ >> > > I agree with the sentiment that we should listen to our foxfooders, rather > than build a product based on unproven visions. I don't think that this > list, as it stands, represents what we should work on, nor what we should > care about. > > While some of these items would be universally welcomed, and papercuts > would be nice to fix, the overwhelming majority of users don't care about > CardDAV, WebDAV, VPN support, full-disk encryption, or PGP email. I don't > think supporting these features would improve Firefox OS's appeal to most > foxfooders, let alone other enthusiasts. I don't think this list captures > the most actionable, urgent weaknesses in Firefox OS. > > Do we have any quantitative data gathered from ex-foxfooders about why > they no longer dogfood? That might point to more foundational problems we > must address than the feedback we see here. > > I presume that the "Proprietary Messenger" dilemma is the gargantuan > missing piece. If we gave every Mozillian a B2GDroid build instead of a > pure FxOS device, I think we'd be looking at a very different to-do list, > because we'd have a much larger set of active foxfooders and feedback to > work with.[1] Whether that's what's best for Mozilla and the open web is an > open question. > > You're right: foxfooding feedback is important and valuable, and we can > and should implement things in response to user feedback. This list is a > good start. That said, I'd hesitate to put any resources behind these items > without more careful consideration of how this fits into our larger > strategy. > > > Marcus > > > [1]: I'm hoping that our strategic direction regarding the messenger > problem will become clear in Orlando. If we're going to continue building a > phone-based OS (and if the absence of proprietary apps is a major problem), > we should either (A) accept that proprietary apps are a necessity and focus > primarily on B2GDroid-like initiatives, or (B) accept that we're not > targeting an audience who requires proprietary apps, along with its > implications for our products and strategic direction. > > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
