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

[ig-exploration] Generic decision policy might not be appropriate for the Exploration IG #630

Open
michaelchampion opened this issue Feb 10, 2025 · 0 comments

Comments

@michaelchampion
Copy link

From https://w3c.github.io/charter-drafts/2024/ig-exploration.html

Decision Policy
This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 5.2.1, Consensus). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.

However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.

In previous discussions (don't have link, sorry) there was a suggestion that the usual Consensus process might not be appropriate for a group like this that does research, produces possibly diverse perspectives, and doesn't produce normative documents. Something like

  • Gather information, ensuring that both sides of controversial ideas (e.g. blockchain tech, the potential benefits and perils of AI) are considered.
  • Seek consensus on matters of fact, and IF POSSIBLE matters of prediction/prescription.
  • Do not block on lack of consensus, record alternative positions to the satisfaction of their proponents, and record the rough division of opinion in the IG across those positions.
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

No branches or pull requests

1 participant