"Moderating" might be too strong a word to describe this task. Basically, this task encompasses the review and merging of user-submitted content to the devblog branch. Before we merge any submission to the devblog branch, we should follow these steps:
###Blog workflow for reviewers:
- pull PR and check rendering locally
- check/fix markdown as needed
- unless the author expressly consented for content to be edited (see Blog contribution guidelines), DO NOT change or edit the content in any way -- period. If you see issues with phrasing, grammar or structure, please suggest changes/communicate them to author via their PR.
- Make sure required data is included in the PR (Name, Bio, Social Media Contact, etc.)
- Make sure date on file name matches the date in the front matter
- Make sure data in the front matter matches data provided in the PR
- Check categories in the front matter match our guidelines (see below)
- merge PR to
devblogbranch (please note thatdevblogbranch is for blog content only, all non-content PRs for the blog should go againstdev) - create a branch merge PR against
masterand ping blog admin(s) - If you're bouncing back a blog entry PR, please be kind and respectful, we want to encourage authors to submit content and make it a pleasant experience.
######Blog admins: @rdodev if unavalable @ycombinator if unavailable @kenperkins
###Blog Categories
While up to this point categories have been all over the place in terms of consistency, we can change that going forward. So, to this end we're enforcing the following guidelines:
- If it's a proper noun or trademark make lower case i.e. OpenStack -> openstack
- If it contains more than one word, make it slug-lower-case i.e. Cloud Files -> cloud-files