Add-ons/Contribute/Triage

From MozillaWiki
< Add-ons‎ | Contribute
Revision as of 21:35, 21 February 2017 by One (talk | contribs) (Updated queries)
Jump to navigation Jump to search

Purpose of Meeting

A bi-weekly triage session to accomplish these community goals:

  • WebExtensions APIs:
    • Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions.
    • Participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.
    • Experiments: Discuss and provide feedback for WebExtensions Experiments.
  • Good First Bugs: Ensure add-on bugs marked "Good First Bug" are fresh and updated for new contributors. If you are a new contributor who wants to write code for add-on related projects, please start here.

Next Meeting

Next meeting is March 7, 2017.

Details & How to Join

WebExtensions APIs Triage

Triage Guidelines

Bugs marked "design-decision-needed" should be:

  • Tagged with "design-decision-approved" or "wontfix" (including reason)

Bugs marked "design-decision-approved" should have:

  • Clear description of the API and suggested implementation if possible
  • Priority & impact
  • Link to onboarding process
  • Advisor

Bug Queries

"design-decision-needed"

These are determined from the Monday WebExtensions triage. They are APIs we need more discussion on.

"design-decision-approved"

These are APIs we would like to have. They should meet the triage criteria listed above.

WebExtensions Experiments

  • Submit your WebExtensions Experiment by opening an issue on the web-ext-experiments github repo.
  • Be sure to include the following in your issue:
    • Link to where your experiment is located
    • A quick overview of what it does
    • Any Bugzilla bugs that it might address
    • If you’d like to move your repository over to this organisation and we can create a repository for you
  • A comment will be added to the issue when your WebExtensions Experiment has been added to a meeting agenda.

Good First Bugs Triage

Triage Guidelines

All "Good First Bugs" should have:

Bug Queries

"Maybe Good First Bugs" on GitHub

These are tagged "contrib: maybe good first bug". We triage these and change the tag to "Good First Bugs" if determined to be good for new contributors.

"Good First Bugs" that need a mentor on GitHub

These are tagged "contrib: good first bug" and "needs: mentor". We triage these and add replace the "needs: mentor" label by "contrib: mentor assigned" after we decided on a mentor.

"Good First Bugs" that are assigned to a contributor on GitHub

These are tagged "contrib: good first bug" and "contrib: assigned". We triage these and check-in with contributors on their progress and remove "contrib: assigned" after a longer period of inactivity or no response.

"Good First Bugs" on GitHub

This is the query contributors see. We should spot-check them to ensure they are properly triaged.


WebExtensions Bugs on Bugzilla
Add-ons Manager Bugs on Bugzilla

Archive

2017

Feb 21, 2017
Feb 7, 2017
Jan 24, 2017
Jan 10, 2017

2016

Dec 13, 2016
Nov 29, 2016
Nov 15, 2016
Nov 1, 2016
Oct 18, 2016
Oct 4, 2016
Sept 20, 2016
Sept 6, 2016
August 23, 2016
August 9, 2016
July 26, 2016
July 12, 2016
June 28, 2016
May 31, 2016
May 17, 2016
April 28, 2016
April 14, 2016
Mar 31, 2016
Mar 3, 2016
Feb 18, 2016
Feb 4, 2016
Jan 21, 2016
Jan 7, 2016

2015

Nov. 19, 2015
Oct. 29, 2015
Oct. 15, 2015

Aug - Oct 2015

https://drive.google.com/drive/folders/0B2aDMRMZ7uzvYzA4Wm1VYVhvemM

Onboarding information template

If this is your first contribution, please refer to https://wiki.mozilla.org/Add-ons/Contribute/Code on how to get started.

Retrieved from "https://wiki.allizom.org/index.php?title=Add-ons/Contribute/Triage&oldid=1163486"