Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@couchdb.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: [PROPOSAL] Naming releases
From: Robert Samuel Newson <rnewson@apache.org>
In-Reply-To: <9197ACF9-2643-4A11-B0A6-F9D774786E28@apache.org>
Date: Mon, 27 Oct 2014 18:31:38 +0000
Cc: marketing@couchdb.apache.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <42B68B22-A259-4B44-9B18-DD2846ACE1A4@apache.org>
References: 
 <CAPaJBx4PKO+BZK7h9sutJ7++3NYcTechZX5sQMLW9SJmdkYXTg@mail.gmail.com>
 <9197ACF9-2643-4A11-B0A6-F9D774786E28@apache.org>
To: dev@couchdb.apache.org

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 have enough real ones.

B.


> On 27 Oct 2014, at 16:45, Jan Lehnardt <jan@apache.org> wrote:
>=20
> I=E2=80=99m not a fan, but I won=E2=80=99t be in the way of this.
>=20
> Best
> Jan
> --=20
>=20
>> On 27 Oct 2014, at 14:49 , Noah Slater <nslater@apache.org> wrote:
>>=20
>> Hi folks,
>>=20
>> SUMMARY
>>=20
>> I'm currently working on the rewards for the CouchDB AdvocateHub. =
(See
>> bottom of this email for a refresher.)
>>=20
>> 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 releases
>> using the release number.
>>=20
>> Primarily, I see it as a bit of fun. And a great way to reward =
advocates.
>>=20
>> I'm cross-posting this to dev and marketing because it's both a
>> release management proposal as well as a marketing proposal.
>>=20
>> DETAILS
>>=20
>> The way I see it working:
>>=20
>> - 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
>>=20
>> I'd probably actually want to separate this into three rewards:
>>=20
>> - Name a bugfix release
>> - Name a minor release
>> - Name a major release
>>=20
>> Each one would be require more points than the last.
>>=20
>> REFRESHER
>>=20
>> 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 network. For a
>> project like ours, with limited to no financial budget for =
traditional
>> marketing, this is a huge opportunity for us.
>>=20
>> The AdvocateHub has two important concepts (for the purposes of this
>> email): challenges and rewards. Advocates complete challenges (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.
>>=20
>> RATIONALE
>>=20
>> There are four main categories of reward:
>>=20
>> - 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?)
>>=20
>> 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.
>>=20
>> Thanks,
>>=20
>> --=20
>> Noah Slater
>> https://twitter.com/nslater
>=20