Created Outreachy Application (markdown)
Erlend Sogge Heggen
parent
4c7858f14f
commit
cdb1a67157
|
|
@ -0,0 +1,99 @@
|
|||
**Form 1**
|
||||
|
||||
****
|
||||
|
||||
**Short title:**
|
||||
|
||||
Improve Discourse User Data
|
||||
|
||||
**Approved license:** CHECK
|
||||
|
||||
**No proprietary software:** CHECK
|
||||
|
||||
**Longevity:**
|
||||
|
||||
More than 2 years
|
||||
|
||||
**Community size:**
|
||||
|
||||
50-100 people
|
||||
|
||||
**Intern tasks:**
|
||||
|
||||
Tasks that involve authentication and user data.
|
||||
|
||||
* [https://meta.discourse.org/t/reddit-oauth-api-support/21939](https://meta.discourse.org/t/reddit-oauth-api-support/21939) (good warmup task)
|
||||
|
||||
* [https://meta.discourse.org/t/how-to-add-stackoverflow-login/54201](https://meta.discourse.org/t/how-to-add-stackoverflow-login/54201) (good warmup task)
|
||||
|
||||
* [https://meta.discourse.org/t/api-can-i-authenticate-without-putting-the-key-in-the-url/29425](https://meta.discourse.org/t/api-can-i-authenticate-without-putting-the-key-in-the-url/29425)
|
||||
|
||||
* [https://meta.discourse.org/t/override-profile-background-via-sso/41921](https://meta.discourse.org/t/override-profile-background-via-sso/41921)
|
||||
|
||||
* [https://meta.discourse.org/t/tracking-signups-from-referral/56911](https://meta.discourse.org/t/tracking-signups-from-referral/56911)
|
||||
|
||||
**Repository:**
|
||||
|
||||
[https://github.com/discourse/discourse/](https://github.com/discourse/discourse/)
|
||||
|
||||
**Issue tracker:**
|
||||
|
||||
[https://meta.discourse.org/](https://meta.discourse.org/)
|
||||
|
||||
**Newcomer issue tag:**
|
||||
|
||||
[https://meta.discourse.org/tags/starter-task](https://meta.discourse.org/tags/starter-task)
|
||||
|
||||
---
|
||||
|
||||
**Contribution tasks:**
|
||||
|
||||
### **Recommended reading before applying**
|
||||
|
||||
Yes, it's a fair amount of material, but if we're gonna spend 3 months+ working together, the sooner we can get on the same page the better!
|
||||
|
||||
* [Outreachy: What? How? Why?](http://vakila.github.io/blog/outreachy-what-how-why/)
|
||||
|
||||
* [Bad reasons to hack on open source projects](http://blog.codecombat.com/reasons-why-you-shouldnt-hack-on-open-source-projects)
|
||||
|
||||
* [The ideal GSoC applicant](http://blog.discourse.org/2016/03/the-ideal-gsoc-applicant/)
|
||||
|
||||
* [Discourse Contribution Guidelines: All](https://meta.discourse.org/t/how-to-contribute-to-discourse/53797)
|
||||
|
||||
* [Discourse Contribution Guidelines: Developers](https://meta.discourse.org/t/discourse-development-contribution-guidelines/3823)
|
||||
|
||||
* [How to start building stuff for Discourse as a newbie](https://meta.discourse.org/t/how-to-start-building-stuff-for-discourse-if-youre-newbie-like-myself/45954)
|
||||
|
||||
* [Beginner's guide to creating Discourse plugins](https://meta.discourse.org/t/beginners-guide-to-creating-discourse-plugins/30515)
|
||||
|
||||
Feel free to ask any questions in [#dev](https://meta.discourse.org/c/dev) or email us directly at [team@discourse.org](mailto:team@discourse.org).
|
||||
|
||||
### **What you'll be working on**
|
||||
|
||||
In our experience it's better for applicants to work on an assortment of bite-sized tasks rather than one large project stretching across several months. Therefore we prefer to start with a small and well documented project before we assign you to new tasks tailored to your interests & skillset.
|
||||
|
||||
For your first contribution (required before applying) we recommend extending one of these plugins:
|
||||
|
||||
#### Ruby - New chat provider
|
||||
|
||||
[https://meta.discourse.org/t/adding-a-new-provider-to-discourse-chat-integration/68156](https://meta.discourse.org/t/adding-a-new-provider-to-discourse-chat-integration/68156)
|
||||
|
||||
Pending providers open for contribution are [listed here](https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522). Stride, Microsoft Teams, Basecamp, IRC Cloud and Flock.
|
||||
|
||||
#### Ruby - New backup provider
|
||||
|
||||
[https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018)
|
||||
|
||||
See the TODO section for pending providers open for contribution. We recommend looking at the [Google Drive extension](https://github.com/berlindiamonds/discourse-sync-to-googledrive) to learn how to extend the synchronizer base.
|
||||
|
||||
---
|
||||
|
||||
**Long description:**
|
||||
|
||||
An Outreachy intern for Discourse will get started with well established, thoroughly specced projects. Over time your mentor will provide you with new, increasingly challenging tasks. There is a very good chance you will eventually be making contributions to the Discourse core project, just like other Outreachy participants before you:
|
||||
|
||||
* [@nbianca PRs](https://github.com/discourse/discourse/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Anbianca)
|
||||
|
||||
* [@majakomel PRs](https://github.com/discourse/discourse/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Amajakomel)
|
||||
|
||||
Our primary means of communication is our very own Discourse forum, but you will also have access to instant chat messaging together with your mentor. Prior to the internship the Discourse team at large is available to answer any questions you may have on meta.discourse.org or via team@discourse.org.
|
||||
Loading…
Reference in New Issue