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 725FC17E49 for ; Mon, 29 Sep 2014 14:09:10 +0000 (UTC) Received: (qmail 40809 invoked by uid 500); 29 Sep 2014 14:09:10 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 40763 invoked by uid 500); 29 Sep 2014 14:09:10 -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 40752 invoked by uid 99); 29 Sep 2014 14:09:10 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2014 14:09:10 +0000 Received: from localhost (HELO mail-ig0-f173.google.com) (127.0.0.1) (smtp-auth username nslater, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2014 14:09:10 +0000 Received: by mail-ig0-f173.google.com with SMTP id uq10so2069205igb.6 for ; Mon, 29 Sep 2014 07:09:09 -0700 (PDT) X-Gm-Message-State: ALoCoQlau0oFbifS68GwLtqGb22un4FkzyCdmG7UJrU0459K6EHIdaXOvxt6Op4+tzU7IOPLc8L6 MIME-Version: 1.0 X-Received: by 10.50.43.137 with SMTP id w9mr35409094igl.36.1411999749340; Mon, 29 Sep 2014 07:09:09 -0700 (PDT) Received: by 10.107.7.216 with HTTP; Mon, 29 Sep 2014 07:09:09 -0700 (PDT) X-Originating-IP: [85.12.8.106] In-Reply-To: References: Date: Mon, 29 Sep 2014 16:09:09 +0200 Message-ID: Subject: Re: Recruitment tweets From: Noah Slater To: "marketing@couchdb.apache.org" Content-Type: text/plain; charset=UTF-8 One of the problems with marketing activities is that quantitative data is quite hard to come by. A lot of marketing works by raising awareness of a particular thing, be that a brand, a product, event, or opportunity. More often than not, a person takes action on that awareness many hours, days, or weeks after learning about it. Making the connection between what you did in your marketing efforts, and conversions that you make (in this case, recruiting contributors), can be tricky (but not impossible). How about we take a two-pronged approach: - Regular, but generic, recruitment tweets, cycling between the different areas we want to attract contributions to - Specific, and sporadic, recruitment tweets for specific JIRA tickets, as and when we need it I can handle the first one with very little input. But how would we do the second one? Is there something we could in JIRA that would indicate that a ticket ought to be promoted from a recruitment perspective? On 29 September 2014 15:38, Alexander Shorin wrote: > Is there any metric to ensure that they'll work? > How about to send more concrete recruitment tweet against specific > issue? Like "CSS hero scrollbars hater wanted for COUCHDB-2305, many > kudos for help!" or something. > > -- > ,,,^..^,,, > > > On Mon, Sep 29, 2014 at 5:31 PM, Noah Slater wrote: >> Hi folks, >> >> I've set up a regular reminder to send out recruitment tweets. >> >> Here are two examples: >> >> https://twitter.com/CouchDB/status/516580274990514179 >> >> (Sent just now. RTs appreciated!) >> >> And here's an earlier one: >> >> https://twitter.com/CouchDB/status/471358568546193412 >> >> What do we think of these? Do you have any ideas about how often I >> should do this, or what sort of stuff I should highlight? >> >> Thanks, >> >> -- >> Noah Slater >> https://twitter.com/nslater -- Noah Slater https://twitter.com/nslater