WebExtensions/SummerOfCode2020: Difference between revisions

WebExtensions/SummerOfCode2020 (view source)

Revision as of 11:32, 6 February 2020

301 bytes added , 6 February 2020

re-format some links

RPL

41

edits

@@ Line 3: / Line 3: @@
 == What is the best way to contact you? ==
-The best way to contact us is by joining Mozilla’s Matrix instance on [https://chat.mozilla.org]. Please say hi and feel welcome to ask questions about this project in the [https://chat.mozilla.org/#/room/#addons:mozilla.org “Add-ons” room]. If you need help setting up your Firefox development environment, please ask for help in the [https://chat.mozilla.org/#/room/#introduction:mozilla.org “Introduction” room].
+The best way to contact us is by joining Mozilla’s Matrix instance on [https://chat.mozilla.org https://chat.mozilla.org]. Please say hi and feel welcome to ask questions about this project in the [https://chat.mozilla.org/#/room/#addons:mozilla.org “Add-ons” room]. If you need help setting up your Firefox development environment, please ask for help in the [https://chat.mozilla.org/#/room/#introduction:mozilla.org “Introduction” room].
 Sending an email to the project mentors is also a good way to contact us, but we ask that you CC the other mentors, so we can respond faster and keep track of the emails that have not been answered yet.
@@ 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].
+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].
 There are a few ways you can start contributing to this project. You do not need to do all of these activities!
@@ Line 15: / Line 15: @@
 * 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]
+* 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 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].
@@ Line 27: / Line 27: @@
 This is usually due to connection issues.
-As a workaround it is possible to manually download a bundle and use mercurial hg command to init an empty mercurial repository and unbundle the content of mozilla-central downloaded into it: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Source_Code/Mercurial/Bundles]
+As a workaround it is possible to manually download a bundle and use mercurial hg command to init an empty mercurial repository and unbundle the content of mozilla-central downloaded into it: [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Source_Code/Mercurial/Bundles https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Source_Code/Mercurial/Bundles]
 == How to use Mercurial while working on Mozilla code? ==
 Mike Conley wrote a very nice document that captures common usage patterns:
-[https://mikeconley.github.io/documents/How_mconley_uses_Mercurial_for_Mozilla_code]
+[https://mikeconley.github.io/documents/How_mconley_uses_Mercurial_for_Mozilla_code https://mikeconley.github.io/documents/How_mconley_uses_Mercurial_for_Mozilla_code]