On 5/06/2014 1:52 PM, Nick Alexander wrote: > > From where I stand, what we must do is pin down what level of > organizational support we are going to give to custom auth and custom > service endpoints. The costs of building UX -- in tree or add-on -- are > small compared to the ongoing maintenance, documentation, and testing > costs that comes from supporting this feature. If we're not going to > commit to the "custom endpoint" feature for at least, say, two years > [1], then we shouldn't spend a minute building an add-on or any support > for an add-on. > > In my opinion, we should absolutely commit to this feature. Principle 5 > of the manifesto states [2], > > "Individuals must have the ability to shape the Internet and their own > experiences on the Internet."
Tangent: I'd love to see a "Cloud Services Manifesto" or similar, that maps the high-level Mozilla principals onto some more concrete properties that our cloud-services offerings should have. IMHO the ability to self-host would feature strongly in such a document. > We are fighting a wave of centralization. We've been pushed to > centralize our own service offerings, and we've discovered first hand > how difficult it is to develop a de-centralized ecosystem. > > We have a relatively low-cost opportunity [3] to do something aligned > with our mission; to do something that is squarely aimed at our valuable > tech wizards user type, many of whom are feeling abandoned by Mozilla's > pro-mass market decisions. Let's ride the wave of anti-surveillance > sentiment and maintain our talking point, that "you don't need to trust > Mozilla to use Firefox Accounts". > > Before we build an add-on, or an add-on API, or a native widget > solution, we need to decide if we're going to make this a first-class > feature of our product offering. And if we're going to support it. > > I know where I stand. You have my sword... Ryan _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
