-
Notifications
You must be signed in to change notification settings - Fork 38
delegate payday #467
Comments
👍 Let's do a trial run today? 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 ... |
Alternating months might be better, less guessing about "am I on this week?" |
👍 for me too, if you need the additional support I'm always up for it. |
!m @clone1018 What kind of schedule do you think we should adopt? |
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 |
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. |
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?
|
What time do we want to standardize on? Making calendar reminders hah |
@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. |
I've updated #467 (comment) to include a concept of pilots and copilots. |
I can't make 8:30 my time, I'm still commuting. 9:30-10:30 would work unless something crazy happens at work. |
Well, it looks like @rohitpaulk is your copilot, so I guess he's the one you have to coordinate with. ;-) |
@rohitpaulk You on payday today? |
Yep, I'll be here in 15-20 mins |
Cool. :) |
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. :-) |
Yep, correct |
Re: #477 (comment) ...
@rohitpaulk I've made a new "Payday Runners" team with you, @clone1018, and I on it, with read/write access to |
@rohitpaulk Once we're done with #477, let's make sure you have DigitalOcean access to use for future paydays. |
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!? 😮 |
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 |
That's 9:30 PM my time - yes, I should be available :) |
Delegation successful? We have a bus factor of 3 now for basic payday |
👍 I guess @rohitpaulk can close the ticket if he's ready? :) |
🍻 |
🍻 |
I liked running payday but I can't wait till @whit537 takes over next week! |
With #628 we are really closed here. :-) |
@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.
The text was updated successfully, but these errors were encountered: