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

delegate payday #467

Closed
chadwhitacre opened this issue Jan 14, 2016 · 30 comments
Closed

delegate payday #467

chadwhitacre opened this issue Jan 14, 2016 · 30 comments

Comments

@chadwhitacre
Copy link
Contributor

@clone1018 @rohitpaulk You two want to start running payday alternating weeks? A cord of three strands is not easily broken. I'd love to leave my computron at home during #314.

@rohitpaulk
Copy link
Contributor

👍 Let's do a trial run today? I'll be able to start by around 8PM IST..

@chadwhitacre
Copy link
Contributor Author

I'll be able to start by around 8PM IST..

Yesssssssss! Looks like that is 9:30 am my time ... about 30 minutes. I'll start going through the team review queue now ...

@chadwhitacre
Copy link
Contributor Author

alternating weeks

Alternating months might be better, less guessing about "am I on this week?"

@clone1018
Copy link
Contributor

👍 for me too, if you need the additional support I'm always up for it.

@chadwhitacre
Copy link
Contributor Author

!m @clone1018

What kind of schedule do you think we should adopt?

@clone1018
Copy link
Contributor

Alternating months sounds fine to me, gives everyone a break. Might have a knowledge gap when you come back after 2 months but I guess that's what docs are for

@chadwhitacre
Copy link
Contributor Author

We could try week by week, too. The only thing is we don't want to screw up and have someone forget it's their week, but I guess with three of us to remind each other and pinch-hit if necessary it's maybe not a big deal.

@chadwhitacre
Copy link
Contributor Author

Since @rohitpaulk didn't quite get to finish today due to PayPal permissions (#468#469) it seems like he should have another shot next week. I guess let's try month by month and see how that goes, eh?

month pilot copilot
January @rohitpaulk @whit537
February @clone1018 @rohitpaulk
March @whit537 @clone1018
April @rohitpaulk @whit537
May @clone1018 @rohitpaulk
June @whit537 @clone1018

@clone1018
Copy link
Contributor

What time do we want to standardize on? Making calendar reminders hah

@chadwhitacre
Copy link
Contributor Author

@clone1018 We haven't observed a standard time in the past. How about ~1430 UTC like we did today? That should be 8 pm @rohitpaulk's time, 9:30 am mine, and 8:30 am yours. Also: it seems like a good idea to have a second person on hand in case issues come up. Always better to have two eyes/hands in a crisis, ya? That will also help with cross-training as the process evolves.

@chadwhitacre
Copy link
Contributor Author

I've updated #467 (comment) to include a concept of pilots and copilots.

@clone1018
Copy link
Contributor

I can't make 8:30 my time, I'm still commuting. 9:30-10:30 would work unless something crazy happens at work.

@chadwhitacre
Copy link
Contributor Author

Well, it looks like @rohitpaulk is your copilot, so I guess he's the one you have to coordinate with. ;-)

@chadwhitacre
Copy link
Contributor Author

@rohitpaulk You on payday today?

@rohitpaulk
Copy link
Contributor

Yep, I'll be here in 15-20 mins

@chadwhitacre
Copy link
Contributor Author

Cool. :)

@rohitpaulk
Copy link
Contributor

I can't make 8:30 my time, I'm still commuting. 9:30-10:30 would work unless something crazy happens at work.

9:30 - 10:30 your time works for me, @clone1018

@chadwhitacre
Copy link
Contributor Author

9:30 - 10:30 your time works for me, @clone1018

@rohitpaulk So we're on the same page: that matters next month, right? This month you are the pilot. :-)

@rohitpaulk
Copy link
Contributor

Yep, correct

@chadwhitacre
Copy link
Contributor Author

Re: #477 (comment) ...

I see a suspicious user, and I don't have access to the violations repo...

@rohitpaulk I've made a new "Payday Runners" team with you, @clone1018, and I on it, with read/write access to violations as well as logs.

@chadwhitacre
Copy link
Contributor Author

@rohitpaulk Once we're done with #477, let's make sure you have DigitalOcean access to use for future paydays.

@chadwhitacre
Copy link
Contributor Author

Looks on #485 like @rohitpaulk has DO access, so we're set on that.

#485 was the last payday of January. Next month, @clone1018 is the pilot and @rohitpaulk is the copilot. Which means that, in the greater interest of Gratipay, I should take the day off next Thursday, February 4. Offline all day. Inaccessible. Checked out. In the woods.

Are we ready for this, @clone1018 @rohitpaulk!? 😮

@clone1018
Copy link
Contributor

I'm ready! I'm going to refresh myself on all of the documentation this week, will you be available on Thursday @rohitpaulk ? I'm planning on doing it around 10AM CST

@rohitpaulk
Copy link
Contributor

That's 9:30 PM my time - yes, I should be available :) ✈️

@clone1018
Copy link
Contributor

Delegation successful? We have a bus factor of 3 now for basic payday

@chadwhitacre
Copy link
Contributor Author

👍

I guess @rohitpaulk can close the ticket if he's ready? :)

@rohitpaulk
Copy link
Contributor

🍻

@chadwhitacre
Copy link
Contributor Author

🍻

@clone1018
Copy link
Contributor

I liked running payday but I can't wait till @whit537 takes over next week!

@chadwhitacre chadwhitacre mentioned this issue Mar 1, 2016
@chadwhitacre
Copy link
Contributor Author

With #628 we are really closed here. :-)

!m @clone1018 @rohitpaulk

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