You are viewing a plain text version of this content. The canonical link for it is here.
Posted to marketing@couchdb.apache.org by Alexander Shorin <kx...@gmail.com> on 2014/04/08 13:59:47 UTC

Provide short annotation for shared posts

Hello,

Recently shared blog posts on G+ starts and ends with the next words:

> New blog post!
> Roll up, roll up. Read all about it!
> Roll up, roll up. Read all about it. Get your copy of the CouchDB Weekly News, March 2
> New post by +Andreas Wenk!
> Woo hoo! See you there!

https://plus.google.com/u/0/109226482722655790973/posts

These reminds me old good 90x with NEW! HOT! links, blinking colorful
texts, marquee magic and a lot of animation on the page. Suddenly,
these good old times had gone away, so could we please provide some
more information about shared items? Technically, this should be first
paragraph from shared post which included the main idea of all the
text, but there is a lot of space for improvisation to highlight the
idea.

I understand reasons about having some short description there: it's
easy to copy-paste news between twitter / reddit / g+ and others
without care about text size limitation, but we should respect
community rules: what's good for twitter, may be not for g+ and fb and
if we have a chance to provide more text, the interesting intro to our
news that would be more attractive for newcomers and respectful for
the people who don't want waste their time on things in the web with
crying titles.

In our information age it's very easy to produce and share
information. To manage this huge stream of information everyone sets
own inner filter to ignore all the trash and catch up only interesting
bits. Suddenly, our current news stream on g+ is a trash with no
useful bits. It could be better, it could be interesting.

When you're walking at night and looking on the sky you see thousands
stars there. If the new one will raise there you would never notice
that. You'll probably wouldn't spend more than 5 minutes looking on
them. However, if only you had an Augment Reality device which would
show a short description for every star in the focus and highlight the
new ones, I bet sky-watching process would be more interesting for you
and will lasts not a single hour.

Let's make our posts on communities better to attract [more] people
and raise the discussion around. Let's annotate our stars.

Thanks.

--
,,,^..^,,,

Re: Provide short annotation for shared posts

Posted by Noah Slater <ns...@apache.org>.
Actually, to put it more into context...

You (sorry to pick on you) just posted:

> CouchDB and the Heartbleed SSL/TLS Vulnerability:

> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl

> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
> blogs.apache.org

Notice how the second title is provided by Google+. So I don't
understand why you're duplicating the title in the description. Now we
have it twice. Looks silly.

You also include a raw URL, which looks ugly. You can share URLs as
links and they are hidden. :)

Compare to the last thing I posted:

> New blog post!
> The Little Things(1): Do Not Delete : CouchDB
> blogs.apache.org

Or:

> Roll up, roll up. Read all about it!
> CouchDB Weekly News, April 3 : CouchDB
> blogs.apache.org

Or:

> New post by +Andreas Wenk 
> On The CouchDB Community : CouchDB
> blogs.apache.org

These are just the ones you picked out. I think if you include the
additional text there, they don't look so bad at all.

Note also: there are plenty of posts we have where we're pulling
quotes, and so on.

Such as:

> "CouchDB has hit the big time[...] NoSQL as a product category is about to be tested." http://buff.ly/1gtxzEd
> IBM & Cloudant: Chapter One of NoSQL - The Orchestrate Blog
> orchestrate.io


On 8 April 2014 13:59, Alexander Shorin <kx...@gmail.com> wrote:
> Hello,
>
> Recently shared blog posts on G+ starts and ends with the next words:
>
>> New blog post!
>> Roll up, roll up. Read all about it!
>> Roll up, roll up. Read all about it. Get your copy of the CouchDB Weekly News, March 2
>> New post by +Andreas Wenk!
>> Woo hoo! See you there!
>
> https://plus.google.com/u/0/109226482722655790973/posts
>
> These reminds me old good 90x with NEW! HOT! links, blinking colorful
> texts, marquee magic and a lot of animation on the page. Suddenly,
> these good old times had gone away, so could we please provide some
> more information about shared items? Technically, this should be first
> paragraph from shared post which included the main idea of all the
> text, but there is a lot of space for improvisation to highlight the
> idea.
>
> I understand reasons about having some short description there: it's
> easy to copy-paste news between twitter / reddit / g+ and others
> without care about text size limitation, but we should respect
> community rules: what's good for twitter, may be not for g+ and fb and
> if we have a chance to provide more text, the interesting intro to our
> news that would be more attractive for newcomers and respectful for
> the people who don't want waste their time on things in the web with
> crying titles.
>
> In our information age it's very easy to produce and share
> information. To manage this huge stream of information everyone sets
> own inner filter to ignore all the trash and catch up only interesting
> bits. Suddenly, our current news stream on g+ is a trash with no
> useful bits. It could be better, it could be interesting.
>
> When you're walking at night and looking on the sky you see thousands
> stars there. If the new one will raise there you would never notice
> that. You'll probably wouldn't spend more than 5 minutes looking on
> them. However, if only you had an Augment Reality device which would
> show a short description for every star in the focus and highlight the
> new ones, I bet sky-watching process would be more interesting for you
> and will lasts not a single hour.
>
> Let's make our posts on communities better to attract [more] people
> and raise the discussion around. Let's annotate our stars.
>
> Thanks.
>
> --
> ,,,^..^,,,



-- 
Noah Slater
https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Noah Slater <ns...@apache.org>.
Okay, so, lemme get this straight... :)

Decision tree:

1. Can a pull quote be provided?

Yes: Provide it, and share the link.

No: ... I'm confused on this one.

I see it that we have two options:

a) Repeat the post title

(But why would we do this, when the post title is clearly visible in
the Google+ card.)

b) Provide no description at all

And it seems like you're saying we shouldn't do:

c) Provide superfluous text like "Check out this post"

P.S. Sorry for mixing you up with Andy... Heh.

On 8 April 2014 18:17, Alexander Shorin <kx...@gmail.com> wrote:
> On Tue, Apr 8, 2014 at 8:07 PM, Noah Slater <ns...@apache.org> wrote:
>> I'm the one who posts to Google+ and uses very short descriptions. All
>> I'm doing is posting a link. Like when you submit a link to HN or
>> Reddit.
>
> Their format matches "just share the url" pattern so it's ok for them
> and having sweet and attractive title is the important.
>
>> Is it common to provide a precis for shared links on Google+?
>
> Yes, by two reasons:
>
> 1. G+ doesn't allows you to set your own custom URL title that may be
> more sweet than default one. Sometimes that's a big issue.
> 2. Providing short intro is always better than just post an URL
> without it. It's additional vector to attract the people, it makes the
> post informative and more interesting. Plus better have solid intro or
> nothing than just "Checkout the post there!", imho.
>
> If service provides such opportunity, it's better use it. For better marketing.
>
> --
> ,,,^..^,,,



-- 
Noah Slater
https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Alexander Shorin <kx...@gmail.com>.
On Tue, Apr 8, 2014 at 8:07 PM, Noah Slater <ns...@apache.org> wrote:
> I'm the one who posts to Google+ and uses very short descriptions. All
> I'm doing is posting a link. Like when you submit a link to HN or
> Reddit.

Their format matches "just share the url" pattern so it's ok for them
and having sweet and attractive title is the important.

> Is it common to provide a precis for shared links on Google+?

Yes, by two reasons:

1. G+ doesn't allows you to set your own custom URL title that may be
more sweet than default one. Sometimes that's a big issue.
2. Providing short intro is always better than just post an URL
without it. It's additional vector to attract the people, it makes the
post informative and more interesting. Plus better have solid intro or
nothing than just "Checkout the post there!", imho.

If service provides such opportunity, it's better use it. For better marketing.

--
,,,^..^,,,

Re: Provide short annotation for shared posts

Posted by Noah Slater <ns...@apache.org>.
I'm the one who posts to Google+ and uses very short descriptions. All
I'm doing is posting a link. Like when you submit a link to HN or
Reddit.

Is it common to provide a precis for shared links on Google+?

On 8 April 2014 13:59, Alexander Shorin <kx...@gmail.com> wrote:
> Hello,
>
> Recently shared blog posts on G+ starts and ends with the next words:
>
>> New blog post!
>> Roll up, roll up. Read all about it!
>> Roll up, roll up. Read all about it. Get your copy of the CouchDB Weekly News, March 2
>> New post by +Andreas Wenk!
>> Woo hoo! See you there!
>
> https://plus.google.com/u/0/109226482722655790973/posts
>
> These reminds me old good 90x with NEW! HOT! links, blinking colorful
> texts, marquee magic and a lot of animation on the page. Suddenly,
> these good old times had gone away, so could we please provide some
> more information about shared items? Technically, this should be first
> paragraph from shared post which included the main idea of all the
> text, but there is a lot of space for improvisation to highlight the
> idea.
>
> I understand reasons about having some short description there: it's
> easy to copy-paste news between twitter / reddit / g+ and others
> without care about text size limitation, but we should respect
> community rules: what's good for twitter, may be not for g+ and fb and
> if we have a chance to provide more text, the interesting intro to our
> news that would be more attractive for newcomers and respectful for
> the people who don't want waste their time on things in the web with
> crying titles.
>
> In our information age it's very easy to produce and share
> information. To manage this huge stream of information everyone sets
> own inner filter to ignore all the trash and catch up only interesting
> bits. Suddenly, our current news stream on g+ is a trash with no
> useful bits. It could be better, it could be interesting.
>
> When you're walking at night and looking on the sky you see thousands
> stars there. If the new one will raise there you would never notice
> that. You'll probably wouldn't spend more than 5 minutes looking on
> them. However, if only you had an Augment Reality device which would
> show a short description for every star in the focus and highlight the
> new ones, I bet sky-watching process would be more interesting for you
> and will lasts not a single hour.
>
> Let's make our posts on communities better to attract [more] people
> and raise the discussion around. Let's annotate our stars.
>
> Thanks.
>
> --
> ,,,^..^,,,



-- 
Noah Slater
https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Noah Slater <ns...@apache.org>.
Yep!

