Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Public OP Stack Calendar Process #91

Closed
tynes opened this issue Sep 24, 2024 · 4 comments · Fixed by #107
Closed

Public OP Stack Calendar Process #91

tynes opened this issue Sep 24, 2024 · 4 comments · Fixed by #107

Comments

@tynes
Copy link
Contributor

tynes commented Sep 24, 2024

This ticket can be closed when there is an open, transparent process for adding events to the OP Stack Protocol calendar and it is documented in the readme.

The purpose of this repo is to drive alignment on engineering decisions in an open way so that it is possible to contribute to the OP Stack from any organization. The general flow of this repo is as follows:

  • open a PR
  • directly communicate with stakeholders asking for review
  • schedule a design review meeting using a ticket
  • place a design review meeting on the public calendar
  • record the design review meeting, drive towards immediate next steps
  • merge the pull request if aligned, otherwise improve it and have another design review meeting if necessary
  • upload design review meeting recording to YouTube or another public place
  • ship it

We need somebody with admin access on the public OP Stack calendar to be able to manage the calendar. It is expected that the person that proposed the meeting runs the meeting and does the recording.

@op-aaron
Copy link

op-aaron commented Sep 26, 2024

As someone w/admin access, I'm happy to take point on adding events. I would propose the following process:

Once ready to schedule the review (after reaching out to stakeholders), an issue is created & owned to me with the following information:

  • Title of meeting
  • Date & Time for meeting
  • Length of meeting
  • Link to design review file/s (included in body of invite)
  • [optional] Additional text for the body of the invite
  • [optional] Additional guests aside from original requester

I can create the meeting with the info above & invite the original requester as a guest who can invite others (stakeholders). I'm also happy to include them from the start if you'd like to provide their email. Once the meeting is reflected on the public calendar, I can confirm with a comment and close the issue.

Let me know how that sounds or if you have any suggestions.

@tynes
Copy link
Contributor Author

tynes commented Sep 27, 2024

Thank you @op-aaron! I created a template for you to streamline this process in ethereum-optimism/.github#26. Now when a person creates an issue, they will have the ability to schedule a design review meeting. I didn't make it auto tag you, that is something that I could add if you would like. Let me know if you have any feedback on this process

@tynes
Copy link
Contributor Author

tynes commented Sep 27, 2024

We can close this issue when the readme of this repo is updated with this information

@op-aaron
Copy link

op-aaron commented Sep 27, 2024

Thanks @tynes could you please:

  • Add a "duration" field to the template to capture meeting length (something I missed in initial request) ... unless you advise that we should timebox it with a default time.
  • Have it auto tag me - Let's start there since I'm the only one (other than you) who can add the events.

I'd say once that is done feel free to push it, update README, and we can begin trying it out!

tynes added a commit that referenced this issue Oct 3, 2024
@tynes tynes closed this as completed in #107 Oct 3, 2024
@tynes tynes closed this as completed in 15a3866 Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants