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

Rework governance #97

Merged
merged 6 commits into from
Mar 6, 2025
Merged

Rework governance #97

merged 6 commits into from
Mar 6, 2025

Conversation

mattam82
Copy link
Member

@mattam82 mattam82 commented Mar 5, 2025

This implements a proposed change to the process for leader election and renewal, along with a reorganization/relabelling of the teams/governance pages.

Voting process/renewal:
image

Rocq Teams and Governance pages. Rather than just "governance" this page really is about listing all the teams and contributors.

image

New footer:
image

It now feels weird to have "Rocq Teams" under the "Policies" heading in the footer, while "Governance" links to the policy, appropriately. Shouldn't we rather move Rocq Teams under "About Rocq" or in "Ecosystem" above "Community" ?

@mattam82 mattam82 requested review from Zimmi48 and tabareau March 5, 2025 09:57
@tabareau
Copy link
Contributor

tabareau commented Mar 5, 2025

@mattam82 this PR subsumes #95, right ?

@tabareau
Copy link
Contributor

tabareau commented Mar 5, 2025

I indeed would move Rocq Teams to Ecosystem indeed, and remove governance from the title of the webpage. Also remove the h2 header "team" as I did on #95 as it looks redundant now.

@Zimmi48
Copy link
Member

Zimmi48 commented Mar 5, 2025

Sorry, I did not see this PR before merging #95.

@tabareau
Copy link
Contributor

tabareau commented Mar 6, 2025

I think we can rebase it on main

@tabareau tabareau closed this Mar 6, 2025
@tabareau tabareau reopened this Mar 6, 2025
@mattam82 mattam82 force-pushed the rework-governance branch from 191b20d to 35ecf10 Compare March 6, 2025 09:52
@tabareau tabareau merged commit 27a6d3a into coq:main Mar 6, 2025
2 checks passed
Copy link
Member

@Zimmi48 Zimmi48 left a comment

Choose a reason for hiding this comment

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

I understand the point about removing the "governance" team if it only contained the core team, but now I don't know where we would put the new consortium and roadmap teams that were discussed in the last Coq Call.

@mattam82
Copy link
Member Author

mattam82 commented Mar 6, 2025

Fixed in #99

@mattam82 mattam82 deleted the rework-governance branch March 6, 2025 16:14
@mattam82
Copy link
Member Author

mattam82 commented Mar 6, 2025

I understand the point about removing the "governance" team if it only contained the core team, but now I don't know where we would put the new consortium and roadmap teams that were discussed in the last Coq Call.

I think the new consortium page should be another toplevel page. For roadmap it is still a bit unclear to me how to handle it. After some more discussion after the Coq Call with Yves and Nicolas, I would like to propose a separate "Animation" team that would encompass responsibility for maintaining/animating the work on the roadmap (not about setting its contents but making sure it is up-to-date, communicating with the Core team, Consortium and interested parties) as well as community and scientific animation (e.g. workshop, working groups and CUDW/Rocq'n'code steering).

@Zimmi48
Copy link
Member

Zimmi48 commented Mar 8, 2025

I understand the point about removing the "governance" team if it only contained the core team, but now I don't know where we would put the new consortium and roadmap teams that were discussed in the last Coq Call.

I think the new consortium page should be another toplevel page. For roadmap it is still a bit unclear to me how to handle it. After some more discussion after the Coq Call with Yves and Nicolas, I would like to propose a separate "Animation" team that would encompass responsibility for maintaining/animating the work on the roadmap (not about setting its contents but making sure it is up-to-date, communicating with the Core team, Consortium and interested parties) as well as community and scientific animation (e.g. workshop, working groups and CUDW/Rocq'n'code steering).

Sounds good to me, but note that we already have the Community team which covers all of this except the roadmap: https://rocq-prover.org/rocq-team/community

So this team could be renamed into Animation and the sub-team about roadmap coordination could be added to it.

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

Successfully merging this pull request may close these issues.

3 participants