Return-Path: 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 198EB17E85 for ; Fri, 31 Oct 2014 17:38:39 +0000 (UTC) Received: (qmail 67916 invoked by uid 500); 31 Oct 2014 17:38:39 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 67881 invoked by uid 500); 31 Oct 2014 17:38:39 -0000 Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: marketing@couchdb.apache.org Delivered-To: mailing list marketing@couchdb.apache.org Received: (qmail 67870 invoked by uid 99); 31 Oct 2014 17:38:38 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Oct 2014 17:38:38 +0000 Received: from localhost (HELO mail-ig0-f174.google.com) (127.0.0.1) (smtp-auth username nslater, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Oct 2014 17:38:38 +0000 Received: by mail-ig0-f174.google.com with SMTP id hn18so1390549igb.7 for ; Fri, 31 Oct 2014 10:38:38 -0700 (PDT) X-Gm-Message-State: ALoCoQke83txp0vdbOAmYFxpdm61ywoeaU/ndiHkhXZh8JOSGUJwiuwq966u6oE/K5jwBbn5D2gd MIME-Version: 1.0 X-Received: by 10.50.164.194 with SMTP id ys2mr6005288igb.43.1414777118016; Fri, 31 Oct 2014 10:38:38 -0700 (PDT) Received: by 10.107.37.204 with HTTP; Fri, 31 Oct 2014 10:38:37 -0700 (PDT) X-Originating-IP: [85.12.8.106] In-Reply-To: References: Date: Fri, 31 Oct 2014 18:38:37 +0100 Message-ID: Subject: Re: AdvocateHub rewards From: Noah Slater To: "marketing@couchdb.apache.org" , "andywenk@apache.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable So, I actually brought up the idea of dedicating the release on a dev@ thread. The only people to respond there were +1 on the idea. But Jan and Lena are -1 one on the idea here and have requested we put this reward on hold. I still think it would be a good idea, but I'm happy to put the idea on the back burner. I'll also table the "name the news" idea. We can revisit in the future. Thanks for the feedback folks. On 31 October 2014 14:15, Andy Wenk wrote: > On 31 October 2014 13:30, Jan Lehnardt wrote: > >> >> > On 31 Oct 2014, at 09:25 , Andy Wenk wrote: >> > >> > Jan, >> > >> > this is a very fair point. But I think it could be avoided if we add s= th. >> > like "Thanks to all the awesome work of the contributors, this release= is >> > again so cool ..." If there is a very big part created by one person, = why >> > not name him also? >> >> Or her. It puts focus on things that are shippable. It shadows things th= at >> go on in the background, that are essential, say JIRA triaging or Pull >> Request Reviews. Someone might spend more time on that than someone else >> with a big new feature and they wouldn=E2=80=99t get credit. I=E2=80=99d= like to avoid >> that, >> and I think we have plenty of good incentives. It=E2=80=99s not that we = are at a >> loss as to what to offer people. >> > > sry - for sure her also. I do understand this. Again, dedicating a relea= se > does not have to do anything with value compared to other contributions. > But I see the point that this could be viewed from the outside in that wa= y. > What would be wrong. > > >> > But on the other hand, we have the contributors list and >> > the people earn respect because they can be found in the commit histor= y. >> > The developers working on CouchDB do it, because they believe in the >> > project and want to help creating awesome software. Not to see their n= ame >> > in any special announcement. At least, that's the point for me. >> >> Exactly, we should value people because they are committed to CouchDB, >> regardless of their contribution. Highlighting some people in the commun= ity >> creates a disparity that can have very adverse effects on a community. >> > > That is very true. You are right. > > >> > So I can understand your (and Lena's) concerns but I personally do not >> see >> > this a s such a big issue. >> >> Both Lena and I had some experience with this this year in a community o= f >> six people and avoiding a mix of =E2=80=9Cshipping culture=E2=80=9D and = =E2=80=9Chero worship=E2=80=9D and >> instead a focus on people made all the difference for us. >> > > sorry to hear that. I would be more than sad if the outcome of this > marketing idea would be something like this. With this knowledge, I am > starting to be convinced, that the idea could result in problems for the > community. I am strongly against taking this risk. > > >> > Maybe we could make a quick questionnaire (Google form thingy?) on dev= @ >> > to get a feeling for this? >> >> Why is there a need to push this through? We have plenty of rewards for >> AdvocateHub. Let=E2=80=99s get that out and see how it goes. If we need = to dial >> up the reward-meter, let=E2=80=99s get back together and think about wha= t we can >> offer. >> > > Because it is good to know how we can rise the reward-meter from the > beginning. That was the idea. Keep it open and learn what the community > thinks about this. But .... > > > I hear you! I am now at the point top agree, that we should start with th= e > other rewards. Thanls for taking the time to outline this very clearly <3= :) > > >> Best >> Jan >> -- >> > > So I am -0 with the idea to dedicate releases at this moment. > > Cheers > > Andy > >> On 30 October 2014 17:43, Jan Lehnardt wrote: >> > >> >> >> >>> On 30 Oct 2014, at 17:37 , Noah Slater wrote: >> >>> >> >>> Jan/Lena, could you expand a little on why you don't like the idea o= f >> >>> dedicating a release? >> >> >> >> I fear that someone who built a significant feature for a release wou= ld >> >> feel they need recognition as well, but they don=E2=80=99t because th= ey aren=E2=80=99t >> >> reflected in this (AFAIK). If we get into dedicated specific code- >> >> contributors, where do we do the cutoff? What about people who not wr= ite >> >> features, but review every pull request? It gets messy fast. I don=E2= =80=99t >> want >> >> to get into that. Plus there are plenty of great rewards already and = I=E2=80=99m >> >> sure once this is rolling, we will think of a lot more, too :) >> >> >> >> Best >> >> Jan >> >> -- >> >> >> >> >> >> >> >> >> >>> >> >>> I'm thinking it would be a small para at the bottom of the release >> >>> announcement, something like this: >> >>> >> >>> "This release is dedicated to the following advocates as a thank you >> >>> for helping grow the community: Alice, Bob, Chris" >> >>> >> >>> Perhaps we could even add some sort of clarification as to why they'= re >> >>> being thanked. >> >>> >> >>> Lena, for naming the release: we can exercise editorial control by >> >>> simply saying "that's not gonna fly, pick a different name." Would >> >>> that allay your concerns? >> >>> >> >>> On 30 October 2014 17:11, Lena Reinhard >> wrote: >> >>>> Also like all of them, except >> >>>> >> >>>>>> - Have a release dedicated to you >> >>>> >> >>>> I'd rather avoid that, as it sets the reward at a wrong place, imo. >> >>>> >> >>>>>> - Name the weekly news >> >>>> >> >>>> My main issue with this is that I fear running into discussions wha= t >> is >> >> appropriate as a name (in terms of our bylaws and CoC (which wouldn't >> have >> >> to be a discussion then at all), but also in terms of marketing. >> >>>> >> >>>> Rest looks great from my side. >> >>>> >> >>>> On 30 Oct 2014, at 16:51, Jan Lehnardt wrote: >> >>>> >> >>>>> I like them al except =E2=80=9CHave a release dedicated to you=E2= =80=9D :) >> >>>>> >> >>>>> >> >>>>>> On 30 Oct 2014, at 16:41 , Noah Slater wrote= : >> >>>>>> >> >>>>>> Hello, >> >>>>>> >> >>>>>> I'd like to set up the following rewards. Please review. If nobod= y >> >>>>>> objects to this email, I will assume consensus. >> >>>>>> >> >>>>>> Lena, a few of these relate to the weekly news, so I'm hoping you >> can >> >>>>>> look it over specifically in case you have any objections or >> >>>>>> suggestions for improvement! >> >>>>>> >> >>>>>> - #FollowFriday >> >>>>>> >> >>>>>> We include the advocate in a #FollowFriday tweet sent from @Couch= DB. >> >>>>>> >> >>>>>> - Individual Twitter thank you >> >>>>>> >> >>>>>> We post a tweet from @CouchDB, individually thanking the advocate= . >> >>>>>> >> >>>>>> - Thank you in the weekly news >> >>>>>> >> >>>>>> We include the advocate's name on a list of people we're thanking= in >> >>>>>> the next weekly news. (This would appear at the bottom of the pos= t.) >> >>>>>> >> >>>>>> - Individual profile in the weekly news >> >>>>>> >> >>>>>> We add a short para, no longer than a tweet (perhaps?) to the bot= tom >> >>>>>> of the weekly news, in a special thanks section (or similar). >> >>>>>> >> >>>>>> - Get featured on the website >> >>>>>> >> >>>>>> Join the list of featured advocates on our main homepage. We'd ke= ep >> X >> >>>>>> advocates here, removing people off as new people join. >> >>>>>> >> >>>>>> (This actually doubles as recruitment for new advocates.) >> >>>>>> >> >>>>>> - Enter the Hall of Fame >> >>>>>> >> >>>>>> The advocates name is added to the ADVOCATES file in the root of = the >> >>>>>> main CouchDB repository. >> >>>>>> >> >>>>>> - Have a release dedicated to you >> >>>>>> >> >>>>>> The advocates name is added to a list of people that our next >> release >> >>>>>> is dedicated to. This will appear at the bottom of the release >> >>>>>> announcement. >> >>>>>> >> >>>>>> - Name the weekly news >> >>>>>> >> >>>>>> The advocate gets to pick a fun name for the next weekly news. Th= is >> is >> >>>>>> included at the top of the weekly news in the style of "aka the X >> >>>>>> update" or similar. >> >>>>>> >> >>>>>> (This is just a small selection of the rewards, focusing here on >> >>>>>> recognition. I have other ideas, but I don't want to swap you.) >> >>>>>> >> >>>>>> Thanks, >> >>>>>> >> >>>>>> -- >> >>>>>> Noah Slater >> >>>>>> https://twitter.com/nslater >> >>>>> >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> 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 >> >> > > > -- > 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 --=20 Noah Slater https://twitter.com/nslater