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

Radar 27 #364

Closed
chadwhitacre opened this issue Oct 5, 2015 · 28 comments
Closed

Radar 27 #364

chadwhitacre opened this issue Oct 5, 2015 · 28 comments

Comments

@chadwhitacre
Copy link
Contributor

What are you working on this week and why?

last week

@chadwhitacre
Copy link
Contributor Author

Roadmap (what?)

This Week
Longer Term

roadmap

@chadwhitacre
Copy link
Contributor Author

Queues (what?)

Open Closed Queue Description
0 23 Violations private communication amongst the safety team
11 14 Security private communication with security researchers
5 25 Legal private communication with our counsel
3 904 Support private communication with users
3 108 L2 Support escalated support issues
12 66 Team Review public review of applications for new teams
? ? Errors production errors
0 1,734 Vendors, etc. private communication with our vendors
(also includes low-volume mailboxes: safety and security)
21 115 Pivot a milestone
16 48 Balanced Shutdown a milestone
6 10 Milestones all milestones
5 516 PR Review work in the final stage before deployment
21 1,667 PRs all work in progress
777 4,479 Issues public communication with contributors

@chadwhitacre
Copy link
Contributor Author

Alright, top priority is getting refunds out the door. We're really getting clogged up on Security, L2 Support and Pivot issues.

@chadwhitacre
Copy link
Contributor Author

I finally ordered Traction.

@mattbk
Copy link
Contributor

mattbk commented Oct 6, 2015

@kzisme
Copy link

kzisme commented Oct 6, 2015

@mattbk I'm confused by that Tweet as well I haven't been around to be able to reply yet. It was my understanding that tweeting about the refund and everything else we've done was "notifying users"

I've been busy with classes and such but I've been working on some smaller things as well as setting up vim and my dev stuff on my mac...slowly getting there.

@chadwhitacre
Copy link
Contributor Author

We (I) didn't move money to Balanced in time, so we're not going to be able to pull off the big 1.0 refund (gratipay/gratipay.com#3539) after all. I'm looking at the advances refund: gratipay/gratipay.com#3763.

@mattbk
Copy link
Contributor

mattbk commented Oct 8, 2015

Support 0
L2 Support 4

@mattbk
Copy link
Contributor

mattbk commented Oct 8, 2015

@kzisme No need to reply to it just because I called it out. I thought we had emailed everyone about the refund already.

@chadwhitacre
Copy link
Contributor Author

Great post on "What makes a good community?"

@kzisme
Copy link

kzisme commented Oct 9, 2015

@mattbk that's what I thought as well. We had a discussion about getting in
contact with all users.
On Oct 8, 2015 12:24 PM, "mattbk" [email protected] wrote:

@kzisme https://github.com/kzisme No need to reply to it just because I
called it out. I thought we had emailed everyone about the refund already.


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

@chadwhitacre
Copy link
Contributor Author

We published the blog post and linked it from the website and Twitter, but we never got around to mass-emailing everyone again. We mass-emailed people months ago when we first announced our intention to do the refunds. We actually had a handful of people complain at the time that we were spamming them, and no doubt we would've again in this case. Always gonna find some someone to disappoint, I guess. :-)

@chadwhitacre
Copy link
Contributor Author

The reality is starting to sink in over here that we're not doing the 1.0 refunds after all. I believe instead that means that we're going to be holding onto that money indefinitely, until such time as folks bother to withdraw it. We should post about this on Monday.

@chadwhitacre
Copy link
Contributor Author

Finished up payday: #365.

@chadwhitacre
Copy link
Contributor Author

I made an Accounting label in this repo.

@chadwhitacre
Copy link
Contributor Author

Re: #345 (comment) ...

Ratio of active teams to total approved teams is 58/91 (64%). Ideally we'd want this as close to 100% as possible.

Currently running at 100%! ;-)

screen shot 2015-10-08 at 9 19 47 pm

@chadwhitacre
Copy link
Contributor Author

Contracting today. Hoping to run the advances refund this afternoon (tonight after I get home if I can't get to it this afternoon): gratipay/gratipay.com#3810.

@chadwhitacre
Copy link
Contributor Author

Alright! Let's see about this ...

@chadwhitacre
Copy link
Contributor Author

First PR landed from @yifeiwu! 💃

gratipay/gratipay.com#3772

@kzisme
Copy link

kzisme commented Oct 10, 2015

I apologize for the lack of Twitter posts this week. Any suggestions on material for the weekend?

Also if possible I would like to get into more code based work as well if there are small things or things someone and I could work together on (if at all possible).

@chadwhitacre
Copy link
Contributor Author

@kzisme No worries! Maybe promoting recently-joined teams? Maybe start talking about #334?

I know @mattbk has been making some tickets lately, maybe he has some suggestions for code to work on?

@mattbk
Copy link
Contributor

mattbk commented Oct 10, 2015

I think one of my prs has a review tag on it. There's at least one easy pr in my recent tickets (can't check right now).

@kzisme
Copy link

kzisme commented Oct 11, 2015

Could you link it when you get a chance and I'll take a look? :)

Also - @whit537 refunding advances has been done correct - BUT not our 1.0 refund right?

I'm trying to figure out what this tweet was about.

Twitter is slightly irritating because it's like shouting across a busy street to someone and expecting them to hear your full thought...

@chadwhitacre chadwhitacre mentioned this issue Oct 12, 2015
@mattbk
Copy link
Contributor

mattbk commented Oct 12, 2015

@chadwhitacre
Copy link
Contributor Author

Twitter is slightly irritating because it's like shouting across a busy street to someone and expecting them to hear your full thought...

Indeed. In the past, Twitter has worked best for me as a way to guide people into the right GitHub ticket. Plenty of times there is no good ticket yet and you should make one.

@chadwhitacre
Copy link
Contributor Author

Also - @whit537 refunding advances has been done correct - BUT not our 1.0 refund right?

Correct. I'm hoping to write up a blog post today explaining the situation.

@chadwhitacre
Copy link
Contributor Author

Gonna close out here and pick up on #368 ...

@chadwhitacre
Copy link
Contributor Author

Email (what?)

screen shot 2015-10-14 at 12 55 32 pm

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