This is a tracking ticket to consolidate suggestions for improving tasks related to Fedora Community Blog.
For example,
In today's meeting (2017-10-16), we had a discussion on how to manage the pending posts for review in Community Blog. @bt0dotninja suggested and will work on sending bi-weekly reminders about pending CommBlog posts on mailing list and IRC. We will test it for a few weeks and see how this works. Any suggestions/help here is welcome.
Metadata Update from @bee2502: - Issue tagged with: community blog, help wanted, needs feedback
the mail was sent to the editors list in
https://fedoraproject.org/wiki/Community_Blog#Editors
if we don't have any response i will try to ping then on IRC channels the next Friday :clock830:
I saw the first email reminder come out. I liked it. The one change I would make is that the person who does the email should consider triaging the requests. For example, does the test day post still need to be run if the day has past?
Ok, I got it :smile: thanks b e x
As a note, this is a high priority task for me. We spent a lot of time getting the Community Blog set up and reaching out to folks to share their content here. Some of the recent negligence (on my part) is reversing the effects of that work.
I don't have specific sub-tasks yet, but I've identified this as a high priority item for 2017 and I hope to make progress on streamlining the process and making it easier for people to submit content and get it published quickly. Self-assigning this ticket and removing "needs feedback" tag. When I have more to share, I'll file new tickets for more narrow tasks and update this tracking ticket.
Metadata Update from @jflory7: - Issue untagged with: help wanted, needs feedback - Issue assigned to jflory7 - Issue priority set to: normal (1-2 weeks) - Issue set to the milestone: Fedora 27 (to Nov. 2017)
Metadata Update from @jflory7: - Issue priority set to: minor (3-4 weeks) (was: normal (1-2 weeks)) - Issue set to the milestone: Fedora 28 (to May 2018) (was: Fedora 27 (to Nov. 2017))
Coming back to this ticket. Since the last comment, here is what has happened:
Issue #124 is still open, but it is lower on the priority list. I am closing this issue as complete.
Metadata Update from @jflory7: - Issue close_status updated to: Complete - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.