[Go Faster] Followup: modularity, WebExtensions, and going faster

[Sylvestre Ledru]

Le 06/10/2016 à 17:08, Benjamin Smedberg a écrit :
> I spent a week writing a thing about modularity, webextensions, and going faster. I think it's important for us to decide the module structure of our code especially as we start shipping independent modules/going faster. And I believe that having better module structure, boundaries, and
> documentation is critical to our teams being more agile and also attracting contributors to the project.
>
> http://benjamin.smedbergs.us/blog/2016-09-03/modularity-and-webextensions/
>
> I personally think that we should double down on WebExtensions as a model and start using that for large parts of Firefox. But Andy McKay and Rob Helper had some good counter-thoughts and I've asked them to post here to elaborate.
>
> In the post I asked everyone to send followups to firefox-dev, so I wanted to start a thread here to collect responses. Over the next months I'd like this to turn into a firm decision about how we're going to build system addons; but I'd like to start by seeing what feedback people have and even
> whether I've framed the problem correctly.
I like the idea of having more flexibility and modularity.
However, from my perspective, I don't have the feeling that moving faster is what our users are asking. I believe they are asking for stability and no regression. And, for now, I don't think we have been able to achieve that.
I am concerned that not having features riding the train might lead with poorer quality as we need time to have the feature backing properly and gather user feedback.

In parallel, we will need to streamline our workflows once/if we start using this capability to ship outside of the release cycle. The Go Faster is already adding a lot of complexity for release managers.

Sylvestre