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

Radar 24 #343

Closed
chadwhitacre opened this issue Sep 14, 2015 · 52 comments
Closed

Radar 24 #343

chadwhitacre opened this issue Sep 14, 2015 · 52 comments

Comments

@chadwhitacre
Copy link
Contributor

What are you working on this week and why?

last week

@chadwhitacre
Copy link
Contributor Author

Roadmap (what?)

Next Three Weeks
Longer Term

roadmap

@chadwhitacre
Copy link
Contributor Author

Queues (what?)

Open Closed Queue Description
0 23 Violations private communication amongst the safety team
9 12 Security private communication with security researchers
5 25 Legal private communication with our counsel
0 892 Support private communication with users
0 107 L2 Support escalated support issues
11 49 Team Review public review of applications for new teams
? ? Errors production errors
0 1,684 Vendors, etc. private communication with our vendors
(also includes low-volume mailboxes: safety and security)
21 113 Pivot a milestone
16 44 Balanced Shutdown a milestone
7 9 Milestones all milestones
5 509 PR Review work in the final stage before deployment
22 1,652 PRs all work in progress
768 4,420 Issues public communication with contributors

@kzisme
Copy link

kzisme commented Sep 14, 2015

Twitter, and random issues I see that I can tackle. Also still getting used to my new machine. I hope to be able to contribute more soon 😄

If you do find anything to post to Twitter ping me!

@chadwhitacre
Copy link
Contributor Author

Well, we're outta time to work on the Pivot, if we're going to get the work done we want before the Balanced Shutdown. I'm switching gears to that.

Another new thing since last week: our competition with Bountysource (#316) has come to a head. @kzisme Can you work with these two links on Twitter this week?

Bountysource puts pressure on us to deliver on product, and Balance Shutdown does not really help in terms of user-facing changes. Pivot is about user-facing changes, but they're nothing flashy. Could something like gratipay/gratipay.com#5 be a quick win for us vis-à-vis Bountysource? Should we fast-track something like that to stay competitive in the short term?

Not that I have time, if we're to be ready for me to meet with the CPA next week. :-/

@techtonik
Copy link
Contributor

Then there are again, a couple of issues with Aspen

I've got some progress speaking with lawyers about how to receive money from Belarus. Now I just need a lot of time to validate all information and make a write up on that.

@chadwhitacre
Copy link
Contributor Author

@kzisme Another post for Twitter?

http://coffeeonthekeyboard.com/bounties-and-tips-1204/

@kzisme
Copy link

kzisme commented Sep 14, 2015

@whit537 I'm going to reach out to a few FOSS org's this week and see if they know about Gratipay and such (and direct them towards out blog).

Any suggestions on how to not sound like a sales-person?

@chadwhitacre
Copy link
Contributor Author

@kzisme This is from Twitter, you mean? I would say definitely don't cold-tweet personal Twitter accounts. I think if you're communicating with project accounts it's probably okay. Also consider linking to https://gratipay.com/about/.

@chadwhitacre
Copy link
Contributor Author

@kzisme What do you think about http://gratipay-or-bountysource.guide/ for Twitter?

@kzisme
Copy link

kzisme commented Sep 14, 2015

Yeah, those are for Twitter.

When speaking to other people ie: Openhatch how should I introduce the idea?

I like http://gratipay-or-bountysource.guide/ - but my only concern is that some people may not even be aware of the launch of Salt, so we may be doing more harm than good.

This is not to say that it can't be used or a great resource, but I think timing is important.

@chadwhitacre
Copy link
Contributor Author

This is not to say that it can't be used or a great resource, but I think timing is important.

Okay, your call. :-)

When speaking to other people ie: Openhatch how should I introduce the idea?

Maybe something like "Would you consider applying for Gratipay?" Remember that we can't promise anything, they still have to go through Team review.

@kzisme
Copy link

kzisme commented Sep 14, 2015

I'll see what I can do and keep you posted :)

@chadwhitacre
Copy link
Contributor Author

!m @kzisme

@mattbk
Copy link
Contributor

mattbk commented Sep 14, 2015

