OpenNewsLabs/field-guide-open-source-newsroom
A community-driven guidebook to releasing open-source code in the newsroom.
MIT
Issues
- 0
- 0
- 0
Consistency pass: Read through with a focus on fixing instances of "open-sourcing" (as verb and adjective) vs. "open source" as noun
#90 opened by ryanpitts - 0
- 0
Testing an issue. Ignore
#123 opened by kavyasukumar - 2
Footer links to GitHub are incorrect
#122 opened by benlk - 0
- 0
Review: Take a look at the project-linter, identify any chapters where we should reference it
#120 opened by ryanpitts - 0
Clean up existing issues from before 2018
#119 opened by ryanpitts - 0
Ch 7 - Fix or remove dead link for Zulip roadmap
#118 opened by ryanpitts - 0
- 0
Ch 6 - In the "governance" section, we should explain what we mean by "governance"
#116 opened by ryanpitts - 0
Ch 4 - In the "versioning" section, the semantic versioning reference should link to our own Ch 7 extensive discussion of version numbers rather than point to external resource
#115 opened by ryanpitts - 0
Ch 4 - In the tracking issues section, update "GitHub allows you to make issue templates, which are really helpful for efficiency"
#114 opened by ryanpitts - 0
Ch 4 - In the tracking issues section, update language around "Consider avoiding using GitHub issues for support"
#113 opened by ryanpitts - 0
Ch 4 - In the tracking issues section, "it's probably a good idea" is waffly language, we should just recommend adding instructions to the readme
#112 opened by ryanpitts - 0
Ch 4 - Change heading: "Tracking issues" -> something like "Keeping track of bugs & issues"
#111 opened by ryanpitts - 0
- 0
- 0
- 0
- 0
Ch 2 - Reorder checklist to move identify audience, etc, BEFORE name your project
#106 opened by ryanpitts - 0
Ch 2 - Reframe "use the MIT license" to something more like "when in doubt, choose MIT"
#105 opened by ryanpitts - 0
Ch 2 - license section, this should start with something like "a license gives explicit permission for people to use this stuff"
#104 opened by ryanpitts - 0
- 0
Ch 1 - Change heading: "Questions and misconceptions about open sourcing" -> "How to answer questions and misconceptions from different stakeholder groups"
#102 opened by ryanpitts - 0
Ch 1 - Revise/rewrite Quartz case study at end to chapter to clarify this is a summary quote with link to full writeup
#101 opened by ryanpitts - 0
Tracking issue: Are there sections that are crying out for case studies but don't have them?
#100 opened by ryanpitts - 0
Tracking issue: Do any of the current case study entries now feel awkward or not applicable?
#99 opened by ryanpitts - 0
- 0
Discussion: Do we want to foreground or highlight checklists in a different way?
#97 opened by ryanpitts - 0
- 0
Consistency pass: Read through with a focus on things that are _too_ specific
#94 opened by ryanpitts - 0
- 0
- 0
Consistency pass: Read through with a focus on not being overly clever, but playing it straight
#91 opened by ryanpitts - 0
Review: In the Ch. 1 section on answers to stakeholders, do we need to change/add any answers?
#88 opened by ryanpitts - 0
Review: Does Chapter 7 need to stand on its own? Or should we fold it in as a section of Chapter 4?
#87 opened by ryanpitts - 0
Review: Can we collapse Chapters 2 & 3 into a single chapter with two sections?
#86 opened by ryanpitts - 0
- 0
Discussion: Should chapter titles include hints to WHEN these themes are important?
#84 opened by ryanpitts - 0
Investigate: Is it possible to change Read The Docs' formatting so that H3 heading don't look just like links?
#83 opened by ryanpitts - 0
- 4
Spanish translation
#61 opened by ryanpitts - 0
add reference to Google's new open-source docs
#62 opened by ryanpitts - 0
- 0
add references to the linter!
#49 opened by ryanpitts - 1
Add output options
#53 opened by davisshaver - 1
add chapter trailers with contact info
#48 opened by ryanpitts - 0
Chapter 1 - add checklist
#47 opened by tsl-lindsay