WebExtensions/SummerOfCode2020: Difference between revisions

WebExtensions/SummerOfCode2020 (view source)

Revision as of 18:14, 26 February 2020

393 bytes added , 26 February 2020

tweak to the content to better align to the https://github.com/mozilla/GSOC2020 readme

RPL

41

edits

@@ Line 9: / Line 9: @@
 == How do I get started with this project? ==
-If you are new to the browser extensions, a good starting point is the [https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions WebExtensions wiki page on MDN]. You can use the documentation available on MDN to start to build a small extension for Firefox. You can also find more information about the Firefox extension ecosystem on [https://extensionworkshop.com https://extensionworkshop.com].
+If you are new to the browser extensions, a good starting point to write a great proposal for this project is to learn more about the WebExtensions ecosystem and WebExtensions APIs.
+The [https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions WebExtensions wiki page on MDN] provides the documentation needed to start to build a small extension for Firefox. You can also find more information about the Firefox extension ecosystem on [https://extensionworkshop.com https://extensionworkshop.com].
-There are a few ways you can start contributing to this project. You do not need to do all of these activities!
+Another way to get more experience on this project's topic is to look into (and/or contribute to) one of Mozilla projects related to the WebExtensions, but you don't have to already be a contributor to the WebExtensions projects to be eligible for this project proposal, your main goal in this phase is to ''craft an excellent GSOC proposal''.
 * You can become more familiar with the activityLog API by experimenting with the API itself. As the API is still in development, there is no official documentation available yet. The development of this API was tracked on Bugzilla at [https://bugzilla.mozilla.org/show_bug.cgi?id=1542402 Bug 1542402] (see the referenced bugs for more information).
-* You can practice using the WebExtensions API by contributing to one of Mozilla’s officially supported extensions. As an example, here are some good-first-bugs related to the [https://color.firefox.com/ “Firefox Color” extension]: [https://github.com/mozilla/FirefoxColor/labels/good%20first%20issue https://github.com/mozilla/FirefoxColor/labels/good%20first%20issue]
+* You can practice using the WebExtensions API by studying (and/or contributing) to one of Mozilla’s officially supported extensions. As an example, here are some good-first-bugs related to the [https://color.firefox.com/ “Firefox Color” extension]: [https://github.com/mozilla/FirefoxColor/labels/good%20first%20issue https://github.com/mozilla/FirefoxColor/labels/good%20first%20issue]
-* You can contribute to the WebExtensions API by fixing one of [https://bugzilla.mozilla.org/buglist.cgi?keywords=good-first-bug%2C%20&f1=assigned_to&keywords_type=allwords&o1=equals&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=nobody%40mozilla.org&component=Android&component=Compatibility&component=Developer%20Tools&component=Experiments&component=Frontend&component=General&component=Request%20Handling&component=Storage&component=Themes&component=Untriaged&product=WebExtensions these good-first-bugs in Firefox]. Having additional experience extending or fixing bugs in the API itself is definitely a “bonus” skill for an applicant that we would appreciate and take into account. We recommend reading our onboarding documentation to help you get started with fixing bugs in Firefox. If you have any questions or issues when setting up your developer environment, please join [https://chat.mozilla.org/ Mozilla’s Matrix instance] and ask for help in the [https://chat.mozilla.org/#/room/#introduction:mozilla.org “Introduction” room]. If you have questions on this project or issues with WebExtensions APIs, you may ask for help [https://chat.mozilla.org/#/room/#addons:mozilla.org “Add-ons” room].
+* You can contribute to the WebExtensions API by looking into one of [https://bugzilla.mozilla.org/buglist.cgi?keywords=good-first-bug%2C%20&f1=assigned_to&keywords_type=allwords&o1=equals&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=nobody%40mozilla.org&component=Android&component=Compatibility&component=Developer%20Tools&component=Experiments&component=Frontend&component=General&component=Request%20Handling&component=Storage&component=Themes&component=Untriaged&product=WebExtensions these good-first-bugs in Firefox]. Having additional experience extending or fixing bugs in the API itself is definitely a “bonus” skill for an applicant that we would appreciate and take into account, but it is absolutely not mandatory. We recommend reading our onboarding documentation to help you get started with fixing bugs in Firefox. If you have any questions or issues when setting up your developer environment, please join [https://chat.mozilla.org/ Mozilla’s Matrix instance] and ask for help in the [https://chat.mozilla.org/#/room/#introduction:mozilla.org “Introduction” room]. If you have questions on this project or issues with WebExtensions APIs, you may ask for help [https://chat.mozilla.org/#/room/#addons:mozilla.org “Add-ons” room].
 == Is the project goal to build something like the extension activity log available on Chrome? ==