There are currently over 20 drafts in the Community Blog queue. Not all of the articles may be relevant still. An editor needs to contact every author to follow up if they still want their post published.
The Community Blog doesn't have an editorial process established (that is, that scales beyond one or two editors). Because of this, it was neglected over the last few months since only one or two people were publishing posts. It's important to improve the response time for articles and submissions so that people can trust that their content will be published in a timely way on the blog.
Before we start thinking ahead, we need to clear the queue of articles we have now. Since there are so many and not so many people, I prefer a hard stance where we decide to publish the article based on the reply of the author. If the author says yes, we will edit it and review it. If they say no or we do not hear back at all, we will move it to the trash. Two weeks after the author is contacted, the article will be permanently deleted.
We need to…
Metadata Update from @jflory7: - Issue priority set to: normal (1-2 weeks) - Issue set to the milestone: Fedora 27 (to Nov. 2017) - Issue tagged with: Community Blog, easyfix
This is a semi-important task because we need to get a flow / routine for publishing articles on the CommBlog. I will have time in the next two weeks to work on it, but this would be a great task for someone new to work on, or if you're looking for a way to contribute. We can help you do this if you're interested too. :smile:
Metadata Update from @jflory7: - Issue marked as blocking: #119
Metadata Update from @jflory7: - Issue assigned to jflory7
Metadata Update from @jflory7: - Issue priority set to: critical (next week) (was: normal (1-2 weeks)) - Issue set to the milestone: Fedora 28 (to May 2018) (was: Fedora 27 (to Nov. 2017))
Metadata Update from @jflory7: - Issue assigned to bt0dotninja (was: jflory7) - Issue priority set to: normal (1-2 weeks) (was: critical (next week)) - Issue tagged with: meeting
Discussed in 2017-12-04 meeting.
@bt0dotninja is reaching out to half of the authors that have a draft in the CommBlog by the next meeting on Dec. 11. He's checking to see if the author is still interested in having their blog posts published. As of now, there are 25 drafts at various levels of "completeness".
All current drafts are found here.
Mails sended to:
Discussed during 2017-12-11 meeting.
@bt0dotninja did the long overdue work (on my part) of following up with authors who have unfinished drafts in the CommBlog. In the meeting, we agreed to mark this ticket as blocked, until we hear back from all authors. When we hear back from everyone and have an updated status on all articles, we'll be "back to normal", and this ticket can be closed.
Thanks again @bt0dotninja for spending time on this one!
Metadata Update from @jflory7: - Issue untagged with: meeting - Issue priority set to: critical (next week) (was: normal (1-2 weeks)) - Issue tagged with: blocked
@bt0dotninja Any word back from some of the other authors?
No more replies after the last update :crying_cat_face:
@bt0dotninja Any final updates? Otherwise, I think we can close this ticket as complete. We're down to a much more manageable amount of drafts now. Anyone we haven't heard back from, we can move their articles to "On hold" for two weeks, and then move them to the trash after.
Before closing this ticket, I'll make sure to get a list of those articles – but want to confirm if there were any new updates first.
no, 0 new updates :broken_heart:
Ouch, okay. Thanks anyways for your work in following up here, @bt0dotninja. I'm closing this as complete.
Metadata Update from @jflory7: - Issue untagged with: blocked - Issue close_status updated to: Complete - Issue status updated to: Closed (was: Open)
These articles were moved to On hold status since @bt0dotninja did not hear back from the authors in his follow-up emails. In two weeks, if there are still no responses, they will be deleted.
I sent an email on commops mailing list regarding this too.
Articles moved to On hold These articles were moved to On hold status since @bt0dotninja did not hear back from the authors in his follow-up emails. In two weeks, if there are still no responses, they will be deleted. FOSSWave with Fedora at KGISL, Coimbatore by @siddharthvipul1
Articles moved to On hold These articles were moved to On hold status since @bt0dotninja did not hear back from the authors in his follow-up emails. In two weeks, if there are still no responses, they will be deleted.
FOSSWave with Fedora at KGISL, Coimbatore by @siddharthvipul1
Hey @jflory7, I didn't receive any warning or notice mail regarding this earlier. If possible, I would still like to see this blog published :)
@siddharthvipul1 Thanks for chiming in! Not sure why you didn't get the email. :confused: Anyways, we'll move this to pending review and work on getting it published in the next week or two.
@jflory7 you can publish mine, the OLF report
Login to comment on this ticket.