This repository has been archived by the owner. It is now read-only.

turn the ship #3399

Closed
chadwhitacre opened this Issue May 11, 2015 · 110 comments

Comments

Projects
None yet
9 participants
@chadwhitacre
Contributor

chadwhitacre commented May 11, 2015

Last week, Gratipay stopped processing payments because of legal concerns with our old terms of service that became apparent after our processor, Balanced, announced that they're going out of business, and Stripe wouldn't take us. So in addition to migrating our processing infrastructure (#3377), we also have to change our business model at the same time. No 😓, right? :)

We hashed out our new business model on gratipay/inside.gratipay.com#180 and gratipay/inside.gratipay.com#192. This ticket is to track implementation. See also the Pivot milestone.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@chadwhitacre chadwhitacre added this to the Pivot milestone May 11, 2015

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

I'm stuck thinking about the relationship between individuals, groups, and projects. I think #3337 is the cleanest way to go:

Users optionally have Projects.
Projects optionally have Payroll.

Projects would be what you give money to.

But right now Users are what you give money to. We don't want to drop existing funding streams if we can at all help it. We want to give Users a way to migrate to a Project. Forcing migration before we process payments is okay since we're requiring acceptance of our new terms anyway.

Contributor

chadwhitacre commented May 11, 2015

I'm stuck thinking about the relationship between individuals, groups, and projects. I think #3337 is the cleanest way to go:

Users optionally have Projects.
Projects optionally have Payroll.

Projects would be what you give money to.

But right now Users are what you give money to. We don't want to drop existing funding streams if we can at all help it. We want to give Users a way to migrate to a Project. Forcing migration before we process payments is okay since we're requiring acceptance of our new terms anyway.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

I'm not sure how to pull off this pivot without #3337. That's a fair chunk of work.

Contributor

chadwhitacre commented May 11, 2015

I'm not sure how to pull off this pivot without #3337. That's a fair chunk of work.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

Let's think about Participants (Users above) and Teams (Projects above).

Currently Teams are a kind of Participant (those with plural number and > 0 takes), but I think we should promote Teams to a first-class citizen with a new teams table.

A Team is a group of people (some of whom may even be Participants) working together to deliver a given product or service.

Teams have Members (Participants of ours who are part of the Team). Some Members are Owners.

(Note that Participants can still be singular or plural.)

Right now, Tips attach to Participants. How do we migrate Tips from Participants to Teams? We basically need Participants to create a new Team, to which we will reattach their Tips.

Since giving to Participants has been ambiguous in regard to products or services delivered, migrating giving to a single-purpose Team will be a judgement call for our users. If I have 100 supporters, and 60 would say they were giving to me because of one product or service I provide, and 30 because of another, and 10 just because they love me, then how should I migrate? I don't even know who my supporters are, so it's not like I can manually review and make assignments ("Oh, this person is a Fizzbuzz user, that's probably why they've been supporting me. Let's move their payment to the new Fizzbuzz Team"). No: I have to guess at the 60-supporter product/service, and migrate all of my giving to a new Team dedicated to that. Then I can make a second Team for the 30-supporter product/service.

Contributor

chadwhitacre commented May 11, 2015

Let's think about Participants (Users above) and Teams (Projects above).

Currently Teams are a kind of Participant (those with plural number and > 0 takes), but I think we should promote Teams to a first-class citizen with a new teams table.

A Team is a group of people (some of whom may even be Participants) working together to deliver a given product or service.

Teams have Members (Participants of ours who are part of the Team). Some Members are Owners.

(Note that Participants can still be singular or plural.)

Right now, Tips attach to Participants. How do we migrate Tips from Participants to Teams? We basically need Participants to create a new Team, to which we will reattach their Tips.

Since giving to Participants has been ambiguous in regard to products or services delivered, migrating giving to a single-purpose Team will be a judgement call for our users. If I have 100 supporters, and 60 would say they were giving to me because of one product or service I provide, and 30 because of another, and 10 just because they love me, then how should I migrate? I don't even know who my supporters are, so it's not like I can manually review and make assignments ("Oh, this person is a Fizzbuzz user, that's probably why they've been supporting me. Let's move their payment to the new Fizzbuzz Team"). No: I have to guess at the 60-supporter product/service, and migrate all of my giving to a new Team dedicated to that. Then I can make a second Team for the 30-supporter product/service.

@chadwhitacre chadwhitacre referenced this issue May 11, 2015

Closed

implement projects #3337

0 of 4 tasks complete
@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

Can a Team give to another Team?

Contributor

chadwhitacre commented May 11, 2015

Can a Team give to another Team?

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

Can a Team give to another Team?

I think not, but I think the Owner of a Team can give to other Teams. Let's say that Exchange Routes still attach to Participants. The Owner of a Team is a Participant, and that's where the leftover money drains after Payroll, so we still have the chance to offset their giving with their receiving in a given cycle.

Contributor

chadwhitacre commented May 11, 2015

Can a Team give to another Team?

I think not, but I think the Owner of a Team can give to other Teams. Let's say that Exchange Routes still attach to Participants. The Owner of a Team is a Participant, and that's where the leftover money drains after Payroll, so we still have the chance to offset their giving with their receiving in a given cycle.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

The approach I'm considering is to make new tables teams, subscriptions, payroll, payments that are parallel to participants, tips, takes, transfers. We no longer write to the old tables, but they're available to use for migrating. Migrating happens when a Participant takes the initiative; we're not migrating all tips at once.

Contributor

chadwhitacre commented May 11, 2015

The approach I'm considering is to make new tables teams, subscriptions, payroll, payments that are parallel to participants, tips, takes, transfers. We no longer write to the old tables, but they're available to use for migrating. Migrating happens when a Participant takes the initiative; we're not migrating all tips at once.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

Where do we put Teams in our URL structure? And in our IA, for that matter?

Do we demote Participants? https://gratipay.com/whit537https://gratipay.com/~whit537. Does that redirect? Almost certainly, or we'd break lots of inbound links.

But then does https://gratipay.com/~Gratipay redirect back to https://gratipay.com/Gratipay? Do we have a single namespace for Participant and Team slugs, even if we differentiate them in the URL? Probably. It doesn't seem right to allow someone to register https://gratipay.com/~Gratipay. On the other hand, we're saying that we want an Owner Participant for a Team, so I guess we should allow ~Gratipay to be the Owner of Gratipay. Right?

Contributor

chadwhitacre commented May 11, 2015

Where do we put Teams in our URL structure? And in our IA, for that matter?

Do we demote Participants? https://gratipay.com/whit537https://gratipay.com/~whit537. Does that redirect? Almost certainly, or we'd break lots of inbound links.

But then does https://gratipay.com/~Gratipay redirect back to https://gratipay.com/Gratipay? Do we have a single namespace for Participant and Team slugs, even if we differentiate them in the URL? Probably. It doesn't seem right to allow someone to register https://gratipay.com/~Gratipay. On the other hand, we're saying that we want an Owner Participant for a Team, so I guess we should allow ~Gratipay to be the Owner of Gratipay. Right?

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

In terms of IA, I think we're looking at the following changes as the absolute minimum to pull this off this week:

  • /$USERNAME//~$USERNAME/
  • Add $TEAM at /$TEAM/, with a Profile at top level.
  • /$USERNAME/members//$TEAM/payroll/.
Contributor

chadwhitacre commented May 11, 2015

In terms of IA, I think we're looking at the following changes as the absolute minimum to pull this off this week:

  • /$USERNAME//~$USERNAME/
  • Add $TEAM at /$TEAM/, with a Profile at top level.
  • /$USERNAME/members//$TEAM/payroll/.
@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

How do Participants register new Teams?

Contributor

chadwhitacre commented May 11, 2015

How do Participants register new Teams?

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

How about adding /new for that? Then we add /dashboard/teams for the new Teams review queue.

Contributor

chadwhitacre commented May 11, 2015

How about adding /new for that? Then we add /dashboard/teams for the new Teams review queue.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

The first time a Participant with Tips creates a new Team, we should migrate all their Tips to Subscriptions for the Team (with prompting and confirmation, of course).

Contributor

chadwhitacre commented May 11, 2015

The first time a Participant with Tips creates a new Team, we should migrate all their Tips to Subscriptions for the Team (with prompting and confirmation, of course).

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor

This feels good. I like how this is coming together, it's an evolution of Teams, a pretty natural step.

Contributor

chadwhitacre commented May 11, 2015

This feels good. I like how this is coming together, it's an evolution of Teams, a pretty natural step.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 11, 2015

Contributor
  • replace UI over tips & takes with UI over subscriptions & payroll (#3400)
  • implement UI for making/migrating to a new team
  • revise payday to use subscriptions & payroll instead of tips & takes
Contributor

chadwhitacre commented May 11, 2015

  • replace UI over tips & takes with UI over subscriptions & payroll (#3400)
  • implement UI for making/migrating to a new team
  • revise payday to use subscriptions & payroll instead of tips & takes
@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 12, 2015

Contributor
  • unroll the interaction of number w/ takes
  • text fields on teams want to be i18n'd like statement
  • implement is_approved
  • implement closing a team
  • sort out interaction with take_over
  • don't forget about the API, especially tips.json
  • should be able to search over teams
  • don't forget about db self-checks
  • don't forget OG headers
  • don't forget about fake_data
Contributor

chadwhitacre commented May 12, 2015

  • unroll the interaction of number w/ takes
  • text fields on teams want to be i18n'd like statement
  • implement is_approved
  • implement closing a team
  • sort out interaction with take_over
  • don't forget about the API, especially tips.json
  • should be able to search over teams
  • don't forget about db self-checks
  • don't forget OG headers
  • don't forget about fake_data
@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 12, 2015

Contributor

After bashing around on #3400 all day yesterday, I'm starting to get a better idea of how to approach this. I've made three clean PRs:

  • #3402 makes room in the URL structure for Teams
  • #3403 cuts out pledging
  • #3405 cuts out goals

We should be able to clean up tip limits based on number as well. Is there any other code we can simply cut out?

Beyond that, here's a review of work based on looking at a profile (hard, medium, easy):

  • Dashboard - Quarter-baked as it is. Copy is all wrong but nothing besides that.
  • Profile - Teams section will need to work with new Teams.
  • Members - This will be moved entirely to Teams. I'm not sure how anonymous_receiving interacts with this but that's probably out of scope for this ticket.
  • Receiving - Still want this, but it should only show payments from teams under the new system. It should also continue to respect anonymous_receiving.
  • Giving - Still want this, but it should only show payments to teams under the new system. It should also continue to respect anonymous_giving.
  • History - This should show history under both the old and new systems.
  • Widgets - Widgets are going to have to change somehow as part of this transition. How?
  • Identity - We almost certainly want identity information for any Team Owner. Right now we store this info at Balanced (they verify it with some API we don't know about). Do we need to start storing identity info locally as part of this ticket, even if we don't programmatically verify it yet?
  • Settings - I think this is pretty much fine. Notifications looks goofier than every without the "notify patrons" option, but I'm not going to worry about it here.
  • Events - No references to other tables here, so I think we're good.
Contributor

chadwhitacre commented May 12, 2015

After bashing around on #3400 all day yesterday, I'm starting to get a better idea of how to approach this. I've made three clean PRs:

  • #3402 makes room in the URL structure for Teams
  • #3403 cuts out pledging
  • #3405 cuts out goals

We should be able to clean up tip limits based on number as well. Is there any other code we can simply cut out?

Beyond that, here's a review of work based on looking at a profile (hard, medium, easy):

  • Dashboard - Quarter-baked as it is. Copy is all wrong but nothing besides that.
  • Profile - Teams section will need to work with new Teams.
  • Members - This will be moved entirely to Teams. I'm not sure how anonymous_receiving interacts with this but that's probably out of scope for this ticket.
  • Receiving - Still want this, but it should only show payments from teams under the new system. It should also continue to respect anonymous_receiving.
  • Giving - Still want this, but it should only show payments to teams under the new system. It should also continue to respect anonymous_giving.
  • History - This should show history under both the old and new systems.
  • Widgets - Widgets are going to have to change somehow as part of this transition. How?
  • Identity - We almost certainly want identity information for any Team Owner. Right now we store this info at Balanced (they verify it with some API we don't know about). Do we need to start storing identity info locally as part of this ticket, even if we don't programmatically verify it yet?
  • Settings - I think this is pretty much fine. Notifications looks goofier than every without the "notify patrons" option, but I'm not going to worry about it here.
  • Events - No references to other tables here, so I think we're good.
@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 12, 2015

Contributor

What should we do with tips.json? I think we should make a new API that uses team id instead, and just let tips.json go 404. How are we supposed to interpret tips to usernames from the old tipping system under the new system?

Contributor

chadwhitacre commented May 12, 2015

What should we do with tips.json? I think we should make a new API that uses team id instead, and just let tips.json go 404. How are we supposed to interpret tips to usernames from the old tipping system under the new system?

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 12, 2015

Contributor

In which case, I think I'll rip out tips.json for this week, and reticket bringing back something similar.

Contributor

chadwhitacre commented May 12, 2015

In which case, I think I'll rip out tips.json for this week, and reticket bringing back something similar.

@chadwhitacre chadwhitacre changed the title from execute the pivot to turn the ship May 12, 2015

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 12, 2015

Contributor

URL structure

  1. move /username/ to /~username/ (#3402)

Reduce Surface Area

  1. remove pledging entirely (#3403)
  2. turn off giving in the UI/JSON (#3406)
  3. remove goal (#3405)
  4. turn off taking in the UI/JSON (#3407)

Rewrite Payday

  1. make new subscriptions, payroll, and payments tables
  2. promote _mixin_team to a Team class
  3. rewrite payday to use new teams (#3414)

Wire Up Teams

  1. application/approval/migration for teams (#3412)
  2. set payment to team
  3. set take from team
  4. rewrite History
Contributor

chadwhitacre commented May 12, 2015

URL structure

  1. move /username/ to /~username/ (#3402)

Reduce Surface Area

  1. remove pledging entirely (#3403)
  2. turn off giving in the UI/JSON (#3406)
  3. remove goal (#3405)
  4. turn off taking in the UI/JSON (#3407)

Rewrite Payday

  1. make new subscriptions, payroll, and payments tables
  2. promote _mixin_team to a Team class
  3. rewrite payday to use new teams (#3414)

Wire Up Teams

  1. application/approval/migration for teams (#3412)
  2. set payment to team
  3. set take from team
  4. rewrite History
@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 12, 2015

Contributor

I have the feeling that I'm going to be doing most of this work myself. I'm not even sure we'll be able to wait for proper review before merging and deploying. I'm at least going to keep using PRs, even if I end up merging them myself.

Contributor

chadwhitacre commented May 12, 2015

I have the feeling that I'm going to be doing most of this work myself. I'm not even sure we'll be able to wait for proper review before merging and deploying. I'm at least going to keep using PRs, even if I end up merging them myself.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 12, 2015

Contributor

I went ahead and merged/deployed #3402, to get the ball rolling.

Contributor

chadwhitacre commented May 12, 2015

I went ahead and merged/deployed #3402, to get the ball rolling.

@chadwhitacre chadwhitacre referenced this issue May 12, 2015

Merged

kill goal #3405

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre May 12, 2015

Contributor

From #3406, here's a census of the parts of the user experience that touch the tips table:

  • closing, merging, and archiving accounts
  • updating team takes (#3407)
  • adding/updating exchange routes
  • setting tips (#3406)
  • the pricing, stats, receiving, and giving pages
  • tips.json (#3406)
  • the old button widget (#3406)

Here's the details:

  _check_tips
  _check_orphans_no_tips

  Participant.update_number
  Participant.clear_tips_giving - close
  Participant.clear_tips_receiving - close
  Participant.update_giving - team takes, exchange routes, setting tips, take over
  Participant.update_receiving - team takes, setting tips, take over
  Participant.set_tip_to - {tip,tips}.json, close, throughout the test suite
  Participant.get_tip_to - tip widget, old button widget, pricing
  Participant.get_tip_distribution - stats, receiving page
  Participant.get_giving_for_profile - giving page, tips.json, close
  Participant.get_tips_receiving - unused!
  Participant.get_current_tips - tips.json
  Participant.take_over - take over
  Participant.final_check - archive, close

  www/about/stats.spt
  www/about/tip-distribution.json.spt
Contributor

chadwhitacre commented May 12, 2015

From #3406, here's a census of the parts of the user experience that touch the tips table:

  • closing, merging, and archiving accounts
  • updating team takes (#3407)
  • adding/updating exchange routes
  • setting tips (#3406)
  • the pricing, stats, receiving, and giving pages
  • tips.json (#3406)
  • the old button widget (#3406)

Here's the details:

  _check_tips
  _check_orphans_no_tips

  Participant.update_number
  Participant.clear_tips_giving - close
  Participant.clear_tips_receiving - close
  Participant.update_giving - team takes, exchange routes, setting tips, take over
  Participant.update_receiving - team takes, setting tips, take over
  Participant.set_tip_to - {tip,tips}.json, close, throughout the test suite
  Participant.get_tip_to - tip widget, old button widget, pricing
  Participant.get_tip_distribution - stats, receiving page
  Participant.get_giving_for_profile - giving page, tips.json, close
  Participant.get_tips_receiving - unused!
  Participant.get_current_tips - tips.json
  Participant.take_over - take over
  Participant.final_check - archive, close

  www/about/stats.spt
  www/about/tip-distribution.json.spt
@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Aug 17, 2015

Contributor

Alright, let's bring this in for a landing. We have 24 tickets still open on the Pivot milestone, and this is the main ticket.

Contributor

chadwhitacre commented Aug 17, 2015

Alright, let's bring this in for a landing. We have 24 tickets still open on the Pivot milestone, and this is the main ticket.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Aug 18, 2015

Contributor

I've been looking at site copy (#3398) today, specifically the About pages. I guess I was feeling overwhelmed and that seemed like an easy place to start that will certainly provide value when we drive traffic for #3539. It also solidifies the work we did to standardize nomenclature, and queues us up to revise the Team application in #3677.

Contributor

chadwhitacre commented Aug 18, 2015

I've been looking at site copy (#3398) today, specifically the About pages. I guess I was feeling overwhelmed and that seemed like an easy place to start that will certainly provide value when we drive traffic for #3539. It also solidifies the work we did to standardize nomenclature, and queues us up to revise the Team application in #3677.

This was referenced Aug 24, 2015

@webmaven

This comment has been minimized.

Show comment
Hide comment
@webmaven

webmaven Nov 23, 2015

Contributor

@whit537:

Echoing @ehmatthes comments at gratipay/inside.gratipay.com#251 (comment), I'm using the term "open company" loosely. A non-profit can definitely be "an open company in gratipay's eyes."

So, perhaps 'open organizations' could be an improvement? This would be inclusive of companies, non-profits, co-ops, and (potentially) eventually other more exotic arrangements (such as decentralized autonomous organizations). We can link the term to the glossary, although a tooltip would perhaps be even better.

Contributor

webmaven commented Nov 23, 2015

@whit537:

Echoing @ehmatthes comments at gratipay/inside.gratipay.com#251 (comment), I'm using the term "open company" loosely. A non-profit can definitely be "an open company in gratipay's eyes."

So, perhaps 'open organizations' could be an improvement? This would be inclusive of companies, non-profits, co-ops, and (potentially) eventually other more exotic arrangements (such as decentralized autonomous organizations). We can link the term to the glossary, although a tooltip would perhaps be even better.

@webmaven

This comment has been minimized.

Show comment
Hide comment
@webmaven

webmaven Nov 23, 2015

Contributor

It would also likely be helpful if the gratipay and inside.gratipay.com repos were to have 2.1 milestones.

Contributor

webmaven commented Nov 23, 2015

It would also likely be helpful if the gratipay and inside.gratipay.com repos were to have 2.1 milestones.

@tshepang

This comment has been minimized.

Show comment
Hide comment
@tshepang

tshepang Nov 24, 2015

Contributor

👍 @webmaven for "open organisations"

Contributor

tshepang commented Nov 24, 2015

👍 @webmaven for "open organisations"

@chadwhitacre chadwhitacre referenced this issue Nov 25, 2015

Closed

Radar 34 #419

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Nov 25, 2015

Contributor

+1 for "open organizations"

Contributor

chadwhitacre commented Nov 25, 2015

+1 for "open organizations"

@mitar

This comment has been minimized.

Show comment
Hide comment
@mitar

mitar Jan 17, 2016

Hm, but how does PayPal handle the fact that they keep money in their accounts and not immediately transfer the money? Are they incorporated as a bank?

mitar commented Jan 17, 2016

Hm, but how does PayPal handle the fact that they keep money in their accounts and not immediately transfer the money? Are they incorporated as a bank?

@rohitpaulk

This comment has been minimized.

Show comment
Hide comment
@rohitpaulk

rohitpaulk Jan 17, 2016

Contributor

Paypal is registered as an MSB (money services business), yes. https://www.paypal.com/webapps/mpp/licenses

Contributor

rohitpaulk commented Jan 17, 2016

Paypal is registered as an MSB (money services business), yes. https://www.paypal.com/webapps/mpp/licenses

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Jan 18, 2016

Contributor

Still, PayPal's licensing applies to the transfer of money, not to the storage of it. As best I can tell, they avoid regulation as a bank in the U.S. largely by asserting that they're not a bank. :-)

We've talked about this elsewhere, I believe. I'm not sure this is the best place for this convo.

Contributor

chadwhitacre commented Jan 18, 2016

Still, PayPal's licensing applies to the transfer of money, not to the storage of it. As best I can tell, they avoid regulation as a bank in the U.S. largely by asserting that they're not a bank. :-)

We've talked about this elsewhere, I believe. I'm not sure this is the best place for this convo.

@chadwhitacre chadwhitacre referenced this issue Feb 9, 2016

Closed

Radar 45 #494

@chadwhitacre chadwhitacre referenced this issue May 6, 2016

Closed

Bring back takes for Team Gratipay #3994

34 of 34 tasks complete
@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Aug 29, 2016

Contributor

So, perhaps 'open organizations' could be an improvement?

You anticipated Jim Whitehurst, @webmaven. ;-)

https://www.redhat.com/en/explore/the-open-organization-book

cf. gratipay/inside.gratipay.com#672

Contributor

chadwhitacre commented Aug 29, 2016

So, perhaps 'open organizations' could be an improvement?

You anticipated Jim Whitehurst, @webmaven. ;-)

https://www.redhat.com/en/explore/the-open-organization-book

cf. gratipay/inside.gratipay.com#672

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Aug 29, 2016

Contributor

We have 24 tickets still open on the Pivot milestone, and this is the main ticket.

We're now down to eight!

Contributor

chadwhitacre commented Aug 29, 2016

We have 24 tickets still open on the Pivot milestone, and this is the main ticket.

We're now down to eight!

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Jan 4, 2017

Contributor

Well, we did pivot another degree, but towards projects instead of open companies:

We still believe in open work, but our new goal is to onboard a million projects with 10% offering open work, instead of ten thousand with 100% offering open work.

Now the Pivot is down to one last ticket: this one. Time to close it out!

Congratulations, everyone! We have successfully turned the ship! 💃 🌻

Contributor

chadwhitacre commented Jan 4, 2017

Well, we did pivot another degree, but towards projects instead of open companies:

We still believe in open work, but our new goal is to onboard a million projects with 10% offering open work, instead of ten thousand with 100% offering open work.

Now the Pivot is down to one last ticket: this one. Time to close it out!

Congratulations, everyone! We have successfully turned the ship! 💃 🌻

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