Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of klaus_trainer@posteo.de
 designates 89.146.194.165 as permitted sender)
Message-ID: <544E9FB2.5050508@posteo.de>
Date: Mon, 27 Oct 2014 20:40:34 +0100
From: Klaus Trainer <klaus_trainer@posteo.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: marketing@couchdb.apache.org
Subject: Re: [PROPOSAL] Naming releases
References: 
 <CAPaJBx4PKO+BZK7h9sutJ7++3NYcTechZX5sQMLW9SJmdkYXTg@mail.gmail.com>
 <9197ACF9-2643-4A11-B0A6-F9D774786E28@apache.org>
 <42B68B22-A259-4B44-9B18-DD2846ACE1A4@apache.org>
 <544E9A70.5090700@posteo.de>
 <CADA9kr_cgKa8aMw-AcfhQ7GnLiLG=y+458to+k1MrHB0DHsx_A@mail.gmail.com>
In-Reply-To: 
 <CADA9kr_cgKa8aMw-AcfhQ7GnLiLG=y+458to+k1MrHB0DHsx_A@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="Q2AeVlTsGfd6rqgBWHfK5cle2NjUDULLh"

--Q2AeVlTsGfd6rqgBWHfK5cle2NjUDULLh
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 27.10.2014 20:30, Andy Wenk wrote:
> I have a bit of a feeling, that the proposal is a bit misunderstood. No=
ah
> has written:
>=20
> "We'd mention the name in the release announcement and
> in the changelog. But otherwise, we'd continue to talk about releases
> using the release number."
>=20
> So we use the name for a CouchDB release solely for marketing activitie=
s.
> 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 number is .=
=2E. a
> number.

That's why I wrote "Please make sure that our project won't run the risk
of creating such unnecessary confusion" and why I'm not generally -1 for
that matter :)

Cheers,
Klaus


> On 27 October 2014 20:18, Klaus Trainer <klaus_trainer@posteo.de> wrote=
:
>=20
>> I agree that it can be confusing.  Ubuntu is doing that, and even thou=
gh
>> I've been using it for almost a decade now (and thus follow its releas=
e
>> cycles pretty closely), I'm still getting confused about their release=

>> 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 involved =
in coming
>> up with a name, an artificial impediment to release cycles, and we hav=
e
>> enough real ones.
>>>
>>> B.
>>>
>>>
>>>> On 27 Oct 2014, at 16:45, Jan Lehnardt <jan@apache.org> wrote:
>>>>
>>>> I=E2=80=99m not a fan, but I won=E2=80=99t be in the way of this.
>>>>
>>>> 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 AdvocateHub. (=
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 announcement =
and
>>>>> in the changelog. But otherwise, we'd continue to talk about releas=
es
>>>>> using the release number.
>>>>>
>>>>> Primarily, I see it as a bit of fun. And a great way to reward
>> advocates.
>>>>>
>>>>> I'm cross-posting this to dev and marketing because it's both 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 put on a=

>> queue
>>>>> - The next release picks the oldest name on the queue
>>>>>
>>>>> I'd probably actually want to separate this into three rewards:
>>>>>
>>>>> - 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, promo=
te,
>>>>> and advocate CouchDB to on social media, and to their network. For =
a
>>>>> project like ours, with limited to no financial budget for traditio=
nal
>>>>> marketing, this is a huge opportunity for us.
>>>>>
>>>>> The AdvocateHub has two important concepts (for the purposes of thi=
s
>>>>> email): challenges and rewards. Advocates complete challenges (like=

>>>>> "leave a review" or "write a case-study") and in return, we give th=
em
>>>>> 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, social
>> 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 i=
s
>>>>> decided by the community. This category would be much easier to fil=
l
>>>>> out if we were a regular business. But I figure that naming a relea=
se
>>>>> is a fun approach.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --
>>>>> Noah Slater
>>>>> https://twitter.com/nslater
>>>>
>>>
>>
>>
>=20
>=20


--Q2AeVlTsGfd6rqgBWHfK5cle2NjUDULLh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUTp+yAAoJEMnOE6PgK7OZ6ncP/RuOfyCNt54akQ5oTCCvjoaG
uhBwFa6H7ibv8rv2IK2lnLlGFIIquClRcd6Rxog7CSEPb7A0CkQhwCpJTQpFoH0E
phXEcMOvgqT3wqaZmNkwr4KqOOEg49umnMLACuknwvxHvB04YVtQmYxMx0V9jdM4
GYG00XIn8s3+B+CqdF6bDCOgzHcSKjou02KD0rEvqlipZx4blPSqYT4rgMISvIrM
Z7v3rCUUrbertpPZKYsVB+jMxwaDwl245fxTZRGafGYzsZUkd8WYlmPwVaDwCg61
qawLmRUS4U7SdvhtoT9TJz6GoRwR2oqMyk0HBssY7g6Ow20NuEuUtXHlE8Sad2q7
SZ0HksBC5AkQSRHvnyxlcd+/R838R0IPnefT5N6K4VM8WoqQ+lkv60MeulMe+q4X
xgltL0+kbkAPUwXDhxtRs06GrVbuHj6rv3LCeuR5P0ED6jBCELmlzA8SGzyGHI4R
6TvjKwNwY3/A2JxxHSmG2c6K7RjA1U5L+GF3gYPzSj3/kXEvVz12K/BYYKKZG/JY
2+vhmg8Xx32gOOu4OpV/4tz5ggcA59U8HSVuXj5oc7RS+yS/AFhBYHgqoAvn/sDC
kfyBUgfftA1pfXJkMDCwBSxBMkGrlIHChX3waaPWvPcpTA/w1gDGfR6inMLtSALN
4cAOlam2uEgxvXwVjxJf
=JnKz
-----END PGP SIGNATURE-----

--Q2AeVlTsGfd6rqgBWHfK5cle2NjUDULLh--