Core Radar 81

[gratipay-bot]

← Core Radar 80

---

Docs

http://inside.gratipay.com/howto/sweep-the-radar

Org Chart

Teams

Teams besides core are folded in from separate radars that didn't have enough vitality to remain separate.

Core

The mission of the core team is to steer Gratipay as a whole in pursuit of our overall mission: to cultivate an economy of gratitude, generosity, and love.

Scope

This radar implicitly covers everything in the Gratipay organization that is not explicitly covered by another radar. It explicitly covers:

• Mission and Brand
• Strategy
• Governance
• repos:
  • https://github.com/gratipay/inside.gratipay.com
  • https://github.com/gratipay/bot
  • https://github.com/gratipay/access-dashboard
  • https://github.com/gratipay/gratipay-queue-dashboard

Marketing

The mission of the marketing team is to communicate with the market, listening for problems relevant to our organizational mission, and sharing our solutions.

Scope

• https://gratipay.news/
• social media:
  • https://twitter.com/Gratipay
  • https://www.facebook.com/Gratipay
• Events
• repos:
  • https://github.com/gratipay/guide
  • https://github.com/gratipay/gratipay-or-bountysource.guide
  • https://github.com/gratipay/blog.gittip.com

Upcoming

• October 26-27—All Things Open conference (go to All Things Open #757)

Support

The mission of the support team is to help people use our products.

Scope

• [email protected]
• the Support and L2 Support queues in Freshdesk
• https://github.com/gratipay/team-review

Product

The mission of the product team is to design and implement solutions to the problems identified by the marketing team.

Scope

• https://github.com/gratipay/gratipay.com
  • translation (docs)
• https://github.com/gratipay/grtp.co
• https://github.com/gratipay/gratipay-everywhere
• https://github.com/gratipay/gratipay-badge

Roadmap

1. Finish cleaning up from the Gratipocalypse:
   1. Decouple (IG)
   2. Finish Team Basics
   3. Pivot
2. Knock pay-what-you-want out of the park:
   1. Make Widgets 2.0
   2. Tighten Onboarding Flow
   3. Solve Corporate Sponsorship of Open-Source
3. Knock take-what-you-want out of the park:
   1. Implement an AML Program
   2. Expand Take-What-You-Want Beyond Gratipay

Color code:

• red—external forces that we're under
• green—product development tasks

Accounting

The mission of the accounting team is to account for the money we move.

Scope

• @gratipay/finances
• the https://github.com/gratipay/finances repo
• the statements directory in the https://github.com/gratipay/logs repo
• the [email protected] email address

Priorities

• collect historical statement data (More statements finances#26)
• settle on tooling (convert to GnuCash finances#22)
• catch up on books (catch up on books finances#3)
• resolve escrow imprecision (Radar 31 #389 (comment))

Tech

The mission of the tech team is to support the product team in solving problems in the market.

Scope

• dev
• ops
• hosting
  • Heroku
  • Digital Ocean
  • AWS
• monitoring
  • Sentry
  • PagerDuty
  • UptimeRobot
  • Librato
• Payday
• https://github.com/gratipay/postgres.py
• https://github.com/gratipay/gip.rocks
• https://github.com/gratipay/honcho
• https://github.com/gratipay/environment.py

Priorites

• stop using immutable ids as primary key (use id as primary key instead of username gratipay.com#835)
• other embarrassments

[chadwhitacre]

Inbox 2, H1GH 1, Pipedrive 0, L2 Support 0, Vendors, etc. 0.

[chadwhitacre]

My big goal right now is to get the Fund Open Source thing done. Based on my conversation at #844 (comment), I think that that's going to be of interest to CTOs, and it's the CTOs at enlightened organizations that we want to connect with.

[chadwhitacre]

I want to be able to demo that at ATO next week (#757), especially in my lightning talk, and then write up a blog post to promote on Twitter and in emails under #844.

[chadwhitacre]

Our friends over at Internet of Ownership are working on forming a cooperative to buy Twitter (I kicked off the Loomio group but have since been lurking). They launched a PR campaign today to see if they can build some momentum around the idea. Signatures, RTs and upvotes appreciated! :-)

http://wearetwitter.global/
https://twitter.com/hashtag/WeAreTwitter
https://news.ycombinator.com/item?id=12747027

[chadwhitacre]

Made some tweets about it from the Gratipay account:

https://twitter.com/Gratipay/status/788859008949944321
https://twitter.com/internetowners/status/788824485231144960

[chadwhitacre]

Okay! Where are we? My head is spinning from all the activity on gratipay/gratipay.com#4135 and gratipay/gdr.rocks#2. Phew! What can we realistically hope to get done before my lightning talk at All Things Open next week (#757)?

I think the "automatic dependency bundles" idea in gratipay/gratipay.com#4135 is really strong, but that depends on associating dependencies with Teams (Projects), which is not uninteresting in itself. I want to have something real and new and interesting to announce from the stage at ATO. New news, as it were. "Today, you can use Gratipay to give to any package on npm" is, I think, pretty strong. Is it strong enough to drop the rest for now, and focus just on that ahead of next week?

[mattbk]

On a more prosaic front, could use a review on gratipay/gratipay.com#4146 if anyone gets a chance.

!m @whit537 for all the work!

[chadwhitacre]

From gratipay/gratipay.com#4135 (comment):

In terms of next week, librariesio/libraries.io#14 prevents us from using Libraries.io for the /on/*pm/foo/ pages, so I think we should limit ourselves to just /on/npm/foo/ and use the npm API directly. We can still use Libraries.io for search ("Powered by") on /on/npm/. Once librariesio/libraries.io#14 is done we can expand to other package managers.

[chadwhitacre]

Here's a working draft for my #757 lightning talk. Subscribe to https://github.com/whit537/openorg/issues/6 if you want to follow progress.

[chadwhitacre]

Here's the bit relevant to what we would need to get done under gratipay/gratipay.com#4148:

Today, I’m happy to announce that Gratipay has taken a small step forward. Starting today, all packages on the npm package registry for JavaScript automatically have a listing on Gratipay. If you are the owner of a package, it’s a simple process to start accepting payments on Gratipay, and if you depend on the npm ecosystem, you can search on Gratipay today for any npm package. This is a small step in the right direction, and we look forward to announcing even more soon.

[chadwhitacre]

I just deployed, to get gratipay/gratipay.com#4146 out there.

[chadwhitacre]

Ah, 1987. The year I first realized that time is linear, that each summer is in fact different than the one before. :)

[chadwhitacre]

2016 in 2016? 2017 in 2017, more likely. ;-)

[mattbk]

L1 Support 0.

[chadwhitacre]

Inbox 1, H1GH 2, L2 Support 0, Vendors, etc. 0, Pipedrive 0.