You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Andrew Grieve <ag...@chromium.org> on 2013/08/06 16:41:49 UTC
Posting Blog Posts
Here's a draft of a "how to write a blog post". I intend to add this to the
website's README.md. Wanted to get some feedback / +1 since this is a
"process".
Writting a Blog 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 your post reviewed by at least one other committer
> 1. via http://reviews.apache.org.
> 2. Should be able to do this by running the "post-review" tool. If
> the tool is not working, upload the diff manually (via "svn diff > file",
> and be sure to add the "cordova" group to the review request).
> 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 `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 :).
Re: Posting Blog Posts
Posted by Carlos Santana <cs...@gmail.com>.
Andrew
I think that's a good compromise *"approved by at least one committer
other than*
*> yourself"*
On Thu, Aug 8, 2013 at 3:48 PM, Andrew Grieve <ag...@chromium.org> wrote:
> 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 <fi...@adobe.com> wrote:
> >
> > > SGTM
> > >
> > > On 8/6/13 11:57 AM, "Michal Mocny" <mm...@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 <ic...@chromium.org>
> > > >wrote:
> > > >
> > > >> On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj <fi...@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
> > <cs...@gmail.com>
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: Posting Blog Posts
Posted by Andrew Grieve <ag...@chromium.org>.
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 <cs...@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 <fi...@adobe.com> wrote:
>
> > SGTM
> >
> > On 8/6/13 11:57 AM, "Michal Mocny" <mm...@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 <ic...@chromium.org>
> > >wrote:
> > >
> > >> On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj <fi...@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
> <cs...@gmail.com>
>
Re: Posting Blog Posts
Posted by Carlos Santana <cs...@gmail.com>.
+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 <fi...@adobe.com> wrote:
> SGTM
>
> On 8/6/13 11:57 AM, "Michal Mocny" <mm...@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 <ic...@chromium.org>
> >wrote:
> >
> >> On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj <fi...@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
<cs...@gmail.com>
Re: Posting Blog Posts
Posted by Filip Maj <fi...@adobe.com>.
SGTM
On 8/6/13 11:57 AM, "Michal Mocny" <mm...@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 <ic...@chromium.org>
>wrote:
>
>> On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj <fi...@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
>>
Re: Posting Blog Posts
Posted by Michal Mocny <mm...@chromium.org>.
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 <ic...@chromium.org> wrote:
> On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj <fi...@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
>
Re: Posting Blog Posts
Posted by Ian Clelland <ic...@chromium.org>.
On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj <fi...@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
Re: Posting Blog Posts
Posted by Ken Wallis <kw...@blackberry.com>.
+1 as well. I plan to write some posts on BlackBerry and Cordova and a method to "link" would be great.
Sent from my BlackBerry 10 smartphone on the Bell network.
From: dgualdron@gmail.com
Sent: Tuesday, August 6, 2013 1:48 PM
To: dev@cordova.apache.org
Reply To: dev@cordova.apache.org
Subject: Re: Posting Blog Posts
+1
Sent from my BlackBerry® wireless device
-----Original Message-----
From: Tommy Williams <to...@devgeeks.org>
Date: Tue, 6 Aug 2013 10:46:15
To: <de...@cordova.apache.org>
Reply-To: dev@cordova.apache.org
Subject: Re: Posting Blog Posts
+1 from me as well.
I like the idea of official posts looking official as well as the side
effect of third party posts getting the traffic benefits.
- tommy
On 7 Aug 2013 03:44, "Ian Clelland" <ic...@chromium.org> wrote:
> +1. That's a good approach to separating them, and should encourage
> third-party authors to submit pieces -- knowing that Apache will drive
> traffic to their site.
>
>
>
>
> On Tue, Aug 6, 2013 at 1:35 PM, David Kemp <dr...@google.com> wrote:
>
> > +1 for Michals approach
> >
> >
> > On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > I'de like to make a proposal about how we go about publishing certain
> > blog
> > > posts. I think this is a good practice for Organizational-type blogs
> to
> > > clearly identify posts which are (1) genuinely origination from the
> > > organization, vs (2) those which are just being curated from within the
> > > community. This is already widely accepted practice on many other
> blogs
> > as
> > > well as on Twitter, and I think already the strategy that PhoneGap blog
> > > uses.
> > >
> > > Basically:
> > > (1) If the content has to do with cordova-core, i.e. announcing
> releases,
> > > or publishing guides, etc., we should publish the full text directly on
> > the
> > > cordova Blog (by whichever author), as-if written by the organization.
> > > (2) 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.
> > >
> > > I think this makes it both easier to identify those posts which are
> > really
> > > organizationally important, as well as giving us a way to post things
> > that
> > > otherwise maybe would not have made the cut.
> > >
> > > WDYT?
> > >
> > > -Michal
> > >
> > >
> > > On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > > > Here's a draft of a "how to write a blog post". I intend to add this
> to
> > > the
> > > > website's README.md. Wanted to get some feedback / +1 since this is a
> > > > "process".
> > > >
> > > > Writting a Blog 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 your post reviewed by at least one other committer
> > > > > 1. via http://reviews.apache.org.
> > > > > 2. Should be able to do this by running the "post-review"
> tool.
> > If
> > > > > the tool is not working, upload the diff manually (via "svn diff >
> > > file",
> > > > > and be sure to add the "cordova" group to the review request).
> > > > > 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 `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 :).
> > > >
> > >
> >
>
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Re: Posting Blog Posts
Posted by dg...@gmail.com.
+1
Sent from my BlackBerry® wireless device
-----Original Message-----
From: Tommy Williams <to...@devgeeks.org>
Date: Tue, 6 Aug 2013 10:46:15
To: <de...@cordova.apache.org>
Reply-To: dev@cordova.apache.org
Subject: Re: Posting Blog Posts
+1 from me as well.
I like the idea of official posts looking official as well as the side
effect of third party posts getting the traffic benefits.
- tommy
On 7 Aug 2013 03:44, "Ian Clelland" <ic...@chromium.org> wrote:
> +1. That's a good approach to separating them, and should encourage
> third-party authors to submit pieces -- knowing that Apache will drive
> traffic to their site.
>
>
>
>
> On Tue, Aug 6, 2013 at 1:35 PM, David Kemp <dr...@google.com> wrote:
>
> > +1 for Michals approach
> >
> >
> > On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > I'de like to make a proposal about how we go about publishing certain
> > blog
> > > posts. I think this is a good practice for Organizational-type blogs
> to
> > > clearly identify posts which are (1) genuinely origination from the
> > > organization, vs (2) those which are just being curated from within the
> > > community. This is already widely accepted practice on many other
> blogs
> > as
> > > well as on Twitter, and I think already the strategy that PhoneGap blog
> > > uses.
> > >
> > > Basically:
> > > (1) If the content has to do with cordova-core, i.e. announcing
> releases,
> > > or publishing guides, etc., we should publish the full text directly on
> > the
> > > cordova Blog (by whichever author), as-if written by the organization.
> > > (2) 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.
> > >
> > > I think this makes it both easier to identify those posts which are
> > really
> > > organizationally important, as well as giving us a way to post things
> > that
> > > otherwise maybe would not have made the cut.
> > >
> > > WDYT?
> > >
> > > -Michal
> > >
> > >
> > > On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > > > Here's a draft of a "how to write a blog post". I intend to add this
> to
> > > the
> > > > website's README.md. Wanted to get some feedback / +1 since this is a
> > > > "process".
> > > >
> > > > Writting a Blog 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 your post reviewed by at least one other committer
> > > > > 1. via http://reviews.apache.org.
> > > > > 2. Should be able to do this by running the "post-review"
> tool.
> > If
> > > > > the tool is not working, upload the diff manually (via "svn diff >
> > > file",
> > > > > and be sure to add the "cordova" group to the review request).
> > > > > 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 `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 :).
> > > >
> > >
> >
>
Re: Posting Blog Posts
Posted by Filip Maj <fi...@adobe.com>.
Will this mean we will be discussing blog post curation stuff on
dev@cordova.apache.org ?
On 8/6/13 10:46 AM, "Tommy Williams" <to...@devgeeks.org> wrote:
>+1 from me as well.
>
>I like the idea of official posts looking official as well as the side
>effect of third party posts getting the traffic benefits.
>
>- tommy
>On 7 Aug 2013 03:44, "Ian Clelland" <ic...@chromium.org> wrote:
>
>> +1. That's a good approach to separating them, and should encourage
>> third-party authors to submit pieces -- knowing that Apache will drive
>> traffic to their site.
>>
>>
>>
>>
>> On Tue, Aug 6, 2013 at 1:35 PM, David Kemp <dr...@google.com> wrote:
>>
>> > +1 for Michals approach
>> >
>> >
>> > On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny <mm...@chromium.org>
>> wrote:
>> >
>> > > I'de like to make a proposal about how we go about publishing
>>certain
>> > blog
>> > > posts. I think this is a good practice for Organizational-type
>>blogs
>> to
>> > > clearly identify posts which are (1) genuinely origination from the
>> > > organization, vs (2) those which are just being curated from within
>>the
>> > > community. This is already widely accepted practice on many other
>> blogs
>> > as
>> > > well as on Twitter, and I think already the strategy that PhoneGap
>>blog
>> > > uses.
>> > >
>> > > Basically:
>> > > (1) If the content has to do with cordova-core, i.e. announcing
>> releases,
>> > > or publishing guides, etc., we should publish the full text
>>directly on
>> > the
>> > > cordova Blog (by whichever author), as-if written by the
>>organization.
>> > > (2) 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.
>> > >
>> > > I think this makes it both easier to identify those posts which are
>> > really
>> > > organizationally important, as well as giving us a way to post
>>things
>> > that
>> > > otherwise maybe would not have made the cut.
>> > >
>> > > WDYT?
>> > >
>> > > -Michal
>> > >
>> > >
>> > > On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve
>><ag...@chromium.org>
>> > > wrote:
>> > >
>> > > > Here's a draft of a "how to write a blog post". I intend to add
>>this
>> to
>> > > the
>> > > > website's README.md. Wanted to get some feedback / +1 since this
>>is a
>> > > > "process".
>> > > >
>> > > > Writting a Blog 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 your post reviewed by at least one other committer
>> > > > > 1. via http://reviews.apache.org.
>> > > > > 2. Should be able to do this by running the "post-review"
>> tool.
>> > If
>> > > > > the tool is not working, upload the diff manually (via "svn
>>diff >
>> > > file",
>> > > > > and be sure to add the "cordova" group to the review request).
>> > > > > 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 `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 :).
>> > > >
>> > >
>> >
>>
Re: Posting Blog Posts
Posted by Tommy Williams <to...@devgeeks.org>.
+1 from me as well.
I like the idea of official posts looking official as well as the side
effect of third party posts getting the traffic benefits.
- tommy
On 7 Aug 2013 03:44, "Ian Clelland" <ic...@chromium.org> wrote:
> +1. That's a good approach to separating them, and should encourage
> third-party authors to submit pieces -- knowing that Apache will drive
> traffic to their site.
>
>
>
>
> On Tue, Aug 6, 2013 at 1:35 PM, David Kemp <dr...@google.com> wrote:
>
> > +1 for Michals approach
> >
> >
> > On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > I'de like to make a proposal about how we go about publishing certain
> > blog
> > > posts. I think this is a good practice for Organizational-type blogs
> to
> > > clearly identify posts which are (1) genuinely origination from the
> > > organization, vs (2) those which are just being curated from within the
> > > community. This is already widely accepted practice on many other
> blogs
> > as
> > > well as on Twitter, and I think already the strategy that PhoneGap blog
> > > uses.
> > >
> > > Basically:
> > > (1) If the content has to do with cordova-core, i.e. announcing
> releases,
> > > or publishing guides, etc., we should publish the full text directly on
> > the
> > > cordova Blog (by whichever author), as-if written by the organization.
> > > (2) 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.
> > >
> > > I think this makes it both easier to identify those posts which are
> > really
> > > organizationally important, as well as giving us a way to post things
> > that
> > > otherwise maybe would not have made the cut.
> > >
> > > WDYT?
> > >
> > > -Michal
> > >
> > >
> > > On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > > > Here's a draft of a "how to write a blog post". I intend to add this
> to
> > > the
> > > > website's README.md. Wanted to get some feedback / +1 since this is a
> > > > "process".
> > > >
> > > > Writting a Blog 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 your post reviewed by at least one other committer
> > > > > 1. via http://reviews.apache.org.
> > > > > 2. Should be able to do this by running the "post-review"
> tool.
> > If
> > > > > the tool is not working, upload the diff manually (via "svn diff >
> > > file",
> > > > > and be sure to add the "cordova" group to the review request).
> > > > > 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 `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 :).
> > > >
> > >
> >
>
Re: Posting Blog Posts
Posted by Ian Clelland <ic...@chromium.org>.
+1. That's a good approach to separating them, and should encourage
third-party authors to submit pieces -- knowing that Apache will drive
traffic to their site.
On Tue, Aug 6, 2013 at 1:35 PM, David Kemp <dr...@google.com> wrote:
> +1 for Michals approach
>
>
> On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny <mm...@chromium.org> wrote:
>
> > I'de like to make a proposal about how we go about publishing certain
> blog
> > posts. I think this is a good practice for Organizational-type blogs to
> > clearly identify posts which are (1) genuinely origination from the
> > organization, vs (2) those which are just being curated from within the
> > community. This is already widely accepted practice on many other blogs
> as
> > well as on Twitter, and I think already the strategy that PhoneGap blog
> > uses.
> >
> > Basically:
> > (1) If the content has to do with cordova-core, i.e. announcing releases,
> > or publishing guides, etc., we should publish the full text directly on
> the
> > cordova Blog (by whichever author), as-if written by the organization.
> > (2) 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.
> >
> > I think this makes it both easier to identify those posts which are
> really
> > organizationally important, as well as giving us a way to post things
> that
> > otherwise maybe would not have made the cut.
> >
> > WDYT?
> >
> > -Michal
> >
> >
> > On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > Here's a draft of a "how to write a blog post". I intend to add this to
> > the
> > > website's README.md. Wanted to get some feedback / +1 since this is a
> > > "process".
> > >
> > > Writting a Blog 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 your post reviewed by at least one other committer
> > > > 1. via http://reviews.apache.org.
> > > > 2. Should be able to do this by running the "post-review" tool.
> If
> > > > the tool is not working, upload the diff manually (via "svn diff >
> > file",
> > > > and be sure to add the "cordova" group to the review request).
> > > > 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 `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 :).
> > >
> >
>
Re: Posting Blog Posts
Posted by David Kemp <dr...@google.com>.
+1 for Michals approach
On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny <mm...@chromium.org> wrote:
> I'de like to make a proposal about how we go about publishing certain blog
> posts. I think this is a good practice for Organizational-type blogs to
> clearly identify posts which are (1) genuinely origination from the
> organization, vs (2) those which are just being curated from within the
> community. This is already widely accepted practice on many other blogs as
> well as on Twitter, and I think already the strategy that PhoneGap blog
> uses.
>
> Basically:
> (1) If the content has to do with cordova-core, i.e. announcing releases,
> or publishing guides, etc., we should publish the full text directly on the
> cordova Blog (by whichever author), as-if written by the organization.
> (2) 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.
>
> I think this makes it both easier to identify those posts which are really
> organizationally important, as well as giving us a way to post things that
> otherwise maybe would not have made the cut.
>
> WDYT?
>
> -Michal
>
>
> On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Here's a draft of a "how to write a blog post". I intend to add this to
> the
> > website's README.md. Wanted to get some feedback / +1 since this is a
> > "process".
> >
> > Writting a Blog 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 your post reviewed by at least one other committer
> > > 1. via http://reviews.apache.org.
> > > 2. Should be able to do this by running the "post-review" tool. If
> > > the tool is not working, upload the diff manually (via "svn diff >
> file",
> > > and be sure to add the "cordova" group to the review request).
> > > 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 `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 :).
> >
>
Re: Posting Blog Posts
Posted by Michal Mocny <mm...@chromium.org>.
I'de like to make a proposal about how we go about publishing certain blog
posts. I think this is a good practice for Organizational-type blogs to
clearly identify posts which are (1) genuinely origination from the
organization, vs (2) those which are just being curated from within the
community. This is already widely accepted practice on many other blogs as
well as on Twitter, and I think already the strategy that PhoneGap blog
uses.
Basically:
(1) If the content has to do with cordova-core, i.e. announcing releases,
or publishing guides, etc., we should publish the full text directly on the
cordova Blog (by whichever author), as-if written by the organization.
(2) 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.
I think this makes it both easier to identify those posts which are really
organizationally important, as well as giving us a way to post things that
otherwise maybe would not have made the cut.
WDYT?
-Michal
On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve <ag...@chromium.org> wrote:
> Here's a draft of a "how to write a blog post". I intend to add this to the
> website's README.md. Wanted to get some feedback / +1 since this is a
> "process".
>
> Writting a Blog 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 your post reviewed by at least one other committer
> > 1. via http://reviews.apache.org.
> > 2. Should be able to do this by running the "post-review" tool. If
> > the tool is not working, upload the diff manually (via "svn diff > file",
> > and be sure to add the "cordova" group to the review request).
> > 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 `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 :).
>