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

Pending providers open for contribution are listed here. Stride, Microsoft Teams, Basecamp, IRC Cloud and Flock.

Ruby - New backup provider

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 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:

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.

Form 2 - UX

Short title:

Improve Discourse UX

Approved license: CHECK

No proprietary software: CHECK

Longevity:

More than 2 years

Community size:

50-100 people

Intern tasks:

Tasks that involve a lot of user experience work, and will benefit from some prior UX experience as some tasks require further specification.

Repository:

https://github.com/discourse/discourse/

Issue tracker:

https://meta.discourse.org/

Newcomer issue tag:

https://meta.discourse.org/tags/starter-task

Contribution tasks:

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

Pending providers open for contribution are listed here. Stride, Microsoft Teams, Basecamp, IRC Cloud and Flock.

Ruby - New backup provider

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 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:

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.

Form 3 - Email

Short title:

Improve Discourse Email Handling

Approved license: CHECK

No proprietary software: CHECK

Longevity:

More than 2 years

Community size:

50-100 people

Intern tasks:

Anything that touches on email.

Repository:

https://github.com/discourse/discourse/

Issue tracker:

https://meta.discourse.org/

Newcomer issue tag:

https://meta.discourse.org/tags/starter-task

Contribution tasks:

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

Pending providers open for contribution are listed here. Stride, Microsoft Teams, Basecamp, IRC Cloud and Flock.

Ruby - New backup provider

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 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:

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.

Form 1 - User Data

Recommended reading before applying

What you'll be working on

Ruby - New chat provider

Ruby - New backup provider

Form 2 - UX

Recommended reading before applying

What you'll be working on

Ruby - New chat provider

Ruby - New backup provider

Form 3 - Email

Recommended reading before applying

What you'll be working on

Ruby - New chat provider

Ruby - New backup provider