Survey results: web-ext

Sylvain Giroux sylvaing at spoluck.ca
Fri Oct 6 15:20:55 UTC 2017


The same limitation is present on CWS. You have to upload manually the 
first version from their website, adding icons, screenshots and other 
metadata.

Then, you can automate your deployment with tools such as 
https://github.com/c301/grunt-webstore-upload


On 2017-10-06 11:16 AM, Andrew Williamson wrote:
> You can't yet fully automate the deployment of a new extension with
> listed versions, alas.  AMO requires extra metadata for listing
> (categories, a summary, and a license) that aren't collected by the
> signing API, so the first listed version must be submitted via the
> website.
>
> On 6 October 2017 at 15:44, Kumar McMillan <kmcmillan at mozilla.com> wrote:
>> I meant that when one submits an extension to addons.mozilla.org it is now
>> published immediately without needing to go through any review. This makes
>> it possible to fully automate the deployment of a new extension, something
>> that wasn't possible before. Thus, we should definitely support this in
>> web-ext.
>>
>> On Fri, Oct 6, 2017 at 2:18 AM Alexis Krier <alexis.krier at toujours.top>
>> wrote:
>>> you mean, looking on the extension code submitted ? Or developing a bot to
>>> do the job?
>>>
>>> Indeed I've submitted mine end of September and it was really quick to be
>>> validated
>>>
>>>
>>> Le 06/10/2017 à 00:43, Kumar McMillan a écrit :
>>>
>>> This is great feedback, thanks all!
>>>
>>> We have a contributor working on the config patch (thank you, Elvina).
>>>
>>> We do not have anyone working on the AMO submission command. Now that
>>> there is no human reviewer blocking add-on submission, this command would be
>>> really useful.
>>>
>>> If anyone would like to get involved, I can possibly make time to review
>>> patches.
>>>
>>> On Wed, Oct 4, 2017 at 6:11 PM Andrew McKay <amckay at mozilla.com> wrote:
>>>> A while back we sent out a survey about web-ext. Apologies for
>>>> reporting the results so late, but I got a bit caught up in 57. If you
>>>> missed it and you want to tell us about web-ext, please go to
>>>> https://goo.gl/forms/zFzhgW0KkuxDxyhS2, we'd love your feedback.
>>>>
>>>> Here's my summarization of the results from 26 respondents,
>>>>
>>>> 73.1% of responders use web-ext.
>>>>
>>>> Some of the reasons give for not using web-ext where:
>>>> * lack of webextensions APIs
>>>> * storage API not being persistent
>>>> * no chrome support
>>>> * don't know what its for
>>>>
>>>> Which feature do you use the most?
>>>> * run (89.5%)
>>>> * build (68.4%)
>>>> * lint (31.6%)
>>>> * sign (15.8%)
>>>>
>>>> Which feature would you like to see?
>>>> * Support for a config file to specify options (26.3%)
>>>>    > Bug https://github.com/mozilla/web-ext/issues/176
>>>>
>>>> * Ability to push listed add-ons to AMO (26.3%)
>>>>     > Bug https://github.com/mozilla/web-ext/issues/1096 added.
>>>>
>>>> * Improved testing options for your extension (21.1%)
>>>> * Ability to create extensions from pre-defined extensions (10.5%)
>>>> ...The rest had one or less responses.
>>>>
>>>> Anything else you want to tell us about web-ext?
>>>> * Creating a fresh session every time is cumbersome
>>>>
>>>> * web-ext is a great addition to the add-on developer, thanks.
>>>> _______________________________________________
>>>> Dev-addons mailing list
>>>> Dev-addons at mozilla.org
>>>> https://mail.mozilla.org/listinfo/dev-addons
>>>
>>>
>>> _______________________________________________
>>> Dev-addons mailing list
>>> Dev-addons at mozilla.org
>>> https://mail.mozilla.org/listinfo/dev-addons
>>>
>>>
>>> _______________________________________________
>>> Dev-addons mailing list
>>> Dev-addons at mozilla.org
>>> https://mail.mozilla.org/listinfo/dev-addons
>>
>> _______________________________________________
>> Dev-addons mailing list
>> Dev-addons at mozilla.org
>> https://mail.mozilla.org/listinfo/dev-addons
>>
>
>



More information about the Dev-addons mailing list