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: Governance, Mar 12 2019 #71

Closed
2 of 3 tasks
lehnberg opened this issue Mar 1, 2019 · 5 comments
Closed
2 of 3 tasks

Agenda: Governance, Mar 12 2019 #71

lehnberg opened this issue Mar 1, 2019 · 5 comments
Labels
governance Anything related to governance meetings Anything related to meetings

Comments

@lehnberg
Copy link
Collaborator

lehnberg commented Mar 1, 2019

Solicit suggestions for agenda items for the Governance meeting to be held on Tuesday Mar 12 @ 15:00 UTC in Gitter main lobby. Please comment to provide topics or suggestions.

Proposed agenda

  1. Agenda review
  2. Action point follow ups from previous meeting
    • @lehnberg fund spending transparency report created?
    • @antiochp funding processed?
    • Audit initiated?
  3. Security audit status
  4. CVE-2019-9195
    1. Current network status
    2. What went well
    3. What could be improved
    4. Questions
    5. Insights
  5. Treasury management
    1. Policy of how to keep funds? Do we convert a portion into BTC? Should we try to hedge against volatility?
    2. ETH donation address
    3. Income/Spending logs, adding entries
    4. Quarterly/monthly reports?
  6. Promotion of other projects
  7. Continuation of Gary Yuu's proposal to hire developers
  8. Risk mgmt brainstorm
  9. Other questions
@lehnberg lehnberg added meetings Anything related to meetings governance Anything related to governance labels Mar 1, 2019
@antiochp
Copy link
Member

antiochp commented Mar 6, 2019

Funding (@antiochp) not yet processed. Currently on hold (update coming shortly).

@garyyu
Copy link
Contributor

garyyu commented Mar 10, 2019

1.fund spending transparency report moving to site repo instead of https://github.com/mimblewimble/grin-pm/blob/master/financials/income_log.csv

to avoid 2 PRs (one for site and one for grin-pm) to add/modify the FoG page of site: (demo version:) https://nijynot.github.io/site/friends

2.Continue incomplete topic in last governance meeting: https://github.com/mimblewimble/grin-pm/blob/master/notes/20190226-meeting-governance.md#7-gary-yuu-proposal-to-hire-developers

Ref:
https://gitter.im/grin_community/Lobby?at=5c7566182ca5ec5474439fd6

Gary Yu @garyyu Feb 27 00:15
don’t forget this one:

and do we need vote here for Igno also? once the funding pool is enough, we can go same as Antioch for Igno?

Ignotus Peverell @ignopeverell Feb 27 00:15
@garyyu how about giving this one until next meeting?
baby steps and all

Gary Yu @garyyu Feb 27 00:17
Okay, if that’s better

@lehnberg
Copy link
Collaborator Author

Agenda updated: Clarified and expanded on some points.

Thanks @garyyu, I've added your second point.

Question regarding the first point (income_log.csv): As per the leaderboard PR, the leaderboard actually reads straight from the csv file in /grin-pm. So is this still a relevant issue? Would you still like to discuss moving our financial reporting into /site?

@ignopeverell
Copy link
Contributor

My personal situation has eroded a bit over the past few months and is not as cushy as it used to be. So I'm planning on moving forward and asking for funding during this meeting. If the vote is positive, I'd be more than happy to accept Grins (to address that treasury management issue). I think it'd be a good thing for the project if I'm directly exposed to it as my livelihood.

@antiochp
Copy link
Member

I can provide a limited update on my situation. My client is still not willing to be made public though - we have some things to work through there (working on getting this made public).

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

No branches or pull requests

4 participants