Skip to content
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

Open
quaid opened this issue Jun 7, 2021 · 6 comments
Open

News feed for new "releases" of operate-first.cloud #14

quaid opened this issue Jun 7, 2021 · 6 comments
Labels
area/community Indicates an issue/PR is related to the overall community. area/user Indicates an issue/PR is related to a project platform user. kind/marketing Indicates an issue/PR is related to marketing. kind/news Indicates an issue/PR is related to project news and outreach. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@quaid
Copy link
Member

quaid commented Jun 7, 2021

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.

@quaid quaid created this issue from a note in SIG Community project board (Backlog) Jun 7, 2021
@quaid quaid added kind/marketing Indicates an issue/PR is related to marketing. kind/news Indicates an issue/PR is related to project news and outreach. area/user Indicates an issue/PR is related to a project platform user. area/community Indicates an issue/PR is related to the overall community. labels Aug 1, 2021
@sesheta
Copy link
Member

sesheta commented Oct 30, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 30, 2021
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 16, 2021
@sesheta
Copy link
Member

sesheta commented Feb 15, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 15, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2022
@sesheta
Copy link
Member

sesheta commented Jun 10, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 10, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 25, 2022
@sesheta
Copy link
Member

sesheta commented Sep 24, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 24, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2022
@sesheta
Copy link
Member

sesheta commented Jan 5, 2023

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 5, 2023
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 26, 2023
@sesheta
Copy link
Member

sesheta commented Apr 26, 2023

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/community Indicates an issue/PR is related to the overall community. area/user Indicates an issue/PR is related to a project platform user. kind/marketing Indicates an issue/PR is related to marketing. kind/news Indicates an issue/PR is related to project news and outreach. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
Development

No branches or pull requests

2 participants