Skip to content

update governance after election and add discourse team #5238

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

Merged
merged 3 commits into from
Jan 7, 2022
Merged

Conversation

OriolAbril
Copy link
Member

@OriolAbril OriolAbril commented Dec 4, 2021

Follow up of https://discourse.pymc.io/t/steering-council-election-results/8391

Maybe I should have splitted the PR in two but I have not. The request discussion label is not for the election results but for the team permissions and so on we defined, do we want to enforce that? Should we change it or remove it instead? We should probably make sure everyone is listed as part of the teams they want and in the roles they should have.

Note that after merging this PR I'll do my best to enforce it, so things not being right here will probably mean people losing access or permissions they should still have.

@codecov
Copy link

codecov bot commented Dec 4, 2021

Codecov Report

Merging #5238 (355b920) into main (95bd5e5) will increase coverage by 0.07%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #5238      +/-   ##
==========================================
+ Coverage   78.94%   79.02%   +0.07%     
==========================================
  Files          88       87       -1     
  Lines       14237    14376     +139     
==========================================
+ Hits        11240    11360     +120     
- Misses       2997     3016      +19     
Impacted Files Coverage Δ
pymc/backends/ndarray.py 79.64% <0.00%> (-9.74%) ⬇️
pymc/bart/utils.py 82.60% <0.00%> (-5.92%) ⬇️
pymc/backends/report.py 89.51% <0.00%> (-2.10%) ⬇️
pymc/distributions/dist_math.py 86.78% <0.00%> (-0.92%) ⬇️
pymc/sampling.py 86.23% <0.00%> (-0.57%) ⬇️
pymc/gp/gp.py 93.18% <0.00%> (-0.43%) ⬇️
pymc/smc/smc.py 97.89% <0.00%> (-0.41%) ⬇️
pymc/backends/arviz.py 89.16% <0.00%> (-0.40%) ⬇️
pymc/plots/__init__.py 95.65% <0.00%> (-0.19%) ⬇️
pymc/util.py 74.83% <0.00%> (-0.17%) ⬇️
... and 14 more

@OriolAbril
Copy link
Member Author

main todo: add community team membership indicators

@cluhmann
Copy link
Member

cluhmann commented Dec 9, 2021

I think there may be related changes needed to docs/community_diagram.png to bring it inline with these changes?

@OriolAbril
Copy link
Member Author

I think there may be related changes needed to docs/community_diagram.png to bring it inline with these changes?

I think the idea is still clear enough? I can do it but I'd rather do it after a while in case we end up creating some more teams like pymcon one maybe

@canyon289
Copy link
Member

@junpenglao @fonnesbeck any comment, if not lets merge this in 72 hours

@OriolAbril
Copy link
Member Author

Let's make it 6 better maybe, 3 days would include only 31st, 1st and a Sunday. I wouldn't expect anyone to answer really

@fonnesbeck
Copy link
Member

Looks great. Just one clarification requested and a couple of nit-picks.

@twiecki twiecki merged commit 4e378ca into main Jan 7, 2022
@twiecki twiecki deleted the post_election branch January 7, 2022 09:56
@OriolAbril
Copy link
Member Author

The PR didn't yet reflect what we discussed at the meeting yesterday. I'll open a follow up to fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants