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

Decisions #338

Closed
jeffjaffe opened this issue Nov 3, 2019 · 18 comments
Closed

Decisions #338

jeffjaffe opened this issue Nov 3, 2019 · 18 comments
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion
Milestone

Comments

@jeffjaffe
Copy link

Section 3.3 of the Process Document provides the location for reaching decisions: "Decisions may be made during meetings (face-to-face or distributed) as well as through email." Should we allow other venues such as in github threads?

@mnot
Copy link
Member

mnot commented Nov 3, 2019

FWIW in the IETF, we confirm consensus of closing issues on the WG mailing list, since our process requires us to call consensus on the list. It's cumbersome, but is good for assuring everyone is on the same page -- some people don't follow Github.

Perhaps the Process could say something like "Groups MAY designate another venue for forming consensus, as long as that change itself has consensus."

@fantasai
Copy link
Collaborator

fantasai commented Nov 4, 2019

We also need to require that the venue be a) accessible to all members and b) archived on w3.org

@dwsinger
Copy link
Contributor

dwsinger commented Nov 6, 2019

It's not even clear if that is an exhaustive list (these are the only places you can make decisions) or an explicit call-out of one possibility (yes, you are allowed to make decisions in X, among other places, in case you wondered).

we should probably re-write as a set of conditions for making a valid decision (that all stakeholders are made aware, that they have time, that the question, responses, and decision are archived and recorded, and so on)?

@dwsinger
Copy link
Contributor

I suspect that this is awaiting a volunteer. It's also associated with the (undocumented) "where are you allowed to do w3c business and discussions?" (email, IRC, CVS, Github, Slack, Converse…?)

@jeffjaffe
Copy link
Author

I suggest we defer to P2021.

@dwsinger
Copy link
Contributor

I suggest we defer to P2021.

It's not assigned to P2020, which means it's now in the indefinite future. You want it addressed (a) in 2021 or (b) sometime in the indefinite future?

see also #322

@jeffjaffe
Copy link
Author

@dwsinger This is not urgent. If P2021 is a quick spin edit-pass, then this can be deferred further.

@chaals
Copy link
Contributor

chaals commented Aug 18, 2020

Perhaps as part of where they can be recorded, we could actually describe how to know that there has been a Working Group decision.

Update s/how you know/how to know

@dwsinger
Copy link
Contributor

@chaals who is "you"? I'm not sure if you are saying more than I say about valid decisions in my comment

@chaals
Copy link
Contributor

chaals commented Aug 18, 2020

@dwsinger the additional piece is that there is no clear definition of how to know that there is a Working Group decision. It is meant to be done by consensus, unless the chair calls a vote, and there's some nice stuff about how consensus isn't exactly unanimity.

I think the answer is probably something like "the chair declares in a written record there is a decision", and the question of where that record can be is the one you have asked. But now it's just convention / "obvious" that there has to be a written record, and that if the chair says it is so they somehow have the authority to make that true.

@dwsinger
Copy link
Contributor

This also links to questions of Minutes, as raised in #511 ?

@frivoal
Copy link
Collaborator

frivoal commented Mar 23, 2021

Right. I think #512 would actually solve this.

@frivoal
Copy link
Collaborator

frivoal commented Apr 15, 2021

I believe this has now been solved by merging #436 and #512. I suggest closing. Agenda+ to make sure we don't miss it (If @dwsinger as chair thinks this can be closed without discussion on the call, fine by me).

@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Apr 15, 2021
@jeffjaffe
Copy link
Author

I believe this has now been solved by merging #436 and #512. I suggest closing.

Could you clarify how #436 (tooling) and #512 (minutes) addresses #338 (venues for decisions)?

@frivoal
Copy link
Collaborator

frivoal commented Apr 15, 2021

#512 (minutes) clarifies that decisions must be recorded in minutes. #436 (tooling) says (with a must) what kind of archival/retention is expected of minutes, and is explicit that it's not limited to email. Preexisting text (such as https://www.w3.org/Consortium/Process/Drafts/#decisions) say how decisions are arrived to. So all in all, if you make a decision according to these sections, record it in your minutes, and have your minutes published and archived correctly, you're good.

However, I now think you're right that we're not actually done. I think that what I just referred to would be enough, but the sentence you quoted ("Decisions may be made during meetings (face-to-face or distributed) as well as through email.") overconstrains the problem. Maybe we should just delete it.

@jeffjaffe
Copy link
Author

jeffjaffe commented Apr 15, 2021

If #512 clarifies that decisions must be recorded in minutes, does that mean that decisions made in GH are not decisions until there is actually some meeting in which the decision is recorded?

Or are you saying that #436 defines minutes in a way that a GH decision can be considered a "minuted recording"?

@fantasai
Copy link
Collaborator

@jeffjaffe #512 clarifies that decisions made during meetings must be recorded in the minutes; it doesn't say anything about decisions made outside of meetings. Tooling #436 says that all decisions (regardless of whether in the minutes or not) must be archived by W3C for future reference.

frivoal added a commit to frivoal/w3process that referenced this issue Apr 26, 2021
Now that we have tools other than email, allow them as well.

See w3c#338
frivoal added a commit to frivoal/w3process that referenced this issue Apr 26, 2021
Now that we have tools other than email, allow them as well.

See w3c#338
@frivoal
Copy link
Collaborator

frivoal commented Apr 26, 2021

Just added a pull request (#519) to fix up the original offending sentence, rather than delete it as I earlier suggested. I think that ought to make things clear.

frivoal added a commit to frivoal/w3process that referenced this issue May 11, 2021
Now that we have tools other than email, allow them as well.

See w3c#338
frivoal added a commit that referenced this issue May 12, 2021
Now that we have tools other than email, allow them as well.

See #338
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed Agenda+ Marks issues that are ready for discussion on the call labels May 12, 2021
@frivoal frivoal closed this as completed May 12, 2021
@frivoal frivoal modified the milestones: Deferred, Process 2021 May 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion
Projects
None yet
Development

No branches or pull requests

6 participants