chore: update flamingo rotation manual #1376
Conversation
morph-dev
added
documentation
morph-dev
requested review from
carver,
mrferris,
njgheorghita,
KolbyML and
ogenev
|
Here is the current checklist template but I think we need to simplify and improve it if we plan to use it: Weekly
|
|
Thanks. I simplified and added checklist. Another topic that I would like to discuss. Should we restart using Flamingo rotation document? |
| 1. Signal to the next Flamingo that you're done writing up the notes | ||
| 2. Give the next Flamingo a reminder that their turn is coming up | ||
| 3. A failsafe to make sure we didn't forget to pick a Flamingo for the following week | ||
| Think through: what kinds of things do you think should on the checklist? |
There was a problem hiding this comment.
do you think should be on the checklist
|
|
||
| Especially while we continue to develop the procedure, try to be available the following Monday to help the subsequent Flamingo transition in, and get started. | ||
| Double check the [Flamingo schedule](https://notes.ethereum.org/@njgheorghita/r1angO2lT) and make sure you're available for your next rotation. If not, please switch with somebody asap. |
There was a problem hiding this comment.
This is also another remnant that isn't actively maintained.
- I can update the schedule
- Update this to say something like... "estimate when you'll be flamingo next and make sure you're available..."
There was a problem hiding this comment.
As I said in the other comment, I think we should restart using it.
And there shouldn't be "estimation" on when next shift should come, meaning that it should always be planned at least one-two months in the future. With that being said, I would leave it as it is written now.
I volunteer to take responsibility and make sure we always have a schedule ahead. Others just have to be sure they keep it updated when they change shifts.
I don't have access to this document, @njgheorghita if you are the owner, could you add me? :) |
|
@ogenev @morph-dev Yup, I'm happy to open access to that document... but maybe there's a simpler place to host this message? Like an open issue in this repo or something else more github-y |
I already gave access to @ogenev. I'm fine with a current document. But if preferred, we can easily make a .md file in github (e.g. at root folder). |
|
I am not a fan of having a constantly updated flamingo whose turn it is document in the trin repo, if we want a repo with a md document we should make a flamingo repo for it or a discord channel |
|
|
||
| - **Daily** | ||
| - Read Discord, especially for help requests or signs of network issues | ||
| - Monitor [Glados](http://glados.ethportal.net/) changes, and correlate with releases (trin, glados, other clients?) |
There was a problem hiding this comment.
| - Monitor [Glados](http://glados.ethportal.net/) changes, and correlate with releases (trin, glados, other clients?) | |
| - Monitor [Glados](https://glados.ethdevops.io/) changes, and correlate with releases (trin, glados, other clients?) |
I know this url was out of date elsewhere in the docs. Might as well update it while you're tweaking.
|
I'm merging this one. If anybody has additional followup, I will make another PR. |
What was wrong?
Some information on the Flamingo manual seems to be outdated, most notably the "notes".
While I don't have access to the notes and checklist, Kolby told me that we weren't really using them for the last couple of months.
How was it fixed?
Remove the references to the notes. If people think they were useful, should we consider restarting doing them? Should we consider alternatives?
I'm not sure what items are on the checklist (no access), but maybe we can put them on the Flamingo page directly? Can anybody share it with me?
To-Do