serverlessworkflow
Update governance model
What would you like to be added:
Update/define the governance model by defining some kind of community, vote-based decision making on breaking changes/issues deemed "controversial".
Create a new tag, such as Up to vote and/or Controversial to mark issues requiring debate/vote on a meeting call
Why is this needed:
Ensure that breaking and/or controversial changes are backed up by both implementers and users, and by the community in a wider sense.
Vote sessions, if any is required, could be held in a monthly fashion to ensure that voters can make a documented decision.
Vote privilege should IMO only be given to some kind of privileged users, such as contributor - or even maintainer.
Great idea and def something that we need to come up with and try to enforce.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.