Yeah, we're planning to move forward with AdvocateHub too. We can trade
tips as we do.


On Tue, Feb 18, 2014 at 12:15 PM, Noah Slater <nsla...@apache.org> wrote:

> Unfortunately, it needs to be a regular effort. Very hard to rely on
> volunteer effort, especially with a cadence as tight as one week.
>
> Benjamin, are you interested in helping out with the blog? Max has
> indicated that he is interested in reposting some of the content he
> writes for Cloudant on the project blog. Would you be willing to do
> the same?
>
> I'm also pleased to say that it looks like we're able to move forward
> with our AdvocateHub, which is my big focus for 2014. So I'd love your
> help on that too, if you can spare the cycles.
>
> cf.
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201310.mbox/%3CCAPaJBx4xz5=ht9_yu7ooeyh2lq2mjwppr_o9qb0jwycxdeh...@mail.gmail.com%3E
>
> On 18 February 2014 16:25, Benjamin Young <byo...@bigbluehat.com> wrote:
> > On 2/18/14, 10:00 AM, Noah Slater wrote:
> >>
> >> Think we need to pay someone to do this. It's too much for a volunteer
> >> to do. I know, because I tried it and I failed. Exploring some
> >> options. Will get back to the list with details later.
> >
> >
> > It is a gargantuan task which is why I'd hoped it could be a community
> > effort. :) It should still be regardless of someone being hired to click
> the
> > links, etc.
> >
> > Cloudant, fwiw, already has developer advocates, etc on payroll who's
> job it
> > is to do "this sort of thing" (I'm one of them, fwiw). Some of my cycles
> > already go to finding (or writing) interesting bits about Cloudant and
> > Apache CouchDB bringing peoples attention to them.
> >
> > I'll start relaying interesting finds to this list, and anyone who wants
> > (payed or otherwise) can hopefully help with (re)promotion.
> >
> > If nothing else, we'll keep this list stocked with interesting content
> about
> > CouchDB. :)
> >
> >
> >>
> >> On 18 February 2014 15:51, Benjamin Young <byo...@bigbluehat.com>
> wrote:
> >>>
> >>> On 2/18/14, 9:39 AM, Noah Slater wrote:
> >>>>
> >>>> "This is only the 2nd time in quite a while I'm reading an article
> >>>> mentioning CouchDB -- after the February
> >>>> "no-releases-but-we're-still-merging-BigCouch" report for ASF. And
> >>>> according to the story, CouchDB is on the way out."
> >>>>
> >>>> Aye. We really need to get this next release out.
> >>>>
> >>>> But to get back to the topic: what we really need is someone who can
> >>>> collect weekly news and do a regular blog post with a link round-up
> >>>> that points people to all the stuff going on in the world of CouchDB.
> >>>> Sort of like how the Hoodie project do it.
> >>>
> >>>
> >>> I'd love to see this happen--and had plans to do it for years/months
> past
> >>> both on my own and at Cloudant. Time's come, I guess. :)
> >>>
> >>> To that end, what if we simply begin sharing CouchDB ecosystem related
> >>> links
> >>> on this marketing@ list and each do what we can to promote them
> (retweet,
> >>> reblog, sum up in a weekly post on our personal/company blogs, etc).
> >>>
> >>> I'd love to see the PMC aggregate these into a weekly/bi-weekly or even
> >>> monthly "CouchDB Land Links" (or whatever).
> >>>
> >>> The more of us linking (and posting, etc) these things, the greater
> >>> chance
> >>> it has to raise the volume for CouchDB.
> >>>
> >>> Sound like a plan?
> >>>
> >>>
> >>>> http://blog.hood.ie/
> >>>>
> >>>> On 18 February 2014 15:19, Jan Lehnardt <j...@apache.org> wrote:
> >>>>>
> >>>>> Hi all,
> >>>>>
> >>>>> I just came across this article:
> >>>>>
> >>>>>
> http://nosql.mypopescu.com/post/77055582692/storage-technologies-at-hipchat-couchdb
> >>>>>
> >>>>> Footnote number two hurts a little "This is only the 2nd time in
> quite
> >>>>> a
> >>>>> while I'm reading an article mentioning CouchDB..."
> >>>>>
> >>>>> We should figure out a way to make the things that are happening
> around
> >>>>> CouchDB a bit more public :)
> >>>>>
> >>>>> Best
> >>>>> Jan
> >>>>> --
> >>>>>
> >>>>
> >>
> >>
> >
>
>
>
> --
> Noah Slater
> https://twitter.com/nslater
>

Reply via email to