Confirmed users
656
edits
Community:SummerOfCode19: Difference between revisions
→Project List
(→Project List: Update details for `An Android file downloader designed for Emerging Markets`) |
|||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 4: | Line 4: | ||
If you're interested in participating in Mozilla's GSoC program, you can choose from the list below, '''but you do not have to'''. You can submit a proposal for your own idea. You should look at the [[Community:SummerOfCode19:Brainstorming|guidelines]], though, and discuss your ideas or application in the #introduction channel on IRC.Mozilla.org. This is important, as GSoC projects '''must have''' a supporting member of the Mozilla community to evaluate and mentor them, named in the application. | If you're interested in participating in Mozilla's GSoC program, you can choose from the list below, '''but you do not have to'''. You can submit a proposal for your own idea. You should look at the [[Community:SummerOfCode19:Brainstorming|guidelines]], though, and discuss your ideas or application in the #introduction channel on IRC.Mozilla.org. This is important, as GSoC projects '''must have''' a supporting member of the Mozilla community to evaluate and mentor them, named in the application. | ||
Please bear in mind that a '''preexisting relationship with Mozilla is not a requirement for a successful GSOC proposal'''. While participating in Bugzilla is a good way to become familiar with how Mozilla works, "spamming" Bugzilla to establish your ''bona fides'' or improve your chances of a successful application has not historically been a successful approach. We're grateful for our volunteers' contributions, as always, but often that effort would be best put towards focusing on the proposals you are specifically interested in, and putting your effort into crafting an application for them specifically. | |||
===Application Advice=== | ===Application Advice=== | ||
| Line 15: | Line 17: | ||
* Apply on [https://summerofcode.withgoogle.com/ the GSoC site] (note that we have an [[SummerOfCode/ApplicationTemplate|application template]]). | * Apply on [https://summerofcode.withgoogle.com/ the GSoC site] (note that we have an [[SummerOfCode/ApplicationTemplate|application template]]). | ||
* It is entirely acceptable to apply for 2 or 3 projects, if more than one catches your eye; if the applications are high quality, that can improve your chances. Applying to more than that will seem like spam. | * It is entirely acceptable to apply for 2 or 3 projects, if more than one catches your eye; if the applications are high quality, that can improve your chances. Applying to more than that will seem like spam. | ||
* Participation in any Mozilla spaces, forums or events, including our GSOC projects, are subject to Mozilla's [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines], and you should read them carefully. | |||
Questions about individual projects are best addressed to the potential mentor of that project. These should be listed in the table below. If you want to contact a mentor and contact details are not here, ask people in the #introduction channel on IRC: irc://irc.mozilla.org/#introduction. If you have questions of any other sort, send mail to [mailto:mhoye@mozilla.com Mike Hoye]. He will try and respond promptly and direct your questions to the right person. | Questions about individual projects are best addressed to the potential mentor of that project. These should be listed in the table below. If you want to contact a mentor and contact details are not here, ask people in the #introduction channel on IRC: irc://irc.mozilla.org/#introduction. If you have questions of any other sort, send mail to [mailto:mhoye@mozilla.com Mike Hoye]. He will try and respond promptly and direct your questions to the right person. | ||
| Line 90: | Line 93: | ||
| | | | ||
|- | |- | ||
| GitHub Checks Support Improvements | | <s>GitHub Checks Support Improvements</s> | ||
| | | (withdrawn) | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| Support GitHub Logins in Taskcluster | | <s>Support GitHub Logins in Taskcluster</s> | ||
| | | (withdrawn) | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| Line 158: | Line 161: | ||
| [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)] | | [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)] | ||
| [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)] (mTwTm@mozilla.com), [https://github.com/cnevinc/ Nevin Chen] (nevin@mozilla.com) | | [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)] (mTwTm@mozilla.com), [https://github.com/cnevinc/ Nevin Chen] (nevin@mozilla.com) | ||
| We're receiving requests for mockups already; thank you! However, to | | We're receiving requests for mockups already; thank you! However, the core of this project to me is the downloading library rather than the App. To illustrate what might make a good proposal, we want you to imagine what would be a convenient way to schedule downloads. There are many ways we could do this: Copy-pasting download links, have the app opened whenever a link is clicked, or find a way to give other third-party apps access to your App's download queue. | ||
I would also encourage candidates to differentiate onself by focusing on demonstrating your understanding to Android Apps and download protocols. Brainstorming for more use cases is encouraged but we would really like to learn more about how you can implement this project efficently instead of what you can plan in your proposal. | |||
Also, we're utilizing the Mozilla Asia Product mail-list (https://groups.google.com/forum/#!forum/mozilla-asia-products) for discussions around this project. You might find some useful discussions there as well. | Also, we're utilizing the Mozilla Asia Product mail-list (https://groups.google.com/forum/#!forum/mozilla-asia-products) for discussions around this project. You might find some useful discussions there as well. | ||
|- | |- | ||
| Line 228: | Line 234: | ||
| [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt] | | [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt] | ||
| [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt] | | [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt] | ||
| Writing docs for Firefox's in-tree [https://firefox-source-docs.mozilla.org/ source docs] is time consuming and difficult and the end result is difficult to navigate. | | Please see [https://bugzilla.mozilla.org/show_bug.cgi?id=1535452 bug 1535452] for technical information. | ||
Writing docs for Firefox's in-tree [https://firefox-source-docs.mozilla.org/ source docs] is time consuming and difficult and the end result is difficult to navigate. | |||
With [https://developer.mozilla.org/en-US/ MDN] de-prioritizing build and workflow docs, we need a suitable replacement for all of Firefox's contribution and workflow documentation. The great advantage of documentation living in-tree, is that it can be updated along with the source. Unfortunately the current system to build and generate docs is difficult to write for, slow to build and generates poorly organized documentation. These factors discourage developers from creating or updating docs. | With [https://developer.mozilla.org/en-US/ MDN] de-prioritizing build and workflow docs, we need a suitable replacement for all of Firefox's contribution and workflow documentation. The great advantage of documentation living in-tree, is that it can be updated along with the source. Unfortunately the current system to build and generate docs is difficult to write for, slow to build and generates poorly organized documentation. These factors discourage developers from creating or updating docs. | ||