Open contraexemplo opened 2 weeks ago
We still have time to discuss this as a policy change for the May 2025 cohort if we finalize a draft for a policy change in the first week of September.
Changing the wording from "public artifacts" to "public works" to make that concept less abstract. Adding "enforce" because we do have some existing policies related to those expectations, but we need to transform and enforce them.
We should talk about the expectation of having 'intermediate' public works (drafts, etc.)
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
[^1]: I can personally attest that my Outreachy reports helped a Google Season of Docs participant with Wikimedia. [^2]: I still consider my mid-internship and final internship reports as some of my best technical writing and public comms work.