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

CfC: Github Centric Mode of Work #17

Open
seanturner opened this issue Jan 6, 2025 · 1 comment
Open

CfC: Github Centric Mode of Work #17

seanturner opened this issue Jan 6, 2025 · 1 comment
Assignees
Labels
call-for-consensus Indicates a PR or Issue is at a state where we are calling for participants to reach consensus

Comments

@seanturner
Copy link
Contributor

At the 2024-12-19 PAT meeting, we had consensus for the PAT to be "GitHub centric"; the primary mode of work and discussions about that work is via the PAT repo. All of the PAT repo's issues & pull requests are sent to the mailing list so that those who are not following/watching the PAT repo still see everything posted there.

Also discussed at the 2024-12-19 meeting was the notable exception of the PAT slack channel; see w3ccommunity slack#patwg (invite). The PAT slack channel is used for logistics and during meetings. The PAT slack channel is not archived so any meaningful discussions need to occur in the PAT repo.

We would like to confirm this consensus so please let us know if you object to this proposed process by 2025-01-13, and please suggest an alternative if you do object.

@seanturner seanturner added the call-for-consensus Indicates a PR or Issue is at a state where we are calling for participants to reach consensus label Jan 6, 2025
@myonlinematters
Copy link

As an IE I cannot vote, but this is my recollection of the agreement that was reached.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
call-for-consensus Indicates a PR or Issue is at a state where we are calling for participants to reach consensus
Projects
None yet
Development

No branches or pull requests

3 participants