From 725816abc58c7dc5e06cda2c2025d55cfd5b4acf Mon Sep 17 00:00:00 2001 From: lehnberg Date: Sun, 26 May 2019 19:16:37 +0300 Subject: [PATCH 1/3] add May 21 governance notes --- README.md | 3 +- notes/20190521-meeting-governance.md | 95 ++++++++++++++++++++++++++++ 2 files changed, 97 insertions(+), 1 deletion(-) create mode 100644 notes/20190521-meeting-governance.md diff --git a/README.md b/README.md index bf0cf47..d67e67b 100644 --- a/README.md +++ b/README.md @@ -8,8 +8,9 @@ A chronological list of decisions made by the Grin project, with references. Ava ### 2019 Date | Topic | Agenda | Notes | Tl;dr |:---|:---|---|---|:---| +Jun 04 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/141) | Notes | | May 28 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/137)| Notes | | -May 21 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/134) | Notes | | +May 21 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/134) | [Notes](notes/20190521-meeting-governance.md) | Coinspect audit payment, Grin budget feedback, Wiki access control | May 14 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/126)| [Notes](notes/20190514-meeting-development.md) | v1.1.0, and future version planning, Hard fork, Http depreciation | May 07 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/115) | [Notes](notes/20190507-meeting-governance.md) | Budget, Transparency report, Simplified onboarding | Apr 30 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/111)| [Notes](notes/20190430-meeting-development.md) | i2p, v1.1.0 + CI, Git branching, Slate versioning | diff --git a/notes/20190521-meeting-governance.md b/notes/20190521-meeting-governance.md new file mode 100644 index 0000000..b8cffd5 --- /dev/null +++ b/notes/20190521-meeting-governance.md @@ -0,0 +1,95 @@ +# Meeting Notes: Governance, May 21 2019 + +Governance meeting held May 21 2019 @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grin/Lobby on Gitter](https://gitter.im/grin_community/Lobby), full chat transcript [here](https://gitter.im/grin_community/Lobby?at=5cd19dc12e2caa1aa6242bb3). Meeting lasted ~ 60 min. + +Notes are truncated, and conversations sorted based on topic and not always chronological. Quotes are edited for brevity and clarity, and not always exact. + +**Community attendance:** +* antiochp +* chisa0a +* davidburkett +* emptykeg +* garyyu +* hashmap +* ignopeverell +* jaspervdm +* kargakis +* lehnberg +* mcdallas +* quentinlesceller +* tromp +* yeastplume + + +_(apologies if I missed someone - open a PR or contact @lehnberg to add)_ + + +## Agenda points & Actions + +### 1. Agenda review +[Proposed agenda](https://github.com/mimblewimble/grin-pm/issues/134) accepted. + +### 2. Action point follow ups from previous meetings + +#### 2.1 Status of misc. /site improvements + +* _ignopeverell:_ I don't think anything new was done to the site, unless I missed something. + * _quentinlesceller:_ I could tackle the onboarding the issue this week. + +### 3. [Security audits](https://github.com/mimblewimble/grin/issues/1609) + +* _ignopeverell:_ We got the full report and had a few back-and-forths since then with Coinspect. They will update the report and review as we fix issues, several I believe have already been fixed. I'm personally satisfied with the work performed, the findings and report were solid. I think we should pay them the remainder of what we owe them. + * _kargakis:_ Will coinspect make it public, i.e. issue a press release, that they worked on the audit? + * _lehnberg:_ Dunno, we can ask them about this. + +#### Decision: Coinspect payment +The meeting agreed to pay the final 10.458 BTC installment for the audit work conducted by Coinspect. @lehnberg to obtain an address and also ask about jointly announcing the audit results. + +### 4. Funding status + +#### 4.1 2019 Budget +* _lehnberg:_ Relevant [issue](https://github.com/mimblewimble/grin-pm/issues/130). I insterted placeholder items in the budget to stimulate a discussion. Haven’t received much feedback or comments, would be great to have some more. + * _kargakis:_ It would be good to be consistent with how we mark payments: If they are one-off, they should be marked as such. + * _lehnberg:_ I agree, I should change that. + * _antiochp:_ Regarding my own situation, I am likely to be good for another 3 months, but I have no firm plans out beyond that. + * _lehnberg:_ Understood. + * _ignopeverell:_ Perhaps different color for cost already incurred? + * _lehnberg:_ Makes sense. + * _ignopeverell:_ We want all the devs we can get, but we're cheap and poor. We need help, but you shouldn't think about money too hard. There is still a ton of things to do, core things move slower but we have plenty of space for bug fixes, more user-friendly stuff, QoL, tests, etc. + * _lehnberg:_ It’s good to forecast, to get a sense of our current burn rate and also our runway. But maybe it’s pointless to do so? we can also be completely ad hoc and reactive, and just say “yes, we need more donations” and “yes, we need more developers" - “please contribute". + * _ignopeverell:_ Exactly. Don't think the budget is pointless though, it's just a good plan to have. + * _yeastplume:_ It's hard to put out a reasonable budget and cash flow predictions when there's zero regular income. + * _lehnberg:_ I just find it hard to say we need money if we got a big donation and can’t explain how we plan to use it. Even if the plan is wrong (doesn’t matter), it’s still better to be able to say “yes, we got a donation, but it will last us until x approximately, and then we’ll need more. so we need your help!" + * _yeastplume:_ Yes, so an 'indicative' budget is good to have and maintain, if lightly. + * _ignopeverell:_ Budget is just setting up a budget, not deciding all that's on it. We're not a company, we're a collective, it takes more time to get to those decisions and that's a good thing for this project + +_[... truncated]_ + +* _lehnberg:_ Okay so this was really helpful. I think I got an idea for the level / direction of the budget. We think a budget is good to have, but it should focus on existing/known spends, and not plan for future undecided items. It helps us keep track of our existing burn rate, rather than projected burn rate. I’ll work on it some more and circulate here again. And then we can look at moving it away from google sheets. + * _ignopeverell:_ Yes, and we can always add something to the discussion at some point that may (or may not) find its way into the budget. + +_Meeting agreed._ + +### 5. Promotion of other projects + +* _kargakis:_ We could consider adding a page that includes all promoters in the [grin presentation template]( +https://github.com/mimblewimble/grin-pm/tree/master/presentations/templates), then anyone presenting can potentially choose to include it in their slides and say a good word about the sponsors. + +### 7. Grin evangelism + +* _ignopeverell:_ I haven't heard anything new on Grin evangelism, other than meetups that keep happening like the one organized by @hashmap in Moscow. If you're thinking about doing a meetup in your own region, it's a great way to get more people interested. + + +### 8. Other questions + +#### 8.1 Wiki access control + +* _chisa0a:_ Some troll deleted the wallet docs last week. Prehaps we should set up some kind of access control? Even wikipedia has access control setup for a min threshold + reputation. + * _ignopeverell:_ Yeah, unfortunately, that's not available in github yet. It's easy to find and restore any attacks though no? + * _kargakis:_ Also, if one wants to help out, they can click Watch on mimblewimble/docs. Then every update on the wiki shows up in your activity. The deletion is obvious in the git history, the only problem is that you have to pull the wiki locally in order to see that. +* _chisa0a:_ Don't want to make a big issue of it if more experienced feel its a non-issue atm. + * _ignopeverell:_ Indeed, maybe we wait until we have at least a few occurrences of this before we make any changes that can stifle contribution. + +_Meeting agreed._ + +**Meeting adjourned.** From 5ea417818ed752fa1f9abc1bd3a62c2edd7945c8 Mon Sep 17 00:00:00 2001 From: lehnberg Date: Sun, 26 May 2019 19:17:40 +0300 Subject: [PATCH 2/3] fix: correct dev meeting note filename --- ...14-meeeting-development.md => 20190514-meeting-development.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename notes/{20190514-meeeting-development.md => 20190514-meeting-development.md} (100%) diff --git a/notes/20190514-meeeting-development.md b/notes/20190514-meeting-development.md similarity index 100% rename from notes/20190514-meeeting-development.md rename to notes/20190514-meeting-development.md From d8cdbf7717f80ad2db2d088a1eaef710c63115d5 Mon Sep 17 00:00:00 2001 From: lehnberg Date: Sun, 26 May 2019 19:27:22 +0300 Subject: [PATCH 3/3] update decision log --- decision_log.md | 1 + 1 file changed, 1 insertion(+) diff --git a/decision_log.md b/decision_log.md index 41c8b41..8e1e982 100644 --- a/decision_log.md +++ b/decision_log.md @@ -7,6 +7,7 @@ This document tracks decisions made by the Grin project and points to documentat ID | Date | Decision | Reference | |---|:---|:---|:---| +32 | 20190521 | Pay final Coinspect installment | [Meeting Note](notes/20190521-meeting-governance.md#decision-coinspect-payment) 31 | 20190409 | Funding for @lehnberg | [Meeting Note](notes/20190409-meeting-governance.md#decision-lehnberg-funding) 30 | 20190326 | Next steps in POW phase out discussion | [Meeting Note](notes/20190326-meeting-governance.md#decision-next-steps-regarding-phase-out-discussion) 29 | 20190326 | Treasury management of ETH | [Meeting Note](notes/20190326-meeting-governance.md#decision-treasury-management-of-eth)