Skip to content

Conversation

@lornajane
Copy link
Contributor

Fixes #3527 by formalizing our proposals process.

We have had a proposals process, but few proposals have been successfully accepted, and the pull requests tend to be open for a long time. To try to ease the process and be more open to suggestions, this follows the approach discussed in recent TSC meetings:

  • open a discussion
  • implement the thing as an extension if possible
  • if good engagement results, then proceed to make a proposal
  • proposal gets formal scrutiny by TSC and the rest of the project
  • if accepted, the proposal pull request is merged, and an appropriate pull request adds the actual specification change to the relevant spec release version

Copy link
Contributor

@mikekistler mikekistler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! 👍

@earth2marsh earth2marsh self-requested a review March 28, 2024 16:17
Copy link
Member

@earth2marsh earth2marsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM -- nice improvements!

@earth2marsh earth2marsh merged commit d63036c into OAI:main Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Define process for the "proposals" directory

4 participants