Could something like gratipay/gratipay.com#5 be a quick win for us vis-à-vis Bountysource? Should we fast-track something like that to stay competitive in the short term?

Wish I had the time to learn this week. There's an $80 bounty on that one! Maybe I'm better off chipping $10 more into that...

Support is still 0 for now.

@kzisme
Copy link

kzisme commented Sep 14, 2015

@whit537 @mattbk How do bounties work? I have a general idea, but what has to be done to receive payment?

EDIT: I also think that gratipay/gratipay.com#5 would be a quick win and it was a feature that I feel we are lacking. Although it does depend if we want to provide recurring (weekly) funds and one-offs (more like a one time donation)

@chadwhitacre
Copy link
Contributor Author

Noting the irony ... #116. :-)

@mattbk
Copy link
Contributor

mattbk commented Sep 14, 2015

For Twitter, could keep reminding people that direct contributions help a direct economy that isn't ad-based:

@mattbk
Copy link
Contributor

mattbk commented Sep 14, 2015

@mattbk
Copy link
Contributor

mattbk commented Sep 15, 2015

Does AdBlock fit with Gratipay's values? https://getadblock.com/pay/

@chadwhitacre
Copy link
Contributor Author

It does unless someone wants to make a case that it doesn't. ;-)

@chadwhitacre
Copy link
Contributor Author

And, of course, they'd have to apply first! 💃

I started getting my head back into gratipay/gratipay.com#3653 yesterday, the accounting refactor. I salvaged an orthogonal commit from there and made a PR, gratipay/gratipay.com#3785, and started thinking about what to do with the rest.

I'm starting over on that work, reframing it in terms of the dashboard, which is currently moribund (we no longer use it for Team review after gratipay/gratipay.com#3484, and we don't really review ~users anymore (though we should double-check the implications of that—are we not charging some people that we should be?). What I want to show the accountant next week is an accounting application, a general ledger and chart of accounts. This will become the new heart of Gratipay as an application, and I'm approaching this in terms of writing an accounting web app to be parked at /dashboard. I evaluated JavaScript frameworks yesterday. I couldn't get Angular's hello world to run(?!), and am settling on Backbone (fits my brain the best). I'm afk today but will resume tomorrow, hopefully starting a new PR.

!m *

@mattbk
Copy link
Contributor

mattbk commented Sep 15, 2015

Yes, they'd have to apply, and they'd have to be open. I think they're pretty open: http://support.getadblock.com/kb/about-the-project/how-can-i-support-adblock

@kzisme
Copy link

kzisme commented Sep 15, 2015

@whit537 One tweet posted. I'm trying not to attack Bountysource - but promote openness and open work. Let me know what you think: https://twitter.com/Gratipay/status/643853044187299840

@kzisme
Copy link

kzisme commented Sep 15, 2015

@whit537 Also would it be beneficial to post on HN in the coming weeks about Gratipay 2.0 and payouts and such? I feel it would be.

@tshepang
Copy link

It still comes off to me as an attack. I would be more happy with something as boring as "Some comparison with our closest competitor".

@kzisme
Copy link

kzisme commented Sep 15, 2015

@tshepang Tweet removed and re-tweeted a revised version. Thanks for the feedback!

@kzisme
Copy link

kzisme commented Sep 15, 2015

Also after reading through http://coffeeonthekeyboard.com/bounties-and-tips-1204/ it does seem that most users looking at Gratipay are interested in a one-off donation sometimes.

Just some food for thought 🍔

Next post will be tomorrow probably about the above article

Author is: https://twitter.com/jamessocol

@chadwhitacre
Copy link
Contributor Author

Here's a dozen projects that should know about Gratipay:

http://us5.campaign-archive2.com/?u=744876426414b018c030e670a&id=0ff3704aaa

@chadwhitacre
Copy link
Contributor Author

Also would it be beneficial to post on HN in the coming weeks about Gratipay 2.0 and payouts and such? I feel it would be.

Yeah, probably. I say go for it! :-)

It still comes off to me as an attack.

It's supposed to be an attack, predicated on the idea that we're competing with Bountysource (#316). If we're not competing with them (#316 (comment)) then I think we should just talk about other stuff on Twitter.

Also, @kzisme: https://gratipay.com/~kaytrance/ is false. That's a link to a ~user account, and the ~user doesn't have a Team.

@chadwhitacre
Copy link
Contributor Author

Sorry, I meant https://twitter.com/typwrittr/status/602717349754568704 is false.

@kzisme
Copy link

kzisme commented Sep 16, 2015

Will remove when I get home. I've been searching for people who tweeted
about us in the past.
On Sep 16, 2015 10:11 AM, "Chad Whitacre" [email protected] wrote:

Sorry, I meant https://twitter.com/typwrittr/status/602717349754568704 is
false.


Reply to this email directly or view it on GitHub
#343 (comment)
.

@chadwhitacre
Copy link
Contributor Author

Let's not forget https://gratipay.com/dashboard/1.0-payouts before payday this week.

@tshepang
Copy link

I see no need to attack competitors. Am I missing something here? Why attack? You can still talk about how Gratipay is better without attacking (unless we are here having different definitions for the same word).

@chadwhitacre
Copy link
Contributor Author

@tshepang Yes, let's drop the martial language, sorry. I mean, "Engage in direct competition."

@kzisme
Copy link

kzisme commented Sep 16, 2015

Most recent Twitter post.

@chadwhitacre
Copy link
Contributor Author

!m @kzisme

@mattbk
Copy link
Contributor

mattbk commented Sep 17, 2015

Let's not forget https://gratipay.com/dashboard/1.0-payouts before payday this week.

To be approved, we are applying the same standards as new teams?

@chadwhitacre
Copy link
Contributor Author

@mattbk No. For individual payouts the only criteria is that they provided some product or service (no "give me money for no reason at all"). It doesn't have to have been open work. You up for tackling that queue?

@mattbk
Copy link
Contributor

mattbk commented Sep 17, 2015

Okay, that's much clearer, thanks. I'm going through some of them now.

@chadwhitacre
Copy link
Contributor Author

!m @mattbk

@chadwhitacre
Copy link
Contributor Author

I'm working on gratipay/gratipay.com#3786. I've stumbled upon a nice pattern for improving our API and our software documentation at the same time. :-)

@mattbk
Copy link
Contributor

mattbk commented Sep 17, 2015

Majority are explicitly doing work. Others had already deleted their profile description, but from github pages and others they are involved in various projects that are work.

@chadwhitacre
Copy link
Contributor Author

Cool. That's about what I've been expecting.

@kzisme
Copy link

kzisme commented Sep 17, 2015

Newest Twitter post.

@mattbk
Copy link
Contributor

mattbk commented Sep 17, 2015

You could also chime in with this conversation, if you want: https://twitter.com/untitaker/status/644525326098395136

@kzisme
Copy link

kzisme commented Sep 17, 2015

Will do

!m @mattbk

@mattbk
Copy link
Contributor

mattbk commented Sep 17, 2015

Building forms (e.g., gratipay/gratipay.com#3767) is interesting to me, but I'm not sure I understand how to build and then do the database I/O in Python/Gratipay specifically. Are there any resources out there about this?

@chadwhitacre
Copy link
Contributor Author

@mattbk Best bet is to start with existing code that is close to what you want, and work from those examples. My hope and dream is the docs I've got going on gratipay/gratipay.com#3786 (comment) can evolve into what you need.

@chadwhitacre
Copy link
Contributor Author

Alright, hitting pause on gratipay/gratipay.com#3786 in order to run payday: #344.

@kzisme
Copy link

kzisme commented Sep 19, 2015

Before replying to this Tweet....We don't have any plans to move from PayPal? I had an inquiry reguarding us moving away from Paypal to avoid fees.

I'm not aware of us moving away from that current model, but just wanted to check.

https://twitter.com/failvarez/status/644672998088163328

@mattbk
Copy link
Contributor

mattbk commented Sep 19, 2015

The hope is to get bank transfers back with something like Dwolla (not sure of status of that issue, @whit537). Right now you can't apply without a payout route, and the only payout route we have right now is PayPal.

@chadwhitacre
Copy link
Contributor Author

Email (what?)

screen shot 2015-09-22 at 10 03 27 am

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

5 participants