You are viewing a plain text version of this content. The canonical link for it is here.
Posted to marketing@couchdb.apache.org by Javier Candeira <ja...@candeira.com> on 2014/10/04 02:17:18 UTC
Re: Recruitment tweets
Thanks Noah and Andy.
I am subscribed to marketing, dev, user and erlang. I'm also both on
#couchdb and #couchdb-dev.
Now looking at tickets sorted by skill level. Will comment on IRC.
Cheers,
Javier
On Tue, Sep 30, 2014 at 5:35 PM, Andy Wenk <an...@apache.org> wrote:
> Hi Javier,
>
> welcome :). As I understood, you want to start working on some topics. A
> good entry point is to scan
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20COUCHDB%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
>
> You will find a bunch of unresolved issues. They should be labelled with a
> difficulty indicator but as I just had a quick look it seems that not all
> have been labelled. You could pick some of the UI tickets and start working
> on it.
>
> Please make sure that you have subscribed to the dev@couchdb.apache.org
> mailinglist (http://couchdb.apache.org/#mailing-lists) and you should also
> jump into irc.freenode.net#couchdb-dev
>
> For the UI topics you can get in touch with robertkowalski and garren on
> IRC.
>
> Happy hacking :)
>
> Cheers
>
> Andy
>
>
> On 29 September 2014 22:04, Noah Slater <ns...@apache.org> wrote:
>
>> Javier,
>>
>> Could you clarify your request. Not sure I understood. Also, hi! :)
>>
>> On 29 September 2014 16:11, Javier Candeira <ja...@candeira.com> wrote:
>> > Hi Noah,
>> >
>> > I'm here, if you can help me triage a couple of easy bugs for a
>> > beginner to sink his teeth on.
>> >
>> > Javier
>> >
>> > On Tue, Sep 30, 2014 at 12:09 AM, Noah Slater <ns...@apache.org>
>> wrote:
>> >> 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 <kx...@gmail.com> 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 <ns...@apache.org>
>> 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
>>
>>
>>
>> --
>> 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
Re: Recruitment tweets
Posted by Andy Wenk <an...@apache.org>.
Welcome Javier :)
On 4 October 2014 11:57, Noah Slater <ns...@apache.org> wrote:
> Cool, thanks Javier!
>
> On 4 October 2014 02:17, Javier Candeira <ja...@candeira.com> wrote:
> > Thanks Noah and Andy.
> >
> > I am subscribed to marketing, dev, user and erlang. I'm also both on
> > #couchdb and #couchdb-dev.
> >
> > Now looking at tickets sorted by skill level. Will comment on IRC.
> >
> > Cheers,
> >
> > Javier
> >
> > On Tue, Sep 30, 2014 at 5:35 PM, Andy Wenk <an...@apache.org> wrote:
> >> Hi Javier,
> >>
> >> welcome :). As I understood, you want to start working on some topics. A
> >> good entry point is to scan
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20COUCHDB%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
> >>
> >> You will find a bunch of unresolved issues. They should be labelled
> with a
> >> difficulty indicator but as I just had a quick look it seems that not
> all
> >> have been labelled. You could pick some of the UI tickets and start
> working
> >> on it.
> >>
> >> Please make sure that you have subscribed to the dev@couchdb.apache.org
> >> mailinglist (http://couchdb.apache.org/#mailing-lists) and you should
> also
> >> jump into irc.freenode.net#couchdb-dev
> >>
> >> For the UI topics you can get in touch with robertkowalski and garren on
> >> IRC.
> >>
> >> Happy hacking :)
> >>
> >> Cheers
> >>
> >> Andy
> >>
> >>
> >> On 29 September 2014 22:04, Noah Slater <ns...@apache.org> wrote:
> >>
> >>> Javier,
> >>>
> >>> Could you clarify your request. Not sure I understood. Also, hi! :)
> >>>
> >>> On 29 September 2014 16:11, Javier Candeira <ja...@candeira.com>
> wrote:
> >>> > Hi Noah,
> >>> >
> >>> > I'm here, if you can help me triage a couple of easy bugs for a
> >>> > beginner to sink his teeth on.
> >>> >
> >>> > Javier
> >>> >
> >>> > On Tue, Sep 30, 2014 at 12:09 AM, Noah Slater <ns...@apache.org>
> >>> wrote:
> >>> >> 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 <kx...@gmail.com>
> 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 <ns...@apache.org>
> >>> 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
> >>>
> >>>
> >>>
> >>> --
> >>> 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
>
--
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
Re: Recruitment tweets
Posted by Noah Slater <ns...@apache.org>.
Cool, thanks Javier!
On 4 October 2014 02:17, Javier Candeira <ja...@candeira.com> wrote:
> Thanks Noah and Andy.
>
> I am subscribed to marketing, dev, user and erlang. I'm also both on
> #couchdb and #couchdb-dev.
>
> Now looking at tickets sorted by skill level. Will comment on IRC.
>
> Cheers,
>
> Javier
>
> On Tue, Sep 30, 2014 at 5:35 PM, Andy Wenk <an...@apache.org> wrote:
>> Hi Javier,
>>
>> welcome :). As I understood, you want to start working on some topics. A
>> good entry point is to scan
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20COUCHDB%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
>>
>> You will find a bunch of unresolved issues. They should be labelled with a
>> difficulty indicator but as I just had a quick look it seems that not all
>> have been labelled. You could pick some of the UI tickets and start working
>> on it.
>>
>> Please make sure that you have subscribed to the dev@couchdb.apache.org
>> mailinglist (http://couchdb.apache.org/#mailing-lists) and you should also
>> jump into irc.freenode.net#couchdb-dev
>>
>> For the UI topics you can get in touch with robertkowalski and garren on
>> IRC.
>>
>> Happy hacking :)
>>
>> Cheers
>>
>> Andy
>>
>>
>> On 29 September 2014 22:04, Noah Slater <ns...@apache.org> wrote:
>>
>>> Javier,
>>>
>>> Could you clarify your request. Not sure I understood. Also, hi! :)
>>>
>>> On 29 September 2014 16:11, Javier Candeira <ja...@candeira.com> wrote:
>>> > Hi Noah,
>>> >
>>> > I'm here, if you can help me triage a couple of easy bugs for a
>>> > beginner to sink his teeth on.
>>> >
>>> > Javier
>>> >
>>> > On Tue, Sep 30, 2014 at 12:09 AM, Noah Slater <ns...@apache.org>
>>> wrote:
>>> >> 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 <kx...@gmail.com> 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 <ns...@apache.org>
>>> 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
>>>
>>>
>>>
>>> --
>>> 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