Would you like to present? Tag @kris@nateynate and we’ll work to get you added to the agenda!
Feel free to comment on this agenda before the meeting if you want to add an item or have a question.
After the meeting, we will post the chat log and any meeting notes. We welcome you to keep the conversation going here on the forum.
======== By joining the OpenSearch Community Meeting, you grant OpenSearch, and our affiliates the right to record, film, photograph, and capture your voice and image during the OpenSearch Community Meeting (the “Recordings”). You grant to us an irrevocable, nonexclusive, perpetual, worldwide, royalty-free right and license to use, reproduce, modify, distribute, and translate, for any purpose, all or any part of the Recordings and Your Materials. For example, we may distribute Recordings or snippets of Recordings via our social media outlets.
Code isn’t the only thing that makes an open-source project. There’s time. Nearly all unpaid time. Time spent cursing at failing integration tests, crafting PR comments, etc. People willingly give their time to create these projects out of passion and drive.
Content tells the story of how a project is used; not just in a vacuum. It’s much more than documentation; it’s tutorials of all levels, how-to guides, blog posts, release notes, issue tracking and comments… it’s a web of links and text that makes up the context of the project and how it is used.
So, who should write the initial story and context of an open-source project: the team that wrote it and technical writers working closely with them, or users and companies? You can’t control it all, but you can certainly put your best foot forward with some good content to go with a project’s documentation. So why do so many projects leave the story of their code to others?
This talk will cover:
What content means
How it’s made and who makes it
Why it’s more than documentation
Why it’s hard to generate content in open source
