You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Noah Slater <ns...@apache.org> on 2013/10/05 19:04:10 UTC
[PROPOSAL] Use Influitive to help with marketing
Hi devs,
I would like to propose that we use Influitive to help us improve our
marketing efforts.
I fully intend to execute this proposal myself. If you want to volunteer,
that is great. But if you are not interested in this, that is fine also.
Nobody has to participate if they do not want to. I am quite happy to run
it as an experiment myself. If it works we can continue, and if it doesn't,
we can stop.
Unless anybody objects, I will assume lazy consensus after three days, and
let Influitive that we have the green light to move forward.
= Introduction =
Influitive AdvocateHub is an advocacy marketing platform.
Think of it like Kickstarter, for marketing. You post a description of what
you want to accomplish, and then your community members pitch in and help
to make it happen.
As an open source project, we struggle to market ourselves because we have
no budget. Where a typical company might take out ads, or pay people to
write technical content, we rely on volunteer time and word of mouth. But
this is typically disorganised.
AdvocateHub is a tool that that will allow us to coordinate that volunteer
time and word of mouth. We can create a steady stream of challenges or
requests for help and people who are committed to the project can organise
around these, and help us spread the word of CouchDB.
In return for doing these things, we reward them with prestige and swag.
And maybe a few other exclusive items, like conference tickets, or a round
of drinks on me.
You should watch these two intro videos:
http://influitive.com/introduction-to-advocate-marketing/
http://influitive.com/learn-more-about-the-advocatehub/
= Donation =
AdvocateHub is usually premium service. However, Influitive has very
generously offered to donate an account to the project. This is the first
open source project that Influitive has supported like this, so I am very
grateful for the opportunity!
AdvocateHub is designed for commercial companies, but I think we can make
it work for an open source project. Influitive will be monitoring our
progress, and if things are not working out, we’ll end the experiment. As
part of this agreement, I will be the account owner and will be responsible
for its operation. But if you are a committer and you want to help out, I
can add you as an admin. This is similar to how we run our social media
accounts.
In return for the support, I am proposing to:
* Promote the use of our AdvocateHub within our community
* Thank them from our website, wiki, and social media accounts
* Document our progress with the occasional blog or tweet
Promoting the use of our AdvocateHub will probably take the form of
mentioning new challenges on the mailing list, blog, Twitter, Google+, etc.
Obviously, we will want to encourage as many people as possible to get
involved in the AdvocateHub as possible.
As for documenting our progress, I am thinking that the occasional post
covering how we’re using the tool, and what sorts of results we’re seeing
would be appropriate.
I have spoken with the ASF fundraising team already, and there are no
concerns with these plans at the foundation level.
= Challenges =
AdvocateHub is built around the concept of a challenge, or request for
help. We can design these however we want, and I will be looking for input
from the community.
Ideas for easy challenges:
* Retweet an official @CouchDB tweet
* Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
* Publicly mention CouchDB on Twitter, Google+, LinkedIn, your blog, etc
* Share an official project blog post somewhere
Ideas for medium challenges:
* Watch a featured video
* Read a featured blog post, or section of the docs
* Help someone out on the mailing list
* Answer a CouchDB question on Stack Overflow, Server Fault, etc
* Talk about CouchDB in response to a Quora question
* Talk about CouchDB in response to a submission on Hacker News,
Reddit, etc
* Comment on an official blog post, or a blog post about CouchDB
* Post a review on alternativeTo, or other review sites, blog posts, etc
* Provide an official endorsement or quote from your company about
CouchDB
* Complete a survey (I plan to actually make some surveys)
Ideas for hard challenges:
* Create a CouchDB client, library, or tool
* Produce early/mid/late stage technical content
* Produce a CouchDB white paper
* Give a talk or screencast about CouchDB
* Share a CouchDB success story, testimonial, or case-study
* Organise a CouchDB meet-up
* Organise a CouchDB conference
And then, challenges for actually contributing back to CouchDB itself:
* Triage X many JIRA tickets
* Fix up outstanding issues on a CouchDB pull request
* Contribute a fix for a JIRA ticket
(This might be a little outside of the scope of AdvocateHub, as this would
request contribution back to the project itself. Still, it would be
interesting to see if this would work. As a volunteer organisation,
volunteer time and attracting contributions is our top priority.)
= Rewards =
Completing challenges gives you points, levels, and badges. I know that
many people love this kind of system, and are happy to compete with each
other for points alone. However, we also have the option of allowing
advocates to exchange points for prizes.
AdvocateHub has an integration with a swag drop-ship merchant. Hopefully, I
can attract a third-party to help with the bill for this. It would mean
that by completing challenges, we can reward advocates with t-shirts,
hoodies, mugs, pins, stickers, and so on!
In addition to swag, we could also offer:
* Individual promotion for you
* Priority or free tickets to the regular CouchDB Confs
* Email support or advice from the committers (depends on who
volunteers time)
* Private call with one the committers (depends on who volunteers time)
* Drinks on Noah (though, you’ll have to come find me!)
Promotion could be quite a draw. Imagine a weekly Tweet along the lines of
“Thanks to @ARandomPerson for supporting CouchDB this week. You should
follow her on Twitter!” We could also include a mention in our weekly
CouchDB news. (A blog idea that I have not executed on yet.) As far as I
can tell, we’d only be able to promote individual accounts, not businesses.
The ASF has very strict vendor neutrality rules that we must adhere to.
Some other ideas of how we could provide return promotion:
* Mention on our homepage that week
* Get on our weekly @CouchDB #FollowFriday
* Entered into a “hall of fame”
* Get mentioned in our Git commits, issues, or pull requests
The @CouchDB account has close to 10k followers. And our homepage receives
around 8,500 page views per month at the moment. Those numbers are not to
be sniffed at!
(This is heavily inspired by Hoodie, who allow people to sponsor the
project in return for promotion via different channels. I think we can
borrow some of this.)
The specifics of the reward programme is unimportant at this stage. Like
the details of the challenges themselves, we can figure this out as we move
forward.
Thanks,
--
Noah Slater
https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Noah Slater <ns...@apache.org>.
Benoit. You raise some good questions. I'll have a think on it and get back
to you.
On 6 October 2013 22:07, Benoit Chesneau <bc...@gmail.com> wrote:
> On Sun, Oct 6, 2013 at 6:25 PM, Benoit Chesneau <bc...@gmail.com>
> wrote:
>
> >
> > I understand that you want to experiment and I'm OK with that. But I
> > would like to define it a little more the limit of it. In particularly to
> > answer to the following questions:
> >
> > - How to ensure this reward system is optional?
> > - How to ensure that people that not participate do not feel unconsidered
> > by other members of the community because not rewarded by the Influtive
> > system?
> > - What will define the success or failure of the experimentation? What
> is
> > the deadline of the experimentation?
> >
> >
> > If we can find consensus around the responses to theses questions I am
> > definitely +1 to start it.
> >
> >
> >
> Anyway I like I said I would be Ok to start an experimentation, but it
> would be good to fix the limits of such experimentation and especially know
> how to value its success and when we will change its status. I really wish
> we could answer to the questions above before to start it.
>
> - benoit
>
--
Noah Slater
https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Benoit Chesneau <bc...@gmail.com>.
On Sun, Oct 6, 2013 at 6:25 PM, Benoit Chesneau <bc...@gmail.com> wrote:
>
> I understand that you want to experiment and I'm OK with that. But I
> would like to define it a little more the limit of it. In particularly to
> answer to the following questions:
>
> - How to ensure this reward system is optional?
> - How to ensure that people that not participate do not feel unconsidered
> by other members of the community because not rewarded by the Influtive
> system?
> - What will define the success or failure of the experimentation? What is
> the deadline of the experimentation?
>
>
> If we can find consensus around the responses to theses questions I am
> definitely +1 to start it.
>
>
>
Anyway I like I said I would be Ok to start an experimentation, but it
would be good to fix the limits of such experimentation and especially know
how to value its success and when we will change its status. I really wish
we could answer to the questions above before to start it.
- benoit
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Benoit Chesneau <bc...@gmail.com>.
On Sun, Oct 6, 2013 at 5:54 PM, Noah Slater <ns...@apache.org> wrote:
> > This system is quite odd and artificial.
>
> I don't understand what is "artificial" about it. Is JIRA also artificial?
>
> We're defining a list of things we would like help with, and then inviting
> people to help us with them. There's nothing artificial about that. We're
> not asking people to say or do things they don't believe in. We won't be
> asking people to write fake reviews. We will be asking people to review us
> honestly. (For example.)
>
>
I can see the syndrome of the "best employee of the month" behind the
system of reward. And I am definitely uncomfortable with that.
There is no reward system in Jira. Jira items are neutral. People can vote
(see the vote link on the right) on the tickets. What would be good is to
report regularly about waiting tickets in an automated way though.
> Plus, who will choose these items?
>
> Us! :)
>
> Well, initially me. But if you wanna help out, just help out. We will have
> full control.
>
> > Why not simply having a TODO list, aka roadmap in which people can simply
> pick an item on which they think they can can help?
>
> That's exactly what I'm proposing! :) That's what Influitive helps us with.
>
> JIRA is a good TODO list for the code, and Influtive will make a good TODO
> list for marketing activities. Different tools to suit different parts of
> the project.
>
> > There is something really odd an artificial in giving a reward to do such
> thing
>
> Unusual for an open source project, maybe. But not unusual for a company.
> So it's an experiment, I guess. Perhaps it works, perhaps it doesn't.
> There's no worry here. If it doesn't work, we just stop using it. And I
> will find another tool that does.
>
> There is an ulterior motive here for me wanting to reward our passionate
> users with t-shirts, and swag. People wearing CouchDB t-shirts are like
> walking billboards. Free advertising!
>
> But for the RT stuff, or even just #FF, I think it's nice to recognise
> people who contribute to the project. I mean, really, we should be doing
> that with patches, and code. and stuff too!
>
You already recognised them when you take their patch in consideration and
discuss items with them. And to be honest we are not quite good at that
right now. Some patches land for a long time in the tracker, some
discussions about features aren't followed, ... If we want to recognise
better the people, we should first improve that.
About the "free advertising" I am all to have a "store" link like the one
on ubuntu:
http://shop.ubuntu.com/
It helps to create an identity.
And I don't see why sone couldn't be offered to some peoples from time to
time. But why not making it spontaneous instead of having it organised in a
"reward" system ? How would you make the distinction of the guy simply
retweeting a thing and the other one giving a patch. Both helps a project
but in a different manner. How would you recognise the guy that do a lot of
support on the ml vs the other one. What about the guy busy, working on the
things but not participating to such system. How will you thank him?
Such limits are really hard to fix and I am not sure I want to fix them nor
I want to see someone fix them. But I am OK to discuss it anyway.
I understand that you want to experiment and I'm OK with that. But I would
like to define it a little more the limit of it. In particularly to answer
to the following questions:
- How to ensure this reward system is optional?
- How to ensure that people that not participate do not feel unconsidered
by other members of the community because not rewarded by the Influtive
system?
- What will define the success or failure of the experimentation? What is
the deadline of the experimentation?
If we can find consensus around the responses to theses questions I am
definitely +1 to start it.
- benoit
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Noah Slater <ns...@apache.org>.
> This system is quite odd and artificial.
I don't understand what is "artificial" about it. Is JIRA also artificial?
We're defining a list of things we would like help with, and then inviting
people to help us with them. There's nothing artificial about that. We're
not asking people to say or do things they don't believe in. We won't be
asking people to write fake reviews. We will be asking people to review us
honestly. (For example.)
> Plus, who will choose these items?
Us! :)
Well, initially me. But if you wanna help out, just help out. We will have
full control.
> Why not simply having a TODO list, aka roadmap in which people can simply
pick an item on which they think they can can help?
That's exactly what I'm proposing! :) That's what Influitive helps us with.
JIRA is a good TODO list for the code, and Influtive will make a good TODO
list for marketing activities. Different tools to suit different parts of
the project.
> There is something really odd an artificial in giving a reward to do such
thing
Unusual for an open source project, maybe. But not unusual for a company.
So it's an experiment, I guess. Perhaps it works, perhaps it doesn't.
There's no worry here. If it doesn't work, we just stop using it. And I
will find another tool that does.
There is an ulterior motive here for me wanting to reward our passionate
users with t-shirts, and swag. People wearing CouchDB t-shirts are like
walking billboards. Free advertising!
But for the RT stuff, or even just #FF, I think it's nice to recognise
people who contribute to the project. I mean, really, we should be doing
that with patches, and code. and stuff too!
On 6 October 2013 17:44, Benoit Chesneau <bc...@gmail.com> wrote:
> On Sun, Oct 6, 2013 at 5:33 PM, Benoit Chesneau <bc...@gmail.com>
> wrote:
>
> >
> >
> >
> > On Sun, Oct 6, 2013 at 5:08 PM, Noah Slater <ns...@apache.org> wrote:
> >
> >> On 6 October 2013 16:57, Alexander Shorin <kx...@gmail.com> wrote:
> >>
> >> > How does it works on practice (yes, I had watch the videos) and how it
> >> > will change/improve current state of things?
> >> >
> >>
> >> There will be a site you can go to to view the current challenges, and
> you
> >> can work on them. Sort of like how you can go to JIRA, and find tickets
> to
> >> work on. The challenges can be created by the community. It's our way of
> >> saying "hey, if you love CouchDB and you want to help us out, these are
> >> some of the things you could do."
> >>
> >> The current state of things is that nothing very much happens. There is
> >> practically no marketing activity, and no co-ordinated attempts to
> promote
> >> CouchDB. So any sort of improvement or organisation here would be a good
> >> thing.
> >>
> >>
> >> > P.S. I feel that I had read post as "Do X for reward, not because you
> >> > likes/uses/develops/____ (fill the other) CouchDB". Am I wrong?
> >> >
> >>
> >> This isn't about bribing people to do things. If you're not interested
> in
> >> CouchDB, don't take part.
> >>
> >> Influtive is a way for people who are already very passionate about
> >> CouchDB
> >> to co-ordinate with each other and work towards goals that provide a
> >> meaningful benefit to the project.
> >>
> >
> > Hrm this seems a little rude. What about people very passionate and
> > interested in couchdb that don't want to be part of such system?
> >
> >
> >>
> >> The rewards system is our way of thanking them for helping out. And as I
> >> mention, can be as simple as them earning points in Influtive, and us
> >> giving them the occasional shout-out.
> >>
> >>
> > This system is quite odd and artificial. Why do we need to use a carrot
> to
> > encourage someone already passionate? Plus, who will choose these items?
> >
> > Why not simply having a TODO list, aka roadmap in which people can simply
> > pick an item on which they think they can can help? Using the mail, ml,
> > and irc then people could coordinate themselves around the item and let
> > other they are working on.
> >
> >
> >
> This was for the technical todo. I was also thinking of having a media kit
> that people can use for events, website and other.
>
> Fr the RT and co I definitely would prefer it based on the pure
> volunteering. While I also think we need to encourage this behaviour I
> would prefer to do it by proposing tools to do that easily. In one click.
> aka a +1 button, a "share this" link. such thing. There is something really
> odd an artificial in giving a reward to do such thing that makes me really
> uncomfortable.
>
> - benoit
>
--
Noah Slater
https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Benoit Chesneau <bc...@gmail.com>.
On Sun, Oct 6, 2013 at 5:33 PM, Benoit Chesneau <bc...@gmail.com> wrote:
>
>
>
> On Sun, Oct 6, 2013 at 5:08 PM, Noah Slater <ns...@apache.org> wrote:
>
>> On 6 October 2013 16:57, Alexander Shorin <kx...@gmail.com> wrote:
>>
>> > How does it works on practice (yes, I had watch the videos) and how it
>> > will change/improve current state of things?
>> >
>>
>> There will be a site you can go to to view the current challenges, and you
>> can work on them. Sort of like how you can go to JIRA, and find tickets to
>> work on. The challenges can be created by the community. It's our way of
>> saying "hey, if you love CouchDB and you want to help us out, these are
>> some of the things you could do."
>>
>> The current state of things is that nothing very much happens. There is
>> practically no marketing activity, and no co-ordinated attempts to promote
>> CouchDB. So any sort of improvement or organisation here would be a good
>> thing.
>>
>>
>> > P.S. I feel that I had read post as "Do X for reward, not because you
>> > likes/uses/develops/____ (fill the other) CouchDB". Am I wrong?
>> >
>>
>> This isn't about bribing people to do things. If you're not interested in
>> CouchDB, don't take part.
>>
>> Influtive is a way for people who are already very passionate about
>> CouchDB
>> to co-ordinate with each other and work towards goals that provide a
>> meaningful benefit to the project.
>>
>
> Hrm this seems a little rude. What about people very passionate and
> interested in couchdb that don't want to be part of such system?
>
>
>>
>> The rewards system is our way of thanking them for helping out. And as I
>> mention, can be as simple as them earning points in Influtive, and us
>> giving them the occasional shout-out.
>>
>>
> This system is quite odd and artificial. Why do we need to use a carrot to
> encourage someone already passionate? Plus, who will choose these items?
>
> Why not simply having a TODO list, aka roadmap in which people can simply
> pick an item on which they think they can can help? Using the mail, ml,
> and irc then people could coordinate themselves around the item and let
> other they are working on.
>
>
>
This was for the technical todo. I was also thinking of having a media kit
that people can use for events, website and other.
Fr the RT and co I definitely would prefer it based on the pure
volunteering. While I also think we need to encourage this behaviour I
would prefer to do it by proposing tools to do that easily. In one click.
aka a +1 button, a "share this" link. such thing. There is something really
odd an artificial in giving a reward to do such thing that makes me really
uncomfortable.
- benoit
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Benoit Chesneau <bc...@gmail.com>.
On Mon, Oct 7, 2013 at 12:52 AM, Octavian Damiean <od...@linux.com>wrote:
> On Sun, Oct 6, 2013 at 9:53 PM, Benoit Chesneau <bc...@gmail.com>
> wrote:
>
> > Also stack overflow is a site maintained by a private company. I don't
> see
> > it as a completely maintained network more as a service a company founded
> > to make business on jobs and advertising taking advantage of the content
> > posted by others.
>
>
> You might want to check your facts on that one but let's not get off-topic
> on that.
>
>
why do you think a VC firm invested 6 M of $ in stack exchange?
http://blog.stackoverflow.com/2010/05/announcing-our-series-a/
- benoit
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Octavian Damiean <od...@linux.com>.
On Sun, Oct 6, 2013 at 9:53 PM, Benoit Chesneau <bc...@gmail.com> wrote:
> Also stack overflow is a site maintained by a private company. I don't see
> it as a completely maintained network more as a service a company founded
> to make business on jobs and advertising taking advantage of the content
> posted by others.
You might want to check your facts on that one but let's not get off-topic
on that.
--
Octavian Damiean
GitHub: https://github.com/mainerror
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Benoit Chesneau <bc...@gmail.com>.
On Sun, Oct 6, 2013 at 9:19 PM, Octavian Damiean <od...@linux.com> wrote:
> On Sun, Oct 6, 2013 at 8:39 PM, Benoit Chesneau <bc...@gmail.com>
> wrote:
>
> > On Sun, Oct 6, 2013 at 8:08 PM, Octavian Damiean <od...@linux.com>
> > wrote:
> >
> > > On Sun, Oct 6, 2013 at 5:33 PM, Benoit Chesneau <bc...@gmail.com>
> > > wrote:
> > >
> > > > Hrm this seems a little rude. What about people very passionate and
> > > > interested in couchdb that don't want to be part of such system?
> > >
> > >
> > > I don't quite understand this question. Nothing I guess, they keep
> doing
> > > what they do.
> > >
> > >
> > The question is related to:
> >
> > """This isn't about bribing people to do things. If you're not interested
> > in
> > CouchDB, don't take part.
> > """
> >
>
> Well, that's also your answer.
>
no i's not I'm quoting noah.
>
>
> > >
> > >
> > > > This system is quite odd and artificial. Why do we need to use a
> carrot
> > > to
> > > > encourage someone already passionate? Plus, who will choose these
> > items?
> > > >
> > > > Why not simply having a TODO list, aka roadmap in which people can
> > simply
> > > > pick an item on which they think they can can help? Using the mail,
> > ml,
> > > > and irc then people could coordinate themselves around the item and
> let
> > > > other they are working on.
> > > >
> > >
> > > It's about bringing new people to the table, not solely about getting
> the
> > > already contributing member to contribute more. At least that's how I
> > > understand it.
> > >
> > >
> > New people will come if they are interested to. Coming for the carrot is
> > not really healthy imo.
> >
> > - benoit
> >
>
> Well, that's how people work. The system is proven, it's something from
> the gaming world and transitioned over to other parts of our life. Take
> Stack Exchange for example, the system works. It is a completely community
> maintained network (in case you are wondering, StackOverflow.com is part of
> that network).
>
I disagree. It may be part of your life but It is not part of mine at al
neither it is to a lot of people I value people on their merit and I don't
need to mark someone with a badge to recognise its merits.
Also stack overflow is a site maintained by a private company. I don't see
it as a completely maintained network more as a service a company founded
to make business on jobs and advertising taking advantage of the content
posted by others.
> You don't have to see it as bribing someone to do something but as an extra
> reward for people that do something. Of course everyone should be rewarded
> in one or another way, but that's exactly the point of the system Noah told
> us about.
>
>
My point is that you don't need this artificial reward to be recognised.
Working with someone is a good way to recognise him.
- benoit
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Octavian Damiean <od...@linux.com>.
On Sun, Oct 6, 2013 at 8:39 PM, Benoit Chesneau <bc...@gmail.com> wrote:
> On Sun, Oct 6, 2013 at 8:08 PM, Octavian Damiean <od...@linux.com>
> wrote:
>
> > On Sun, Oct 6, 2013 at 5:33 PM, Benoit Chesneau <bc...@gmail.com>
> > wrote:
> >
> > > Hrm this seems a little rude. What about people very passionate and
> > > interested in couchdb that don't want to be part of such system?
> >
> >
> > I don't quite understand this question. Nothing I guess, they keep doing
> > what they do.
> >
> >
> The question is related to:
>
> """This isn't about bribing people to do things. If you're not interested
> in
> CouchDB, don't take part.
> """
>
Well, that's also your answer.
> >
> >
> > > This system is quite odd and artificial. Why do we need to use a carrot
> > to
> > > encourage someone already passionate? Plus, who will choose these
> items?
> > >
> > > Why not simply having a TODO list, aka roadmap in which people can
> simply
> > > pick an item on which they think they can can help? Using the mail,
> ml,
> > > and irc then people could coordinate themselves around the item and let
> > > other they are working on.
> > >
> >
> > It's about bringing new people to the table, not solely about getting the
> > already contributing member to contribute more. At least that's how I
> > understand it.
> >
> >
> New people will come if they are interested to. Coming for the carrot is
> not really healthy imo.
>
> - benoit
>
Well, that's how people work. The system is proven, it's something from
the gaming world and transitioned over to other parts of our life. Take
Stack Exchange for example, the system works. It is a completely community
maintained network (in case you are wondering, StackOverflow.com is part of
that network).
You don't have to see it as bribing someone to do something but as an extra
reward for people that do something. Of course everyone should be rewarded
in one or another way, but that's exactly the point of the system Noah told
us about.
--
Octavian Damiean
GitHub: https://github.com/mainerror
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Benoit Chesneau <bc...@gmail.com>.
On Sun, Oct 6, 2013 at 8:08 PM, Octavian Damiean <od...@linux.com> wrote:
> On Sun, Oct 6, 2013 at 5:33 PM, Benoit Chesneau <bc...@gmail.com>
> wrote:
>
> > Hrm this seems a little rude. What about people very passionate and
> > interested in couchdb that don't want to be part of such system?
>
>
> I don't quite understand this question. Nothing I guess, they keep doing
> what they do.
>
>
The question is related to:
"""This isn't about bribing people to do things. If you're not interested in
CouchDB, don't take part.
"""
>
>
> > This system is quite odd and artificial. Why do we need to use a carrot
> to
> > encourage someone already passionate? Plus, who will choose these items?
> >
> > Why not simply having a TODO list, aka roadmap in which people can simply
> > pick an item on which they think they can can help? Using the mail, ml,
> > and irc then people could coordinate themselves around the item and let
> > other they are working on.
> >
>
> It's about bringing new people to the table, not solely about getting the
> already contributing member to contribute more. At least that's how I
> understand it.
>
>
New people will come if they are interested to. Coming for the carrot is
not really healthy imo.
- benoit
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Octavian Damiean <od...@linux.com>.
On Sun, Oct 6, 2013 at 5:33 PM, Benoit Chesneau <bc...@gmail.com> wrote:
> Hrm this seems a little rude. What about people very passionate and
> interested in couchdb that don't want to be part of such system?
I don't quite understand this question. Nothing I guess, they keep doing
what they do.
> This system is quite odd and artificial. Why do we need to use a carrot to
> encourage someone already passionate? Plus, who will choose these items?
>
> Why not simply having a TODO list, aka roadmap in which people can simply
> pick an item on which they think they can can help? Using the mail, ml,
> and irc then people could coordinate themselves around the item and let
> other they are working on.
>
It's about bringing new people to the table, not solely about getting the
already contributing member to contribute more. At least that's how I
understand it.
--
Octavian Damiean
GitHub: https://github.com/mainerror
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Benoit Chesneau <bc...@gmail.com>.
On Sun, Oct 6, 2013 at 5:08 PM, Noah Slater <ns...@apache.org> wrote:
> On 6 October 2013 16:57, Alexander Shorin <kx...@gmail.com> wrote:
>
> > How does it works on practice (yes, I had watch the videos) and how it
> > will change/improve current state of things?
> >
>
> There will be a site you can go to to view the current challenges, and you
> can work on them. Sort of like how you can go to JIRA, and find tickets to
> work on. The challenges can be created by the community. It's our way of
> saying "hey, if you love CouchDB and you want to help us out, these are
> some of the things you could do."
>
> The current state of things is that nothing very much happens. There is
> practically no marketing activity, and no co-ordinated attempts to promote
> CouchDB. So any sort of improvement or organisation here would be a good
> thing.
>
>
> > P.S. I feel that I had read post as "Do X for reward, not because you
> > likes/uses/develops/____ (fill the other) CouchDB". Am I wrong?
> >
>
> This isn't about bribing people to do things. If you're not interested in
> CouchDB, don't take part.
>
> Influtive is a way for people who are already very passionate about CouchDB
> to co-ordinate with each other and work towards goals that provide a
> meaningful benefit to the project.
>
Hrm this seems a little rude. What about people very passionate and
interested in couchdb that don't want to be part of such system?
>
> The rewards system is our way of thanking them for helping out. And as I
> mention, can be as simple as them earning points in Influtive, and us
> giving them the occasional shout-out.
>
>
This system is quite odd and artificial. Why do we need to use a carrot to
encourage someone already passionate? Plus, who will choose these items?
Why not simply having a TODO list, aka roadmap in which people can simply
pick an item on which they think they can can help? Using the mail, ml,
and irc then people could coordinate themselves around the item and let
other they are working on.
- benoît
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Noah Slater <ns...@apache.org>.
Yep, we'd run it ourselves. It's just a tool for us to organise our
fans/users to help us get the word out about CouchDB and the blog posts,
tweets, and what not that we produce. And also to encourage people to
contribute their own blog posts, testimonials, reviews, and so on. (Which
would be super helpful!)
On 6 October 2013 17:21, Alexander Shorin <kx...@gmail.com> wrote:
> On Sun, Oct 6, 2013 at 7:08 PM, Noah Slater <ns...@apache.org> wrote:
> > On 6 October 2013 16:57, Alexander Shorin <kx...@gmail.com> wrote:
> >
> >> How does it works on practice (yes, I had watch the videos) and how it
> >> will change/improve current state of things?
> >>
> >
> > There will be a site you can go to to view the current challenges, and
> you
> > can work on them. Sort of like how you can go to JIRA, and find tickets
> to
> > work on. The challenges can be created by the community. It's our way of
> > saying "hey, if you love CouchDB and you want to help us out, these are
> > some of the things you could do."
> >
> > The current state of things is that nothing very much happens. There is
> > practically no marketing activity, and no co-ordinated attempts to
> promote
> > CouchDB. So any sort of improvement or organisation here would be a good
> > thing.
> >
> >
> >> P.S. I feel that I had read post as "Do X for reward, not because you
> >> likes/uses/develops/____ (fill the other) CouchDB". Am I wrong?
> >>
> >
> > This isn't about bribing people to do things. If you're not interested in
> > CouchDB, don't take part.
> >
> > Influtive is a way for people who are already very passionate about
> CouchDB
> > to co-ordinate with each other and work towards goals that provide a
> > meaningful benefit to the project.
> >
> > The rewards system is our way of thanking them for helping out. And as I
> > mention, can be as simple as them earning points in Influtive, and us
> > giving them the occasional shout-out.
> >
> >
> > --
> > Noah Slater
> > https://twitter.com/nslater
>
> Aha, I see. Some kind of StackOverflow, but for project's community
> and not for questions, but for actions. I thought wrong that this
> service has his own community that helps their customers with
> "marketing challenges". Thanks for clarification!
>
> --
> ,,,^..^,,,
>
--
Noah Slater
https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Alexander Shorin <kx...@gmail.com>.
On Sun, Oct 6, 2013 at 7:08 PM, Noah Slater <ns...@apache.org> wrote:
> On 6 October 2013 16:57, Alexander Shorin <kx...@gmail.com> wrote:
>
>> How does it works on practice (yes, I had watch the videos) and how it
>> will change/improve current state of things?
>>
>
> There will be a site you can go to to view the current challenges, and you
> can work on them. Sort of like how you can go to JIRA, and find tickets to
> work on. The challenges can be created by the community. It's our way of
> saying "hey, if you love CouchDB and you want to help us out, these are
> some of the things you could do."
>
> The current state of things is that nothing very much happens. There is
> practically no marketing activity, and no co-ordinated attempts to promote
> CouchDB. So any sort of improvement or organisation here would be a good
> thing.
>
>
>> P.S. I feel that I had read post as "Do X for reward, not because you
>> likes/uses/develops/____ (fill the other) CouchDB". Am I wrong?
>>
>
> This isn't about bribing people to do things. If you're not interested in
> CouchDB, don't take part.
>
> Influtive is a way for people who are already very passionate about CouchDB
> to co-ordinate with each other and work towards goals that provide a
> meaningful benefit to the project.
>
> The rewards system is our way of thanking them for helping out. And as I
> mention, can be as simple as them earning points in Influtive, and us
> giving them the occasional shout-out.
>
>
> --
> Noah Slater
> https://twitter.com/nslater
Aha, I see. Some kind of StackOverflow, but for project's community
and not for questions, but for actions. I thought wrong that this
service has his own community that helps their customers with
"marketing challenges". Thanks for clarification!
--
,,,^..^,,,
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Noah Slater <ns...@apache.org>.
On 6 October 2013 16:57, Alexander Shorin <kx...@gmail.com> wrote:
> How does it works on practice (yes, I had watch the videos) and how it
> will change/improve current state of things?
>
There will be a site you can go to to view the current challenges, and you
can work on them. Sort of like how you can go to JIRA, and find tickets to
work on. The challenges can be created by the community. It's our way of
saying "hey, if you love CouchDB and you want to help us out, these are
some of the things you could do."
The current state of things is that nothing very much happens. There is
practically no marketing activity, and no co-ordinated attempts to promote
CouchDB. So any sort of improvement or organisation here would be a good
thing.
> P.S. I feel that I had read post as "Do X for reward, not because you
> likes/uses/develops/____ (fill the other) CouchDB". Am I wrong?
>
This isn't about bribing people to do things. If you're not interested in
CouchDB, don't take part.
Influtive is a way for people who are already very passionate about CouchDB
to co-ordinate with each other and work towards goals that provide a
meaningful benefit to the project.
The rewards system is our way of thanking them for helping out. And as I
mention, can be as simple as them earning points in Influtive, and us
giving them the occasional shout-out.
--
Noah Slater
https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Alexander Shorin <kx...@gmail.com>.
Hi Noah,
May I ask one stupid question?
How does it works on practice (yes, I had watch the videos) and how it
will change/improve current state of things?
P.S. I feel that I had read post as "Do X for reward, not because you
likes/uses/develops/____ (fill the other) CouchDB". Am I wrong?
--
,,,^..^,,,
On Sat, Oct 5, 2013 at 9:04 PM, Noah Slater <ns...@apache.org> wrote:
> Hi devs,
>
> I would like to propose that we use Influitive to help us improve our
> marketing efforts.
>
> I fully intend to execute this proposal myself. If you want to volunteer,
> that is great. But if you are not interested in this, that is fine also.
> Nobody has to participate if they do not want to. I am quite happy to run
> it as an experiment myself. If it works we can continue, and if it doesn't,
> we can stop.
>
> Unless anybody objects, I will assume lazy consensus after three days, and
> let Influitive that we have the green light to move forward.
>
> = Introduction =
>
> Influitive AdvocateHub is an advocacy marketing platform.
>
> Think of it like Kickstarter, for marketing. You post a description of what
> you want to accomplish, and then your community members pitch in and help
> to make it happen.
>
> As an open source project, we struggle to market ourselves because we have
> no budget. Where a typical company might take out ads, or pay people to
> write technical content, we rely on volunteer time and word of mouth. But
> this is typically disorganised.
>
> AdvocateHub is a tool that that will allow us to coordinate that volunteer
> time and word of mouth. We can create a steady stream of challenges or
> requests for help and people who are committed to the project can organise
> around these, and help us spread the word of CouchDB.
>
> In return for doing these things, we reward them with prestige and swag.
> And maybe a few other exclusive items, like conference tickets, or a round
> of drinks on me.
>
> You should watch these two intro videos:
>
> http://influitive.com/introduction-to-advocate-marketing/
>
> http://influitive.com/learn-more-about-the-advocatehub/
>
> = Donation =
>
> AdvocateHub is usually premium service. However, Influitive has very
> generously offered to donate an account to the project. This is the first
> open source project that Influitive has supported like this, so I am very
> grateful for the opportunity!
>
> AdvocateHub is designed for commercial companies, but I think we can make
> it work for an open source project. Influitive will be monitoring our
> progress, and if things are not working out, we’ll end the experiment. As
> part of this agreement, I will be the account owner and will be responsible
> for its operation. But if you are a committer and you want to help out, I
> can add you as an admin. This is similar to how we run our social media
> accounts.
>
> In return for the support, I am proposing to:
>
> * Promote the use of our AdvocateHub within our community
> * Thank them from our website, wiki, and social media accounts
> * Document our progress with the occasional blog or tweet
>
> Promoting the use of our AdvocateHub will probably take the form of
> mentioning new challenges on the mailing list, blog, Twitter, Google+, etc.
> Obviously, we will want to encourage as many people as possible to get
> involved in the AdvocateHub as possible.
>
> As for documenting our progress, I am thinking that the occasional post
> covering how we’re using the tool, and what sorts of results we’re seeing
> would be appropriate.
>
> I have spoken with the ASF fundraising team already, and there are no
> concerns with these plans at the foundation level.
>
> = Challenges =
>
> AdvocateHub is built around the concept of a challenge, or request for
> help. We can design these however we want, and I will be looking for input
> from the community.
>
> Ideas for easy challenges:
>
> * Retweet an official @CouchDB tweet
> * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> * Publicly mention CouchDB on Twitter, Google+, LinkedIn, your blog, etc
> * Share an official project blog post somewhere
>
> Ideas for medium challenges:
>
> * Watch a featured video
> * Read a featured blog post, or section of the docs
> * Help someone out on the mailing list
> * Answer a CouchDB question on Stack Overflow, Server Fault, etc
> * Talk about CouchDB in response to a Quora question
> * Talk about CouchDB in response to a submission on Hacker News,
> Reddit, etc
> * Comment on an official blog post, or a blog post about CouchDB
> * Post a review on alternativeTo, or other review sites, blog posts, etc
> * Provide an official endorsement or quote from your company about
> CouchDB
> * Complete a survey (I plan to actually make some surveys)
>
> Ideas for hard challenges:
>
> * Create a CouchDB client, library, or tool
> * Produce early/mid/late stage technical content
> * Produce a CouchDB white paper
> * Give a talk or screencast about CouchDB
> * Share a CouchDB success story, testimonial, or case-study
> * Organise a CouchDB meet-up
> * Organise a CouchDB conference
>
> And then, challenges for actually contributing back to CouchDB itself:
>
> * Triage X many JIRA tickets
> * Fix up outstanding issues on a CouchDB pull request
> * Contribute a fix for a JIRA ticket
>
> (This might be a little outside of the scope of AdvocateHub, as this would
> request contribution back to the project itself. Still, it would be
> interesting to see if this would work. As a volunteer organisation,
> volunteer time and attracting contributions is our top priority.)
>
> = Rewards =
>
> Completing challenges gives you points, levels, and badges. I know that
> many people love this kind of system, and are happy to compete with each
> other for points alone. However, we also have the option of allowing
> advocates to exchange points for prizes.
>
> AdvocateHub has an integration with a swag drop-ship merchant. Hopefully, I
> can attract a third-party to help with the bill for this. It would mean
> that by completing challenges, we can reward advocates with t-shirts,
> hoodies, mugs, pins, stickers, and so on!
>
> In addition to swag, we could also offer:
>
> * Individual promotion for you
> * Priority or free tickets to the regular CouchDB Confs
> * Email support or advice from the committers (depends on who
> volunteers time)
> * Private call with one the committers (depends on who volunteers time)
> * Drinks on Noah (though, you’ll have to come find me!)
>
> Promotion could be quite a draw. Imagine a weekly Tweet along the lines of
> “Thanks to @ARandomPerson for supporting CouchDB this week. You should
> follow her on Twitter!” We could also include a mention in our weekly
> CouchDB news. (A blog idea that I have not executed on yet.) As far as I
> can tell, we’d only be able to promote individual accounts, not businesses.
> The ASF has very strict vendor neutrality rules that we must adhere to.
>
> Some other ideas of how we could provide return promotion:
>
> * Mention on our homepage that week
> * Get on our weekly @CouchDB #FollowFriday
> * Entered into a “hall of fame”
> * Get mentioned in our Git commits, issues, or pull requests
>
> The @CouchDB account has close to 10k followers. And our homepage receives
> around 8,500 page views per month at the moment. Those numbers are not to
> be sniffed at!
>
> (This is heavily inspired by Hoodie, who allow people to sponsor the
> project in return for promotion via different channels. I think we can
> borrow some of this.)
>
> The specifics of the reward programme is unimportant at this stage. Like
> the details of the challenges themselves, we can figure this out as we move
> forward.
>
> Thanks,
>
> --
> Noah Slater
> https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Garren Smith <ga...@apache.org>.
Hi Noah,
I am +1 its always worth trying new tools to see if they can help us. I will definitely be interested to see how well this works.
Cheers
Garren
On 05 Oct 2013, at 7:04 PM, Noah Slater <ns...@apache.org> wrote:
> Hi devs,
>
> I would like to propose that we use Influitive to help us improve our
> marketing efforts.
>
> I fully intend to execute this proposal myself. If you want to volunteer,
> that is great. But if you are not interested in this, that is fine also.
> Nobody has to participate if they do not want to. I am quite happy to run
> it as an experiment myself. If it works we can continue, and if it doesn't,
> we can stop.
>
> Unless anybody objects, I will assume lazy consensus after three days, and
> let Influitive that we have the green light to move forward.
>
> = Introduction =
>
> Influitive AdvocateHub is an advocacy marketing platform.
>
> Think of it like Kickstarter, for marketing. You post a description of what
> you want to accomplish, and then your community members pitch in and help
> to make it happen.
>
> As an open source project, we struggle to market ourselves because we have
> no budget. Where a typical company might take out ads, or pay people to
> write technical content, we rely on volunteer time and word of mouth. But
> this is typically disorganised.
>
> AdvocateHub is a tool that that will allow us to coordinate that volunteer
> time and word of mouth. We can create a steady stream of challenges or
> requests for help and people who are committed to the project can organise
> around these, and help us spread the word of CouchDB.
>
> In return for doing these things, we reward them with prestige and swag.
> And maybe a few other exclusive items, like conference tickets, or a round
> of drinks on me.
>
> You should watch these two intro videos:
>
> http://influitive.com/introduction-to-advocate-marketing/
>
> http://influitive.com/learn-more-about-the-advocatehub/
>
> = Donation =
>
> AdvocateHub is usually premium service. However, Influitive has very
> generously offered to donate an account to the project. This is the first
> open source project that Influitive has supported like this, so I am very
> grateful for the opportunity!
>
> AdvocateHub is designed for commercial companies, but I think we can make
> it work for an open source project. Influitive will be monitoring our
> progress, and if things are not working out, we’ll end the experiment. As
> part of this agreement, I will be the account owner and will be responsible
> for its operation. But if you are a committer and you want to help out, I
> can add you as an admin. This is similar to how we run our social media
> accounts.
>
> In return for the support, I am proposing to:
>
> * Promote the use of our AdvocateHub within our community
> * Thank them from our website, wiki, and social media accounts
> * Document our progress with the occasional blog or tweet
>
> Promoting the use of our AdvocateHub will probably take the form of
> mentioning new challenges on the mailing list, blog, Twitter, Google+, etc.
> Obviously, we will want to encourage as many people as possible to get
> involved in the AdvocateHub as possible.
>
> As for documenting our progress, I am thinking that the occasional post
> covering how we’re using the tool, and what sorts of results we’re seeing
> would be appropriate.
>
> I have spoken with the ASF fundraising team already, and there are no
> concerns with these plans at the foundation level.
>
> = Challenges =
>
> AdvocateHub is built around the concept of a challenge, or request for
> help. We can design these however we want, and I will be looking for input
> from the community.
>
> Ideas for easy challenges:
>
> * Retweet an official @CouchDB tweet
> * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> * Publicly mention CouchDB on Twitter, Google+, LinkedIn, your blog, etc
> * Share an official project blog post somewhere
>
> Ideas for medium challenges:
>
> * Watch a featured video
> * Read a featured blog post, or section of the docs
> * Help someone out on the mailing list
> * Answer a CouchDB question on Stack Overflow, Server Fault, etc
> * Talk about CouchDB in response to a Quora question
> * Talk about CouchDB in response to a submission on Hacker News,
> Reddit, etc
> * Comment on an official blog post, or a blog post about CouchDB
> * Post a review on alternativeTo, or other review sites, blog posts, etc
> * Provide an official endorsement or quote from your company about
> CouchDB
> * Complete a survey (I plan to actually make some surveys)
>
> Ideas for hard challenges:
>
> * Create a CouchDB client, library, or tool
> * Produce early/mid/late stage technical content
> * Produce a CouchDB white paper
> * Give a talk or screencast about CouchDB
> * Share a CouchDB success story, testimonial, or case-study
> * Organise a CouchDB meet-up
> * Organise a CouchDB conference
>
> And then, challenges for actually contributing back to CouchDB itself:
>
> * Triage X many JIRA tickets
> * Fix up outstanding issues on a CouchDB pull request
> * Contribute a fix for a JIRA ticket
>
> (This might be a little outside of the scope of AdvocateHub, as this would
> request contribution back to the project itself. Still, it would be
> interesting to see if this would work. As a volunteer organisation,
> volunteer time and attracting contributions is our top priority.)
>
> = Rewards =
>
> Completing challenges gives you points, levels, and badges. I know that
> many people love this kind of system, and are happy to compete with each
> other for points alone. However, we also have the option of allowing
> advocates to exchange points for prizes.
>
> AdvocateHub has an integration with a swag drop-ship merchant. Hopefully, I
> can attract a third-party to help with the bill for this. It would mean
> that by completing challenges, we can reward advocates with t-shirts,
> hoodies, mugs, pins, stickers, and so on!
>
> In addition to swag, we could also offer:
>
> * Individual promotion for you
> * Priority or free tickets to the regular CouchDB Confs
> * Email support or advice from the committers (depends on who
> volunteers time)
> * Private call with one the committers (depends on who volunteers time)
> * Drinks on Noah (though, you’ll have to come find me!)
>
> Promotion could be quite a draw. Imagine a weekly Tweet along the lines of
> “Thanks to @ARandomPerson for supporting CouchDB this week. You should
> follow her on Twitter!” We could also include a mention in our weekly
> CouchDB news. (A blog idea that I have not executed on yet.) As far as I
> can tell, we’d only be able to promote individual accounts, not businesses.
> The ASF has very strict vendor neutrality rules that we must adhere to.
>
> Some other ideas of how we could provide return promotion:
>
> * Mention on our homepage that week
> * Get on our weekly @CouchDB #FollowFriday
> * Entered into a “hall of fame”
> * Get mentioned in our Git commits, issues, or pull requests
>
> The @CouchDB account has close to 10k followers. And our homepage receives
> around 8,500 page views per month at the moment. Those numbers are not to
> be sniffed at!
>
> (This is heavily inspired by Hoodie, who allow people to sponsor the
> project in return for promotion via different channels. I think we can
> borrow some of this.)
>
> The specifics of the reward programme is unimportant at this stage. Like
> the details of the challenges themselves, we can figure this out as we move
> forward.
>
> Thanks,
>
> --
> Noah Slater
> https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Noah Slater <ns...@apache.org>.
Great! Thanks!
On 6 October 2013 15:15, Lena Reinhard <le...@thehoodiefirm.com> wrote:
> +1
> like the idea, would love to try this + help out with it
>
> On 05.10.2013, at 19:04, Noah Slater wrote:
>
> > Hi devs,
> >
> > I would like to propose that we use Influitive to help us improve our
> > marketing efforts.
> >
> > I fully intend to execute this proposal myself. If you want to volunteer,
> > that is great. But if you are not interested in this, that is fine also.
> > Nobody has to participate if they do not want to. I am quite happy to run
> > it as an experiment myself. If it works we can continue, and if it
> doesn't,
> > we can stop.
> >
> > Unless anybody objects, I will assume lazy consensus after three days,
> and
> > let Influitive that we have the green light to move forward.
> >
> > = Introduction =
> >
> > Influitive AdvocateHub is an advocacy marketing platform.
> >
> > Think of it like Kickstarter, for marketing. You post a description of
> what
> > you want to accomplish, and then your community members pitch in and help
> > to make it happen.
> >
> > As an open source project, we struggle to market ourselves because we
> have
> > no budget. Where a typical company might take out ads, or pay people to
> > write technical content, we rely on volunteer time and word of mouth. But
> > this is typically disorganised.
> >
> > AdvocateHub is a tool that that will allow us to coordinate that
> volunteer
> > time and word of mouth. We can create a steady stream of challenges or
> > requests for help and people who are committed to the project can
> organise
> > around these, and help us spread the word of CouchDB.
> >
> > In return for doing these things, we reward them with prestige and swag.
> > And maybe a few other exclusive items, like conference tickets, or a
> round
> > of drinks on me.
> >
> > You should watch these two intro videos:
> >
> > http://influitive.com/introduction-to-advocate-marketing/
> >
> > http://influitive.com/learn-more-about-the-advocatehub/
> >
> > = Donation =
> >
> > AdvocateHub is usually premium service. However, Influitive has very
> > generously offered to donate an account to the project. This is the first
> > open source project that Influitive has supported like this, so I am very
> > grateful for the opportunity!
> >
> > AdvocateHub is designed for commercial companies, but I think we can make
> > it work for an open source project. Influitive will be monitoring our
> > progress, and if things are not working out, we’ll end the experiment. As
> > part of this agreement, I will be the account owner and will be
> responsible
> > for its operation. But if you are a committer and you want to help out, I
> > can add you as an admin. This is similar to how we run our social media
> > accounts.
> >
> > In return for the support, I am proposing to:
> >
> > * Promote the use of our AdvocateHub within our community
> > * Thank them from our website, wiki, and social media accounts
> > * Document our progress with the occasional blog or tweet
> >
> > Promoting the use of our AdvocateHub will probably take the form of
> > mentioning new challenges on the mailing list, blog, Twitter, Google+,
> etc.
> > Obviously, we will want to encourage as many people as possible to get
> > involved in the AdvocateHub as possible.
> >
> > As for documenting our progress, I am thinking that the occasional post
> > covering how we’re using the tool, and what sorts of results we’re seeing
> > would be appropriate.
> >
> > I have spoken with the ASF fundraising team already, and there are no
> > concerns with these plans at the foundation level.
> >
> > = Challenges =
> >
> > AdvocateHub is built around the concept of a challenge, or request for
> > help. We can design these however we want, and I will be looking for
> input
> > from the community.
> >
> > Ideas for easy challenges:
> >
> > * Retweet an official @CouchDB tweet
> > * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> > * Publicly mention CouchDB on Twitter, Google+, LinkedIn, your blog,
> etc
> > * Share an official project blog post somewhere
> >
> > Ideas for medium challenges:
> >
> > * Watch a featured video
> > * Read a featured blog post, or section of the docs
> > * Help someone out on the mailing list
> > * Answer a CouchDB question on Stack Overflow, Server Fault, etc
> > * Talk about CouchDB in response to a Quora question
> > * Talk about CouchDB in response to a submission on Hacker News,
> > Reddit, etc
> > * Comment on an official blog post, or a blog post about CouchDB
> > * Post a review on alternativeTo, or other review sites, blog posts,
> etc
> > * Provide an official endorsement or quote from your company about
> > CouchDB
> > * Complete a survey (I plan to actually make some surveys)
> >
> > Ideas for hard challenges:
> >
> > * Create a CouchDB client, library, or tool
> > * Produce early/mid/late stage technical content
> > * Produce a CouchDB white paper
> > * Give a talk or screencast about CouchDB
> > * Share a CouchDB success story, testimonial, or case-study
> > * Organise a CouchDB meet-up
> > * Organise a CouchDB conference
> >
> > And then, challenges for actually contributing back to CouchDB itself:
> >
> > * Triage X many JIRA tickets
> > * Fix up outstanding issues on a CouchDB pull request
> > * Contribute a fix for a JIRA ticket
> >
> > (This might be a little outside of the scope of AdvocateHub, as this
> would
> > request contribution back to the project itself. Still, it would be
> > interesting to see if this would work. As a volunteer organisation,
> > volunteer time and attracting contributions is our top priority.)
> >
> > = Rewards =
> >
> > Completing challenges gives you points, levels, and badges. I know that
> > many people love this kind of system, and are happy to compete with each
> > other for points alone. However, we also have the option of allowing
> > advocates to exchange points for prizes.
> >
> > AdvocateHub has an integration with a swag drop-ship merchant.
> Hopefully, I
> > can attract a third-party to help with the bill for this. It would mean
> > that by completing challenges, we can reward advocates with t-shirts,
> > hoodies, mugs, pins, stickers, and so on!
> >
> > In addition to swag, we could also offer:
> >
> > * Individual promotion for you
> > * Priority or free tickets to the regular CouchDB Confs
> > * Email support or advice from the committers (depends on who
> > volunteers time)
> > * Private call with one the committers (depends on who volunteers
> time)
> > * Drinks on Noah (though, you’ll have to come find me!)
> >
> > Promotion could be quite a draw. Imagine a weekly Tweet along the lines
> of
> > “Thanks to @ARandomPerson for supporting CouchDB this week. You should
> > follow her on Twitter!” We could also include a mention in our weekly
> > CouchDB news. (A blog idea that I have not executed on yet.) As far as I
> > can tell, we’d only be able to promote individual accounts, not
> businesses.
> > The ASF has very strict vendor neutrality rules that we must adhere to.
> >
> > Some other ideas of how we could provide return promotion:
> >
> > * Mention on our homepage that week
> > * Get on our weekly @CouchDB #FollowFriday
> > * Entered into a “hall of fame”
> > * Get mentioned in our Git commits, issues, or pull requests
> >
> > The @CouchDB account has close to 10k followers. And our homepage
> receives
> > around 8,500 page views per month at the moment. Those numbers are not to
> > be sniffed at!
> >
> > (This is heavily inspired by Hoodie, who allow people to sponsor the
> > project in return for promotion via different channels. I think we can
> > borrow some of this.)
> >
> > The specifics of the reward programme is unimportant at this stage. Like
> > the details of the challenges themselves, we can figure this out as we
> move
> > forward.
> >
> > Thanks,
> >
> > --
> > Noah Slater
> > https://twitter.com/nslater
>
>
--
Noah Slater
https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Lena Reinhard <le...@thehoodiefirm.com>.
+1
like the idea, would love to try this + help out with it
On 05.10.2013, at 19:04, Noah Slater wrote:
> Hi devs,
>
> I would like to propose that we use Influitive to help us improve our
> marketing efforts.
>
> I fully intend to execute this proposal myself. If you want to volunteer,
> that is great. But if you are not interested in this, that is fine also.
> Nobody has to participate if they do not want to. I am quite happy to run
> it as an experiment myself. If it works we can continue, and if it doesn't,
> we can stop.
>
> Unless anybody objects, I will assume lazy consensus after three days, and
> let Influitive that we have the green light to move forward.
>
> = Introduction =
>
> Influitive AdvocateHub is an advocacy marketing platform.
>
> Think of it like Kickstarter, for marketing. You post a description of what
> you want to accomplish, and then your community members pitch in and help
> to make it happen.
>
> As an open source project, we struggle to market ourselves because we have
> no budget. Where a typical company might take out ads, or pay people to
> write technical content, we rely on volunteer time and word of mouth. But
> this is typically disorganised.
>
> AdvocateHub is a tool that that will allow us to coordinate that volunteer
> time and word of mouth. We can create a steady stream of challenges or
> requests for help and people who are committed to the project can organise
> around these, and help us spread the word of CouchDB.
>
> In return for doing these things, we reward them with prestige and swag.
> And maybe a few other exclusive items, like conference tickets, or a round
> of drinks on me.
>
> You should watch these two intro videos:
>
> http://influitive.com/introduction-to-advocate-marketing/
>
> http://influitive.com/learn-more-about-the-advocatehub/
>
> = Donation =
>
> AdvocateHub is usually premium service. However, Influitive has very
> generously offered to donate an account to the project. This is the first
> open source project that Influitive has supported like this, so I am very
> grateful for the opportunity!
>
> AdvocateHub is designed for commercial companies, but I think we can make
> it work for an open source project. Influitive will be monitoring our
> progress, and if things are not working out, we’ll end the experiment. As
> part of this agreement, I will be the account owner and will be responsible
> for its operation. But if you are a committer and you want to help out, I
> can add you as an admin. This is similar to how we run our social media
> accounts.
>
> In return for the support, I am proposing to:
>
> * Promote the use of our AdvocateHub within our community
> * Thank them from our website, wiki, and social media accounts
> * Document our progress with the occasional blog or tweet
>
> Promoting the use of our AdvocateHub will probably take the form of
> mentioning new challenges on the mailing list, blog, Twitter, Google+, etc.
> Obviously, we will want to encourage as many people as possible to get
> involved in the AdvocateHub as possible.
>
> As for documenting our progress, I am thinking that the occasional post
> covering how we’re using the tool, and what sorts of results we’re seeing
> would be appropriate.
>
> I have spoken with the ASF fundraising team already, and there are no
> concerns with these plans at the foundation level.
>
> = Challenges =
>
> AdvocateHub is built around the concept of a challenge, or request for
> help. We can design these however we want, and I will be looking for input
> from the community.
>
> Ideas for easy challenges:
>
> * Retweet an official @CouchDB tweet
> * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> * Publicly mention CouchDB on Twitter, Google+, LinkedIn, your blog, etc
> * Share an official project blog post somewhere
>
> Ideas for medium challenges:
>
> * Watch a featured video
> * Read a featured blog post, or section of the docs
> * Help someone out on the mailing list
> * Answer a CouchDB question on Stack Overflow, Server Fault, etc
> * Talk about CouchDB in response to a Quora question
> * Talk about CouchDB in response to a submission on Hacker News,
> Reddit, etc
> * Comment on an official blog post, or a blog post about CouchDB
> * Post a review on alternativeTo, or other review sites, blog posts, etc
> * Provide an official endorsement or quote from your company about
> CouchDB
> * Complete a survey (I plan to actually make some surveys)
>
> Ideas for hard challenges:
>
> * Create a CouchDB client, library, or tool
> * Produce early/mid/late stage technical content
> * Produce a CouchDB white paper
> * Give a talk or screencast about CouchDB
> * Share a CouchDB success story, testimonial, or case-study
> * Organise a CouchDB meet-up
> * Organise a CouchDB conference
>
> And then, challenges for actually contributing back to CouchDB itself:
>
> * Triage X many JIRA tickets
> * Fix up outstanding issues on a CouchDB pull request
> * Contribute a fix for a JIRA ticket
>
> (This might be a little outside of the scope of AdvocateHub, as this would
> request contribution back to the project itself. Still, it would be
> interesting to see if this would work. As a volunteer organisation,
> volunteer time and attracting contributions is our top priority.)
>
> = Rewards =
>
> Completing challenges gives you points, levels, and badges. I know that
> many people love this kind of system, and are happy to compete with each
> other for points alone. However, we also have the option of allowing
> advocates to exchange points for prizes.
>
> AdvocateHub has an integration with a swag drop-ship merchant. Hopefully, I
> can attract a third-party to help with the bill for this. It would mean
> that by completing challenges, we can reward advocates with t-shirts,
> hoodies, mugs, pins, stickers, and so on!
>
> In addition to swag, we could also offer:
>
> * Individual promotion for you
> * Priority or free tickets to the regular CouchDB Confs
> * Email support or advice from the committers (depends on who
> volunteers time)
> * Private call with one the committers (depends on who volunteers time)
> * Drinks on Noah (though, you’ll have to come find me!)
>
> Promotion could be quite a draw. Imagine a weekly Tweet along the lines of
> “Thanks to @ARandomPerson for supporting CouchDB this week. You should
> follow her on Twitter!” We could also include a mention in our weekly
> CouchDB news. (A blog idea that I have not executed on yet.) As far as I
> can tell, we’d only be able to promote individual accounts, not businesses.
> The ASF has very strict vendor neutrality rules that we must adhere to.
>
> Some other ideas of how we could provide return promotion:
>
> * Mention on our homepage that week
> * Get on our weekly @CouchDB #FollowFriday
> * Entered into a “hall of fame”
> * Get mentioned in our Git commits, issues, or pull requests
>
> The @CouchDB account has close to 10k followers. And our homepage receives
> around 8,500 page views per month at the moment. Those numbers are not to
> be sniffed at!
>
> (This is heavily inspired by Hoodie, who allow people to sponsor the
> project in return for promotion via different channels. I think we can
> borrow some of this.)
>
> The specifics of the reward programme is unimportant at this stage. Like
> the details of the challenges themselves, we can figure this out as we move
> forward.
>
> Thanks,
>
> --
> Noah Slater
> https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Noah Slater <ns...@apache.org>.
Okay, thanks for the feedback, and offers of help, everyone. I am going to
let Influitive know we're moving forward with this.
On 10 October 2013 13:55, Florian Westreicher Bakk.techn. <
stuff@meredrica.org> wrote:
> I'm interested, followed the thread but never posted. :-)
>
> Noah Slater <ns...@apache.org> wrote:
> >Okay, thanks Benoit!
> >
> >I agree that such things should be optional, and that if they work, we
> >should look at ways of replicating their success in other areas of the
> >project.
> >
> >The Influitive privacy policy is here: http://influitive.com/privacy/
> >
> >"You may withdraw your permission for us to collect, use and disclose
> >your
> >personal data at any time, subject to legal and contractual
> >restrictions
> >and reasonable notice."
> >
> >"You have the right to ask whether we hold any personal information
> >about
> >you, to see that information, and to ask us to correct or update your
> >information."
> >
> >I hope this answers your question.
> >
> >Unless there's no further objection, I will let Influitive know we have
> >the
> >green light to move forward.
> >
> >Once I've done that, they'll set us up with a hub, and I will invite
> >people
> >to be admins. Anyone is welcome. If you're already expressed an
> >interest in
> >this thread, I will reach out to you. If you haven't, let me know at
> >any
> >time.
> >
> >
> >On 8 October 2013 18:55, Benoit Chesneau <bc...@gmail.com> wrote:
> >
> >> On Mon, Oct 7, 2013 at 5:20 PM, Noah Slater <ns...@apache.org>
> >wrote:
> >>
> >> > Okay, some answers:
> >> >
> >> > - How to ensure this reward system is optional?
> >> >
> >> > I think we can experiment with the reward system. The default is
> >just to
> >> > award points for completing tasks. So you can have leader-boards
> >within
> >> > Influitive, and you can see who has the most points, etc.
> >> >
> >> > What we do with those points is how we experiment. I think the
> >first step
> >> > should be to offer some sort of public thanks, as I outline in my
> >> proposal.
> >> > Even a Twitter #FF would go a long way, I think.
> >> >
> >> > Secondly, I think we should experiment with allow people to
> >exchange
> >> points
> >> > for swag. Perhaps this will be received positively, perhaps some
> >people
> >> > will complain. If it causes a problem, we remove it.
> >> >
> >> >
> >> I think we should just make sure to propose the system as an option.
> >> Otherwise such things looks OK for me Sort of achievements like in
> >games in
> >> fact.
> >>
> >>
> >> > - How to ensure that people that not participate do not feel
> >unconsidered
> >> > by other members of the community because not rewarded by the
> >Influtive
> >> > system?
> >> >
> >> > I think you're right: we should recognise people who help out on
> >JIRA,
> >> and
> >> > on the mailing lists, and so on. I think that's a worthwhile
> >discussion
> >> to
> >> > have, but I don't think it blocks this work. In fact, perhaps we
> >can look
> >> > at what works for Influitive, and then try to replicate that in
> >other
> >> parts
> >> > of the project.
> >> >
> >> > So, for example, if the Twitter promotion, or blog mentions, really
> >work,
> >> > and people like them, then perhaps in a few months, we have a
> >> conversation
> >> > about how to do the same sort of thing for people who contribute in
> >other
> >> > ways.
> >> >
> >> > The same can be said for swag too. Assuming I even find a budget
> >for this
> >> > (which I may not be able to do) then presumably we can extend that
> >and
> >> say
> >> > thank you to other people with a t-shirt too. (Actually, recently,
> >> Cloudant
> >> > very kindly sent a t-shirt to committers at my suggestion. So that
> >is one
> >> > example of this. I assume you got yours, Benoit? I've been wearing
> >mine!)
> >> >
> >> > I think it's important to consider the different types of people
> >we're
> >> > talking about here. As a core contributor, I really don't feel like
> >I
> >> need
> >> > to be rewarded for my contributions. The community is enough of a
> >reward
> >> > for me.
> >> >
> >> > But Influtive is targeting people who may only be on the
> >peripheries.
> >> > People who have used CouchDB, love it, and will jump at the
> >opportunity
> >> to
> >> > help out by telling their network about their experiences. And for
> >that,
> >> > sending them a pack of CouchDB stickers, or whatever, makes obvious
> >> sense.
> >> > We're trying to mobilise a volunteer workforce of people who will
> >promote
> >> > us! So let's give them the swag to do that!
> >> >
> >> > In fact, we might want to use that as a metric for what we give
> >out. We
> >> > could say, okay, we're only gonna give out swag that has some
> >promotional
> >> > value to the project. So in a way, it an extension of the
> >initiative
> >> > itself. People who are interested in marketing and promoting
> >CouchDB will
> >> > be rewarded with shipments of stickers, keyrings, etc, to help them
> >with
> >> > that. Perfect!
> >> >
> >>
> >>
> >> The thing is that some people that already help the project without
> >extra
> >> rewards and for any reason (cultural, philosophy, ....) may not want
> >to be
> >> part of a reward system. Witch is their choice but I just want to
> >make sure
> >> they won't be forgotten. Or more exactly that we don't forget to
> >thanks
> >> them. Just because they are outside the metrics. We can continue the
> >> discussion in a separate thread, but that is important for me. Imo
> >just
> >> because some people like achievements and be shown with a badge
> >doesn't
> >> mean we should encourage such system (I certainly not) or rather that
> >it
> >> should be the only system. If we can have let choice then I am fine.
> >>
> >> (Also yes got my shirt, and I thanks them again :)
> >>
> >>
> >>
> >>
> >> > - What will define the success or failure of the experimentation?
> >What
> >> is
> >> > the deadline of the experimentation?
> >> >
> >> > With something like this, I think the success of failure has to be
> >> measured
> >> > qualitatively.
> >> >
> >> > So we could look at a number of things:
> >> >
> >> > * What has the take-up been like? Are many people using it?
> >> > * What has been the reaction to the programme within the community?
> >Do
> >> > people feel positively about it?
> >> > * What has been the reaction to the programme outside of our
> >community?
> >> Has
> >> > it engaged people or attracted new users? Is it seen favourably by
> >other
> >> > people?
> >> >
> >> > Note also that Influtive themselves will be keeping a very close
> >eye on
> >> the
> >> > experiment, because obviously, it is important to them that the
> >> experiment
> >> > is a success. So if it's not working out, we may not have a choice
> >in the
> >> > matter.
> >> >
> >> > I'd say, let's run the experiment for three months, and then
> >review. Then
> >> > again in another three months.
> >>
> >>
> >> > Are you happy with that?
> >> >
> >> >
> >> >
> >> Modulo what I am said, yes. One last thing, what is the privacy
> >policy of
> >> such system? Can people easily remove them from it? (to be complete)
> >>
> >> - benoit
> >>
> >>
> >> >
> >> > On 7 October 2013 09:47, Jan Lehnardt <ja...@apache.org> wrote:
> >> >
> >> > > +1, love this initiative Noah! I am really curious about what
> >comes
> >> > > out of this.
> >> > >
> >> > > Thanks for the lively discussion around this, everyone. I’m
> >seeing
> >> > > all my concerns addressed, so I can just thumb up :D
> >> > >
> >> > > Best
> >> > > Jan
> >> > > --
> >> > >
> >> > > On Oct 5, 2013, at 19:04 , Noah Slater <ns...@apache.org>
> >wrote:
> >> > >
> >> > > > Hi devs,
> >> > > >
> >> > > > I would like to propose that we use Influitive to help us
> >improve our
> >> > > > marketing efforts.
> >> > > >
> >> > > > I fully intend to execute this proposal myself. If you want to
> >> > volunteer,
> >> > > > that is great. But if you are not interested in this, that is
> >fine
> >> > also.
> >> > > > Nobody has to participate if they do not want to. I am quite
> >happy to
> >> > run
> >> > > > it as an experiment myself. If it works we can continue, and if
> >it
> >> > > doesn't,
> >> > > > we can stop.
> >> > > >
> >> > > > Unless anybody objects, I will assume lazy consensus after
> >three
> >> days,
> >> > > and
> >> > > > let Influitive that we have the green light to move forward.
> >> > > >
> >> > > > = Introduction =
> >> > > >
> >> > > > Influitive AdvocateHub is an advocacy marketing platform.
> >> > > >
> >> > > > Think of it like Kickstarter, for marketing. You post a
> >description
> >> of
> >> > > what
> >> > > > you want to accomplish, and then your community members pitch
> >in and
> >> > help
> >> > > > to make it happen.
> >> > > >
> >> > > > As an open source project, we struggle to market ourselves
> >because we
> >> > > have
> >> > > > no budget. Where a typical company might take out ads, or pay
> >people
> >> to
> >> > > > write technical content, we rely on volunteer time and word of
> >mouth.
> >> > But
> >> > > > this is typically disorganised.
> >> > > >
> >> > > > AdvocateHub is a tool that that will allow us to coordinate
> >that
> >> > > volunteer
> >> > > > time and word of mouth. We can create a steady stream of
> >challenges
> >> or
> >> > > > requests for help and people who are committed to the project
> >can
> >> > > organise
> >> > > > around these, and help us spread the word of CouchDB.
> >> > > >
> >> > > > In return for doing these things, we reward them with prestige
> >and
> >> > swag.
> >> > > > And maybe a few other exclusive items, like conference tickets,
> >or a
> >> > > round
> >> > > > of drinks on me.
> >> > > >
> >> > > > You should watch these two intro videos:
> >> > > >
> >> > > > http://influitive.com/introduction-to-advocate-marketing/
> >> > > >
> >> > > > http://influitive.com/learn-more-about-the-advocatehub/
> >> > > >
> >> > > > = Donation =
> >> > > >
> >> > > > AdvocateHub is usually premium service. However, Influitive has
> >very
> >> > > > generously offered to donate an account to the project. This is
> >the
> >> > first
> >> > > > open source project that Influitive has supported like this, so
> >I am
> >> > very
> >> > > > grateful for the opportunity!
> >> > > >
> >> > > > AdvocateHub is designed for commercial companies, but I think
> >we can
> >> > make
> >> > > > it work for an open source project. Influitive will be
> >monitoring our
> >> > > > progress, and if things are not working out, we’ll end the
> >> experiment.
> >> > As
> >> > > > part of this agreement, I will be the account owner and will be
> >> > > responsible
> >> > > > for its operation. But if you are a committer and you want to
> >help
> >> > out, I
> >> > > > can add you as an admin. This is similar to how we run our
> >social
> >> media
> >> > > > accounts.
> >> > > >
> >> > > > In return for the support, I am proposing to:
> >> > > >
> >> > > > * Promote the use of our AdvocateHub within our community
> >> > > > * Thank them from our website, wiki, and social media
> >accounts
> >> > > > * Document our progress with the occasional blog or tweet
> >> > > >
> >> > > > Promoting the use of our AdvocateHub will probably take the
> >form of
> >> > > > mentioning new challenges on the mailing list, blog, Twitter,
> >> Google+,
> >> > > etc.
> >> > > > Obviously, we will want to encourage as many people as possible
> >to
> >> get
> >> > > > involved in the AdvocateHub as possible.
> >> > > >
> >> > > > As for documenting our progress, I am thinking that the
> >occasional
> >> post
> >> > > > covering how we’re using the tool, and what sorts of results
> >we’re
> >> > seeing
> >> > > > would be appropriate.
> >> > > >
> >> > > > I have spoken with the ASF fundraising team already, and there
> >are no
> >> > > > concerns with these plans at the foundation level.
> >> > > >
> >> > > > = Challenges =
> >> > > >
> >> > > > AdvocateHub is built around the concept of a challenge, or
> >request
> >> for
> >> > > > help. We can design these however we want, and I will be
> >looking for
> >> > > input
> >> > > > from the community.
> >> > > >
> >> > > > Ideas for easy challenges:
> >> > > >
> >> > > > * Retweet an official @CouchDB tweet
> >> > > > * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> >> > > > * Publicly mention CouchDB on Twitter, Google+, LinkedIn,
> >your
> >> blog,
> >> > > etc
> >> > > > * Share an official project blog post somewhere
> >> > > >
> >> > > > Ideas for medium challenges:
> >> > > >
> >> > > > * Watch a featured video
> >> > > > * Read a featured blog post, or section of the docs
> >> > > > * Help someone out on the mailing list
> >> > > > * Answer a CouchDB question on Stack Overflow, Server Fault,
> >etc
> >> > > > * Talk about CouchDB in response to a Quora question
> >> > > > * Talk about CouchDB in response to a submission on Hacker
> >News,
> >> > > > Reddit, etc
> >> > > > * Comment on an official blog post, or a blog post about
> >CouchDB
> >> > > > * Post a review on alternativeTo, or other review sites,
> >blog
> >> posts,
> >> > > etc
> >> > > > * Provide an official endorsement or quote from your company
> >about
> >> > > > CouchDB
> >> > > > * Complete a survey (I plan to actually make some surveys)
> >> > > >
> >> > > > Ideas for hard challenges:
> >> > > >
> >> > > > * Create a CouchDB client, library, or tool
> >> > > > * Produce early/mid/late stage technical content
> >> > > > * Produce a CouchDB white paper
> >> > > > * Give a talk or screencast about CouchDB
> >> > > > * Share a CouchDB success story, testimonial, or case-study
> >> > > > * Organise a CouchDB meet-up
> >> > > > * Organise a CouchDB conference
> >> > > >
> >> > > > And then, challenges for actually contributing back to CouchDB
> >> itself:
> >> > > >
> >> > > > * Triage X many JIRA tickets
> >> > > > * Fix up outstanding issues on a CouchDB pull request
> >> > > > * Contribute a fix for a JIRA ticket
> >> > > >
> >> > > > (This might be a little outside of the scope of AdvocateHub, as
> >this
> >> > > would
> >> > > > request contribution back to the project itself. Still, it
> >would be
> >> > > > interesting to see if this would work. As a volunteer
> >organisation,
> >> > > > volunteer time and attracting contributions is our top
> >priority.)
> >> > > >
> >> > > > = Rewards =
> >> > > >
> >> > > > Completing challenges gives you points, levels, and badges. I
> >know
> >> that
> >> > > > many people love this kind of system, and are happy to compete
> >with
> >> > each
> >> > > > other for points alone. However, we also have the option of
> >allowing
> >> > > > advocates to exchange points for prizes.
> >> > > >
> >> > > > AdvocateHub has an integration with a swag drop-ship merchant.
> >> > > Hopefully, I
> >> > > > can attract a third-party to help with the bill for this. It
> >would
> >> mean
> >> > > > that by completing challenges, we can reward advocates with
> >t-shirts,
> >> > > > hoodies, mugs, pins, stickers, and so on!
> >> > > >
> >> > > > In addition to swag, we could also offer:
> >> > > >
> >> > > > * Individual promotion for you
> >> > > > * Priority or free tickets to the regular CouchDB Confs
> >> > > > * Email support or advice from the committers (depends on
> >who
> >> > > > volunteers time)
> >> > > > * Private call with one the committers (depends on who
> >volunteers
> >> > > time)
> >> > > > * Drinks on Noah (though, you’ll have to come find me!)
> >> > > >
> >> > > > Promotion could be quite a draw. Imagine a weekly Tweet along
> >the
> >> lines
> >> > > of
> >> > > > “Thanks to @ARandomPerson for supporting CouchDB this week. You
> >> should
> >> > > > follow her on Twitter!” We could also include a mention in our
> >weekly
> >> > > > CouchDB news. (A blog idea that I have not executed on yet.) As
> >far
> >> as
> >> > I
> >> > > > can tell, we’d only be able to promote individual accounts, not
> >> > > businesses.
> >> > > > The ASF has very strict vendor neutrality rules that we must
> >adhere
> >> to.
> >> > > >
> >> > > > Some other ideas of how we could provide return promotion:
> >> > > >
> >> > > > * Mention on our homepage that week
> >> > > > * Get on our weekly @CouchDB #FollowFriday
> >> > > > * Entered into a “hall of fame”
> >> > > > * Get mentioned in our Git commits, issues, or pull requests
> >> > > >
> >> > > > The @CouchDB account has close to 10k followers. And our
> >homepage
> >> > > receives
> >> > > > around 8,500 page views per month at the moment. Those numbers
> >are
> >> not
> >> > to
> >> > > > be sniffed at!
> >> > > >
> >> > > > (This is heavily inspired by Hoodie, who allow people to
> >sponsor the
> >> > > > project in return for promotion via different channels. I think
> >we
> >> can
> >> > > > borrow some of this.)
> >> > > >
> >> > > > The specifics of the reward programme is unimportant at this
> >stage.
> >> > Like
> >> > > > the details of the challenges themselves, we can figure this
> >out as
> >> we
> >> > > move
> >> > > > forward.
> >> > > >
> >> > > > Thanks,
> >> > > >
> >> > > > --
> >> > > > Noah Slater
> >> > > > https://twitter.com/nslater
> >> > >
> >> > >
> >> >
> >> >
> >> > --
> >> > Noah Slater
> >> > https://twitter.com/nslater
> >> >
> >>
>
> --
> Sent from Kaiten Mail. Please excuse my brevity.
>
--
Noah Slater
https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by "Florian Westreicher Bakk.techn." <st...@meredrica.org>.
I'm interested, followed the thread but never posted. :-)
Noah Slater <ns...@apache.org> wrote:
>Okay, thanks Benoit!
>
>I agree that such things should be optional, and that if they work, we
>should look at ways of replicating their success in other areas of the
>project.
>
>The Influitive privacy policy is here: http://influitive.com/privacy/
>
>"You may withdraw your permission for us to collect, use and disclose
>your
>personal data at any time, subject to legal and contractual
>restrictions
>and reasonable notice."
>
>"You have the right to ask whether we hold any personal information
>about
>you, to see that information, and to ask us to correct or update your
>information."
>
>I hope this answers your question.
>
>Unless there's no further objection, I will let Influitive know we have
>the
>green light to move forward.
>
>Once I've done that, they'll set us up with a hub, and I will invite
>people
>to be admins. Anyone is welcome. If you're already expressed an
>interest in
>this thread, I will reach out to you. If you haven't, let me know at
>any
>time.
>
>
>On 8 October 2013 18:55, Benoit Chesneau <bc...@gmail.com> wrote:
>
>> On Mon, Oct 7, 2013 at 5:20 PM, Noah Slater <ns...@apache.org>
>wrote:
>>
>> > Okay, some answers:
>> >
>> > - How to ensure this reward system is optional?
>> >
>> > I think we can experiment with the reward system. The default is
>just to
>> > award points for completing tasks. So you can have leader-boards
>within
>> > Influitive, and you can see who has the most points, etc.
>> >
>> > What we do with those points is how we experiment. I think the
>first step
>> > should be to offer some sort of public thanks, as I outline in my
>> proposal.
>> > Even a Twitter #FF would go a long way, I think.
>> >
>> > Secondly, I think we should experiment with allow people to
>exchange
>> points
>> > for swag. Perhaps this will be received positively, perhaps some
>people
>> > will complain. If it causes a problem, we remove it.
>> >
>> >
>> I think we should just make sure to propose the system as an option.
>> Otherwise such things looks OK for me Sort of achievements like in
>games in
>> fact.
>>
>>
>> > - How to ensure that people that not participate do not feel
>unconsidered
>> > by other members of the community because not rewarded by the
>Influtive
>> > system?
>> >
>> > I think you're right: we should recognise people who help out on
>JIRA,
>> and
>> > on the mailing lists, and so on. I think that's a worthwhile
>discussion
>> to
>> > have, but I don't think it blocks this work. In fact, perhaps we
>can look
>> > at what works for Influitive, and then try to replicate that in
>other
>> parts
>> > of the project.
>> >
>> > So, for example, if the Twitter promotion, or blog mentions, really
>work,
>> > and people like them, then perhaps in a few months, we have a
>> conversation
>> > about how to do the same sort of thing for people who contribute in
>other
>> > ways.
>> >
>> > The same can be said for swag too. Assuming I even find a budget
>for this
>> > (which I may not be able to do) then presumably we can extend that
>and
>> say
>> > thank you to other people with a t-shirt too. (Actually, recently,
>> Cloudant
>> > very kindly sent a t-shirt to committers at my suggestion. So that
>is one
>> > example of this. I assume you got yours, Benoit? I've been wearing
>mine!)
>> >
>> > I think it's important to consider the different types of people
>we're
>> > talking about here. As a core contributor, I really don't feel like
>I
>> need
>> > to be rewarded for my contributions. The community is enough of a
>reward
>> > for me.
>> >
>> > But Influtive is targeting people who may only be on the
>peripheries.
>> > People who have used CouchDB, love it, and will jump at the
>opportunity
>> to
>> > help out by telling their network about their experiences. And for
>that,
>> > sending them a pack of CouchDB stickers, or whatever, makes obvious
>> sense.
>> > We're trying to mobilise a volunteer workforce of people who will
>promote
>> > us! So let's give them the swag to do that!
>> >
>> > In fact, we might want to use that as a metric for what we give
>out. We
>> > could say, okay, we're only gonna give out swag that has some
>promotional
>> > value to the project. So in a way, it an extension of the
>initiative
>> > itself. People who are interested in marketing and promoting
>CouchDB will
>> > be rewarded with shipments of stickers, keyrings, etc, to help them
>with
>> > that. Perfect!
>> >
>>
>>
>> The thing is that some people that already help the project without
>extra
>> rewards and for any reason (cultural, philosophy, ....) may not want
>to be
>> part of a reward system. Witch is their choice but I just want to
>make sure
>> they won't be forgotten. Or more exactly that we don't forget to
>thanks
>> them. Just because they are outside the metrics. We can continue the
>> discussion in a separate thread, but that is important for me. Imo
>just
>> because some people like achievements and be shown with a badge
>doesn't
>> mean we should encourage such system (I certainly not) or rather that
>it
>> should be the only system. If we can have let choice then I am fine.
>>
>> (Also yes got my shirt, and I thanks them again :)
>>
>>
>>
>>
>> > - What will define the success or failure of the experimentation?
>What
>> is
>> > the deadline of the experimentation?
>> >
>> > With something like this, I think the success of failure has to be
>> measured
>> > qualitatively.
>> >
>> > So we could look at a number of things:
>> >
>> > * What has the take-up been like? Are many people using it?
>> > * What has been the reaction to the programme within the community?
>Do
>> > people feel positively about it?
>> > * What has been the reaction to the programme outside of our
>community?
>> Has
>> > it engaged people or attracted new users? Is it seen favourably by
>other
>> > people?
>> >
>> > Note also that Influtive themselves will be keeping a very close
>eye on
>> the
>> > experiment, because obviously, it is important to them that the
>> experiment
>> > is a success. So if it's not working out, we may not have a choice
>in the
>> > matter.
>> >
>> > I'd say, let's run the experiment for three months, and then
>review. Then
>> > again in another three months.
>>
>>
>> > Are you happy with that?
>> >
>> >
>> >
>> Modulo what I am said, yes. One last thing, what is the privacy
>policy of
>> such system? Can people easily remove them from it? (to be complete)
>>
>> - benoit
>>
>>
>> >
>> > On 7 October 2013 09:47, Jan Lehnardt <ja...@apache.org> wrote:
>> >
>> > > +1, love this initiative Noah! I am really curious about what
>comes
>> > > out of this.
>> > >
>> > > Thanks for the lively discussion around this, everyone. I’m
>seeing
>> > > all my concerns addressed, so I can just thumb up :D
>> > >
>> > > Best
>> > > Jan
>> > > --
>> > >
>> > > On Oct 5, 2013, at 19:04 , Noah Slater <ns...@apache.org>
>wrote:
>> > >
>> > > > Hi devs,
>> > > >
>> > > > I would like to propose that we use Influitive to help us
>improve our
>> > > > marketing efforts.
>> > > >
>> > > > I fully intend to execute this proposal myself. If you want to
>> > volunteer,
>> > > > that is great. But if you are not interested in this, that is
>fine
>> > also.
>> > > > Nobody has to participate if they do not want to. I am quite
>happy to
>> > run
>> > > > it as an experiment myself. If it works we can continue, and if
>it
>> > > doesn't,
>> > > > we can stop.
>> > > >
>> > > > Unless anybody objects, I will assume lazy consensus after
>three
>> days,
>> > > and
>> > > > let Influitive that we have the green light to move forward.
>> > > >
>> > > > = Introduction =
>> > > >
>> > > > Influitive AdvocateHub is an advocacy marketing platform.
>> > > >
>> > > > Think of it like Kickstarter, for marketing. You post a
>description
>> of
>> > > what
>> > > > you want to accomplish, and then your community members pitch
>in and
>> > help
>> > > > to make it happen.
>> > > >
>> > > > As an open source project, we struggle to market ourselves
>because we
>> > > have
>> > > > no budget. Where a typical company might take out ads, or pay
>people
>> to
>> > > > write technical content, we rely on volunteer time and word of
>mouth.
>> > But
>> > > > this is typically disorganised.
>> > > >
>> > > > AdvocateHub is a tool that that will allow us to coordinate
>that
>> > > volunteer
>> > > > time and word of mouth. We can create a steady stream of
>challenges
>> or
>> > > > requests for help and people who are committed to the project
>can
>> > > organise
>> > > > around these, and help us spread the word of CouchDB.
>> > > >
>> > > > In return for doing these things, we reward them with prestige
>and
>> > swag.
>> > > > And maybe a few other exclusive items, like conference tickets,
>or a
>> > > round
>> > > > of drinks on me.
>> > > >
>> > > > You should watch these two intro videos:
>> > > >
>> > > > http://influitive.com/introduction-to-advocate-marketing/
>> > > >
>> > > > http://influitive.com/learn-more-about-the-advocatehub/
>> > > >
>> > > > = Donation =
>> > > >
>> > > > AdvocateHub is usually premium service. However, Influitive has
>very
>> > > > generously offered to donate an account to the project. This is
>the
>> > first
>> > > > open source project that Influitive has supported like this, so
>I am
>> > very
>> > > > grateful for the opportunity!
>> > > >
>> > > > AdvocateHub is designed for commercial companies, but I think
>we can
>> > make
>> > > > it work for an open source project. Influitive will be
>monitoring our
>> > > > progress, and if things are not working out, we’ll end the
>> experiment.
>> > As
>> > > > part of this agreement, I will be the account owner and will be
>> > > responsible
>> > > > for its operation. But if you are a committer and you want to
>help
>> > out, I
>> > > > can add you as an admin. This is similar to how we run our
>social
>> media
>> > > > accounts.
>> > > >
>> > > > In return for the support, I am proposing to:
>> > > >
>> > > > * Promote the use of our AdvocateHub within our community
>> > > > * Thank them from our website, wiki, and social media
>accounts
>> > > > * Document our progress with the occasional blog or tweet
>> > > >
>> > > > Promoting the use of our AdvocateHub will probably take the
>form of
>> > > > mentioning new challenges on the mailing list, blog, Twitter,
>> Google+,
>> > > etc.
>> > > > Obviously, we will want to encourage as many people as possible
>to
>> get
>> > > > involved in the AdvocateHub as possible.
>> > > >
>> > > > As for documenting our progress, I am thinking that the
>occasional
>> post
>> > > > covering how we’re using the tool, and what sorts of results
>we’re
>> > seeing
>> > > > would be appropriate.
>> > > >
>> > > > I have spoken with the ASF fundraising team already, and there
>are no
>> > > > concerns with these plans at the foundation level.
>> > > >
>> > > > = Challenges =
>> > > >
>> > > > AdvocateHub is built around the concept of a challenge, or
>request
>> for
>> > > > help. We can design these however we want, and I will be
>looking for
>> > > input
>> > > > from the community.
>> > > >
>> > > > Ideas for easy challenges:
>> > > >
>> > > > * Retweet an official @CouchDB tweet
>> > > > * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
>> > > > * Publicly mention CouchDB on Twitter, Google+, LinkedIn,
>your
>> blog,
>> > > etc
>> > > > * Share an official project blog post somewhere
>> > > >
>> > > > Ideas for medium challenges:
>> > > >
>> > > > * Watch a featured video
>> > > > * Read a featured blog post, or section of the docs
>> > > > * Help someone out on the mailing list
>> > > > * Answer a CouchDB question on Stack Overflow, Server Fault,
>etc
>> > > > * Talk about CouchDB in response to a Quora question
>> > > > * Talk about CouchDB in response to a submission on Hacker
>News,
>> > > > Reddit, etc
>> > > > * Comment on an official blog post, or a blog post about
>CouchDB
>> > > > * Post a review on alternativeTo, or other review sites,
>blog
>> posts,
>> > > etc
>> > > > * Provide an official endorsement or quote from your company
>about
>> > > > CouchDB
>> > > > * Complete a survey (I plan to actually make some surveys)
>> > > >
>> > > > Ideas for hard challenges:
>> > > >
>> > > > * Create a CouchDB client, library, or tool
>> > > > * Produce early/mid/late stage technical content
>> > > > * Produce a CouchDB white paper
>> > > > * Give a talk or screencast about CouchDB
>> > > > * Share a CouchDB success story, testimonial, or case-study
>> > > > * Organise a CouchDB meet-up
>> > > > * Organise a CouchDB conference
>> > > >
>> > > > And then, challenges for actually contributing back to CouchDB
>> itself:
>> > > >
>> > > > * Triage X many JIRA tickets
>> > > > * Fix up outstanding issues on a CouchDB pull request
>> > > > * Contribute a fix for a JIRA ticket
>> > > >
>> > > > (This might be a little outside of the scope of AdvocateHub, as
>this
>> > > would
>> > > > request contribution back to the project itself. Still, it
>would be
>> > > > interesting to see if this would work. As a volunteer
>organisation,
>> > > > volunteer time and attracting contributions is our top
>priority.)
>> > > >
>> > > > = Rewards =
>> > > >
>> > > > Completing challenges gives you points, levels, and badges. I
>know
>> that
>> > > > many people love this kind of system, and are happy to compete
>with
>> > each
>> > > > other for points alone. However, we also have the option of
>allowing
>> > > > advocates to exchange points for prizes.
>> > > >
>> > > > AdvocateHub has an integration with a swag drop-ship merchant.
>> > > Hopefully, I
>> > > > can attract a third-party to help with the bill for this. It
>would
>> mean
>> > > > that by completing challenges, we can reward advocates with
>t-shirts,
>> > > > hoodies, mugs, pins, stickers, and so on!
>> > > >
>> > > > In addition to swag, we could also offer:
>> > > >
>> > > > * Individual promotion for you
>> > > > * Priority or free tickets to the regular CouchDB Confs
>> > > > * Email support or advice from the committers (depends on
>who
>> > > > volunteers time)
>> > > > * Private call with one the committers (depends on who
>volunteers
>> > > time)
>> > > > * Drinks on Noah (though, you’ll have to come find me!)
>> > > >
>> > > > Promotion could be quite a draw. Imagine a weekly Tweet along
>the
>> lines
>> > > of
>> > > > “Thanks to @ARandomPerson for supporting CouchDB this week. You
>> should
>> > > > follow her on Twitter!” We could also include a mention in our
>weekly
>> > > > CouchDB news. (A blog idea that I have not executed on yet.) As
>far
>> as
>> > I
>> > > > can tell, we’d only be able to promote individual accounts, not
>> > > businesses.
>> > > > The ASF has very strict vendor neutrality rules that we must
>adhere
>> to.
>> > > >
>> > > > Some other ideas of how we could provide return promotion:
>> > > >
>> > > > * Mention on our homepage that week
>> > > > * Get on our weekly @CouchDB #FollowFriday
>> > > > * Entered into a “hall of fame”
>> > > > * Get mentioned in our Git commits, issues, or pull requests
>> > > >
>> > > > The @CouchDB account has close to 10k followers. And our
>homepage
>> > > receives
>> > > > around 8,500 page views per month at the moment. Those numbers
>are
>> not
>> > to
>> > > > be sniffed at!
>> > > >
>> > > > (This is heavily inspired by Hoodie, who allow people to
>sponsor the
>> > > > project in return for promotion via different channels. I think
>we
>> can
>> > > > borrow some of this.)
>> > > >
>> > > > The specifics of the reward programme is unimportant at this
>stage.
>> > Like
>> > > > the details of the challenges themselves, we can figure this
>out as
>> we
>> > > move
>> > > > forward.
>> > > >
>> > > > Thanks,
>> > > >
>> > > > --
>> > > > Noah Slater
>> > > > https://twitter.com/nslater
>> > >
>> > >
>> >
>> >
>> > --
>> > Noah Slater
>> > https://twitter.com/nslater
>> >
>>
--
Sent from Kaiten Mail. Please excuse my brevity.
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Noah Slater <ns...@apache.org>.
Okay, thanks Benoit!
I agree that such things should be optional, and that if they work, we
should look at ways of replicating their success in other areas of the
project.
The Influitive privacy policy is here: http://influitive.com/privacy/
"You may withdraw your permission for us to collect, use and disclose your
personal data at any time, subject to legal and contractual restrictions
and reasonable notice."
"You have the right to ask whether we hold any personal information about
you, to see that information, and to ask us to correct or update your
information."
I hope this answers your question.
Unless there's no further objection, I will let Influitive know we have the
green light to move forward.
Once I've done that, they'll set us up with a hub, and I will invite people
to be admins. Anyone is welcome. If you're already expressed an interest in
this thread, I will reach out to you. If you haven't, let me know at any
time.
On 8 October 2013 18:55, Benoit Chesneau <bc...@gmail.com> wrote:
> On Mon, Oct 7, 2013 at 5:20 PM, Noah Slater <ns...@apache.org> wrote:
>
> > Okay, some answers:
> >
> > - How to ensure this reward system is optional?
> >
> > I think we can experiment with the reward system. The default is just to
> > award points for completing tasks. So you can have leader-boards within
> > Influitive, and you can see who has the most points, etc.
> >
> > What we do with those points is how we experiment. I think the first step
> > should be to offer some sort of public thanks, as I outline in my
> proposal.
> > Even a Twitter #FF would go a long way, I think.
> >
> > Secondly, I think we should experiment with allow people to exchange
> points
> > for swag. Perhaps this will be received positively, perhaps some people
> > will complain. If it causes a problem, we remove it.
> >
> >
> I think we should just make sure to propose the system as an option.
> Otherwise such things looks OK for me Sort of achievements like in games in
> fact.
>
>
> > - How to ensure that people that not participate do not feel unconsidered
> > by other members of the community because not rewarded by the Influtive
> > system?
> >
> > I think you're right: we should recognise people who help out on JIRA,
> and
> > on the mailing lists, and so on. I think that's a worthwhile discussion
> to
> > have, but I don't think it blocks this work. In fact, perhaps we can look
> > at what works for Influitive, and then try to replicate that in other
> parts
> > of the project.
> >
> > So, for example, if the Twitter promotion, or blog mentions, really work,
> > and people like them, then perhaps in a few months, we have a
> conversation
> > about how to do the same sort of thing for people who contribute in other
> > ways.
> >
> > The same can be said for swag too. Assuming I even find a budget for this
> > (which I may not be able to do) then presumably we can extend that and
> say
> > thank you to other people with a t-shirt too. (Actually, recently,
> Cloudant
> > very kindly sent a t-shirt to committers at my suggestion. So that is one
> > example of this. I assume you got yours, Benoit? I've been wearing mine!)
> >
> > I think it's important to consider the different types of people we're
> > talking about here. As a core contributor, I really don't feel like I
> need
> > to be rewarded for my contributions. The community is enough of a reward
> > for me.
> >
> > But Influtive is targeting people who may only be on the peripheries.
> > People who have used CouchDB, love it, and will jump at the opportunity
> to
> > help out by telling their network about their experiences. And for that,
> > sending them a pack of CouchDB stickers, or whatever, makes obvious
> sense.
> > We're trying to mobilise a volunteer workforce of people who will promote
> > us! So let's give them the swag to do that!
> >
> > In fact, we might want to use that as a metric for what we give out. We
> > could say, okay, we're only gonna give out swag that has some promotional
> > value to the project. So in a way, it an extension of the initiative
> > itself. People who are interested in marketing and promoting CouchDB will
> > be rewarded with shipments of stickers, keyrings, etc, to help them with
> > that. Perfect!
> >
>
>
> The thing is that some people that already help the project without extra
> rewards and for any reason (cultural, philosophy, ....) may not want to be
> part of a reward system. Witch is their choice but I just want to make sure
> they won't be forgotten. Or more exactly that we don't forget to thanks
> them. Just because they are outside the metrics. We can continue the
> discussion in a separate thread, but that is important for me. Imo just
> because some people like achievements and be shown with a badge doesn't
> mean we should encourage such system (I certainly not) or rather that it
> should be the only system. If we can have let choice then I am fine.
>
> (Also yes got my shirt, and I thanks them again :)
>
>
>
>
> > - What will define the success or failure of the experimentation? What
> is
> > the deadline of the experimentation?
> >
> > With something like this, I think the success of failure has to be
> measured
> > qualitatively.
> >
> > So we could look at a number of things:
> >
> > * What has the take-up been like? Are many people using it?
> > * What has been the reaction to the programme within the community? Do
> > people feel positively about it?
> > * What has been the reaction to the programme outside of our community?
> Has
> > it engaged people or attracted new users? Is it seen favourably by other
> > people?
> >
> > Note also that Influtive themselves will be keeping a very close eye on
> the
> > experiment, because obviously, it is important to them that the
> experiment
> > is a success. So if it's not working out, we may not have a choice in the
> > matter.
> >
> > I'd say, let's run the experiment for three months, and then review. Then
> > again in another three months.
>
>
> > Are you happy with that?
> >
> >
> >
> Modulo what I am said, yes. One last thing, what is the privacy policy of
> such system? Can people easily remove them from it? (to be complete)
>
> - benoit
>
>
> >
> > On 7 October 2013 09:47, Jan Lehnardt <ja...@apache.org> wrote:
> >
> > > +1, love this initiative Noah! I am really curious about what comes
> > > out of this.
> > >
> > > Thanks for the lively discussion around this, everyone. I’m seeing
> > > all my concerns addressed, so I can just thumb up :D
> > >
> > > Best
> > > Jan
> > > --
> > >
> > > On Oct 5, 2013, at 19:04 , Noah Slater <ns...@apache.org> wrote:
> > >
> > > > Hi devs,
> > > >
> > > > I would like to propose that we use Influitive to help us improve our
> > > > marketing efforts.
> > > >
> > > > I fully intend to execute this proposal myself. If you want to
> > volunteer,
> > > > that is great. But if you are not interested in this, that is fine
> > also.
> > > > Nobody has to participate if they do not want to. I am quite happy to
> > run
> > > > it as an experiment myself. If it works we can continue, and if it
> > > doesn't,
> > > > we can stop.
> > > >
> > > > Unless anybody objects, I will assume lazy consensus after three
> days,
> > > and
> > > > let Influitive that we have the green light to move forward.
> > > >
> > > > = Introduction =
> > > >
> > > > Influitive AdvocateHub is an advocacy marketing platform.
> > > >
> > > > Think of it like Kickstarter, for marketing. You post a description
> of
> > > what
> > > > you want to accomplish, and then your community members pitch in and
> > help
> > > > to make it happen.
> > > >
> > > > As an open source project, we struggle to market ourselves because we
> > > have
> > > > no budget. Where a typical company might take out ads, or pay people
> to
> > > > write technical content, we rely on volunteer time and word of mouth.
> > But
> > > > this is typically disorganised.
> > > >
> > > > AdvocateHub is a tool that that will allow us to coordinate that
> > > volunteer
> > > > time and word of mouth. We can create a steady stream of challenges
> or
> > > > requests for help and people who are committed to the project can
> > > organise
> > > > around these, and help us spread the word of CouchDB.
> > > >
> > > > In return for doing these things, we reward them with prestige and
> > swag.
> > > > And maybe a few other exclusive items, like conference tickets, or a
> > > round
> > > > of drinks on me.
> > > >
> > > > You should watch these two intro videos:
> > > >
> > > > http://influitive.com/introduction-to-advocate-marketing/
> > > >
> > > > http://influitive.com/learn-more-about-the-advocatehub/
> > > >
> > > > = Donation =
> > > >
> > > > AdvocateHub is usually premium service. However, Influitive has very
> > > > generously offered to donate an account to the project. This is the
> > first
> > > > open source project that Influitive has supported like this, so I am
> > very
> > > > grateful for the opportunity!
> > > >
> > > > AdvocateHub is designed for commercial companies, but I think we can
> > make
> > > > it work for an open source project. Influitive will be monitoring our
> > > > progress, and if things are not working out, we’ll end the
> experiment.
> > As
> > > > part of this agreement, I will be the account owner and will be
> > > responsible
> > > > for its operation. But if you are a committer and you want to help
> > out, I
> > > > can add you as an admin. This is similar to how we run our social
> media
> > > > accounts.
> > > >
> > > > In return for the support, I am proposing to:
> > > >
> > > > * Promote the use of our AdvocateHub within our community
> > > > * Thank them from our website, wiki, and social media accounts
> > > > * Document our progress with the occasional blog or tweet
> > > >
> > > > Promoting the use of our AdvocateHub will probably take the form of
> > > > mentioning new challenges on the mailing list, blog, Twitter,
> Google+,
> > > etc.
> > > > Obviously, we will want to encourage as many people as possible to
> get
> > > > involved in the AdvocateHub as possible.
> > > >
> > > > As for documenting our progress, I am thinking that the occasional
> post
> > > > covering how we’re using the tool, and what sorts of results we’re
> > seeing
> > > > would be appropriate.
> > > >
> > > > I have spoken with the ASF fundraising team already, and there are no
> > > > concerns with these plans at the foundation level.
> > > >
> > > > = Challenges =
> > > >
> > > > AdvocateHub is built around the concept of a challenge, or request
> for
> > > > help. We can design these however we want, and I will be looking for
> > > input
> > > > from the community.
> > > >
> > > > Ideas for easy challenges:
> > > >
> > > > * Retweet an official @CouchDB tweet
> > > > * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> > > > * Publicly mention CouchDB on Twitter, Google+, LinkedIn, your
> blog,
> > > etc
> > > > * Share an official project blog post somewhere
> > > >
> > > > Ideas for medium challenges:
> > > >
> > > > * Watch a featured video
> > > > * Read a featured blog post, or section of the docs
> > > > * Help someone out on the mailing list
> > > > * Answer a CouchDB question on Stack Overflow, Server Fault, etc
> > > > * Talk about CouchDB in response to a Quora question
> > > > * Talk about CouchDB in response to a submission on Hacker News,
> > > > Reddit, etc
> > > > * Comment on an official blog post, or a blog post about CouchDB
> > > > * Post a review on alternativeTo, or other review sites, blog
> posts,
> > > etc
> > > > * Provide an official endorsement or quote from your company about
> > > > CouchDB
> > > > * Complete a survey (I plan to actually make some surveys)
> > > >
> > > > Ideas for hard challenges:
> > > >
> > > > * Create a CouchDB client, library, or tool
> > > > * Produce early/mid/late stage technical content
> > > > * Produce a CouchDB white paper
> > > > * Give a talk or screencast about CouchDB
> > > > * Share a CouchDB success story, testimonial, or case-study
> > > > * Organise a CouchDB meet-up
> > > > * Organise a CouchDB conference
> > > >
> > > > And then, challenges for actually contributing back to CouchDB
> itself:
> > > >
> > > > * Triage X many JIRA tickets
> > > > * Fix up outstanding issues on a CouchDB pull request
> > > > * Contribute a fix for a JIRA ticket
> > > >
> > > > (This might be a little outside of the scope of AdvocateHub, as this
> > > would
> > > > request contribution back to the project itself. Still, it would be
> > > > interesting to see if this would work. As a volunteer organisation,
> > > > volunteer time and attracting contributions is our top priority.)
> > > >
> > > > = Rewards =
> > > >
> > > > Completing challenges gives you points, levels, and badges. I know
> that
> > > > many people love this kind of system, and are happy to compete with
> > each
> > > > other for points alone. However, we also have the option of allowing
> > > > advocates to exchange points for prizes.
> > > >
> > > > AdvocateHub has an integration with a swag drop-ship merchant.
> > > Hopefully, I
> > > > can attract a third-party to help with the bill for this. It would
> mean
> > > > that by completing challenges, we can reward advocates with t-shirts,
> > > > hoodies, mugs, pins, stickers, and so on!
> > > >
> > > > In addition to swag, we could also offer:
> > > >
> > > > * Individual promotion for you
> > > > * Priority or free tickets to the regular CouchDB Confs
> > > > * Email support or advice from the committers (depends on who
> > > > volunteers time)
> > > > * Private call with one the committers (depends on who volunteers
> > > time)
> > > > * Drinks on Noah (though, you’ll have to come find me!)
> > > >
> > > > Promotion could be quite a draw. Imagine a weekly Tweet along the
> lines
> > > of
> > > > “Thanks to @ARandomPerson for supporting CouchDB this week. You
> should
> > > > follow her on Twitter!” We could also include a mention in our weekly
> > > > CouchDB news. (A blog idea that I have not executed on yet.) As far
> as
> > I
> > > > can tell, we’d only be able to promote individual accounts, not
> > > businesses.
> > > > The ASF has very strict vendor neutrality rules that we must adhere
> to.
> > > >
> > > > Some other ideas of how we could provide return promotion:
> > > >
> > > > * Mention on our homepage that week
> > > > * Get on our weekly @CouchDB #FollowFriday
> > > > * Entered into a “hall of fame”
> > > > * Get mentioned in our Git commits, issues, or pull requests
> > > >
> > > > The @CouchDB account has close to 10k followers. And our homepage
> > > receives
> > > > around 8,500 page views per month at the moment. Those numbers are
> not
> > to
> > > > be sniffed at!
> > > >
> > > > (This is heavily inspired by Hoodie, who allow people to sponsor the
> > > > project in return for promotion via different channels. I think we
> can
> > > > borrow some of this.)
> > > >
> > > > The specifics of the reward programme is unimportant at this stage.
> > Like
> > > > the details of the challenges themselves, we can figure this out as
> we
> > > move
> > > > forward.
> > > >
> > > > Thanks,
> > > >
> > > > --
> > > > Noah Slater
> > > > https://twitter.com/nslater
> > >
> > >
> >
> >
> > --
> > Noah Slater
> > https://twitter.com/nslater
> >
>
--
Noah Slater
https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Benoit Chesneau <bc...@gmail.com>.
On Mon, Oct 7, 2013 at 5:20 PM, Noah Slater <ns...@apache.org> wrote:
> Okay, some answers:
>
> - How to ensure this reward system is optional?
>
> I think we can experiment with the reward system. The default is just to
> award points for completing tasks. So you can have leader-boards within
> Influitive, and you can see who has the most points, etc.
>
> What we do with those points is how we experiment. I think the first step
> should be to offer some sort of public thanks, as I outline in my proposal.
> Even a Twitter #FF would go a long way, I think.
>
> Secondly, I think we should experiment with allow people to exchange points
> for swag. Perhaps this will be received positively, perhaps some people
> will complain. If it causes a problem, we remove it.
>
>
I think we should just make sure to propose the system as an option.
Otherwise such things looks OK for me Sort of achievements like in games in
fact.
> - How to ensure that people that not participate do not feel unconsidered
> by other members of the community because not rewarded by the Influtive
> system?
>
> I think you're right: we should recognise people who help out on JIRA, and
> on the mailing lists, and so on. I think that's a worthwhile discussion to
> have, but I don't think it blocks this work. In fact, perhaps we can look
> at what works for Influitive, and then try to replicate that in other parts
> of the project.
>
> So, for example, if the Twitter promotion, or blog mentions, really work,
> and people like them, then perhaps in a few months, we have a conversation
> about how to do the same sort of thing for people who contribute in other
> ways.
>
> The same can be said for swag too. Assuming I even find a budget for this
> (which I may not be able to do) then presumably we can extend that and say
> thank you to other people with a t-shirt too. (Actually, recently, Cloudant
> very kindly sent a t-shirt to committers at my suggestion. So that is one
> example of this. I assume you got yours, Benoit? I've been wearing mine!)
>
> I think it's important to consider the different types of people we're
> talking about here. As a core contributor, I really don't feel like I need
> to be rewarded for my contributions. The community is enough of a reward
> for me.
>
> But Influtive is targeting people who may only be on the peripheries.
> People who have used CouchDB, love it, and will jump at the opportunity to
> help out by telling their network about their experiences. And for that,
> sending them a pack of CouchDB stickers, or whatever, makes obvious sense.
> We're trying to mobilise a volunteer workforce of people who will promote
> us! So let's give them the swag to do that!
>
> In fact, we might want to use that as a metric for what we give out. We
> could say, okay, we're only gonna give out swag that has some promotional
> value to the project. So in a way, it an extension of the initiative
> itself. People who are interested in marketing and promoting CouchDB will
> be rewarded with shipments of stickers, keyrings, etc, to help them with
> that. Perfect!
>
The thing is that some people that already help the project without extra
rewards and for any reason (cultural, philosophy, ....) may not want to be
part of a reward system. Witch is their choice but I just want to make sure
they won't be forgotten. Or more exactly that we don't forget to thanks
them. Just because they are outside the metrics. We can continue the
discussion in a separate thread, but that is important for me. Imo just
because some people like achievements and be shown with a badge doesn't
mean we should encourage such system (I certainly not) or rather that it
should be the only system. If we can have let choice then I am fine.
(Also yes got my shirt, and I thanks them again :)
> - What will define the success or failure of the experimentation? What is
> the deadline of the experimentation?
>
> With something like this, I think the success of failure has to be measured
> qualitatively.
>
> So we could look at a number of things:
>
> * What has the take-up been like? Are many people using it?
> * What has been the reaction to the programme within the community? Do
> people feel positively about it?
> * What has been the reaction to the programme outside of our community? Has
> it engaged people or attracted new users? Is it seen favourably by other
> people?
>
> Note also that Influtive themselves will be keeping a very close eye on the
> experiment, because obviously, it is important to them that the experiment
> is a success. So if it's not working out, we may not have a choice in the
> matter.
>
> I'd say, let's run the experiment for three months, and then review. Then
> again in another three months.
> Are you happy with that?
>
>
>
Modulo what I am said, yes. One last thing, what is the privacy policy of
such system? Can people easily remove them from it? (to be complete)
- benoit
>
> On 7 October 2013 09:47, Jan Lehnardt <ja...@apache.org> wrote:
>
> > +1, love this initiative Noah! I am really curious about what comes
> > out of this.
> >
> > Thanks for the lively discussion around this, everyone. I’m seeing
> > all my concerns addressed, so I can just thumb up :D
> >
> > Best
> > Jan
> > --
> >
> > On Oct 5, 2013, at 19:04 , Noah Slater <ns...@apache.org> wrote:
> >
> > > Hi devs,
> > >
> > > I would like to propose that we use Influitive to help us improve our
> > > marketing efforts.
> > >
> > > I fully intend to execute this proposal myself. If you want to
> volunteer,
> > > that is great. But if you are not interested in this, that is fine
> also.
> > > Nobody has to participate if they do not want to. I am quite happy to
> run
> > > it as an experiment myself. If it works we can continue, and if it
> > doesn't,
> > > we can stop.
> > >
> > > Unless anybody objects, I will assume lazy consensus after three days,
> > and
> > > let Influitive that we have the green light to move forward.
> > >
> > > = Introduction =
> > >
> > > Influitive AdvocateHub is an advocacy marketing platform.
> > >
> > > Think of it like Kickstarter, for marketing. You post a description of
> > what
> > > you want to accomplish, and then your community members pitch in and
> help
> > > to make it happen.
> > >
> > > As an open source project, we struggle to market ourselves because we
> > have
> > > no budget. Where a typical company might take out ads, or pay people to
> > > write technical content, we rely on volunteer time and word of mouth.
> But
> > > this is typically disorganised.
> > >
> > > AdvocateHub is a tool that that will allow us to coordinate that
> > volunteer
> > > time and word of mouth. We can create a steady stream of challenges or
> > > requests for help and people who are committed to the project can
> > organise
> > > around these, and help us spread the word of CouchDB.
> > >
> > > In return for doing these things, we reward them with prestige and
> swag.
> > > And maybe a few other exclusive items, like conference tickets, or a
> > round
> > > of drinks on me.
> > >
> > > You should watch these two intro videos:
> > >
> > > http://influitive.com/introduction-to-advocate-marketing/
> > >
> > > http://influitive.com/learn-more-about-the-advocatehub/
> > >
> > > = Donation =
> > >
> > > AdvocateHub is usually premium service. However, Influitive has very
> > > generously offered to donate an account to the project. This is the
> first
> > > open source project that Influitive has supported like this, so I am
> very
> > > grateful for the opportunity!
> > >
> > > AdvocateHub is designed for commercial companies, but I think we can
> make
> > > it work for an open source project. Influitive will be monitoring our
> > > progress, and if things are not working out, we’ll end the experiment.
> As
> > > part of this agreement, I will be the account owner and will be
> > responsible
> > > for its operation. But if you are a committer and you want to help
> out, I
> > > can add you as an admin. This is similar to how we run our social media
> > > accounts.
> > >
> > > In return for the support, I am proposing to:
> > >
> > > * Promote the use of our AdvocateHub within our community
> > > * Thank them from our website, wiki, and social media accounts
> > > * Document our progress with the occasional blog or tweet
> > >
> > > Promoting the use of our AdvocateHub will probably take the form of
> > > mentioning new challenges on the mailing list, blog, Twitter, Google+,
> > etc.
> > > Obviously, we will want to encourage as many people as possible to get
> > > involved in the AdvocateHub as possible.
> > >
> > > As for documenting our progress, I am thinking that the occasional post
> > > covering how we’re using the tool, and what sorts of results we’re
> seeing
> > > would be appropriate.
> > >
> > > I have spoken with the ASF fundraising team already, and there are no
> > > concerns with these plans at the foundation level.
> > >
> > > = Challenges =
> > >
> > > AdvocateHub is built around the concept of a challenge, or request for
> > > help. We can design these however we want, and I will be looking for
> > input
> > > from the community.
> > >
> > > Ideas for easy challenges:
> > >
> > > * Retweet an official @CouchDB tweet
> > > * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> > > * Publicly mention CouchDB on Twitter, Google+, LinkedIn, your blog,
> > etc
> > > * Share an official project blog post somewhere
> > >
> > > Ideas for medium challenges:
> > >
> > > * Watch a featured video
> > > * Read a featured blog post, or section of the docs
> > > * Help someone out on the mailing list
> > > * Answer a CouchDB question on Stack Overflow, Server Fault, etc
> > > * Talk about CouchDB in response to a Quora question
> > > * Talk about CouchDB in response to a submission on Hacker News,
> > > Reddit, etc
> > > * Comment on an official blog post, or a blog post about CouchDB
> > > * Post a review on alternativeTo, or other review sites, blog posts,
> > etc
> > > * Provide an official endorsement or quote from your company about
> > > CouchDB
> > > * Complete a survey (I plan to actually make some surveys)
> > >
> > > Ideas for hard challenges:
> > >
> > > * Create a CouchDB client, library, or tool
> > > * Produce early/mid/late stage technical content
> > > * Produce a CouchDB white paper
> > > * Give a talk or screencast about CouchDB
> > > * Share a CouchDB success story, testimonial, or case-study
> > > * Organise a CouchDB meet-up
> > > * Organise a CouchDB conference
> > >
> > > And then, challenges for actually contributing back to CouchDB itself:
> > >
> > > * Triage X many JIRA tickets
> > > * Fix up outstanding issues on a CouchDB pull request
> > > * Contribute a fix for a JIRA ticket
> > >
> > > (This might be a little outside of the scope of AdvocateHub, as this
> > would
> > > request contribution back to the project itself. Still, it would be
> > > interesting to see if this would work. As a volunteer organisation,
> > > volunteer time and attracting contributions is our top priority.)
> > >
> > > = Rewards =
> > >
> > > Completing challenges gives you points, levels, and badges. I know that
> > > many people love this kind of system, and are happy to compete with
> each
> > > other for points alone. However, we also have the option of allowing
> > > advocates to exchange points for prizes.
> > >
> > > AdvocateHub has an integration with a swag drop-ship merchant.
> > Hopefully, I
> > > can attract a third-party to help with the bill for this. It would mean
> > > that by completing challenges, we can reward advocates with t-shirts,
> > > hoodies, mugs, pins, stickers, and so on!
> > >
> > > In addition to swag, we could also offer:
> > >
> > > * Individual promotion for you
> > > * Priority or free tickets to the regular CouchDB Confs
> > > * Email support or advice from the committers (depends on who
> > > volunteers time)
> > > * Private call with one the committers (depends on who volunteers
> > time)
> > > * Drinks on Noah (though, you’ll have to come find me!)
> > >
> > > Promotion could be quite a draw. Imagine a weekly Tweet along the lines
> > of
> > > “Thanks to @ARandomPerson for supporting CouchDB this week. You should
> > > follow her on Twitter!” We could also include a mention in our weekly
> > > CouchDB news. (A blog idea that I have not executed on yet.) As far as
> I
> > > can tell, we’d only be able to promote individual accounts, not
> > businesses.
> > > The ASF has very strict vendor neutrality rules that we must adhere to.
> > >
> > > Some other ideas of how we could provide return promotion:
> > >
> > > * Mention on our homepage that week
> > > * Get on our weekly @CouchDB #FollowFriday
> > > * Entered into a “hall of fame”
> > > * Get mentioned in our Git commits, issues, or pull requests
> > >
> > > The @CouchDB account has close to 10k followers. And our homepage
> > receives
> > > around 8,500 page views per month at the moment. Those numbers are not
> to
> > > be sniffed at!
> > >
> > > (This is heavily inspired by Hoodie, who allow people to sponsor the
> > > project in return for promotion via different channels. I think we can
> > > borrow some of this.)
> > >
> > > The specifics of the reward programme is unimportant at this stage.
> Like
> > > the details of the challenges themselves, we can figure this out as we
> > move
> > > forward.
> > >
> > > Thanks,
> > >
> > > --
> > > Noah Slater
> > > https://twitter.com/nslater
> >
> >
>
>
> --
> Noah Slater
> https://twitter.com/nslater
>
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Noah Slater <ns...@apache.org>.
Okay, some answers:
- How to ensure this reward system is optional?
I think we can experiment with the reward system. The default is just to
award points for completing tasks. So you can have leader-boards within
Influitive, and you can see who has the most points, etc.
What we do with those points is how we experiment. I think the first step
should be to offer some sort of public thanks, as I outline in my proposal.
Even a Twitter #FF would go a long way, I think.
Secondly, I think we should experiment with allow people to exchange points
for swag. Perhaps this will be received positively, perhaps some people
will complain. If it causes a problem, we remove it.
- How to ensure that people that not participate do not feel unconsidered
by other members of the community because not rewarded by the Influtive
system?
I think you're right: we should recognise people who help out on JIRA, and
on the mailing lists, and so on. I think that's a worthwhile discussion to
have, but I don't think it blocks this work. In fact, perhaps we can look
at what works for Influitive, and then try to replicate that in other parts
of the project.
So, for example, if the Twitter promotion, or blog mentions, really work,
and people like them, then perhaps in a few months, we have a conversation
about how to do the same sort of thing for people who contribute in other
ways.
The same can be said for swag too. Assuming I even find a budget for this
(which I may not be able to do) then presumably we can extend that and say
thank you to other people with a t-shirt too. (Actually, recently, Cloudant
very kindly sent a t-shirt to committers at my suggestion. So that is one
example of this. I assume you got yours, Benoit? I've been wearing mine!)
I think it's important to consider the different types of people we're
talking about here. As a core contributor, I really don't feel like I need
to be rewarded for my contributions. The community is enough of a reward
for me.
But Influtive is targeting people who may only be on the peripheries.
People who have used CouchDB, love it, and will jump at the opportunity to
help out by telling their network about their experiences. And for that,
sending them a pack of CouchDB stickers, or whatever, makes obvious sense.
We're trying to mobilise a volunteer workforce of people who will promote
us! So let's give them the swag to do that!
In fact, we might want to use that as a metric for what we give out. We
could say, okay, we're only gonna give out swag that has some promotional
value to the project. So in a way, it an extension of the initiative
itself. People who are interested in marketing and promoting CouchDB will
be rewarded with shipments of stickers, keyrings, etc, to help them with
that. Perfect!
- What will define the success or failure of the experimentation? What is
the deadline of the experimentation?
With something like this, I think the success of failure has to be measured
qualitatively.
So we could look at a number of things:
* What has the take-up been like? Are many people using it?
* What has been the reaction to the programme within the community? Do
people feel positively about it?
* What has been the reaction to the programme outside of our community? Has
it engaged people or attracted new users? Is it seen favourably by other
people?
Note also that Influtive themselves will be keeping a very close eye on the
experiment, because obviously, it is important to them that the experiment
is a success. So if it's not working out, we may not have a choice in the
matter.
I'd say, let's run the experiment for three months, and then review. Then
again in another three months.
Are you happy with that?
On 7 October 2013 09:47, Jan Lehnardt <ja...@apache.org> wrote:
> +1, love this initiative Noah! I am really curious about what comes
> out of this.
>
> Thanks for the lively discussion around this, everyone. I’m seeing
> all my concerns addressed, so I can just thumb up :D
>
> Best
> Jan
> --
>
> On Oct 5, 2013, at 19:04 , Noah Slater <ns...@apache.org> wrote:
>
> > Hi devs,
> >
> > I would like to propose that we use Influitive to help us improve our
> > marketing efforts.
> >
> > I fully intend to execute this proposal myself. If you want to volunteer,
> > that is great. But if you are not interested in this, that is fine also.
> > Nobody has to participate if they do not want to. I am quite happy to run
> > it as an experiment myself. If it works we can continue, and if it
> doesn't,
> > we can stop.
> >
> > Unless anybody objects, I will assume lazy consensus after three days,
> and
> > let Influitive that we have the green light to move forward.
> >
> > = Introduction =
> >
> > Influitive AdvocateHub is an advocacy marketing platform.
> >
> > Think of it like Kickstarter, for marketing. You post a description of
> what
> > you want to accomplish, and then your community members pitch in and help
> > to make it happen.
> >
> > As an open source project, we struggle to market ourselves because we
> have
> > no budget. Where a typical company might take out ads, or pay people to
> > write technical content, we rely on volunteer time and word of mouth. But
> > this is typically disorganised.
> >
> > AdvocateHub is a tool that that will allow us to coordinate that
> volunteer
> > time and word of mouth. We can create a steady stream of challenges or
> > requests for help and people who are committed to the project can
> organise
> > around these, and help us spread the word of CouchDB.
> >
> > In return for doing these things, we reward them with prestige and swag.
> > And maybe a few other exclusive items, like conference tickets, or a
> round
> > of drinks on me.
> >
> > You should watch these two intro videos:
> >
> > http://influitive.com/introduction-to-advocate-marketing/
> >
> > http://influitive.com/learn-more-about-the-advocatehub/
> >
> > = Donation =
> >
> > AdvocateHub is usually premium service. However, Influitive has very
> > generously offered to donate an account to the project. This is the first
> > open source project that Influitive has supported like this, so I am very
> > grateful for the opportunity!
> >
> > AdvocateHub is designed for commercial companies, but I think we can make
> > it work for an open source project. Influitive will be monitoring our
> > progress, and if things are not working out, we’ll end the experiment. As
> > part of this agreement, I will be the account owner and will be
> responsible
> > for its operation. But if you are a committer and you want to help out, I
> > can add you as an admin. This is similar to how we run our social media
> > accounts.
> >
> > In return for the support, I am proposing to:
> >
> > * Promote the use of our AdvocateHub within our community
> > * Thank them from our website, wiki, and social media accounts
> > * Document our progress with the occasional blog or tweet
> >
> > Promoting the use of our AdvocateHub will probably take the form of
> > mentioning new challenges on the mailing list, blog, Twitter, Google+,
> etc.
> > Obviously, we will want to encourage as many people as possible to get
> > involved in the AdvocateHub as possible.
> >
> > As for documenting our progress, I am thinking that the occasional post
> > covering how we’re using the tool, and what sorts of results we’re seeing
> > would be appropriate.
> >
> > I have spoken with the ASF fundraising team already, and there are no
> > concerns with these plans at the foundation level.
> >
> > = Challenges =
> >
> > AdvocateHub is built around the concept of a challenge, or request for
> > help. We can design these however we want, and I will be looking for
> input
> > from the community.
> >
> > Ideas for easy challenges:
> >
> > * Retweet an official @CouchDB tweet
> > * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> > * Publicly mention CouchDB on Twitter, Google+, LinkedIn, your blog,
> etc
> > * Share an official project blog post somewhere
> >
> > Ideas for medium challenges:
> >
> > * Watch a featured video
> > * Read a featured blog post, or section of the docs
> > * Help someone out on the mailing list
> > * Answer a CouchDB question on Stack Overflow, Server Fault, etc
> > * Talk about CouchDB in response to a Quora question
> > * Talk about CouchDB in response to a submission on Hacker News,
> > Reddit, etc
> > * Comment on an official blog post, or a blog post about CouchDB
> > * Post a review on alternativeTo, or other review sites, blog posts,
> etc
> > * Provide an official endorsement or quote from your company about
> > CouchDB
> > * Complete a survey (I plan to actually make some surveys)
> >
> > Ideas for hard challenges:
> >
> > * Create a CouchDB client, library, or tool
> > * Produce early/mid/late stage technical content
> > * Produce a CouchDB white paper
> > * Give a talk or screencast about CouchDB
> > * Share a CouchDB success story, testimonial, or case-study
> > * Organise a CouchDB meet-up
> > * Organise a CouchDB conference
> >
> > And then, challenges for actually contributing back to CouchDB itself:
> >
> > * Triage X many JIRA tickets
> > * Fix up outstanding issues on a CouchDB pull request
> > * Contribute a fix for a JIRA ticket
> >
> > (This might be a little outside of the scope of AdvocateHub, as this
> would
> > request contribution back to the project itself. Still, it would be
> > interesting to see if this would work. As a volunteer organisation,
> > volunteer time and attracting contributions is our top priority.)
> >
> > = Rewards =
> >
> > Completing challenges gives you points, levels, and badges. I know that
> > many people love this kind of system, and are happy to compete with each
> > other for points alone. However, we also have the option of allowing
> > advocates to exchange points for prizes.
> >
> > AdvocateHub has an integration with a swag drop-ship merchant.
> Hopefully, I
> > can attract a third-party to help with the bill for this. It would mean
> > that by completing challenges, we can reward advocates with t-shirts,
> > hoodies, mugs, pins, stickers, and so on!
> >
> > In addition to swag, we could also offer:
> >
> > * Individual promotion for you
> > * Priority or free tickets to the regular CouchDB Confs
> > * Email support or advice from the committers (depends on who
> > volunteers time)
> > * Private call with one the committers (depends on who volunteers
> time)
> > * Drinks on Noah (though, you’ll have to come find me!)
> >
> > Promotion could be quite a draw. Imagine a weekly Tweet along the lines
> of
> > “Thanks to @ARandomPerson for supporting CouchDB this week. You should
> > follow her on Twitter!” We could also include a mention in our weekly
> > CouchDB news. (A blog idea that I have not executed on yet.) As far as I
> > can tell, we’d only be able to promote individual accounts, not
> businesses.
> > The ASF has very strict vendor neutrality rules that we must adhere to.
> >
> > Some other ideas of how we could provide return promotion:
> >
> > * Mention on our homepage that week
> > * Get on our weekly @CouchDB #FollowFriday
> > * Entered into a “hall of fame”
> > * Get mentioned in our Git commits, issues, or pull requests
> >
> > The @CouchDB account has close to 10k followers. And our homepage
> receives
> > around 8,500 page views per month at the moment. Those numbers are not to
> > be sniffed at!
> >
> > (This is heavily inspired by Hoodie, who allow people to sponsor the
> > project in return for promotion via different channels. I think we can
> > borrow some of this.)
> >
> > The specifics of the reward programme is unimportant at this stage. Like
> > the details of the challenges themselves, we can figure this out as we
> move
> > forward.
> >
> > Thanks,
> >
> > --
> > Noah Slater
> > https://twitter.com/nslater
>
>
--
Noah Slater
https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Jan Lehnardt <ja...@apache.org>.
+1, love this initiative Noah! I am really curious about what comes
out of this.
Thanks for the lively discussion around this, everyone. I’m seeing
all my concerns addressed, so I can just thumb up :D
Best
Jan
--
On Oct 5, 2013, at 19:04 , Noah Slater <ns...@apache.org> wrote:
> Hi devs,
>
> I would like to propose that we use Influitive to help us improve our
> marketing efforts.
>
> I fully intend to execute this proposal myself. If you want to volunteer,
> that is great. But if you are not interested in this, that is fine also.
> Nobody has to participate if they do not want to. I am quite happy to run
> it as an experiment myself. If it works we can continue, and if it doesn't,
> we can stop.
>
> Unless anybody objects, I will assume lazy consensus after three days, and
> let Influitive that we have the green light to move forward.
>
> = Introduction =
>
> Influitive AdvocateHub is an advocacy marketing platform.
>
> Think of it like Kickstarter, for marketing. You post a description of what
> you want to accomplish, and then your community members pitch in and help
> to make it happen.
>
> As an open source project, we struggle to market ourselves because we have
> no budget. Where a typical company might take out ads, or pay people to
> write technical content, we rely on volunteer time and word of mouth. But
> this is typically disorganised.
>
> AdvocateHub is a tool that that will allow us to coordinate that volunteer
> time and word of mouth. We can create a steady stream of challenges or
> requests for help and people who are committed to the project can organise
> around these, and help us spread the word of CouchDB.
>
> In return for doing these things, we reward them with prestige and swag.
> And maybe a few other exclusive items, like conference tickets, or a round
> of drinks on me.
>
> You should watch these two intro videos:
>
> http://influitive.com/introduction-to-advocate-marketing/
>
> http://influitive.com/learn-more-about-the-advocatehub/
>
> = Donation =
>
> AdvocateHub is usually premium service. However, Influitive has very
> generously offered to donate an account to the project. This is the first
> open source project that Influitive has supported like this, so I am very
> grateful for the opportunity!
>
> AdvocateHub is designed for commercial companies, but I think we can make
> it work for an open source project. Influitive will be monitoring our
> progress, and if things are not working out, we’ll end the experiment. As
> part of this agreement, I will be the account owner and will be responsible
> for its operation. But if you are a committer and you want to help out, I
> can add you as an admin. This is similar to how we run our social media
> accounts.
>
> In return for the support, I am proposing to:
>
> * Promote the use of our AdvocateHub within our community
> * Thank them from our website, wiki, and social media accounts
> * Document our progress with the occasional blog or tweet
>
> Promoting the use of our AdvocateHub will probably take the form of
> mentioning new challenges on the mailing list, blog, Twitter, Google+, etc.
> Obviously, we will want to encourage as many people as possible to get
> involved in the AdvocateHub as possible.
>
> As for documenting our progress, I am thinking that the occasional post
> covering how we’re using the tool, and what sorts of results we’re seeing
> would be appropriate.
>
> I have spoken with the ASF fundraising team already, and there are no
> concerns with these plans at the foundation level.
>
> = Challenges =
>
> AdvocateHub is built around the concept of a challenge, or request for
> help. We can design these however we want, and I will be looking for input
> from the community.
>
> Ideas for easy challenges:
>
> * Retweet an official @CouchDB tweet
> * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> * Publicly mention CouchDB on Twitter, Google+, LinkedIn, your blog, etc
> * Share an official project blog post somewhere
>
> Ideas for medium challenges:
>
> * Watch a featured video
> * Read a featured blog post, or section of the docs
> * Help someone out on the mailing list
> * Answer a CouchDB question on Stack Overflow, Server Fault, etc
> * Talk about CouchDB in response to a Quora question
> * Talk about CouchDB in response to a submission on Hacker News,
> Reddit, etc
> * Comment on an official blog post, or a blog post about CouchDB
> * Post a review on alternativeTo, or other review sites, blog posts, etc
> * Provide an official endorsement or quote from your company about
> CouchDB
> * Complete a survey (I plan to actually make some surveys)
>
> Ideas for hard challenges:
>
> * Create a CouchDB client, library, or tool
> * Produce early/mid/late stage technical content
> * Produce a CouchDB white paper
> * Give a talk or screencast about CouchDB
> * Share a CouchDB success story, testimonial, or case-study
> * Organise a CouchDB meet-up
> * Organise a CouchDB conference
>
> And then, challenges for actually contributing back to CouchDB itself:
>
> * Triage X many JIRA tickets
> * Fix up outstanding issues on a CouchDB pull request
> * Contribute a fix for a JIRA ticket
>
> (This might be a little outside of the scope of AdvocateHub, as this would
> request contribution back to the project itself. Still, it would be
> interesting to see if this would work. As a volunteer organisation,
> volunteer time and attracting contributions is our top priority.)
>
> = Rewards =
>
> Completing challenges gives you points, levels, and badges. I know that
> many people love this kind of system, and are happy to compete with each
> other for points alone. However, we also have the option of allowing
> advocates to exchange points for prizes.
>
> AdvocateHub has an integration with a swag drop-ship merchant. Hopefully, I
> can attract a third-party to help with the bill for this. It would mean
> that by completing challenges, we can reward advocates with t-shirts,
> hoodies, mugs, pins, stickers, and so on!
>
> In addition to swag, we could also offer:
>
> * Individual promotion for you
> * Priority or free tickets to the regular CouchDB Confs
> * Email support or advice from the committers (depends on who
> volunteers time)
> * Private call with one the committers (depends on who volunteers time)
> * Drinks on Noah (though, you’ll have to come find me!)
>
> Promotion could be quite a draw. Imagine a weekly Tweet along the lines of
> “Thanks to @ARandomPerson for supporting CouchDB this week. You should
> follow her on Twitter!” We could also include a mention in our weekly
> CouchDB news. (A blog idea that I have not executed on yet.) As far as I
> can tell, we’d only be able to promote individual accounts, not businesses.
> The ASF has very strict vendor neutrality rules that we must adhere to.
>
> Some other ideas of how we could provide return promotion:
>
> * Mention on our homepage that week
> * Get on our weekly @CouchDB #FollowFriday
> * Entered into a “hall of fame”
> * Get mentioned in our Git commits, issues, or pull requests
>
> The @CouchDB account has close to 10k followers. And our homepage receives
> around 8,500 page views per month at the moment. Those numbers are not to
> be sniffed at!
>
> (This is heavily inspired by Hoodie, who allow people to sponsor the
> project in return for promotion via different channels. I think we can
> borrow some of this.)
>
> The specifics of the reward programme is unimportant at this stage. Like
> the details of the challenges themselves, we can figure this out as we move
> forward.
>
> Thanks,
>
> --
> Noah Slater
> https://twitter.com/nslater
Re: [PROPOSAL] Use Influitive to help with marketing
Posted by Octavian Damiean <od...@linux.com>.
On Sat, Oct 5, 2013 at 7:04 PM, Noah Slater <ns...@apache.org> wrote:
> Hi devs,
>
> I would like to propose that we use Influitive to help us improve our
> marketing efforts.
>
> I fully intend to execute this proposal myself. If you want to volunteer,
> that is great. But if you are not interested in this, that is fine also.
> Nobody has to participate if they do not want to. I am quite happy to run
> it as an experiment myself. If it works we can continue, and if it doesn't,
> we can stop.
>
> Unless anybody objects, I will assume lazy consensus after three days, and
> let Influitive that we have the green light to move forward.
>
> = Introduction =
>
> Influitive AdvocateHub is an advocacy marketing platform.
>
> Think of it like Kickstarter, for marketing. You post a description of what
> you want to accomplish, and then your community members pitch in and help
> to make it happen.
>
> As an open source project, we struggle to market ourselves because we have
> no budget. Where a typical company might take out ads, or pay people to
> write technical content, we rely on volunteer time and word of mouth. But
> this is typically disorganised.
>
> AdvocateHub is a tool that that will allow us to coordinate that volunteer
> time and word of mouth. We can create a steady stream of challenges or
> requests for help and people who are committed to the project can organise
> around these, and help us spread the word of CouchDB.
>
> In return for doing these things, we reward them with prestige and swag.
> And maybe a few other exclusive items, like conference tickets, or a round
> of drinks on me.
>
> You should watch these two intro videos:
>
> http://influitive.com/introduction-to-advocate-marketing/
>
> http://influitive.com/learn-more-about-the-advocatehub/
>
> = Donation =
>
> AdvocateHub is usually premium service. However, Influitive has very
> generously offered to donate an account to the project. This is the first
> open source project that Influitive has supported like this, so I am very
> grateful for the opportunity!
>
> AdvocateHub is designed for commercial companies, but I think we can make
> it work for an open source project. Influitive will be monitoring our
> progress, and if things are not working out, we’ll end the experiment. As
> part of this agreement, I will be the account owner and will be responsible
> for its operation. But if you are a committer and you want to help out, I
> can add you as an admin. This is similar to how we run our social media
> accounts.
>
> In return for the support, I am proposing to:
>
> * Promote the use of our AdvocateHub within our community
> * Thank them from our website, wiki, and social media accounts
> * Document our progress with the occasional blog or tweet
>
> Promoting the use of our AdvocateHub will probably take the form of
> mentioning new challenges on the mailing list, blog, Twitter, Google+, etc.
> Obviously, we will want to encourage as many people as possible to get
> involved in the AdvocateHub as possible.
>
> As for documenting our progress, I am thinking that the occasional post
> covering how we’re using the tool, and what sorts of results we’re seeing
> would be appropriate.
>
> I have spoken with the ASF fundraising team already, and there are no
> concerns with these plans at the foundation level.
>
> = Challenges =
>
> AdvocateHub is built around the concept of a challenge, or request for
> help. We can design these however we want, and I will be looking for input
> from the community.
>
> Ideas for easy challenges:
>
> * Retweet an official @CouchDB tweet
> * Upvote a CouchDB story on Hacker News, Reddit, Google+ etc
> * Publicly mention CouchDB on Twitter, Google+, LinkedIn, your blog,
> etc
> * Share an official project blog post somewhere
>
> Ideas for medium challenges:
>
> * Watch a featured video
> * Read a featured blog post, or section of the docs
> * Help someone out on the mailing list
> * Answer a CouchDB question on Stack Overflow, Server Fault, etc
> * Talk about CouchDB in response to a Quora question
> * Talk about CouchDB in response to a submission on Hacker News,
> Reddit, etc
> * Comment on an official blog post, or a blog post about CouchDB
> * Post a review on alternativeTo, or other review sites, blog posts,
> etc
> * Provide an official endorsement or quote from your company about
> CouchDB
> * Complete a survey (I plan to actually make some surveys)
>
> Ideas for hard challenges:
>
> * Create a CouchDB client, library, or tool
> * Produce early/mid/late stage technical content
> * Produce a CouchDB white paper
> * Give a talk or screencast about CouchDB
> * Share a CouchDB success story, testimonial, or case-study
> * Organise a CouchDB meet-up
> * Organise a CouchDB conference
>
> And then, challenges for actually contributing back to CouchDB itself:
>
> * Triage X many JIRA tickets
> * Fix up outstanding issues on a CouchDB pull request
> * Contribute a fix for a JIRA ticket
>
> (This might be a little outside of the scope of AdvocateHub, as this would
> request contribution back to the project itself. Still, it would be
> interesting to see if this would work. As a volunteer organisation,
> volunteer time and attracting contributions is our top priority.)
>
> = Rewards =
>
> Completing challenges gives you points, levels, and badges. I know that
> many people love this kind of system, and are happy to compete with each
> other for points alone. However, we also have the option of allowing
> advocates to exchange points for prizes.
>
> AdvocateHub has an integration with a swag drop-ship merchant. Hopefully, I
> can attract a third-party to help with the bill for this. It would mean
> that by completing challenges, we can reward advocates with t-shirts,
> hoodies, mugs, pins, stickers, and so on!
>
> In addition to swag, we could also offer:
>
> * Individual promotion for you
> * Priority or free tickets to the regular CouchDB Confs
> * Email support or advice from the committers (depends on who
> volunteers time)
> * Private call with one the committers (depends on who volunteers time)
> * Drinks on Noah (though, you’ll have to come find me!)
>
> Promotion could be quite a draw. Imagine a weekly Tweet along the lines of
> “Thanks to @ARandomPerson for supporting CouchDB this week. You should
> follow her on Twitter!” We could also include a mention in our weekly
> CouchDB news. (A blog idea that I have not executed on yet.) As far as I
> can tell, we’d only be able to promote individual accounts, not businesses.
> The ASF has very strict vendor neutrality rules that we must adhere to.
>
> Some other ideas of how we could provide return promotion:
>
> * Mention on our homepage that week
> * Get on our weekly @CouchDB #FollowFriday
> * Entered into a “hall of fame”
> * Get mentioned in our Git commits, issues, or pull requests
>
> The @CouchDB account has close to 10k followers. And our homepage receives
> around 8,500 page views per month at the moment. Those numbers are not to
> be sniffed at!
>
> (This is heavily inspired by Hoodie, who allow people to sponsor the
> project in return for promotion via different channels. I think we can
> borrow some of this.)
>
> The specifics of the reward programme is unimportant at this stage. Like
> the details of the challenges themselves, we can figure this out as we move
> forward.
>
> Thanks,
>
> --
> Noah Slater
> https://twitter.com/nslater
>
I like the idea and think that it is definitely worth a try! If you need
any help with this, just let me know.
+1 on this.
--
Octavian Damiean
GitHub: https://github.com/mainerror