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

[Amye Scavarda]

On Fri, Aug 19, 2016 at 6:12 AM, Niels de Vos <ndevos at redhat.com> wrote:

> On Thu, Aug 18, 2016 at 05:59:56PM -0700, Amye Scavarda wrote:
> > 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.
>
> I assume these guidelines are different for the contents on
> planet.gluster.org. Some posts from other blogs seem to get syndicated
> on blog.gluster.org too. However the posts from blog.gluster.org are not
> all on the planet?
>
>
The planet.gluster.org syndicates everything that's been added to it. It
does not syndicate to the social media accounts.
Blog.gluster.org is tied to social media accounts.

Could you explain the differences between blog and planet from a readers
> point of view? As at one point we recommended our users to only watch
> the planet, and not the blog anymore. This obviously has changed, and
> the blog is still being maintained. I hope the blog gets the updated
> design too now, that wasnt done because the Planet was becoming the main
> source of blog posts.
>
>
>
That's on the roadmap.


>
> > 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.
>
> Ok, so the blog is not intended for very detailed and technical
> articles? Where do you recommend to post those?
>
> > We're focusing on readability - ideally, this should be at a 4th grade
>
> No idea what 4th grade level is... Its definitely different per country.
> Maybe you can point to an example post for this?
>
> > 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.
>
> How do people sign up to become part of the "editorial team"? That
> sounds like a great way for some users to contribute to the community.
>
> > ## 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.
>
> I suggest the "editorial team" hits the publish button, and writers only
> need to care if they get a -1. That is basically how we do patch reviews
> too, the ones approving click the button. (Otherwise you'll need to
> specify how many +1's someone needs, and if only people from the
> editorial team can +1, or others as well.)
>
> > 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.
>
> Once this draft is more complete and ready for broader acceptance,
> please file a pull request so that it can be included in the
> documentation. We already have a note about the Planet, this would be a
> nice addition.
>   http://gluster.readthedocs.io/en/latest/Contributors-Guide/
> Adding-your-blog/
>
> Thanks,
> Niels
>



-- 
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/20160819/91fb34b8/attachment-0001.html>