On 10 April 2014 10:39, Andy Wenk <an...@nms.de> wrote:
> wouldn't this be a good place to add the guide:
>
> https://cwiki.apache.org/confluence/display/COUCHDB/Marketing
>
> ?
>
> Cheers
>
> Andy
>
>
> On 10 April 2014 10:23, Noah Slater <ns...@apache.org> wrote:
>
>> Okay Alexander. Thanks for doing that. I get the picture now! I've
>> updated the release procedure with some notes. But we really need to
>> spin this stuff off into a separate marketing/promotion guide.
>>
>> On 9 April 2014 18:40, Alexander Shorin <kx...@gmail.com> wrote:
>> > Sure I would. Suddenly, I started stop-the-world garbage collector in
>> > my house< so I'm a little bit out of my workspace, access to IM server
>> > and time for other deals, but I'd done with the most recent posts on
>> > G+. You could check them for now, I'll finish the others later at
>> > night.
>> > --
>> > ,,,^..^,,,
>> >
>> >
>> > On Wed, Apr 9, 2014 at 4:03 PM, Noah Slater <ns...@apache.org> wrote:
>> >> Okay, thanks! Lemme know when you're done. *Gonna eat ur brain and
>> >> gain ur knowledge*
>> >>
>> >> On 8 April 2014 19:30, Alexander Shorin <kx...@gmail.com> wrote:
>> >>> Ok, would make a try. No need to setup admin for G+ - I already has
>> that bit.
>> >>> --
>> >>> ,,,^..^,,,
>> >>>
>> >>>
>> >>> On Tue, Apr 8, 2014 at 9:03 PM, Noah Slater <ns...@apache.org>
>> wrote:
>> >>>> Here's something: do you fancy going through through our existing
>> >>>> posts and adding useful descriptions?
>> >>>>
>> >>>> That'd be really handy for me to see how you're doing it.
>> >>>>
>> >>>> I'll set you up as an admin if you're not already.
>> >>>>
>> >>>> On 8 April 2014 18:36, Alexander Shorin <kx...@gmail.com> wrote:
>> >>>>> Unless there is nothing to say with your own words to summarize the
>> >>>>> content and URL's title is quite informative, imho, yes, better leave
>> >>>>> it empty.
>> >>>>> --
>> >>>>> ,,,^..^,,,
>> >>>>>
>> >>>>>
>> >>>>> On Tue, Apr 8, 2014 at 8:32 PM, Noah Slater <ns...@apache.org>
>> wrote:
>> >>>>>> What about when there's nothing to pull quote. Just leave it blank?
>> >>>>>>
>> >>>>>> On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
>> >>>>>>> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org>
>> wrote:
>> >>>>>>>> Can you provide an example of how you'd share the weekly news?
>> >>>>>>>
>> >>>>>>> Sure.
>> >>>>>>>
>> >>>>>>> Instead of:
>> >>>>>>>
>> >>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
>> >>>>>>>>
>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>> >>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>> >>>>>>>> blogs.apache.org
>> >>>>>>>
>> >>>>>>> Use:
>> >>>>>>>
>> >>>>>>>> *IMPORTANT*
>> >>>>>>>> You may or may not have heard about the Heartbleed SSL/TLS
>> Vulnerability yet (http://heartbleed.com).
>> >>>>>>>> Without much exaggeration, this is a big one.
>> >>>>>>>>
>> >>>>>>>> In this post we prepared the instruction how to fix the issue in
>> context of CouchDB usage.
>> >>>>>>>>
>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>> >>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>> >>>>>>>> blogs.apache.org
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Instead of:
>> >>>>>>>
>> >>>>>>>> New blog post!
>> >>>>>>>> The Little Things(1): Do Not Delete : CouchDB
>> >>>>>>>> blogs.apache.org
>> >>>>>>>
>> >>>>>>> Use:
>> >>>>>>>
>> >>>>>>>> *The Little Things(1): Do Not Delete*
>> >>>>>>>> _CouchDB takes data storage extremely seriously. This usually
>> means we work hard to make sure that the CouchDB storage modules are as
>> robust as we can make them. Sometimes though, we go all the way to the HTTP
>> API to secure against accidental data loss, saving users from their
>> mistakes, rather than dealing with hard drives and kernel caches that
>> usually stand in the way of safe data storage._
>> >>>>>>>> _In this post you'll know how to DELETE method works and how
>> CouchDB protects you from accidental mistakes._
>> >>>>>>>> The Little Things(1): Do Not Delete : CouchDB
>> >>>>>>>> blogs.apache.org
>> >>>>>>>
>> >>>>>>> Copying some content from the article shows the topic of
>> discussion.
>> >>>>>>> It's not about "Don't delete CouchDB from your system", it's
>> exactly
>> >>>>>>> about dealing with Document deletion.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Instead of:
>> >>>>>>>
>> >>>>>>>> Roll up, roll up. Read all about it!
>> >>>>>>>> CouchDB Weekly News, April 3 : CouchDB
>> >>>>>>>> blogs.apache.org
>> >>>>>>>
>> >>>>>>> Use:
>> >>>>>>>
>> >>>>>>>> *CouchDB Weekly News, April 3*
>> >>>>>>>> In this article you'll know:
>> >>>>>>>> - How to import CSV to CouchDB using Python-Cloudant module
>> >>>>>>>> - How to setup multiple instances of CouchDB on OS X
>> >>>>>>>> - Proposals for 1.6 release and the results of voting for 1.5.1
>> >>>>>>>> - How to Displaying a million DNA barcodes
>> >>>>>>>>
>> >>>>>>>> And also latest news from PouchDB, NPM and Cloudant and even
>> more. Check it up!
>> >>>>>>>> CouchDB Weekly News, April 3 : CouchDB
>> >>>>>>>> blogs.apache.org
>> >>>>>>>
>> >>>>>>> And so on, and so forth. Short intro looks more attractive, don't
>> it?
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> ,,,^..^,,,
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Noah Slater
>> >>>>>> https://twitter.com/nslater
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Noah Slater
>> >>>> https://twitter.com/nslater
>> >>
>> >>
>> >>
>> >> --
>> >> Noah Slater
>> >> https://twitter.com/nslater
>>
>>
>>
>> --
>> Noah Slater
>> https://twitter.com/nslater
>>
>
>
>
> --
> Andy Wenk
> Hamburg - Germany
> RockIt!
>
> http://www.couchdb-buch.de
> http://www.pg-praxisbuch.de
>
> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
>
> https://people.apache.org/keys/committer/andywenk.asc



-- 
Noah Slater
https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Andy Wenk <an...@nms.de>.
wouldn't this be a good place to add the guide:

https://cwiki.apache.org/confluence/display/COUCHDB/Marketing

?

Cheers

Andy


On 10 April 2014 10:23, Noah Slater <ns...@apache.org> wrote:

> Okay Alexander. Thanks for doing that. I get the picture now! I've
> updated the release procedure with some notes. But we really need to
> spin this stuff off into a separate marketing/promotion guide.
>
> On 9 April 2014 18:40, Alexander Shorin <kx...@gmail.com> wrote:
> > Sure I would. Suddenly, I started stop-the-world garbage collector in
> > my house< so I'm a little bit out of my workspace, access to IM server
> > and time for other deals, but I'd done with the most recent posts on
> > G+. You could check them for now, I'll finish the others later at
> > night.
> > --
> > ,,,^..^,,,
> >
> >
> > On Wed, Apr 9, 2014 at 4:03 PM, Noah Slater <ns...@apache.org> wrote:
> >> Okay, thanks! Lemme know when you're done. *Gonna eat ur brain and
> >> gain ur knowledge*
> >>
> >> On 8 April 2014 19:30, Alexander Shorin <kx...@gmail.com> wrote:
> >>> Ok, would make a try. No need to setup admin for G+ - I already has
> that bit.
> >>> --
> >>> ,,,^..^,,,
> >>>
> >>>
> >>> On Tue, Apr 8, 2014 at 9:03 PM, Noah Slater <ns...@apache.org>
> wrote:
> >>>> Here's something: do you fancy going through through our existing
> >>>> posts and adding useful descriptions?
> >>>>
> >>>> That'd be really handy for me to see how you're doing it.
> >>>>
> >>>> I'll set you up as an admin if you're not already.
> >>>>
> >>>> On 8 April 2014 18:36, Alexander Shorin <kx...@gmail.com> wrote:
> >>>>> Unless there is nothing to say with your own words to summarize the
> >>>>> content and URL's title is quite informative, imho, yes, better leave
> >>>>> it empty.
> >>>>> --
> >>>>> ,,,^..^,,,
> >>>>>
> >>>>>
> >>>>> On Tue, Apr 8, 2014 at 8:32 PM, Noah Slater <ns...@apache.org>
> wrote:
> >>>>>> What about when there's nothing to pull quote. Just leave it blank?
> >>>>>>
> >>>>>> On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
> >>>>>>> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org>
> wrote:
> >>>>>>>> Can you provide an example of how you'd share the weekly news?
> >>>>>>>
> >>>>>>> Sure.
> >>>>>>>
> >>>>>>> Instead of:
> >>>>>>>
> >>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
> >>>>>>>>
> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
> >>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
> >>>>>>>> blogs.apache.org
> >>>>>>>
> >>>>>>> Use:
> >>>>>>>
> >>>>>>>> *IMPORTANT*
> >>>>>>>> You may or may not have heard about the Heartbleed SSL/TLS
> Vulnerability yet (http://heartbleed.com).
> >>>>>>>> Without much exaggeration, this is a big one.
> >>>>>>>>
> >>>>>>>> In this post we prepared the instruction how to fix the issue in
> context of CouchDB usage.
> >>>>>>>>
> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
> >>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
> >>>>>>>> blogs.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>> Instead of:
> >>>>>>>
> >>>>>>>> New blog post!
> >>>>>>>> The Little Things(1): Do Not Delete : CouchDB
> >>>>>>>> blogs.apache.org
> >>>>>>>
> >>>>>>> Use:
> >>>>>>>
> >>>>>>>> *The Little Things(1): Do Not Delete*
> >>>>>>>> _CouchDB takes data storage extremely seriously. This usually
> means we work hard to make sure that the CouchDB storage modules are as
> robust as we can make them. Sometimes though, we go all the way to the HTTP
> API to secure against accidental data loss, saving users from their
> mistakes, rather than dealing with hard drives and kernel caches that
> usually stand in the way of safe data storage._
> >>>>>>>> _In this post you'll know how to DELETE method works and how
> CouchDB protects you from accidental mistakes._
> >>>>>>>> The Little Things(1): Do Not Delete : CouchDB
> >>>>>>>> blogs.apache.org
> >>>>>>>
> >>>>>>> Copying some content from the article shows the topic of
> discussion.
> >>>>>>> It's not about "Don't delete CouchDB from your system", it's
> exactly
> >>>>>>> about dealing with Document deletion.
> >>>>>>>
> >>>>>>>
> >>>>>>> Instead of:
> >>>>>>>
> >>>>>>>> Roll up, roll up. Read all about it!
> >>>>>>>> CouchDB Weekly News, April 3 : CouchDB
> >>>>>>>> blogs.apache.org
> >>>>>>>
> >>>>>>> Use:
> >>>>>>>
> >>>>>>>> *CouchDB Weekly News, April 3*
> >>>>>>>> In this article you'll know:
> >>>>>>>> - How to import CSV to CouchDB using Python-Cloudant module
> >>>>>>>> - How to setup multiple instances of CouchDB on OS X
> >>>>>>>> - Proposals for 1.6 release and the results of voting for 1.5.1
> >>>>>>>> - How to Displaying a million DNA barcodes
> >>>>>>>>
> >>>>>>>> And also latest news from PouchDB, NPM and Cloudant and even
> more. Check it up!
> >>>>>>>> CouchDB Weekly News, April 3 : CouchDB
> >>>>>>>> blogs.apache.org
> >>>>>>>
> >>>>>>> And so on, and so forth. Short intro looks more attractive, don't
> it?
> >>>>>>>
> >>>>>>> --
> >>>>>>> ,,,^..^,,,
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Noah Slater
> >>>>>> https://twitter.com/nslater
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Noah Slater
> >>>> https://twitter.com/nslater
> >>
> >>
> >>
> >> --
> >> Noah Slater
> >> https://twitter.com/nslater
>
>
>
> --
> Noah Slater
> https://twitter.com/nslater
>



-- 
Andy Wenk
Hamburg - Germany
RockIt!

http://www.couchdb-buch.de
http://www.pg-praxisbuch.de

GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588

https://people.apache.org/keys/committer/andywenk.asc

Re: Provide short annotation for shared posts

Posted by Noah Slater <ns...@apache.org>.
Okay Alexander. Thanks for doing that. I get the picture now! I've
updated the release procedure with some notes. But we really need to
spin this stuff off into a separate marketing/promotion guide.

On 9 April 2014 18:40, Alexander Shorin <kx...@gmail.com> wrote:
> Sure I would. Suddenly, I started stop-the-world garbage collector in
> my house< so I'm a little bit out of my workspace, access to IM server
> and time for other deals, but I'd done with the most recent posts on
> G+. You could check them for now, I'll finish the others later at
> night.
> --
> ,,,^..^,,,
>
>
> On Wed, Apr 9, 2014 at 4:03 PM, Noah Slater <ns...@apache.org> wrote:
>> Okay, thanks! Lemme know when you're done. *Gonna eat ur brain and
>> gain ur knowledge*
>>
>> On 8 April 2014 19:30, Alexander Shorin <kx...@gmail.com> wrote:
>>> Ok, would make a try. No need to setup admin for G+ - I already has that bit.
>>> --
>>> ,,,^..^,,,
>>>
>>>
>>> On Tue, Apr 8, 2014 at 9:03 PM, Noah Slater <ns...@apache.org> wrote:
>>>> Here's something: do you fancy going through through our existing
>>>> posts and adding useful descriptions?
>>>>
>>>> That'd be really handy for me to see how you're doing it.
>>>>
>>>> I'll set you up as an admin if you're not already.
>>>>
>>>> On 8 April 2014 18:36, Alexander Shorin <kx...@gmail.com> wrote:
>>>>> Unless there is nothing to say with your own words to summarize the
>>>>> content and URL's title is quite informative, imho, yes, better leave
>>>>> it empty.
>>>>> --
>>>>> ,,,^..^,,,
>>>>>
>>>>>
>>>>> On Tue, Apr 8, 2014 at 8:32 PM, Noah Slater <ns...@apache.org> wrote:
>>>>>> What about when there's nothing to pull quote. Just leave it blank?
>>>>>>
>>>>>> On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
>>>>>>> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org> wrote:
>>>>>>>> Can you provide an example of how you'd share the weekly news?
>>>>>>>
>>>>>>> Sure.
>>>>>>>
>>>>>>> Instead of:
>>>>>>>
>>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
>>>>>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>>>>>> blogs.apache.org
>>>>>>>
>>>>>>> Use:
>>>>>>>
>>>>>>>> *IMPORTANT*
>>>>>>>> You may or may not have heard about the Heartbleed SSL/TLS Vulnerability yet (http://heartbleed.com).
>>>>>>>> Without much exaggeration, this is a big one.
>>>>>>>>
>>>>>>>> In this post we prepared the instruction how to fix the issue in context of CouchDB usage.
>>>>>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>>>>>> blogs.apache.org
>>>>>>>
>>>>>>>
>>>>>>> Instead of:
>>>>>>>
>>>>>>>> New blog post!
>>>>>>>> The Little Things(1): Do Not Delete : CouchDB
>>>>>>>> blogs.apache.org
>>>>>>>
>>>>>>> Use:
>>>>>>>
>>>>>>>> *The Little Things(1): Do Not Delete*
>>>>>>>> _CouchDB takes data storage extremely seriously. This usually means we work hard to make sure that the CouchDB storage modules are as robust as we can make them. Sometimes though, we go all the way to the HTTP API to secure against accidental data loss, saving users from their mistakes, rather than dealing with hard drives and kernel caches that usually stand in the way of safe data storage._
>>>>>>>> _In this post you'll know how to DELETE method works and how CouchDB protects you from accidental mistakes._
>>>>>>>> The Little Things(1): Do Not Delete : CouchDB
>>>>>>>> blogs.apache.org
>>>>>>>
>>>>>>> Copying some content from the article shows the topic of discussion.
>>>>>>> It's not about "Don't delete CouchDB from your system", it's exactly
>>>>>>> about dealing with Document deletion.
>>>>>>>
>>>>>>>
>>>>>>> Instead of:
>>>>>>>
>>>>>>>> Roll up, roll up. Read all about it!
>>>>>>>> CouchDB Weekly News, April 3 : CouchDB
>>>>>>>> blogs.apache.org
>>>>>>>
>>>>>>> Use:
>>>>>>>
>>>>>>>> *CouchDB Weekly News, April 3*
>>>>>>>> In this article you'll know:
>>>>>>>> - How to import CSV to CouchDB using Python-Cloudant module
>>>>>>>> - How to setup multiple instances of CouchDB on OS X
>>>>>>>> - Proposals for 1.6 release and the results of voting for 1.5.1
>>>>>>>> - How to Displaying a million DNA barcodes
>>>>>>>>
>>>>>>>> And also latest news from PouchDB, NPM and Cloudant and even more. Check it up!
>>>>>>>> CouchDB Weekly News, April 3 : CouchDB
>>>>>>>> blogs.apache.org
>>>>>>>
>>>>>>> And so on, and so forth. Short intro looks more attractive, don't it?
>>>>>>>
>>>>>>> --
>>>>>>> ,,,^..^,,,
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Noah Slater
>>>>>> https://twitter.com/nslater
>>>>
>>>>
>>>>
>>>> --
>>>> Noah Slater
>>>> https://twitter.com/nslater
>>
>>
>>
>> --
>> Noah Slater
>> https://twitter.com/nslater



-- 
Noah Slater
https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Andy Wenk <an...@nms.de>.
"stop-the-world garbage collector in my house"

ha ha - awesome :) This is waiting for me also. It's called "Frühjahrsputz"
:)




On 9 April 2014 18:40, Alexander Shorin <kx...@gmail.com> wrote:

> Sure I would. Suddenly, I started stop-the-world garbage collector in
> my house< so I'm a little bit out of my workspace, access to IM server
> and time for other deals, but I'd done with the most recent posts on
> G+. You could check them for now, I'll finish the others later at
> night.
> --
> ,,,^..^,,,
>
>
> On Wed, Apr 9, 2014 at 4:03 PM, Noah Slater <ns...@apache.org> wrote:
> > Okay, thanks! Lemme know when you're done. *Gonna eat ur brain and
> > gain ur knowledge*
> >
> > On 8 April 2014 19:30, Alexander Shorin <kx...@gmail.com> wrote:
> >> Ok, would make a try. No need to setup admin for G+ - I already has
> that bit.
> >> --
> >> ,,,^..^,,,
> >>
> >>
> >> On Tue, Apr 8, 2014 at 9:03 PM, Noah Slater <ns...@apache.org> wrote:
> >>> Here's something: do you fancy going through through our existing
> >>> posts and adding useful descriptions?
> >>>
> >>> That'd be really handy for me to see how you're doing it.
> >>>
> >>> I'll set you up as an admin if you're not already.
> >>>
> >>> On 8 April 2014 18:36, Alexander Shorin <kx...@gmail.com> wrote:
> >>>> Unless there is nothing to say with your own words to summarize the
> >>>> content and URL's title is quite informative, imho, yes, better leave
> >>>> it empty.
> >>>> --
> >>>> ,,,^..^,,,
> >>>>
> >>>>
> >>>> On Tue, Apr 8, 2014 at 8:32 PM, Noah Slater <ns...@apache.org>
> wrote:
> >>>>> What about when there's nothing to pull quote. Just leave it blank?
> >>>>>
> >>>>> On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
> >>>>>> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org>
> wrote:
> >>>>>>> Can you provide an example of how you'd share the weekly news?
> >>>>>>
> >>>>>> Sure.
> >>>>>>
> >>>>>> Instead of:
> >>>>>>
> >>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
> >>>>>>>
> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
> >>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
> >>>>>>> blogs.apache.org
> >>>>>>
> >>>>>> Use:
> >>>>>>
> >>>>>>> *IMPORTANT*
> >>>>>>> You may or may not have heard about the Heartbleed SSL/TLS
> Vulnerability yet (http://heartbleed.com).
> >>>>>>> Without much exaggeration, this is a big one.
> >>>>>>>
> >>>>>>> In this post we prepared the instruction how to fix the issue in
> context of CouchDB usage.
> >>>>>>>
> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
> >>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
> >>>>>>> blogs.apache.org
> >>>>>>
> >>>>>>
> >>>>>> Instead of:
> >>>>>>
> >>>>>>> New blog post!
> >>>>>>> The Little Things(1): Do Not Delete : CouchDB
> >>>>>>> blogs.apache.org
> >>>>>>
> >>>>>> Use:
> >>>>>>
> >>>>>>> *The Little Things(1): Do Not Delete*
> >>>>>>> _CouchDB takes data storage extremely seriously. This usually
> means we work hard to make sure that the CouchDB storage modules are as
> robust as we can make them. Sometimes though, we go all the way to the HTTP
> API to secure against accidental data loss, saving users from their
> mistakes, rather than dealing with hard drives and kernel caches that
> usually stand in the way of safe data storage._
> >>>>>>> _In this post you'll know how to DELETE method works and how
> CouchDB protects you from accidental mistakes._
> >>>>>>> The Little Things(1): Do Not Delete : CouchDB
> >>>>>>> blogs.apache.org
> >>>>>>
> >>>>>> Copying some content from the article shows the topic of discussion.
> >>>>>> It's not about "Don't delete CouchDB from your system", it's exactly
> >>>>>> about dealing with Document deletion.
> >>>>>>
> >>>>>>
> >>>>>> Instead of:
> >>>>>>
> >>>>>>> Roll up, roll up. Read all about it!
> >>>>>>> CouchDB Weekly News, April 3 : CouchDB
> >>>>>>> blogs.apache.org
> >>>>>>
> >>>>>> Use:
> >>>>>>
> >>>>>>> *CouchDB Weekly News, April 3*
> >>>>>>> In this article you'll know:
> >>>>>>> - How to import CSV to CouchDB using Python-Cloudant module
> >>>>>>> - How to setup multiple instances of CouchDB on OS X
> >>>>>>> - Proposals for 1.6 release and the results of voting for 1.5.1
> >>>>>>> - How to Displaying a million DNA barcodes
> >>>>>>>
> >>>>>>> And also latest news from PouchDB, NPM and Cloudant and even more.
> Check it up!
> >>>>>>> CouchDB Weekly News, April 3 : CouchDB
> >>>>>>> blogs.apache.org
> >>>>>>
> >>>>>> And so on, and so forth. Short intro looks more attractive, don't
> it?
> >>>>>>
> >>>>>> --
> >>>>>> ,,,^..^,,,
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Noah Slater
> >>>>> https://twitter.com/nslater
> >>>
> >>>
> >>>
> >>> --
> >>> Noah Slater
> >>> https://twitter.com/nslater
> >
> >
> >
> > --
> > Noah Slater
> > https://twitter.com/nslater
>



-- 
Andy Wenk
Hamburg - Germany
RockIt!

http://www.couchdb-buch.de
http://www.pg-praxisbuch.de

GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588

https://people.apache.org/keys/committer/andywenk.asc

Re: Provide short annotation for shared posts

Posted by Alexander Shorin <kx...@gmail.com>.
Sure I would. Suddenly, I started stop-the-world garbage collector in
my house< so I'm a little bit out of my workspace, access to IM server
and time for other deals, but I'd done with the most recent posts on
G+. You could check them for now, I'll finish the others later at
night.
--
,,,^..^,,,


On Wed, Apr 9, 2014 at 4:03 PM, Noah Slater <ns...@apache.org> wrote:
> Okay, thanks! Lemme know when you're done. *Gonna eat ur brain and
> gain ur knowledge*
>
> On 8 April 2014 19:30, Alexander Shorin <kx...@gmail.com> wrote:
>> Ok, would make a try. No need to setup admin for G+ - I already has that bit.
>> --
>> ,,,^..^,,,
>>
>>
>> On Tue, Apr 8, 2014 at 9:03 PM, Noah Slater <ns...@apache.org> wrote:
>>> Here's something: do you fancy going through through our existing
>>> posts and adding useful descriptions?
>>>
>>> That'd be really handy for me to see how you're doing it.
>>>
>>> I'll set you up as an admin if you're not already.
>>>
>>> On 8 April 2014 18:36, Alexander Shorin <kx...@gmail.com> wrote:
>>>> Unless there is nothing to say with your own words to summarize the
>>>> content and URL's title is quite informative, imho, yes, better leave
>>>> it empty.
>>>> --
>>>> ,,,^..^,,,
>>>>
>>>>
>>>> On Tue, Apr 8, 2014 at 8:32 PM, Noah Slater <ns...@apache.org> wrote:
>>>>> What about when there's nothing to pull quote. Just leave it blank?
>>>>>
>>>>> On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
>>>>>> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org> wrote:
>>>>>>> Can you provide an example of how you'd share the weekly news?
>>>>>>
>>>>>> Sure.
>>>>>>
>>>>>> Instead of:
>>>>>>
>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
>>>>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>>>>> blogs.apache.org
>>>>>>
>>>>>> Use:
>>>>>>
>>>>>>> *IMPORTANT*
>>>>>>> You may or may not have heard about the Heartbleed SSL/TLS Vulnerability yet (http://heartbleed.com).
>>>>>>> Without much exaggeration, this is a big one.
>>>>>>>
>>>>>>> In this post we prepared the instruction how to fix the issue in context of CouchDB usage.
>>>>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>>>>> blogs.apache.org
>>>>>>
>>>>>>
>>>>>> Instead of:
>>>>>>
>>>>>>> New blog post!
>>>>>>> The Little Things(1): Do Not Delete : CouchDB
>>>>>>> blogs.apache.org
>>>>>>
>>>>>> Use:
>>>>>>
>>>>>>> *The Little Things(1): Do Not Delete*
>>>>>>> _CouchDB takes data storage extremely seriously. This usually means we work hard to make sure that the CouchDB storage modules are as robust as we can make them. Sometimes though, we go all the way to the HTTP API to secure against accidental data loss, saving users from their mistakes, rather than dealing with hard drives and kernel caches that usually stand in the way of safe data storage._
>>>>>>> _In this post you'll know how to DELETE method works and how CouchDB protects you from accidental mistakes._
>>>>>>> The Little Things(1): Do Not Delete : CouchDB
>>>>>>> blogs.apache.org
>>>>>>
>>>>>> Copying some content from the article shows the topic of discussion.
>>>>>> It's not about "Don't delete CouchDB from your system", it's exactly
>>>>>> about dealing with Document deletion.
>>>>>>
>>>>>>
>>>>>> Instead of:
>>>>>>
>>>>>>> Roll up, roll up. Read all about it!
>>>>>>> CouchDB Weekly News, April 3 : CouchDB
>>>>>>> blogs.apache.org
>>>>>>
>>>>>> Use:
>>>>>>
>>>>>>> *CouchDB Weekly News, April 3*
>>>>>>> In this article you'll know:
>>>>>>> - How to import CSV to CouchDB using Python-Cloudant module
>>>>>>> - How to setup multiple instances of CouchDB on OS X
>>>>>>> - Proposals for 1.6 release and the results of voting for 1.5.1
>>>>>>> - How to Displaying a million DNA barcodes
>>>>>>>
>>>>>>> And also latest news from PouchDB, NPM and Cloudant and even more. Check it up!
>>>>>>> CouchDB Weekly News, April 3 : CouchDB
>>>>>>> blogs.apache.org
>>>>>>
>>>>>> And so on, and so forth. Short intro looks more attractive, don't it?
>>>>>>
>>>>>> --
>>>>>> ,,,^..^,,,
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Noah Slater
>>>>> https://twitter.com/nslater
>>>
>>>
>>>
>>> --
>>> Noah Slater
>>> https://twitter.com/nslater
>
>
>
> --
> Noah Slater
> https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Noah Slater <ns...@apache.org>.
Okay, thanks! Lemme know when you're done. *Gonna eat ur brain and
gain ur knowledge*

On 8 April 2014 19:30, Alexander Shorin <kx...@gmail.com> wrote:
> Ok, would make a try. No need to setup admin for G+ - I already has that bit.
> --
> ,,,^..^,,,
>
>
> On Tue, Apr 8, 2014 at 9:03 PM, Noah Slater <ns...@apache.org> wrote:
>> Here's something: do you fancy going through through our existing
>> posts and adding useful descriptions?
>>
>> That'd be really handy for me to see how you're doing it.
>>
>> I'll set you up as an admin if you're not already.
>>
>> On 8 April 2014 18:36, Alexander Shorin <kx...@gmail.com> wrote:
>>> Unless there is nothing to say with your own words to summarize the
>>> content and URL's title is quite informative, imho, yes, better leave
>>> it empty.
>>> --
>>> ,,,^..^,,,
>>>
>>>
>>> On Tue, Apr 8, 2014 at 8:32 PM, Noah Slater <ns...@apache.org> wrote:
>>>> What about when there's nothing to pull quote. Just leave it blank?
>>>>
>>>> On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
>>>>> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org> wrote:
>>>>>> Can you provide an example of how you'd share the weekly news?
>>>>>
>>>>> Sure.
>>>>>
>>>>> Instead of:
>>>>>
>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
>>>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>>>> blogs.apache.org
>>>>>
>>>>> Use:
>>>>>
>>>>>> *IMPORTANT*
>>>>>> You may or may not have heard about the Heartbleed SSL/TLS Vulnerability yet (http://heartbleed.com).
>>>>>> Without much exaggeration, this is a big one.
>>>>>>
>>>>>> In this post we prepared the instruction how to fix the issue in context of CouchDB usage.
>>>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>>>> blogs.apache.org
>>>>>
>>>>>
>>>>> Instead of:
>>>>>
>>>>>> New blog post!
>>>>>> The Little Things(1): Do Not Delete : CouchDB
>>>>>> blogs.apache.org
>>>>>
>>>>> Use:
>>>>>
>>>>>> *The Little Things(1): Do Not Delete*
>>>>>> _CouchDB takes data storage extremely seriously. This usually means we work hard to make sure that the CouchDB storage modules are as robust as we can make them. Sometimes though, we go all the way to the HTTP API to secure against accidental data loss, saving users from their mistakes, rather than dealing with hard drives and kernel caches that usually stand in the way of safe data storage._
>>>>>> _In this post you'll know how to DELETE method works and how CouchDB protects you from accidental mistakes._
>>>>>> The Little Things(1): Do Not Delete : CouchDB
>>>>>> blogs.apache.org
>>>>>
>>>>> Copying some content from the article shows the topic of discussion.
>>>>> It's not about "Don't delete CouchDB from your system", it's exactly
>>>>> about dealing with Document deletion.
>>>>>
>>>>>
>>>>> Instead of:
>>>>>
>>>>>> Roll up, roll up. Read all about it!
>>>>>> CouchDB Weekly News, April 3 : CouchDB
>>>>>> blogs.apache.org
>>>>>
>>>>> Use:
>>>>>
>>>>>> *CouchDB Weekly News, April 3*
>>>>>> In this article you'll know:
>>>>>> - How to import CSV to CouchDB using Python-Cloudant module
>>>>>> - How to setup multiple instances of CouchDB on OS X
>>>>>> - Proposals for 1.6 release and the results of voting for 1.5.1
>>>>>> - How to Displaying a million DNA barcodes
>>>>>>
>>>>>> And also latest news from PouchDB, NPM and Cloudant and even more. Check it up!
>>>>>> CouchDB Weekly News, April 3 : CouchDB
>>>>>> blogs.apache.org
>>>>>
>>>>> And so on, and so forth. Short intro looks more attractive, don't it?
>>>>>
>>>>> --
>>>>> ,,,^..^,,,
>>>>
>>>>
>>>>
>>>> --
>>>> Noah Slater
>>>> https://twitter.com/nslater
>>
>>
>>
>> --
>> Noah Slater
>> https://twitter.com/nslater



-- 
Noah Slater
https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Alexander Shorin <kx...@gmail.com>.
Ok, would make a try. No need to setup admin for G+ - I already has that bit.
--
,,,^..^,,,


On Tue, Apr 8, 2014 at 9:03 PM, Noah Slater <ns...@apache.org> wrote:
> Here's something: do you fancy going through through our existing
> posts and adding useful descriptions?
>
> That'd be really handy for me to see how you're doing it.
>
> I'll set you up as an admin if you're not already.
>
> On 8 April 2014 18:36, Alexander Shorin <kx...@gmail.com> wrote:
>> Unless there is nothing to say with your own words to summarize the
>> content and URL's title is quite informative, imho, yes, better leave
>> it empty.
>> --
>> ,,,^..^,,,
>>
>>
>> On Tue, Apr 8, 2014 at 8:32 PM, Noah Slater <ns...@apache.org> wrote:
>>> What about when there's nothing to pull quote. Just leave it blank?
>>>
>>> On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
>>>> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org> wrote:
>>>>> Can you provide an example of how you'd share the weekly news?
>>>>
>>>> Sure.
>>>>
>>>> Instead of:
>>>>
>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
>>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>>> blogs.apache.org
>>>>
>>>> Use:
>>>>
>>>>> *IMPORTANT*
>>>>> You may or may not have heard about the Heartbleed SSL/TLS Vulnerability yet (http://heartbleed.com).
>>>>> Without much exaggeration, this is a big one.
>>>>>
>>>>> In this post we prepared the instruction how to fix the issue in context of CouchDB usage.
>>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>>> blogs.apache.org
>>>>
>>>>
>>>> Instead of:
>>>>
>>>>> New blog post!
>>>>> The Little Things(1): Do Not Delete : CouchDB
>>>>> blogs.apache.org
>>>>
>>>> Use:
>>>>
>>>>> *The Little Things(1): Do Not Delete*
>>>>> _CouchDB takes data storage extremely seriously. This usually means we work hard to make sure that the CouchDB storage modules are as robust as we can make them. Sometimes though, we go all the way to the HTTP API to secure against accidental data loss, saving users from their mistakes, rather than dealing with hard drives and kernel caches that usually stand in the way of safe data storage._
>>>>> _In this post you'll know how to DELETE method works and how CouchDB protects you from accidental mistakes._
>>>>> The Little Things(1): Do Not Delete : CouchDB
>>>>> blogs.apache.org
>>>>
>>>> Copying some content from the article shows the topic of discussion.
>>>> It's not about "Don't delete CouchDB from your system", it's exactly
>>>> about dealing with Document deletion.
>>>>
>>>>
>>>> Instead of:
>>>>
>>>>> Roll up, roll up. Read all about it!
>>>>> CouchDB Weekly News, April 3 : CouchDB
>>>>> blogs.apache.org
>>>>
>>>> Use:
>>>>
>>>>> *CouchDB Weekly News, April 3*
>>>>> In this article you'll know:
>>>>> - How to import CSV to CouchDB using Python-Cloudant module
>>>>> - How to setup multiple instances of CouchDB on OS X
>>>>> - Proposals for 1.6 release and the results of voting for 1.5.1
>>>>> - How to Displaying a million DNA barcodes
>>>>>
>>>>> And also latest news from PouchDB, NPM and Cloudant and even more. Check it up!
>>>>> CouchDB Weekly News, April 3 : CouchDB
>>>>> blogs.apache.org
>>>>
>>>> And so on, and so forth. Short intro looks more attractive, don't it?
>>>>
>>>> --
>>>> ,,,^..^,,,
>>>
>>>
>>>
>>> --
>>> Noah Slater
>>> https://twitter.com/nslater
>
>
>
> --
> Noah Slater
> https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Noah Slater <ns...@apache.org>.
Here's something: do you fancy going through through our existing
posts and adding useful descriptions?

That'd be really handy for me to see how you're doing it.

I'll set you up as an admin if you're not already.

On 8 April 2014 18:36, Alexander Shorin <kx...@gmail.com> wrote:
> Unless there is nothing to say with your own words to summarize the
> content and URL's title is quite informative, imho, yes, better leave
> it empty.
> --
> ,,,^..^,,,
>
>
> On Tue, Apr 8, 2014 at 8:32 PM, Noah Slater <ns...@apache.org> wrote:
>> What about when there's nothing to pull quote. Just leave it blank?
>>
>> On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
>>> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org> wrote:
>>>> Can you provide an example of how you'd share the weekly news?
>>>
>>> Sure.
>>>
>>> Instead of:
>>>
>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>> blogs.apache.org
>>>
>>> Use:
>>>
>>>> *IMPORTANT*
>>>> You may or may not have heard about the Heartbleed SSL/TLS Vulnerability yet (http://heartbleed.com).
>>>> Without much exaggeration, this is a big one.
>>>>
>>>> In this post we prepared the instruction how to fix the issue in context of CouchDB usage.
>>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>>> blogs.apache.org
>>>
>>>
>>> Instead of:
>>>
>>>> New blog post!
>>>> The Little Things(1): Do Not Delete : CouchDB
>>>> blogs.apache.org
>>>
>>> Use:
>>>
>>>> *The Little Things(1): Do Not Delete*
>>>> _CouchDB takes data storage extremely seriously. This usually means we work hard to make sure that the CouchDB storage modules are as robust as we can make them. Sometimes though, we go all the way to the HTTP API to secure against accidental data loss, saving users from their mistakes, rather than dealing with hard drives and kernel caches that usually stand in the way of safe data storage._
>>>> _In this post you'll know how to DELETE method works and how CouchDB protects you from accidental mistakes._
>>>> The Little Things(1): Do Not Delete : CouchDB
>>>> blogs.apache.org
>>>
>>> Copying some content from the article shows the topic of discussion.
>>> It's not about "Don't delete CouchDB from your system", it's exactly
>>> about dealing with Document deletion.
>>>
>>>
>>> Instead of:
>>>
>>>> Roll up, roll up. Read all about it!
>>>> CouchDB Weekly News, April 3 : CouchDB
>>>> blogs.apache.org
>>>
>>> Use:
>>>
>>>> *CouchDB Weekly News, April 3*
>>>> In this article you'll know:
>>>> - How to import CSV to CouchDB using Python-Cloudant module
>>>> - How to setup multiple instances of CouchDB on OS X
>>>> - Proposals for 1.6 release and the results of voting for 1.5.1
>>>> - How to Displaying a million DNA barcodes
>>>>
>>>> And also latest news from PouchDB, NPM and Cloudant and even more. Check it up!
>>>> CouchDB Weekly News, April 3 : CouchDB
>>>> blogs.apache.org
>>>
>>> And so on, and so forth. Short intro looks more attractive, don't it?
>>>
>>> --
>>> ,,,^..^,,,
>>
>>
>>
>> --
>> Noah Slater
>> https://twitter.com/nslater



-- 
Noah Slater
https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Alexander Shorin <kx...@gmail.com>.
Unless there is nothing to say with your own words to summarize the
content and URL's title is quite informative, imho, yes, better leave
it empty.
--
,,,^..^,,,


On Tue, Apr 8, 2014 at 8:32 PM, Noah Slater <ns...@apache.org> wrote:
> What about when there's nothing to pull quote. Just leave it blank?
>
> On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
>> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org> wrote:
>>> Can you provide an example of how you'd share the weekly news?
>>
>> Sure.
>>
>> Instead of:
>>
>>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>> blogs.apache.org
>>
>> Use:
>>
>>> *IMPORTANT*
>>> You may or may not have heard about the Heartbleed SSL/TLS Vulnerability yet (http://heartbleed.com).
>>> Without much exaggeration, this is a big one.
>>>
>>> In this post we prepared the instruction how to fix the issue in context of CouchDB usage.
>>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>>> blogs.apache.org
>>
>>
>> Instead of:
>>
>>> New blog post!
>>> The Little Things(1): Do Not Delete : CouchDB
>>> blogs.apache.org
>>
>> Use:
>>
>>> *The Little Things(1): Do Not Delete*
>>> _CouchDB takes data storage extremely seriously. This usually means we work hard to make sure that the CouchDB storage modules are as robust as we can make them. Sometimes though, we go all the way to the HTTP API to secure against accidental data loss, saving users from their mistakes, rather than dealing with hard drives and kernel caches that usually stand in the way of safe data storage._
>>> _In this post you'll know how to DELETE method works and how CouchDB protects you from accidental mistakes._
>>> The Little Things(1): Do Not Delete : CouchDB
>>> blogs.apache.org
>>
>> Copying some content from the article shows the topic of discussion.
>> It's not about "Don't delete CouchDB from your system", it's exactly
>> about dealing with Document deletion.
>>
>>
>> Instead of:
>>
>>> Roll up, roll up. Read all about it!
>>> CouchDB Weekly News, April 3 : CouchDB
>>> blogs.apache.org
>>
>> Use:
>>
>>> *CouchDB Weekly News, April 3*
>>> In this article you'll know:
>>> - How to import CSV to CouchDB using Python-Cloudant module
>>> - How to setup multiple instances of CouchDB on OS X
>>> - Proposals for 1.6 release and the results of voting for 1.5.1
>>> - How to Displaying a million DNA barcodes
>>>
>>> And also latest news from PouchDB, NPM and Cloudant and even more. Check it up!
>>> CouchDB Weekly News, April 3 : CouchDB
>>> blogs.apache.org
>>
>> And so on, and so forth. Short intro looks more attractive, don't it?
>>
>> --
>> ,,,^..^,,,
>
>
>
> --
> Noah Slater
> https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Noah Slater <ns...@apache.org>.
What about when there's nothing to pull quote. Just leave it blank?

On 8 April 2014 18:26, Alexander Shorin <kx...@gmail.com> wrote:
> On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org> wrote:
>> Can you provide an example of how you'd share the weekly news?
>
> Sure.
>
> Instead of:
>
>> CouchDB and the Heartbleed SSL/TLS Vulnerability:
>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>> blogs.apache.org
>
> Use:
>
>> *IMPORTANT*
>> You may or may not have heard about the Heartbleed SSL/TLS Vulnerability yet (http://heartbleed.com).
>> Without much exaggeration, this is a big one.
>>
>> In this post we prepared the instruction how to fix the issue in context of CouchDB usage.
>> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
>> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
>> blogs.apache.org
>
>
> Instead of:
>
>> New blog post!
>> The Little Things(1): Do Not Delete : CouchDB
>> blogs.apache.org
>
> Use:
>
>> *The Little Things(1): Do Not Delete*
>> _CouchDB takes data storage extremely seriously. This usually means we work hard to make sure that the CouchDB storage modules are as robust as we can make them. Sometimes though, we go all the way to the HTTP API to secure against accidental data loss, saving users from their mistakes, rather than dealing with hard drives and kernel caches that usually stand in the way of safe data storage._
>> _In this post you'll know how to DELETE method works and how CouchDB protects you from accidental mistakes._
>> The Little Things(1): Do Not Delete : CouchDB
>> blogs.apache.org
>
> Copying some content from the article shows the topic of discussion.
> It's not about "Don't delete CouchDB from your system", it's exactly
> about dealing with Document deletion.
>
>
> Instead of:
>
>> Roll up, roll up. Read all about it!
>> CouchDB Weekly News, April 3 : CouchDB
>> blogs.apache.org
>
> Use:
>
>> *CouchDB Weekly News, April 3*
>> In this article you'll know:
>> - How to import CSV to CouchDB using Python-Cloudant module
>> - How to setup multiple instances of CouchDB on OS X
>> - Proposals for 1.6 release and the results of voting for 1.5.1
>> - How to Displaying a million DNA barcodes
>>
>> And also latest news from PouchDB, NPM and Cloudant and even more. Check it up!
>> CouchDB Weekly News, April 3 : CouchDB
>> blogs.apache.org
>
> And so on, and so forth. Short intro looks more attractive, don't it?
>
> --
> ,,,^..^,,,



-- 
Noah Slater
https://twitter.com/nslater

Re: Provide short annotation for shared posts

Posted by Alexander Shorin <kx...@gmail.com>.
On Tue, Apr 8, 2014 at 8:13 PM, Noah Slater <ns...@apache.org> wrote:
> Can you provide an example of how you'd share the weekly news?

Sure.

Instead of:

> CouchDB and the Heartbleed SSL/TLS Vulnerability:
> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
> blogs.apache.org

Use:

> *IMPORTANT*
> You may or may not have heard about the Heartbleed SSL/TLS Vulnerability yet (http://heartbleed.com).
> Without much exaggeration, this is a big one.
>
> In this post we prepared the instruction how to fix the issue in context of CouchDB usage.
> https://blogs.apache.org/couchdb/entry/couchdb_and_the_heartbleed_ssl
> CouchDB and the Heartbleed SSL/TLS Vulnerability : CouchDB
> blogs.apache.org


Instead of:

> New blog post!
> The Little Things(1): Do Not Delete : CouchDB
> blogs.apache.org

Use:

> *The Little Things(1): Do Not Delete*
> _CouchDB takes data storage extremely seriously. This usually means we work hard to make sure that the CouchDB storage modules are as robust as we can make them. Sometimes though, we go all the way to the HTTP API to secure against accidental data loss, saving users from their mistakes, rather than dealing with hard drives and kernel caches that usually stand in the way of safe data storage._
> _In this post you'll know how to DELETE method works and how CouchDB protects you from accidental mistakes._
> The Little Things(1): Do Not Delete : CouchDB
> blogs.apache.org

Copying some content from the article shows the topic of discussion.
It's not about "Don't delete CouchDB from your system", it's exactly
about dealing with Document deletion.


Instead of:

> Roll up, roll up. Read all about it!
> CouchDB Weekly News, April 3 : CouchDB
> blogs.apache.org

Use:

> *CouchDB Weekly News, April 3*
> In this article you'll know:
> - How to import CSV to CouchDB using Python-Cloudant module
> - How to setup multiple instances of CouchDB on OS X
> - Proposals for 1.6 release and the results of voting for 1.5.1
> - How to Displaying a million DNA barcodes
>
> And also latest news from PouchDB, NPM and Cloudant and even more. Check it up!
> CouchDB Weekly News, April 3 : CouchDB
> blogs.apache.org

And so on, and so forth. Short intro looks more attractive, don't it?

--
,,,^..^,,,

Re: Provide short annotation for shared posts

Posted by Noah Slater <ns...@apache.org>.
Can you provide an example of how you'd share the weekly news?

On 8 April 2014 13:59, Alexander Shorin <kx...@gmail.com> wrote:
> Hello,
>
> Recently shared blog posts on G+ starts and ends with the next words:
>
>> New blog post!
>> Roll up, roll up. Read all about it!
>> Roll up, roll up. Read all about it. Get your copy of the CouchDB Weekly News, March 2
>> New post by +Andreas Wenk!
>> Woo hoo! See you there!
>
> https://plus.google.com/u/0/109226482722655790973/posts
>
> These reminds me old good 90x with NEW! HOT! links, blinking colorful
> texts, marquee magic and a lot of animation on the page. Suddenly,
> these good old times had gone away, so could we please provide some
> more information about shared items? Technically, this should be first
> paragraph from shared post which included the main idea of all the
> text, but there is a lot of space for improvisation to highlight the
> idea.
>
> I understand reasons about having some short description there: it's
> easy to copy-paste news between twitter / reddit / g+ and others
> without care about text size limitation, but we should respect
> community rules: what's good for twitter, may be not for g+ and fb and
> if we have a chance to provide more text, the interesting intro to our
> news that would be more attractive for newcomers and respectful for
> the people who don't want waste their time on things in the web with
> crying titles.
>
> In our information age it's very easy to produce and share
> information. To manage this huge stream of information everyone sets
> own inner filter to ignore all the trash and catch up only interesting
> bits. Suddenly, our current news stream on g+ is a trash with no
> useful bits. It could be better, it could be interesting.
>
> When you're walking at night and looking on the sky you see thousands
> stars there. If the new one will raise there you would never notice
> that. You'll probably wouldn't spend more than 5 minutes looking on
> them. However, if only you had an Augment Reality device which would
> show a short description for every star in the focus and highlight the
> new ones, I bet sky-watching process would be more interesting for you
> and will lasts not a single hour.
>
> Let's make our posts on communities better to attract [more] people
> and raise the discussion around. Let's annotate our stars.
>
> Thanks.
>
> --
> ,,,^..^,,,



-- 
Noah Slater
https://twitter.com/nslater