Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

Introduce aggregation story w/ npm announcement(s) #1045

Closed
15 of 18 tasks
chadwhitacre opened this issue Apr 27, 2017 · 24 comments
Closed
15 of 18 tasks

Introduce aggregation story w/ npm announcement(s) #1045

chadwhitacre opened this issue Apr 27, 2017 · 24 comments

Comments

@chadwhitacre
Copy link
Contributor

chadwhitacre commented Apr 27, 2017

Follows on gratipay/gratipay.com#4427. How are we going to promote this new feature?

@chadwhitacre
Copy link
Contributor Author

The most immediate marketing message here is that it is now much easier for npm packages to apply to join Gratipay as projects.

I'm inclined to use this opportunity to start telling our story around aggregation and the three-sided marketplace. On the one hand that telegraphs our strategy to our fellow travelers, but on the other hand with this release we'll be a step ahead on this path, and I think we want to start building awareness
around this story so that we can see if there's any resonance in the marketplace. I think we have a unique take on the problem and that we're building something cool, but at this point we are very much in search of product-market fit.

Here's a blog post stub.

@chadwhitacre chadwhitacre changed the title Promote npm integration Introduce aggregation story w/ npm announcement Apr 27, 2017
@chadwhitacre
Copy link
Contributor Author

Bumping this up a level in scope from project to epic.

@chadwhitacre
Copy link
Contributor Author

@chadwhitacre
Copy link
Contributor Author

We'll need some kind of discovery mechanism (search will probably be easier than bulk, though both would be nice) before we can go live with that.

@chadwhitacre
Copy link
Contributor Author

Search PR in gratipay/gratipay.com#4458.

@chadwhitacre
Copy link
Contributor Author

I did some outreach on Slack/IRC and have also posted to HN.

I guess let's track uptake here?

gratipay::DATABASE=> select count(*) from teams_to_packages;
┌───────┐
│ count │
├───────┤
│     5 │
└───────┘
(1 row)

@chadwhitacre
Copy link
Contributor Author

Leaving open to retry on HN.

@chadwhitacre
Copy link
Contributor Author

@jdorfman to submit to Product Hunt once we have a landing page.

@rohitpaulk
Copy link
Contributor

gratipay::DATABASE=> select count(*) from teams_to_packages;
 count
-------
     9
(1 row)

@chadwhitacre
Copy link
Contributor Author

Our second order of magnitude! 💃

gratipay::DATABASE=> select count(*) from teams_to_packages;
┌───────┐
│ count │
├───────┤
│    10 │
└───────┘
(1 row)

And the person that put us over the top is the founder of npm! 😱 🙀 😍 😻

@chadwhitacre
Copy link
Contributor Author

Adding https://www.reddit.com/r/opensource/ alongside HN and Product Hunt as places to go for our next push.

@chadwhitacre
Copy link
Contributor Author

chadwhitacre commented May 25, 2017

We're flat.

gratipay::DATABASE=> select count(distinct(owner)) as nowners, count(team_id) as npackages from teams_to_packages tp join teams t on tp.team_id = t.id;
┌─────────┬───────────┐
│ nowners │ npackages │
├─────────┼───────────┤
│       7 │        10 │
└─────────┴───────────┘
(1 row)

@chadwhitacre
Copy link
Contributor Author

slack

@jdorfman
Copy link

@whit537 landing page for reddit too.

@chadwhitacre
Copy link
Contributor Author

landing page for reddit too.

Separate or same as for Product Hunt?

@chadwhitacre
Copy link
Contributor Author

chadwhitacre commented May 31, 2017

I've started making progress on gratipay/gratipay.com#4488. How about we aim to deploy that next week, and then make an HN/PH/Reddit push starting on Tuesday, June 13th?

cc: @jdorfman @Jaimeyann @clone1018 @rohitpaulk @mattbk et al.

@chadwhitacre
Copy link
Contributor Author

Testing the Product Hunt waters ...


screen shot 2017-06-02 at 11 13 07 am


screen shot 2017-06-02 at 11 17 57 am


screen shot 2017-06-02 at 11 18 41 am

@chadwhitacre
Copy link
Contributor Author

gratipay::DATABASE=> select count(distinct(owner)) as nowners, count(team_id) as npackages from teams_to_packages tp join teams t on tp.team_id = t.id;
┌─────────┬───────────┐
│ nowners │ npackages │
├─────────┼───────────┤
│       9 │        14 │
└─────────┴───────────┘
(1 row)

@chadwhitacre
Copy link
Contributor Author

I think we should not push to HN/PH/Reddit until we clean things up a lot more. Marketing on Twitter and IRC/Slack/email should be enough to start getting some traffic. The thing about HN/PH is that it seems more one-shot. I think we wait until things are tighter and we're more like beta quality because right now we're more like alpha quality.

@chadwhitacre
Copy link
Contributor Author

chadwhitacre commented Jun 15, 2017

I've started writing a post to announce package.json discovery.

https://gratipay.news/pay-for-your-package-json-cb07341445ca

Here's the script I used to compute the 48% with 2+ and 7% with 10+ figures (based on a dump of the emails field from the packages table):

# -*- coding: utf-8 -*-
from __future__ import absolute_import, division, print_function, unicode_literals

import csv
from collections import defaultdict

counts = defaultdict(int)

for rec in csv.reader(open('emails.csv')):
    emails = rec[0].decode('utf8')[1:-1].split(',')
    for email in emails:
        counts[email] += 1

nmany = nmulti = 0
for email in counts:
    if counts[email] > 10:
        nmany += 1
    if counts[email] > 1:
        nmulti += 1
total = len(counts)

print(nmany , total, nmany / total)
print(nmulti, total, nmulti / total)

@chadwhitacre chadwhitacre changed the title Introduce aggregation story w/ npm announcement Introduce aggregation story w/ npm announcement(s) Jun 16, 2017
@chadwhitacre
Copy link
Contributor Author

gratipay/gratipay.com#4507 is in! Last call for input on the "Pay for your package.json" announcement.

@chadwhitacre
Copy link
Contributor Author

+2 from @jdorfman @mattbk in slack.

@chadwhitacre
Copy link
Contributor Author

https://gratipay.news/pay-for-your-package-json-cb07341445ca
https://twitter.com/Gratipay/status/875755128866971650

@chadwhitacre
Copy link
Contributor Author

I'm going to go ahead and close this out since the first pieces are out. There will be ongoing additional marketing tasks that can have their own tickets.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants