couchdb-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joan Touzet <woh...@apache.org>
Subject Re: [PROPOSAL] Naming releases
Date Thu, 30 Oct 2014 17:59:25 GMT
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 Touzet" <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 > wrote: 


+1 to the dedication idea 



On Thu, Oct 30, 2014 at 10:25 AM, Noah Slater < nslater@apache.org > wrote: 
> (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 edition")

>>> - Having a release dedicated to you (more of a recognition reward, really 
>>> - 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 name 
>>>> releases? What's the point of a "name"? Don't get me wrong, I love the 
>>>> 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 *only* 
>>>> - 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 good 
>>>> 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 >
wrote: 
>>>>> 
>>>>>> -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 refer

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

>>>>>> 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 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’s 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’m not a fan, but I won’t 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 
>>>>>> 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 
>>>>>> 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
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, 
>>>>>> 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
9588 
>>>>>> > 
>>>>>> > 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 

Mime
View raw message