As the posts and editors grow for the CommBlog, we need a way to coordinate post scheduling. I will investigate a few options and come up with a recommendation.
See also #99 https://pagure.io/fedora-commops/issue/99
@bcotton Any updates or progress on this? Or do you want to bump it into Fedora 30 (past October)?
Bumping to F30. I think I know what I want it to look like, but the pieces aren't quite in place to do that yet.
Metadata Update from @bcotton: - Issue set to the milestone: Fedora 30 (to May 2019) (was: Fedora 29 (to Oct. 2018))
@bcotton Do you want to suggest a follow-up date for this ticket in the F30 release cycle?
@jflory7 February 28 seems like a reasonable date to kick me if I don't have something by then.
@bcotton Hey, it has been a while here. What do you suggest we do with this ticket? Are there any updates or should we close this out? If it is on your Taiga board already, I am okay closing this out from the CommOps ticket backlog.
Metadata Update from @jflory7: - Issue set to the milestone: None (was: Fedora 30 (to May 2019))
I'm fine with closing it. The Magazine workflow works well, but is heavier than we need. Right now, I'm just using a pinned post on Discussion and it works well enough. We generally don't have enough content in the queue to merit anything more than that.
@bcotton Makes sense, thanks for following up. I am closing this as Insufficient data – there is insufficient data that this is an urgent need for the CommBlog right now. :)
Insufficient data
Metadata Update from @jflory7: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.