cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: Posting Blog Posts
Date Thu, 08 Aug 2013 19:48:12 GMT
Updated verbiage:

Writing a Blog Post
> --------------------
> *Types of Posts*
> _Announcements_ - releases, call for translators, etc
> _Core Content_ - If the content has to do with cordova-core, or
> publishing guides, etc., we should publish the full text directly on the cordova
> Blog (by whichever author), as-if written by the organization.
> _Linked Posts_ - If the content was written by a contributor and is worth
> curating for the whole community, but is not really core ie. non-core
> plugins, dev tips, research, opinion-pieces, statistics, etc., post a
> short description, perhaps adding a document-snippet, but then link to
> the externally hosted content, making it clearly not written by the
> organization.
> *How to add a Post*
> Blog posts live in `www/_posts`. To create a new post:
>   1. Copy one of the existing posts into a new file (changing the name
> appropriately).
>   2. Run "rake serve" in the background.
>   3. Draft your post.
>   4. Get approval (see below)
>   5. Update the file name to reflect the commit date (if necessary)
>   6. Run "rake build"
>   7. svn commit
> *Post guidelines:*
>   * Use the post title as the first header. Including a header as well
> makes the snippet on the front page look really bad.
>   * Use an appropriate category:
>     * One of: "howto", "news", "releases", "blog" (the catch-all category)
>   * Use appropriate tags:
>     * "android", "ios", "windowsphone", "blackberry", "plugin",
> "plugin-$FOO", "cli", "performance" (add to this list as necessary)
>   * Use `rake serve` and refresh frequently. Jekyll does not do a good job
> at telling you where errors are made.
>   * Review your post yourself before asking for a review. This includes
> spell-check :).
> *Getting Approval:*
> Each blog post must be approved by at least one committer other than
> yourself, and must be available for all to see before going live. To
> request a review:
>   1. Run: `svn diff > new_post.diff`
>   2. Create a new request on http://reviews.apache.org.
>      a. Be sure to add the group "cordova"
>   3. Review it yourself, and also wait for someone to approve it via the
> "Ship it" button.



Note that I've kept in the getting approval from another committer part
(not a vote). Always a good idea to have it proof-read.




On Wed, Aug 7, 2013 at 11:34 AM, Carlos Santana <csantana23@gmail.com>wrote:

> +1 on Andrews process proposal
> +1 on having official posts vs. guest posts
> +1 post template
> +1 voting only on apache/official posts
>
> Additions:
> 1. Want to proposed also linked posts (linked posts vs. official posts vs.
> guest posts)
>     linked posts is just a paragraph with a link "Read More..." pointing to
> the author's blog site (phonegap blog has this concept)
>     tags could be used ( i.e. apache, guest, external). guest and external
> will have a note about "Apache" not legally responsible by content blah
> blah :-)
>
> 2. Use properly categories and tags (it allows for better organization and
> filtering)
>     Should contain 1 or 2 categories, and many tags
>     Categories are usually associated with type of post (tutorial, howto,
> guide, release note, etc..)
>     Tags are usually associated with topics included in the post (ios,
> plugin, cli, javascript, standards, html5, blackberry, devtools,
> performance, etc..)
>
> 3. Document suggested categories and tags ids (don't want 'Android',
> 'android', 'ANDROID', 'Google-Android' creating 4 distinct tags)
>      Post Template can be the place to centralized categories and tags to
> use
>
>
>
>
> On Tue, Aug 6, 2013 at 3:51 PM, Filip Maj <fil@adobe.com> wrote:
>
> > SGTM
> >
> > On 8/6/13 11:57 AM, "Michal Mocny" <mmocny@chromium.org> wrote:
> >
> > >I like Ians suggestion.  I'm happy to trust that contributors know what
> > >constitutes good/bad content and what is/isn't worth sharing, and that
> we
> > >can go to the lists for the few times where confirmation is needed.
>  Fil,
> > >that okay with you?
> > >
> > >Another question, though: should we have templates for these types of
> > >posts?
> > >
> > >-Michal
> > >
> > >
> > >On Tue, Aug 6, 2013 at 2:48 PM, Ian Clelland <iclelland@chromium.org>
> > >wrote:
> > >
> > >> On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj <fil@adobe.com> wrote:
> > >>
> > >> > Will this mean we will be discussing blog post curation stuff on
> > >> > dev@cordova.apache.org ?
> > >>
> > >>
> > >> I hope that we can avoid a lot of that -- I'd hate for every potential
> > >> external contribution to come down to a discussion and vote on the
> > >>mailing
> > >> list.
> > >>
> > >> It might be good to have one person in charge of that section of the
> > >>site
> > >> -- someone responsible whom authors could email for exposure on the
> > >>Cordova
> > >> home page.
> > >>
> > >> If that's not possible, then I would suggest that anyone who currently
> > >>has
> > >> access to update the blog would also be able to publish external
> > >>postings.
> > >> If any problems arise, we can deal with them at the time. Obviously if
> > >> someone has a concern before publishing ("is this legit?", "is this
> spam
> > >> disguised as a blog post?"), then they could certainly run it past the
> > >> mailing list, but it shouldn't be a requirement most of the time.
> > >>
> > >> Ian
> > >>
> >
> >
>
>
> --
> Carlos Santana
> <csantana23@gmail.com>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message