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 4691511DAD for ; Tue, 10 Jun 2014 12:43:20 +0000 (UTC) Received: (qmail 35616 invoked by uid 500); 10 Jun 2014 12:43:20 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 35559 invoked by uid 500); 10 Jun 2014 12:43:19 -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 35549 invoked by uid 99); 10 Jun 2014 12:43:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jun 2014 12:43:19 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [188.94.27.146] (HELO nms02.nmmn.com) (188.94.27.146) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jun 2014 12:43:16 +0000 Received: from localhost (localhost [127.0.0.1]) by nms02.nmmn.com (Postfix) with ESMTP id B13BA5446C4 for ; Tue, 10 Jun 2014 14:42:52 +0200 (CEST) Received: from nms02.nmmn.com ([127.0.0.1]) by localhost (nms02.nmmn.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41luRysoEmGS for ; Tue, 10 Jun 2014 14:42:49 +0200 (CEST) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by nms02.nmmn.com (Postfix) with ESMTPA id 872385446C3 for ; Tue, 10 Jun 2014 14:42:49 +0200 (CEST) Received: by mail-qa0-f54.google.com with SMTP id j15so8966024qaq.41 for ; Tue, 10 Jun 2014 05:42:48 -0700 (PDT) X-Received: by 10.140.40.81 with SMTP id w75mr11493369qgw.112.1402404168799; Tue, 10 Jun 2014 05:42:48 -0700 (PDT) MIME-Version: 1.0 Reply-To: andy@nms.de Received: by 10.229.26.67 with HTTP; Tue, 10 Jun 2014 05:42:18 -0700 (PDT) In-Reply-To: <20982B81-A8D4-4DA0-9961-DC307008CAE8@thehoodiefirm.com> References: <9288993.71.1402069772896.JavaMail.jtouzet@jtouzet> <517584CF-A7C2-4F98-A7AF-B31747948C24@apache.org> <20982B81-A8D4-4DA0-9961-DC307008CAE8@thehoodiefirm.com> From: Andy Wenk Date: Tue, 10 Jun 2014 14:42:18 +0200 Message-ID: Subject: Re: CouchDB referrals? To: "marketing@couchdb.apache.org" Content-Type: multipart/alternative; boundary=001a11c151545022ca04fb7aaae4 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c151545022ca04fb7aaae4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Marketing hat: Noah, I like the additional idea you have. If a an advocate refers to a person who would be a good contributor and the person is finally contributing to CouchDB, the advocate will earn points. This would force the advocate to sieve persons willing to really contribute and not just refer to random persons. I think the tool is usable very nicely if used in a good way. Cheers Andy On 9 June 2014 20:19, Lena Reinhard wrote: > Marketing hat: keeping barriers for rewards low (e.g. already rewarding > contributions of non-elected ppl) sounds good, also adding more points if > the person is elected. From this point of view, I can also agree to seein= g > time and attention as a sort of currency. > > Community Management hat: although I agree that inviting people personall= y > to speak at confs helps, I think that the analogy of speaker invitations > for increasing diversity is only applicable in parts here. > In this case, marginalized people may still be only able to be advocates > (as it's less effort than the actual "contribution"). So even if this > referral option may lead to a more diverse group being able to make > referrals, the people referred still have to be people with enough time a= nd > attention span etc. to contribute freely, especially for then being elect= ed > (-> and bringing the referring person more points). Thus, from this > perspective, it's a good idea for increasing the number of referrals. But > it may be hard or not that effective in terms of increasing diversity. > Still, I think that it would be worth a trial to see how this goes - and > perhaps also to think about how this can be an opportunity to build a > reward system for less privileged people (as there are few to none in OSS > structures at the moment). I know that this is a hard one, but when we're > talking about openness and aiming for diversity, I see this as one of the > core problems (to which I don't know a solution yet myself, but which > doesn't mean that there is none). > > On 09.06.2014, at 15:58, Noah Slater wrote: > > > I have another idea to float: > > > > Advocates have the opportunity to refer a designer, author, marketing > > person, dev, etc. We personally reach out to them with a tailored > > email invitation. (We'd pre-write a few of these, one for each area of > > the project.) The email would outline what we do, and then go into a > > few details about the a certain area of contribution, with pointers to > > resources for getting started, etc. > > > > If the person starts contributing, the person who referred them is > > awarded with points. If we eventually elect that person, the person > > who referred them gets more points. (I believe this is directly > > analogous to how client referrals typically work on the platform.) > > > > Contributions are the capital of OSS. People's time and attention is > > our most important resource. > > > > So here's the analogy: > > > > Traditional referrals program: > > > > - Advocates refer individuals who "convert" by paying (contributing) > money. > > > > OSS referrals program: > > > > - Advocates refer individuals who "convert" by paying (contributing) > time. > > > > I don't think many people explicitly think about OSS in these terms. > > But when you do, a lot of things become clear. For example: > > recruitment should be your number one priority! Recruitment is your > > sales channel, effectively. > > > > "Sales channel" makes sense if you see time and attention as a sort of > currency. > > > > Most people think that the measure of health for an OSS project is how > > many downloads you have, or how many users you have. That's because in > > a business, these things translate to revenue. And revenue is your > > lifeblood > > > > But if time and attention are the capital of OSS, then contributions > > are your lifeblood. And it seems likely that traditional business > > practices used to maximise revenue might be applicable to maximising > > contribution. > > > > If we did something like this, would we be the first OSS project to > > actively reach out to people to invite them to contribute? > > > > Inviting speakers (usually from pools) is a very effective way of > > increasing speaker diversity at a conference. (Citations available > > upon request.) Perhaps invitation is one of the ways we can increase > > our project diversity? > > > > On 6 June 2014 18:47, Jan Lehnardt wrote: > >> just to note that I=E2=80=99d be equally happy with disabling it. > >> > >> On 06 Jun 2014, at 17:49 , Joan Touzet wrote: > >> > >>> Sounds like an impedance mismatch. Disable the functionality. > >>> > >>> It'd be nice to know how people get to our community, and it's good > >>> to have a consultancy network, but this really sounds more like a > >>> support function for channel partnerships and revenue recognition -- > >>> "virtual finders fees" as it were. Not sure if we need that. > >>> > >>> -Joan > >>> > >>> ----- Original Message ----- > >>> From: "Noah Slater" > >>> To: "Noah Slater" > >>> Cc: marketing@couchdb.apache.org, "Benoit Chesneau" < > bchesneau@gmail.com>, "Dave Cottlehuber" , "Jan L" < > jan@apache.org> > >>> Sent: Friday, June 6, 2014 8:11:00 AM > >>> Subject: Re: CouchDB referrals? > >>> > >>> I am particularly interested in the opinions of: > >>> > >>> - PMC members (from a governance perspective) > >>> - Marketing people (from a recruitment/community perspective) > >>> - People who offer CouchDB consulting (Jan, Dave, Benoit, etc.) > >>> > >>> On 4 June 2014 15:57, Noah Slater wrote: > >>>> Hello folks, > >>>> > >>>> The Influitive AdvocateHub has a primary concept of a referral. In t= he > >>>> context of a business, a referral is when an advocate refers a conta= ct > >>>> to the business. Obviously, this is very valuable for B2B business > >>>> that are looking for clients. > >>>> > >>>> CouchDB is not a B2B business, and so I'm not sure this particular > >>>> part of the AdvocateHub fits our use case. > >>>> > >>>> We can turn it off. But before we do, I wanted to explore some other > >>>> options. What could referrals mean for us, as a community? > >>>> > >>>> Some ideas: > >>>> > >>>> - A referral is just an advocate recommending CouchDB to a friend or > >>>> colleague. In this scenario, who does the referral contact? Do we pu= t > >>>> them in touch with a mailing list (seems a little odd), a particular > >>>> person, or particular persons? > >>>> > >>>> - A referral is more about contributors than it is about users. So t= he > >>>> advocate would be referring a contributor to the CouchDB project. > >>>> Perhaps a designer, a marketing person, a video blogger, a technical > >>>> author, or whatever. People we find hard to recruit normally. > >>>> (Remember that recruitment is our #1 biggest challenge.) > >>>> > >>>> - A referral is a business referral. We set up a list for people who > >>>> offer CouchDB services. A referral puts the a person in contact with > >>>> this list of people. So tenders can be made individually by whomever > >>>> is interested in the business. > >>>> > >>>> Thoughts? > >>>> > >>>> Thanks, > >>>> > >>>> -- > >>>> Noah Slater > >>>> https://twitter.com/nslater > >>> > >>> > >>> > >>> -- > >>> Noah Slater > >>> https://twitter.com/nslater > >> > > > > > > > > -- > > Noah Slater > > https://twitter.com/nslater > > --=20 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 --001a11c151545022ca04fb7aaae4--