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
Agenda: Community Council (CC), 1 August 2023 #98
Comments
Since I might not be there during next meeting, some updates and opinions.
Proposed Agenda
The proposed protocol is basically the same as we do now with a few new changes. One, we now have a public channel so everyone can see the discussion and who votes in favor, against, or did not vote either. Yes, we should make it a habit to directly put transaction information on Github at the same time we make the transaction. Since asking merger for this all the time creates a lot of spam, I would propose to simply allow the Grin wallet maintainers to directly merge to keep things fast and smooth (besides, all changes/commits are clearly logged an can be reviewed by anyone at any time.
|
Solicit suggestions for agenda items for the Governance meeting to be held on Tuesday August 1 @ 10:00 UTC in grincoin#general channel on Keybase. Please comment to provide topics or suggestions.
(Meeting can be followed on @keybase-ro channel - GRIN community discord server via GRIN discord bridge).
To Do List.
Proposed Agenda
Suggestion for procedural changes related to CC payments.
For BTC txs:
Community support > CC Payment approved by alteast 4/6 in public CC chat > PR submitted > tx drafted> CC signing the tx > PR merged.
For Grin txs:
Community support > CC Payment approved by alteast 4/6 in public CC chat > PR submitted > PR merged by the CC member who made the payment.
**Since the grin wallet is not multi sig it's harder to keep track of, so the person making the payment needs to be the one who seeks approval to merge.
Discussion: Bounty for new GPU solver with better efficancy than a G1 mini.
The text was updated successfully, but these errors were encountered: