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

OEP-1 could be more clear about announcing #493

Open
robrap opened this issue Jun 2, 2023 · 3 comments
Open

OEP-1 could be more clear about announcing #493

robrap opened this issue Jun 2, 2023 · 3 comments
Assignees

Comments

@robrap
Copy link
Contributor

robrap commented Jun 2, 2023

The main section that notes how to announce an OEP is here: https://open-edx-proposals.readthedocs.io/en/latest/processes/oep-0001.html#step-3-review-with-arbiter. It doesn't have a clear process for announcing merges, which is especially important for OEP updates that didn't necessarily go through a wider review.

@sarina
Copy link
Contributor

sarina commented May 17, 2024

@robrap what is the problem you're experiencing? Do you have a suggestion for how we could resolve the problem?

If you're looking for a push notification that something has merged, would a follow up post on the OEP thread in Discourse or another post in Slack that announces the merge suffice? If the latter, we could just set up an auto post connection between merges in this repo with a slack room.

@sarina sarina added the waiting on author PR author needs to resolve review requests, answer questions, fix tests, etc. label May 17, 2024
@robrap
Copy link
Contributor Author

robrap commented May 17, 2024

I personally started watching the repo, so I personally don't have an issue. That said, if decisions are being made/updated, I think it would be good for the community to see that in anyway that works for people. A slack room might work well.

All this being said, feel free to move forward however you think best. Thank you.

@sarina
Copy link
Contributor

sarina commented May 18, 2024

I don't think it's unreasonable to add a section like what we have in DEPR about announcing - https://open-edx-proposals.readthedocs.io/en/latest/processes/oep-0021-proc-deprecation.html#removed - I'll assign this to myself to address in the coming weeks.

@sarina sarina self-assigned this May 18, 2024
@sarina sarina added help wanted Ready to be picked up by anyone in the community and removed waiting on author PR author needs to resolve review requests, answer questions, fix tests, etc. labels May 18, 2024
sarina added a commit that referenced this issue Jul 4, 2024
Previously, OEP-1 didn't have a clear process for announcing merges,
which is especially important for OEP updates that didn't necessarily
go through a wider review.

Addresses issue #493
@sarina sarina added in review and removed help wanted Ready to be picked up by anyone in the community labels Jul 4, 2024
sarina added a commit that referenced this issue Jul 25, 2024
Previously, OEP-1 didn't have a clear process for announcing merges,
which is especially important for OEP updates that didn't necessarily
go through a wider review.

Addresses issue #493
sarina added a commit that referenced this issue Jul 26, 2024
* docs: OEP-1: Add a section on announcing changes

Previously, OEP-1 didn't have a clear process for announcing merges,
which is especially important for OEP updates that didn't necessarily
go through a wider review.

Addresses issue #493

Co-authored-by: Robert Raposa <[email protected]>
davidjoy pushed a commit to davidjoy/open-edx-proposals that referenced this issue Aug 28, 2024
* docs: OEP-1: Add a section on announcing changes

Previously, OEP-1 didn't have a clear process for announcing merges,
which is especially important for OEP updates that didn't necessarily
go through a wider review.

Addresses issue openedx#493

Co-authored-by: Robert Raposa <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants