-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
News feed for new "releases" of operate-first.cloud #14
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Look at all the ways to make it possible for interested parties to keep up with the project. Automation plus curation?
Think about the various types of users you have and what “release” they care about, then find a way to turn that information into a feed, which may need human curation for news/outreach.
There is another purpose for release management, and that is to establish and advertise to users a cadence of output for things interesting to them. We use this in outreach, support, education, and so on at the center of user attraction and expectation. A large part of open source project marketing is reviewing “what did we release”, then simplifying and amplifying that message. This is an area the project can work to improve in the quest for more users.
The text was updated successfully, but these errors were encountered: