[Gluster-devel] [gluster-devel] New Publishing Guidelines for Blog.Gluster.org

Amye Scavarda amye at redhat.com
Fri Aug 19 00:59:56 UTC 2016

In keeping with Fedora, oVirt and some of our other communities with
vibrant content, I'm extending a new proposal around how we can create more
content that gets published on blog.gluster.org.

Here's some new guidelines patterned after those:

## Make Your Proposal

When you are ready to create a blog article for Gluster.org, you can send a
proposal for your article to social-media at gluster.org. Include:

* Proposed title
* 1-3 sentence summary of the article
* Any relevant date information (Should this be tied to a release?)

When writing articles for the Gluster blog, the goal is to keep your
articles short, sweet, and to the point.
News from all different parts of the community will be posted here, so not
everyone will read longer articles. However, it is encouraged to link to
more detailed blog posts, articles, or other news sources to help those who
are interested learn more about what you are working on! Ideally, your
Gluster blog article should be a quick “headliner” pointing out the “big
stuff” to grab peoples’ attention.

We're focusing on readability - ideally, this should be at a 4th grade
reading level. All of our readers are going to suffer from too much
information, constantly. If you want to check your readability score, try
here: https://readability-score.com/ first.

Once your article is accepted, it will be noted as "Assigned" within the
Gluster blog's WordPress platform.
If you have access to the platform, you can begin the writing process. If
you need access, the editorial team will assign you a username and password
to access WordPress.

## Basic Requirements: Categories and Tags

As you are writing, there are some housekeeping issues to keep in mind.
Every article will need a few things to be published. First, your article
must be added to categories relevant to your team. If you are writing an
article about a new software being worked on, your post would be
categorized as “Development”. If your post is about a Gluster meetup, you
would use the “Events” category. And so on.

Additionally, add a few tags to your article to help categorize posts and
make them easily searchable. You are free to add any tags you wish, but a
good number is between 3-5 per article.

## Email for Final Approval

Once you have finished writing your article, you should change it from
“Draft” status to “Review”. Afterwards, send an email to social-media@
gluster.org with a link to your article, announcing that it is ready for
review. List members will review your article and either give you a +1 or
-1 about whether you can publish. After meeting a threshold of at least two
positive votes, your article will be marked as "published" or scheduled for
the future.

Once your article is published, it will be automatically shared to the
@Gluster Twitter, as well as other social media channels to help bring
greater exposure to your article.

Amye Scavarda | amye at redhat.com | Gluster Community Lead
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20160818/f21505c6/attachment.html>

More information about the Gluster-devel mailing list