Set and enforce expectations for Outreachy projects to produce public works #579
Labels
core team
Issues that can only be solved by the core team of Outreachy
internal policies
stage: community sign-up
stage: internship
One of the pillars of free and open source community is embracing openness in the way we work. Over the years, Software Freedom Conservancy and Outreachy staff has had several discussions about the discoverability of public works produced by Outreachy internships—we believe that embedding it into expectations for Outreachy projects has two main benefits:
What is considered a public work?
Anything publicly available that can be used to showcase an intern's work. It can be:
Ideas for how to tackle this issue
Footnotes
I can personally attest that my Outreachy reports helped a Google Season of Docs participant with Wikimedia. ↩
I still consider my mid-internship and final internship reports as some of my best technical writing and public comms work. ↩
The text was updated successfully, but these errors were encountered: