Return-Path: 
 <marketing-return-911-apmail-couchdb-marketing-archive=couchdb.apache.org@couchdb.apache.org>
X-Original-To: apmail-couchdb-marketing-archive@minotaur.apache.org
Delivered-To: apmail-couchdb-marketing-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B7BE217475
	for <apmail-couchdb-marketing-archive@minotaur.apache.org>;
 Sat,  1 Nov 2014 01:45:11 +0000 (UTC)
Received: (qmail 59447 invoked by uid 500); 1 Nov 2014 01:45:11 -0000
Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org
Received: (qmail 59399 invoked by uid 500); 1 Nov 2014 01:45:11 -0000
Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:marketing-help@couchdb.apache.org>
List-Unsubscribe: <mailto:marketing-unsubscribe@couchdb.apache.org>
List-Post: <mailto:marketing@couchdb.apache.org>
List-Id: <marketing.couchdb.apache.org>
Reply-To: marketing@couchdb.apache.org
Delivered-To: mailing list marketing@couchdb.apache.org
Received: (qmail 59343 invoked by uid 99); 1 Nov 2014 01:45:10 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Nov 2014 01:45:10 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of candeira@gmail.com designates
 209.85.214.181 as permitted sender)
Received: from [209.85.214.181] (HELO mail-ob0-f181.google.com)
 (209.85.214.181)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Nov 2014 01:45:06 +0000
Received: by mail-ob0-f181.google.com with SMTP id uy5so6778474obc.40
        for <multiple recipients>; Fri, 31 Oct 2014 18:44:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:reply-to:sender:in-reply-to:references:date:message-id
         :subject:from:to:cc:content-type:content-transfer-encoding;
        bh=AnDrGOb/Wo2oDeCSLaknN/cTGtq0W2xqwUXJk4WyLak=;
        b=EA8vHosajsDx4wnJd0vF85fRK+fsW5uVxoHkWiGrDK/LoVZBR+6T3jUS8DvL8Up4zv
         uVTZlvwhkhixWBZOBZCJPMMJ4HxgFZFEuIUZihLZnS5BQ5DfVLedcMj7KBAQVOSkSXGz
         2YKr1NRElnXsxMltc+caaIQpIolISCm6SeBJfcPq35bl01wOhGEeCbiQ8i/rCDj6wSw3
         9nH5EKBfWWy4o9o8WuRstKNUJZ/pJ8z2hkd14Uc8Miw8a4XCWMCCa0XQvFxa3sun9DLj
         N2t8N+vuThxaatjC/oKJRnAJDREwvYyIe/C9i8vReh1ZyjQohOdoEQdEKr4flML9o1kb
         i6Vg==
MIME-Version: 1.0
X-Received: by 10.182.245.225 with SMTP id xr1mr23447898obc.13.1414806240689;
 Fri, 31 Oct 2014 18:44:00 -0700 (PDT)
Reply-To: javier@candeira.com
Sender: candeira@gmail.com
Received: by 10.76.97.205 with HTTP; Fri, 31 Oct 2014 18:44:00 -0700 (PDT)
In-Reply-To: 
 <25994587.339.1414691963901.JavaMail.joant@Joans-MacBook-Pro.local>
References: 
 <CADA9kr_hDetpNGC+hQ5U7o4o-9KJbMj9Az1MLfrFOWpUaCuvgQ@mail.gmail.com>
	<25994587.339.1414691963901.JavaMail.joant@Joans-MacBook-Pro.local>
Date: Sat, 1 Nov 2014 12:44:00 +1100
X-Google-Sender-Auth: ZNSUwdllZpJWdb9K7uOa2WloL8c
Message-ID: 
 <CAKADsbfMb90NHC_7CzzNNG2Wxysfi0J+ucC3Uv0ZcH=_XfsHMg@mail.gmail.com>
Subject: Re: [PROPOSAL] Naming releases
From: Javier Candeira <javier@candeira.com>
To: marketing@couchdb.apache.org, Joan Touzet <wohali@apache.org>
Cc: dev@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

IMHO, this is what the blog is for, and what blogs are best at.

The Changelog for the CouchDB release can have a one-line "dedicated
to", and that would be the dedication.

But there could be a longer post on the CouchDB blog with the reasons
this particular release is dedicated to this particular Couchian,
maybe with a brief interview about their involvement with the project,
why and how they use CouchDB, etc. A profile of "people of CouchDB",
if you want. This provides opportunities for extending the promotional
reach as the dedicatee and their friends share the blog post on
twitter and facebook etc.

J

On Fri, Oct 31, 2014 at 4:59 AM, Joan Touzet <wohali@apache.org> wrote:
> Yup, that's fine. +1.
>
> ----- Original Message -----
> From: "Andy Wenk" <andy@nms.de>
> To: marketing@couchdb.apache.org
> Cc: dev@couchdb.apache.org, "Noah Slater" <nslater@apache.org>, "Joan Tou=
zet" <wohali@apache.org>
> Sent: Thursday, October 30, 2014 11:33:16 AM
> Subject: Re: [PROPOSAL] Naming releases
>
>
> yes +1
>
>
> On 30 October 2014 16:27, Paul Davis < paul.joseph.davis@gmail.com > wrot=
e:
>
>
> +1 to the dedication idea
>
>
>
> On Thu, Oct 30, 2014 at 10:25 AM, Noah Slater < nslater@apache.org > wrot=
e:
>> (Moving the rest of this discussion to the marketing@ list.)
>>
>> On 30 October 2014 16:25, Noah Slater < nslater@apache.org > wrote:
>>> If nobody objects, I'm going to assume consensus that "dedicating" a
>>> release to an individual is okay if it takes the form of a footnote.
>>>
>>> On 28 October 2014 17:21, Noah Slater < nslater@apache.org > wrote:
>>>> (Re-copying dev@ here too.)
>>>>
>>>> Nope. Nobody is donating anything. This would be a reward that CouchDB
>>>> advocates can redeem in exchange for advocating CouchDB. (There's a
>>>> quick refresher in my first email, but I'm happy to provide more
>>>> info.)
>>>>
>>>> My goal is to let a highly productive advocate have a bit of "power"
>>>> over something. This ties into a theory about what motivates different
>>>> people. Some people like recognition, some people just like free
>>>> stuff, some people like exclusive access to things, and some people
>>>> like being granted power.
>>>>
>>>> The first three are relatively easy, but the power thing is hard to do
>>>> in a community where anybody can make a decision.
>>>>
>>>> The only things I can think of so far are:
>>>>
>>>> - "Naming" a weekly news edition (just a bit of fun, i.e. "aka the X e=
dition")
>>>> - Having a release dedicated to you (more of a recognition reward, rea=
lly
>>>> - Naming something inside the AdvocateHub (like a challenge)
>>>>
>>>> On 28 October 2014 01:37, Joan Touzet < wohali@apache.org > wrote:
>>>>> I don't understand, are we accepting donations and letting people nam=
e
>>>>> releases? What's the point of a "name"? Don't get me wrong, I love th=
e
>>>>> Toy Story release names for Debian....
>>>>>
>>>>> Counter-counter-proposal 1:
>>>>>
>>>>> If we want to use this to raise awareness...
>>>>>
>>>>> Do what Vim does. If people want to donate, and don't feel like
>>>>> donating to the ASF, they can donate to the official CouchDB charity.
>>>>> That could be something thematic like the Furniture Bank of America,
>>>>> or something that we all feel passionate about TBD.
>>>>>
>>>>> Counter-counter-proposal 2:
>>>>>
>>>>> Yearly thank-yous to people that help, a sort of "awards" thing.
>>>>> No need to tie it to a (possibly irregular) release schedule.
>>>>>
>>>>> -Joan
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Noah Slater" < nslater@apache.org >
>>>>> To: marketing@couchdb.apache.org
>>>>> Cc: "Joan Touzet" < wohali@apache.org >
>>>>> Sent: Monday, October 27, 2014 6:01:06 PM
>>>>> Subject: Re: [PROPOSAL] Naming releases
>>>>>
>>>>> Seems like consensus is that this is a bad idea--as formulated.
>>>>>
>>>>> How about softening the proposal?
>>>>>
>>>>> Counter-proposal A:
>>>>>
>>>>> - Tweets, social media posts, changelog, etc. all use the number *onl=
y*
>>>>> - There is a single sentence in the release announcement email and
>>>>> blog post to the effect of "aka the X release"
>>>>>
>>>>> Counter-proposal B:
>>>>>
>>>>> - Rephrase it slightly so that we're "dedicating" the release to
>>>>> someone as a thank you
>>>>>
>>>>> Only problem with counter-proposal B is that (while it might be a goo=
d
>>>>> idea) it puts it into the "access" category. We're giving someone
>>>>> exclusive access to our platform as a thank you.
>>>>>
>>>>> Does anyone have any ideas for rewards that fall into the "power"
>>>>> category, that we can reasonably offer, without compromising the
>>>>> integrity of the project?
>>>>>
>>>>> We could let people "name" weekly news posts, I suppose. "aka the X
>>>>> update". Heh. Perhaps that's less risky.
>>>>>
>>>>>
>>>>> On 27 October 2014 21:55, Sebastian Rothbucher
>>>>> < sebastianrothbucher@googlemail.com > wrote:
>>>>>> I'd KISS also - and stick with numbers only, so -0.5 as well
>>>>>>
>>>>>> On Mon, Oct 27, 2014 at 9:41 PM, Joan Touzet < wohali@apache.org > w=
rote:
>>>>>>
>>>>>>> -0.5 for all the reasons previously outlined.
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>> From: "Paul Davis" < paul.joseph.davis@gmail.com >
>>>>>>> To: dev@couchdb.apache.org , andywenk@apache.org
>>>>>>> Cc: marketing@couchdb.apache.org
>>>>>>> Sent: Monday, October 27, 2014 3:39:55 PM
>>>>>>> Subject: Re: [PROPOSAL] Naming releases
>>>>>>>
>>>>>>> I'm a bit on the -1 side of things as well. Having two ways to refe=
r
>>>>>>> to a release has always annoyed me with projects like Debian/Ubuntu=
.
>>>>>>> Granted they tend to use them a lot more interchangeably than Noah =
is
>>>>>>> suggesting, though I do wonder if it'd still lead to confusion.
>>>>>>>
>>>>>>> I think for the particular current case I wonder if we can't think =
of
>>>>>>> other perk things for the category that Noah is trying to fill. Tho=
ugh
>>>>>>> I have to say I can't think of anything off the top of my head.
>>>>>>>
>>>>>>> On Mon, Oct 27, 2014 at 2:30 PM, Andy Wenk < andywenk@apache.org > =
wrote:
>>>>>>> > I have a bit of a feeling, that the proposal is a bit misundersto=
od. Noah
>>>>>>> > has written:
>>>>>>> >
>>>>>>> > "We'd mention the name in the release announcement and
>>>>>>> > in the changelog. But otherwise, we'd continue to talk about rele=
ases
>>>>>>> > using the release number."
>>>>>>> >
>>>>>>> > So we use the name for a CouchDB release solely for marketing act=
ivities.
>>>>>>> > We stay with the release numbers. So the number is the important =
part.
>>>>>>> With
>>>>>>> > Mac OS X and Ubuntu, the name is the important part and the numbe=
r is
>>>>>>> ... a
>>>>>>> > number.
>>>>>>> >
>>>>>>> > So I don't see any problems with naming a release if we keep the =
release
>>>>>>> > number as the most important part.
>>>>>>> >
>>>>>>> > Cheers
>>>>>>> >
>>>>>>> > Andy
>>>>>>> >
>>>>>>> > On 27 October 2014 20:18, Klaus Trainer < klaus_trainer@posteo.de=
 > wrote:
>>>>>>> >
>>>>>>> >> I agree that it can be confusing. Ubuntu is doing that, and even=
 though
>>>>>>> >> I've been using it for almost a decade now (and thus follow its =
release
>>>>>>> >> cycles pretty closely), I'm still getting confused about their r=
elease
>>>>>>> >> names from time to time. Please make sure that our project won't=
 run
>>>>>>> >> the risk of creating such unnecessary confusion.
>>>>>>> >>
>>>>>>> >> Thanks,
>>>>>>> >> Klaus
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> On 27.10.2014 19:31, Robert Samuel Newson wrote:
>>>>>>> >> > Also not a fan, its confusing and there=E2=80=99s an effort in=
volved in coming
>>>>>>> >> up with a name, an artificial impediment to release cycles, and =
we have
>>>>>>> >> enough real ones.
>>>>>>> >> >
>>>>>>> >> > B.
>>>>>>> >> >
>>>>>>> >> >
>>>>>>> >> >> On 27 Oct 2014, at 16:45, Jan Lehnardt < jan@apache.org > wro=
te:
>>>>>>> >> >>
>>>>>>> >> >> I=E2=80=99m not a fan, but I won=E2=80=99t be in the way of t=
his.
>>>>>>> >> >>
>>>>>>> >> >> Best
>>>>>>> >> >> Jan
>>>>>>> >> >> --
>>>>>>> >> >>
>>>>>>> >> >>> On 27 Oct 2014, at 14:49 , Noah Slater < nslater@apache.org =
> wrote:
>>>>>>> >> >>>
>>>>>>> >> >>> Hi folks,
>>>>>>> >> >>>
>>>>>>> >> >>> SUMMARY
>>>>>>> >> >>>
>>>>>>> >> >>> I'm currently working on the rewards for the CouchDB Advocat=
eHub.
>>>>>>> (See
>>>>>>> >> >>> bottom of this email for a refresher.)
>>>>>>> >> >>>
>>>>>>> >> >>> One of the rewards I'd like to offer is the ability to "name=
" a
>>>>>>> >> >>> CouchDB release. We'd mention the name in the release announ=
cement
>>>>>>> and
>>>>>>> >> >>> in the changelog. But otherwise, we'd continue to talk about
>>>>>>> releases
>>>>>>> >> >>> using the release number.
>>>>>>> >> >>>
>>>>>>> >> >>> Primarily, I see it as a bit of fun. And a great way to rewa=
rd
>>>>>>> >> advocates.
>>>>>>> >> >>>
>>>>>>> >> >>> I'm cross-posting this to dev and marketing because it's bot=
h a
>>>>>>> >> >>> release management proposal as well as a marketing proposal.
>>>>>>> >> >>>
>>>>>>> >> >>> DETAILS
>>>>>>> >> >>>
>>>>>>> >> >>> The way I see it working:
>>>>>>> >> >>>
>>>>>>> >> >>> - Advocate redeems the "name a release" reward, and picks a =
name
>>>>>>> >> >>> - The name is vetted by the PMC (for brand protection) and p=
ut on a
>>>>>>> >> queue
>>>>>>> >> >>> - The next release picks the oldest name on the queue
>>>>>>> >> >>>
>>>>>>> >> >>> I'd probably actually want to separate this into three rewar=
ds:
>>>>>>> >> >>>
>>>>>>> >> >>> - Name a bugfix release
>>>>>>> >> >>> - Name a minor release
>>>>>>> >> >>> - Name a major release
>>>>>>> >> >>>
>>>>>>> >> >>> Each one would be require more points than the last.
>>>>>>> >> >>>
>>>>>>> >> >>> REFRESHER
>>>>>>> >> >>>
>>>>>>> >> >>> Our AdvocateHub is a professional tool that has been donated=
 to us
>>>>>>> >> >>> that will allow us to mobilise fans of CouchDB to talk about=
,
>>>>>>> promote,
>>>>>>> >> >>> and advocate CouchDB to on social media, and to their networ=
k. For a
>>>>>>> >> >>> project like ours, with limited to no financial budget for
>>>>>>> traditional
>>>>>>> >> >>> marketing, this is a huge opportunity for us.
>>>>>>> >> >>>
>>>>>>> >> >>> The AdvocateHub has two important concepts (for the purposes=
 of this
>>>>>>> >> >>> email): challenges and rewards. Advocates complete challenge=
s (like
>>>>>>> >> >>> "leave a review" or "write a case-study") and in return, we =
give
>>>>>>> them
>>>>>>> >> >>> points. Collect enough points, and they can redeem rewards. =
The
>>>>>>> >> >>> rewards are a thank you helping to advocate CouchDB.
>>>>>>> >> >>>
>>>>>>> >> >>> RATIONALE
>>>>>>> >> >>>
>>>>>>> >> >>> There are four main categories of reward:
>>>>>>> >> >>>
>>>>>>> >> >>> - Stuff (t-shirts, mugs, tickets to conferences, etc)
>>>>>>> >> >>> - Access (dinner with a committer, promotion on our blog, so=
cial
>>>>>>> >> media, etc)
>>>>>>> >> >>> - Status (recognition on our website, hand written thank you=
 note,
>>>>>>> etc)
>>>>>>> >> >>> - Power (name a release, ... what else?)
>>>>>>> >> >>>
>>>>>>> >> >>> Struggling on the "power" category, because everything we do=
 here is
>>>>>>> >> >>> decided by the community. This category would be much easier=
 to fill
>>>>>>> >> >>> out if we were a regular business. But I figure that naming =
a
>>>>>>> release
>>>>>>> >> >>> is a fun approach.
>>>>>>> >> >>>
>>>>>>> >> >>> Thanks,
>>>>>>> >> >>>
>>>>>>> >> >>> --
>>>>>>> >> >>> Noah Slater
>>>>>>> >> >>> https://twitter.com/nslater
>>>>>>> >> >>
>>>>>>> >> >
>>>>>>> >>
>>>>>>> >>
>>>>>>> >
>>>>>>> >
>>>>>>> > --
>>>>>>> > Andy Wenk
>>>>>>> > Hamburg - Germany
>>>>>>> > RockIt!
>>>>>>> >
>>>>>>> > GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 958=
8
>>>>>>> >
>>>>>>> > https://people.apache.org/keys/committer/andywenk.asc
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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