Confirmed users
656
edits
Community:SummerOfCode19: Difference between revisions
Jump to navigation
Jump to search
→Project List
(Added the CPG) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 100: | Line 100: | ||
| | | | ||
|- | |- | ||
| Support GitHub Logins in Taskcluster | | <s>Support GitHub Logins in Taskcluster</s> | ||
| | | (withdrawn) | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| Line 161: | 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 231: | 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. | ||