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

Agenda: Community Council (CC), 1 August 2023 #98

Open
cekickafa opened this issue Jul 22, 2023 · 1 comment
Open

Agenda: Community Council (CC), 1 August 2023 #98

cekickafa opened this issue Jul 22, 2023 · 1 comment

Comments

@cekickafa
Copy link
Contributor

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.

  • Getting wallet information and wallet Txs output from @hendi.
  • Discuss and create predefined process ( that gets documented in the CC repo) for electing/ appointing new CC members moving forward.
  • Review of GrinCC/finance Repo.

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.

@Anynomouss
Copy link

Anynomouss commented Jul 30, 2023

Since I might not be there during next meeting, some updates and opinions.
#TO DO's

  • Getting wallet information and wallet Txs output from @hendi.
    I gave Hendi another ping requesting the trx wallet JSON output, so we can verify. Update: he told me 16th of August he would be at the facility where the wallet is, so I will get Trx overview then

  • Discuss and create predefined process ( that gets documented in the CC repo) for electing/ appointing new CC members moving forward.
    I created a draft election guidelines document after discussing it with Mac, now it needs proper reviewing and input from other CC members

  • Review ofhttps://github.com/Funding payment & spending Log Update, GRINCC wallet corrections, Transparency Reports additions. finance#14#commits-pushed-e181a84 Repo.
    We have enough reviews to merge since Ceky counts as reviewer, but still asked Mike if he is also ok with merging since that would be nicer.

Proposed Agenda

  • Suggestion for procedural changes related to CC payments.

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.

  • Discussion: Agenda: Community Council (CC), 18 July 2023 #96 (comment)
    Personally I believe ASICS are and will be the future of Grin, simply because of energy efficiency and better protection against 51 attacks. Not against such a bounty, but neither much in favor of spending CC funds on this. Regarding bounty proposals, I have four bounty proposals [1],[2],[3] ,[4] on the forum that could use some community input and endorsement. Note that some in the community specifically asked for more bounties, well then they should look at and discuss these proposals

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

No branches or pull requests

2 participants