Community Landing Page
You can see prior landing pages by following the organization landing page links on the Round 14 page. The Fedora landing page is a particularly good example.
Your landing page should include the following sections. Some sections may be written by the Outreachy community coordinator, and some will be written by mentors. Mentors and coordinators should work together to have a coheasive presence for interns.
Make sure to have a description of your open source community. Assume your audience has a
few years experience as a programmer, but has never heard of your
project before. Why is it interesting to you?
You'll also need to document information for newcomers to your community:
are your communication channels? If your project uses IRC, please list
the full server URL and link to the Outreachy instructions for IRC
(https://wiki.gnome.org/Outreachy/IRC). Many applicants will be
unfamiliar with IRC, and need advice on finding an IRC client and tips
on IRC etiquette.
- How can applicants communicate with multiple mentors? Is there a newcomer-friendly mailing list or chat/forum channel?
are the next steps for an applicant to get involved with your
community? See the Fedora Outreachy page as a good example of concrete
steps to get involved:
can people make their first contributions? Applicants will need to make
multiple contributions to your project during the application period.
Do you have newcomer-friendly bugs or feature requests in your bug
tracking system? Or does each project have a separate set of first tasks
that applicants need to complete? If you don't define tasks, you'll be
less likely to have applicants participate.
- Code of Conduct Please link to the Code of Conduct that governs your community's spaces, if you have one.
Each landing page needs a list of mentored projects. It is not acceptable to say interns will just need to pick a feature from the bug tracker; instead you need to provide guidance on what tasks are good ones to tackle. Coordinators should encourage and work with their community's Outreachy
mentors to define the project for their internship. Make sure mentors
document the following about their project:
- A 1-2 paragraph
description, again gearing your audience towards novice to intermediate
programmers who have never heard of your project before.
- Required skills. What skills are absolutely required for the project and what skills are good to have or optional?
documentation. Where can they find project documentation? Where is the
documentation for new contributors to set up their project environment?
What tools will they need? What parts of the code will they need to
build? Is there a test suite they need to run? Coding style? (If these
are common to all projects, you can describe them once.)
- Who is
mentoring? Include their contact information, including email,
IRC/Jabber/Discourse nick, github username, etc. Please do include
private contact information. Many applicants feel scared or concerned
about participating, and may not feel comfortable asking questions on a
public mailing list at first. Including email addresses means they'll
contact you (rather than moving onto a more friendly looking project)
and you can reassure them and redirect them to ask questions on the
public project channels.
- First tasks. What specific first tasks
should someone do to see whether they'll like working on this project
for their internship?
Additional Applicant Questions
Some communities want interns to answer additional questions beyond the standard application (see the Application page). If you have
additional questions you need them to answer, put those on your landing
Landing Page Language Tips
avoid duplicating information that can be found on this website. In
particular, don't duplicate the application form. If you have any
questions applicants need to answer in addition to the standard ones,
only list those questions.
use the term "student" for Outreachy participants. Outreachy is open to
anyone over 18 who meets our eligibility requirements, and while we
often get students participating, we also get people who are in the
middle of switching careers. Use "newcomer", "person/people",
"applicant", "participant", or "intern" instead.
avoid using gender-specific language in your page. Outreachy is open
internationally to cis and trans women, but it is also open to trans
men, gender queer folks (who often have varied pronouns), and men of
color in the United States. We try to make our language as inclusive as
possible to avoid erasing anyone's contribution to the program. If you
want to talk about how you want to increase diversity in your community,
a good description is "people traditionally underrepresented in tech"
with a link to our eligibility requirements. Please use "they/them"
pronouns where ever possible (and yes, they can be both singular and
use "Summer" and "Winter" to designate the rounds. Since Outreachy is
open internationally, "summer" and "winter" are different times of the
year in different hemispheres. Use "May" and "December".
"Outreachy" and "Round 14" or "May 2017" can be a
part of the page URL. If your organization is participating in Google
Summer of Code, you can just link to your Google Summer of Code ideas
page for all the coding project ideas.