Return-Path: 
 <marketing-return-862-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 33E2D17D6C
	for <apmail-couchdb-marketing-archive@minotaur.apache.org>;
 Mon, 27 Oct 2014 19:31:29 +0000 (UTC)
Received: (qmail 43835 invoked by uid 500); 27 Oct 2014 19:31:28 -0000
Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org
Received: (qmail 43801 invoked by uid 500); 27 Oct 2014 19:31:28 -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 43778 invoked by uid 99); 27 Oct 2014 19:31:28 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org)
 (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Oct 2014 19:31:28 +0000
Received: from mail-la0-f54.google.com (mail-la0-f54.google.com
 [209.85.215.54])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with
 ESMTPSA id 73A531A02FC;
	Mon, 27 Oct 2014 19:30:55 +0000 (UTC)
Received: by mail-la0-f54.google.com with SMTP id gm9so6370031lab.41
        for <multiple recipients>; Mon, 27 Oct 2014 12:31:26 -0700 (PDT)
X-Received: by 10.152.29.41 with SMTP id g9mr12172785lah.83.1414438286000;
 Mon, 27 Oct 2014 12:31:26 -0700 (PDT)
MIME-Version: 1.0
Reply-To: andywenk@apache.org
Received: by 10.112.209.105 with HTTP; Mon, 27 Oct 2014 12:30:55 -0700 (PDT)
In-Reply-To: <544E9A70.5090700@posteo.de>
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>
From: Andy Wenk <andywenk@apache.org>
Date: Mon, 27 Oct 2014 20:30:55 +0100
Message-ID: 
 <CADA9kr_cgKa8aMw-AcfhQ7GnLiLG=y+458to+k1MrHB0DHsx_A@mail.gmail.com>
Subject: Re: [PROPOSAL] Naming releases
To: "marketing@couchdb.apache.org" <marketing@couchdb.apache.org>
Cc: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=089e0158c09a9808da05066c93ea

--089e0158c09a9808da05066c93ea
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I have a bit of a feeling, that the proposal is a bit misunderstood. Noah
has written:

"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."

So we use the name for a CouchDB release solely for marketing activities.
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 ... 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 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 have
> 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. (Se=
e
> >>> 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 an=
d
> >>> 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 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, promote=
,
> >>> and advocate CouchDB to on social media, and to their network. For a
> >>> project like ours, with limited to no financial budget for traditiona=
l
> >>> 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 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.
> >>>
> >>> 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, et=
c)
> >>> - 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
> >>
> >
>
>


--=20
Andy Wenk
Hamburg - Germany
RockIt!

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

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

--089e0158c09a9808da05066c93ea--