diff --git a/20210609-meeting-governance.md b/20210609-meeting-governance.md new file mode 100644 index 0000000..6b804a3 --- /dev/null +++ b/20210609-meeting-governance.md @@ -0,0 +1,113 @@ +# Meeting Notes: Development, June 01 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#general channel on Keybase](https://keybase.io/team/grincoin). Meeting lasted ~ 50min. + +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:** +- joltz +- geneferneau +- defistaker +- mcmmike +- hendi +- vegycslol +- jankie1800 +- cekickafa +- phyro +- quentinlesceller +- mark_hollis +- tromp +- dburkett + + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions +### 1. Action follow-up +- _joltz:_ + +### 2. Agenda review +The [proposed agenda](agenda for dev meeting later today - https://github.com/mimblewimble/grin-pm/issues/427) was accepted without changes. + +### 3. Bounty statuses / status update from mark_hollis +- _joltz:_ First up we have bounty statuses. @mark_hollis has been working on ledger support. His latest update is https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/17 Not a ton to note there, looking forward to seeing how the next couple of weeks go- Anything you want to call out there @geneferneau ? + +### 4.RFC update +- _joltz:_ For RFCs it looks like we currently only have one active https://github.com/mimblewimble/grin-rfcs/pull/80 Succinct Atomic Swaps +seems like lots of good discussion is going on there and progress is continuing +- _geneferneau:_ Just working on multiparty outputs. Still discussing some corner cases with SAS transactions. +- _joltz:_ sounds good, excited to see what kind of multiparty we end up wit +- _geneferneau:_ yeah, the multiparty part should be the same regardless. discussion is over whether to add adaptor signature to the Grin Timeout transaction + +### 5. Community funding status for @geneferneau & @mwgrin-fr https://forum.grin.mw/t/request-for-funding-gene-adaptor-signature-atomic-swaps-grn-btc/8632/13 +- _joltz:_ This brings us to community funding status for @geneferneau. I think you are owed payment for May and you are now seeking a continuation for June? Does anyone have any opposition or concern related to Gene's request that they'd like to share here? +- _phyro:_ I'd like him to continue to contribute πŸ‘ +- _dburkett:_ It's good to have @geneferneau around. I've been reading his updates, but haven't been following the RFCs & code as closely as @tromp and @phyro. If they are happy with his progress, then I am on board with continuing his funding πŸ‘ +- _tromp:_ i'm ok with continued funding but do want to see more work on the RFC that are still lacking in detail- for instance, are all the prepared txs done with multiple separate slatepacks (and if so how ,exactly are these communicated back and forth) or will there be a multi-tx slatepack. finally, i'm not a fan of the "atomic nonce" terminolog- just "secret" as in S.A.S. was fine. + - _geneferneau:_ I definitely plan to add more detail to the RFC, including changes to Slate-currently, the setup I have coded uses multiple slates +if everything was with one slate, it would take many rounds (16?) the flow is somewhat non-linear, too +- _joltz:_ Ok it sounds like we will complete Gene's payment for May and continue funding for June πŸ‘ We can continue the technical conversation in the RFC. + +- _joltz:_ Moving on, there is another funding request https://forum.grin.mw/t/request-for-funding-mwgrin-fr/8888 to make onboarding videos for Grin +Personally, I think it's a better idea for the community fund. +- _hendi:_ I agree, and also second Anynomous' post from 4w ago (example first, then funding) +- _tromp:_ i'd be happy to consider funding if we see some good example videos first + - _pyro:_ I think an example video was uploaded btw + - _mcmmike:_ yes, https://streamable.com/mzayob - I recomend zooming into the terminal a bit more, but these are details we can discuss later. +- _cekickafa:_ he done some vids.i seen.He fits for thisπŸ‘ +- _jankie1800:_ It looks like tech documentation. Is this more effective than the github install instructions? Only issue with video tech documentation is that it doesn't age well with updates that may change the terminal cmds + - _grindoggo:_ Just have to keep updating the videos honestly, and tag the videos with (2021 documentation) or something like that +- _tromp:_ but there's no accompaying narrative. i'd like to see an example with audio explanation as well +- _geneferneau:_ if the videos are CC-BY-SA, another community member could add audio, too + +- _joltz:_ Great it sounds like we have some good feedback and interest for supporting their work,Ok, it sounds like the feedback is to share some examples with the community before pursuing funding, regardless of the approach let's see the next round goes and hopefully we can get some quality videos for Grin πŸš€ + +### 6. Council asset audit (followup) +- _joltz:_ Next we have council asset followup. To take things a bit further I've made a proposal and some clarifications at https://forum.grin.mw/t/council-evolution-clarification/9021 +The main takeaways: +- council updates fund key holders to ensure everyone is active +- council provides regular proofs of spendability +- community takes over meetings +I think this helps provide some clarity and certainty around the majority of the concerns and hopefully helps give us a clean way forward as a community while we try to have less and less reliance on council as a point of failure +Will give us a bit to take a look and digest +- _jankie1800:_ question on point 3: Will core be taking future donations? and how will core/rust continue operations + - _joltz:_ the council may take future donations if they want. the council itself is only responsible for operations related to the fund. the repo/rust operations continue as they have since RFC0016, when the operations became responsibility of individual contributor teams and not "core" +- _defistaker:_ who are community Individual Contributors (ICs)? Contributors like mark_hollis, or community council members? + - _joltz:_ all of us are IC's + - _geneferneau:_ I like being an integrated circuit + +- _dburkett:_ How will funding requests to the OC be handled? also, the decision process in particular. Will that be public? + - _joltz:_ In the forum as per the funding guidelines RFC (which is probably due an update) but my hope is to improve the process at some point to make it even more clear, efficient and transparent. Maybe all in a dedicated github repo? As I'm proposing yes it would just happen all in the forum thread- + - _vegycslol:_ Is proof of spendability enough? If it's a 4 of 6, then that means that even if you are only 4 left it's going to seem like everything is fine when the reality is that someone could randomly lose key (i avoided die :D) + - _joltz:_ The proof itself can take many forms, I think that is still open + +- _joltz:_ It might feel like these are big changes, but I think zoomed out, it just makes the process around council funds more reliable and transparent and brings the community council and original council to as equal footing as possible by giving ownership of the meeting time/space over to the community +And hopefully the clarifications around how repos work etc will help us stay on the same page as a community going forward + - _phyro:_ so there will be no scheduled meetings unless someone creates an issue on the github? +as in, the current format dies unless someone picks it up + - _joltz:_ correct, it's just no longer responsibility of "council". it's now our responsibility as a community. but any one of us here can pick it up + - _geneferneau:_ I thought there was discussion about switching to one bi-weekly meeting? or is this only about community meetings? + - _phyro:_ there was, if I recall correctly, we wanted to merge both gov/dev meetings into a single bi-weekly. This is changed with this and suggests that this will take place if someone steps up and organizes and leads them + +- _mcmmike:_ its time for us now to organize and help with meetings,agenda, transcripts etc - I would suggest to keep the same timetable for gov-meetings and we from the CC agreed to attend the gov meetings at least one of us "all" the time. if there are no OC topics we have the bi-weekly CC meetings then +I would suggest to keep the same timetable for gov-meetings and we from the CC agreed to attend the gov meetings at least one of us "all" the time. + - πŸ‘: _grindoggo, _cekickafa, _geneferneau, _defistaker, _jankie1800 + +- _joltz:_ So in some ways this is a bittersweet meeting. Have been here every tuesday since we moved to keybase and hope to continue to see everyone on tuesdays. But sometimes you have to give up some control to have the right outcomes, and I think this is an example of that- I'm looking forward to seeing what we can accomplish together as one of the only truly community-driven project πŸš€ Thanks to everyone for participating in these over the last couple of years, I'm really excited to be a part of our continued evolution + + +###Other Questions +- _joltz:_ With that, are there any other questions that we want to bring up today?:) + +- _grindoggo:_ I'm not sure if this is my place but I wanted to mention Renzokuken's suggestion: keybase://chat/grincoin#community_fund/1582 / In short, he suggested a negligible funding to test the communication of the funding council. + - _joltz:_ Yes I totally forgot to highlight that, Slatepacks marketplace looks amazing! Kudos to everyone working on it + - _grindoggo:_ Well it doesn't necessarily need to have to be with that marketplace, it can be anything negligible probably + +- _phyro:_ decentralize the newsletters πŸš€ + +- _joltz:_ Ok, meeting over. Thanks again everyone for your energy and time today. Hope to see you all in the first meeting we put together as a community! + +**Meeting adjourned.** diff --git a/README.md b/README.md index 5bda81a..00453f9 100644 --- a/README.md +++ b/README.md @@ -25,9 +25,18 @@ Steps to be completed as part of every node or wallet release. Available [here]( Date | Topic | Agenda | Notes | Tl;dr |:---|:---|---|---|:---| -Apr 06 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/412)| | | -Mar 30 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/410)| | | -Mar 23 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/408)| [Notes](notes/20210323-meeting-development.md) | BP Vulnerability, Bug bounties, 5.1.0 release | +Jun 09 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/427) | [Notes](notes/20210609-meeting-governance.md) | Bounty Status, Core-Council Ending Public Meetings, Community Funding Status, Council Asset Audit | +Jun 01 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/424) | [Notes](notes/20210601-meeting-development.md) | 5.1.0 Release Update, Atomic Swap Update, Ledger Hardware Update, Tor Bridge Discussion, Introducing Changelog.md | +May 25 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/422) | [Notes](notes/20210525-meeting-governance.md) | Bounty Statuses, RFC Update, Community Funding Status, Council Asset Audit, Funding Request + Addressing Community Contributions | +May 18 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/419) | [Notes](notes/20210518-meeting-development.md) | Atomic-Swaps Bounty with @geneferneau, 5.1.0 Release, Ledger-Integration Update w/ @mark_hollis | +May 11 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/420) | [Notes](notes/20210511-meeting-governance.md) | Ledger-Integration Update w/ @mark_hollis, Atomic-Swap Update w/ @geneferneau, RFC Updates, Community Funding Status, Council-Funding Audit | +May 04 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/419) | [Notes](notes/20210504-meeting-development.md) | Ledger Support Bounty Update w/ @mark_hollis, 5.1.0 Release-Update | +Apr 27 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/418) | [Notes](notes/20210427-meeting-governance.md) | Ledger Support Moves Forward with Mark_Hollis, Community Funding | +Apr 20 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/416) | [Notes](notes/20210420-meeting-development.md) | Fix-past-fees, 5.1.0 Release-Update | +Apr 13 | Governance | [Agenda](notes/20210413-meeting-governance.md) | [Notes](notes/20210413-meeting-governance.md) | Community Fund Public Announcement, Fix-past-fees | +Apr 06 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/412) | [Notes](notes/20210406-meeting-development.md) | FCP, secp256k1-zkp Rebase | +Mar 30 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/410)| [Notes](notes/20210330-meeting-governance.md) | Atomic Swap, Community Council Application | +Mar 23 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/408) | [Notes](notes/20210323-meeting-development.md) | BP Vulnerability, Bug bounties, 5.1.0 Release-Update | Mar 16 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/403)| [Notes](notes/20210316-meeting-governance.md) | Ledger bounty, Community funding | Mar 09 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/400)| [Notes](notes/20210309-meeting-development.md) | Bug bounties, libsecp fork, PR cleanup, 5.1.0 release, archival nodes | Mar 02 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/398)| [Notes](notes/20210302-meeting-governance.md) | Send ASIC to Hendi, Community funding | @@ -48,15 +57,15 @@ Jan 05 | Hybrid | [Agenda](https://github.com/mimblewimble/grin-pm/issues/378)| Date | Topic | Agenda | Notes | Tl;dr |:---|:---|---|---|:---| Dec 22 | Hybrid | [Agenda](https://github.com/mimblewimble/grin-pm/issues/376) | [Notes](notes/20201222-meeting-development.md) | @dtavarez funding request, v5.0.0 planning, Naming, API listening on 0.0.0.0 | -Dec 15 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/374)| [Notes](notes/20201215-meeting-governance.md) | Holiday planning, Lehnberg Q1 2021 funding, PIBD RFC | +Dec 15 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/374) | [Notes](notes/20201215-meeting-governance.md) | Holiday planning, Lehnberg Q1 2021 funding, PIBD RFC | Dec 08 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/372) | [Notes](notes/20201208-meeting-development.md) | Slatepack, v5.0.0 planning, Naming, API listening on 0.0.0.0 | -Dec 01 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/370)| [Notes](notes/20201201-meeting-governance.md) | Slatepack, Fund for mining proposal, HTTPs deprecation, PIBD RFC | +Dec 01 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/370) | [Notes](notes/20201201-meeting-governance.md) | Slatepack, Fund for mining proposal, HTTPs deprecation, PIBD RFC | Nov 24 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/368) | [Notes](notes/20201124-meeting-development.md) | Slatepack, Testnet, Re-org attack, v5.0.0 planning review | -Nov 17 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/366)| [Notes](notes/20201117-meeting-governance.md) | Slatepack, HTTPs deprecation, PIBD RFC | +Nov 17 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/366) | [Notes](notes/20201117-meeting-governance.md) | Slatepack, HTTPs deprecation, PIBD RFC | Nov 10 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/363) | [Notes](notes/20201110-meeting-development.md) | Testnet mining, Re-org attack, v5.0.0 planning review | -Nov 03 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/360)| [Notes](notes/20201103-meeting-governance.md) | Council accountability, HTTPs deprecation | +Nov 03 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/360) | [Notes](notes/20201103-meeting-governance.md) | Council accountability, HTTPs deprecation | Oct 27 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/358) | [Notes](notes/20201027-meeting-development.md) | v5.0.0Β updates & risk mitigations, testnet mining | -Oct 20 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/355)| [Notes](notes/20201020-meeting-governance.md) | @jaspervdm funding request, RFC reviews, Council accountability | +Oct 20 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/355) | [Notes](notes/20201020-meeting-governance.md) | @jaspervdm funding request, RFC reviews, Council accountability | Oct 13 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/353) | [Notes](notes/20201013-meeting-development.md) | Re-org monitoring, v5.0.0Β scope freeze, Grin-Pi | Oct 06 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/351)| [Notes](notes/20201006-meeting-governance.md) | QA Funding request, @lehnberg funding request, deprecating http(s), floonet, RFC reviews | Sep 29 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/348) | [Notes](notes/20200929-meeting-development.md) | re-org risk monitoring, v5.0.0Β planning, slatepack adoption | @@ -148,7 +157,7 @@ Mar 26 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/87 Mar 19 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/77)| [Notes](notes/20190319-meeting-development.md) | TravisCI alternatives, v1.1.0 release date, v1.0.3 release, Hard fork timeline and process | Mar 12 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/71)| [Notes](notes/20190312-meeting-governance.md) | Funding for Igno, CVE-2019-9195 post-mortem, Treasury management | Mar 05 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/68)| [Notes](notes/20190305-meeting-development.md) | v1.1.0 planning, nightly builds, rust-secp release | -| Feb 26 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/66)| [Notes](https://github.com/mimblewimble/grin-pm/blob/master/notes/20190226-meeting-governance.md)| PR approach, Funding for Antioch | +| Feb 26 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/66)| [Notes](https://github.com/mimblewimble/grin-pm/blob/master/notes/20190226-meeting-governance.md)| PR approach, Funding for Antioch | Feb 19 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/63)| [Notes](https://github.com/mimblewimble/grin-pm/blob/master/notes/20190219-meeting-development.md) | v1.0.2 release, Error management | Feb 12 | Governance | [Agenda](https://github.com/mimblewimble/grin-pm/issues/58) | [Notes](https://github.com/mimblewimble/grin-pm/blob/master/notes/20190212-meeting-governance.md) | Decision on security audit firm, Friends of Grin, Risk mgmt | Feb 05 | Development | [Agenda](https://github.com/mimblewimble/grin-pm/issues/56)| [Notes](https://github.com/mimblewimble/grin-pm/blob/master/notes/20190205-meeting-development.md) | http deprecation, wallets | diff --git a/notes/20210330-meeting-governance.md b/notes/20210330-meeting-governance.md new file mode 100644 index 0000000..11af499 --- /dev/null +++ b/notes/20210330-meeting-governance.md @@ -0,0 +1,108 @@ +# Meeting Notes: Governance, Mar 30 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#general channel on Keybase](https://keybase.io/team/grincoin). 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:** +- lehnberg +- defistaker +- antiochp +- jabfalter +- cekickafa +- geneferneau +- phyro +- trevyn +- joltz +- anynomous + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda Points & Actions + +### 1. Retrospective + + + +### 2. Agenda review +The [proposed agenda](https://github.com/mimblewimble/grin-pm/issues/410) was accepted without changes. + +### 3. Action point follow ups from previous meetings +- _lehnberg:_ spending log has not been updated, we have another spend coming in shortly (details tba) so can update both in the same go + + +### 3. @geneferneau Adaptor Signature Atomic Swap BTC <> GRIN + +- _lehnberg:_ Time-line estimate: ~3-4 months for a minimum-viable-product. +Funds: 40.000 EUR equivalent in BTC, based on the 60-day rolling average 6 at the time of payout. + +- _antiochp:_ can we clarify the funding request (amount) in the context of the discussed timeline? + - _geneferneau:_ definitely, when submitted I was estimating on a 10.000 EUR per month rate + +- _lehnberg_ would you be open to consider month-by-month payments? + - _geneferneau:_ absolutely open to month-by-month payments, and to negotiating the rate + +- _lehnberg_ So we agree in principle today, which gets gene started? and then end of month he submits an update and gets paid? + - πŸ‘:_dburkett, _jabfalter, _anynomous, _defistaker, _vegycslol, _tromp + - _lehnberg:_ yeah if @geneferneau is happy with this setup let's do it + - _geneferneau:_ absolutely, thank you all so much for the opportunity + - _lehnberg:_ play- I consider this accepted - congrats! + +### 4. @trevyn Request for funding:[https://forum.grin.mw/t/request-for-funding-tr evyn-apr-2021/8641] +- _lehnberg:_ 1month funding April 2021, 10k EUR, the floor is open for questions + +- _phyro:_ do you plan any longer periods after april? + - _trevyn:_ i would like to, yes. i thought it best to spend april getting a better sense of the sections of code that i'd like to work on, so i can make a more specific funding request :) + +- _antiochp:_ just want to say thanks again @trevyn for rolling sleeves up and getting involved in various PRs on github + - _phyro:_ I honestly have a feeling you'd be a great candidate for long-term- which would include diving deep into, mw, node, wallet + +- _lehnberg:_ seems like this is another request with a consensus in favour. any objections, now's the time to voice them; + +- _dburkett:_ Can we still get detailed updates? + - _trevyn:_ of course, I was expecting to do that anyway! + +- _lehnberg:_ okay - up front payment, 1 month, 10k EUR β†’ approved! congrats + - πŸ‘: _joltz, _quentinlesceller, _dburkett, _geneferneau, _antiochp, _quentinlesceller, _anynomous, _setsuko, _cekickafa, _antiochp, _defistalker, _trvyn, _phyro + +### 5. TradeOgre Compensation [https://forum.grin.mw/t/recompensate-tradeogre/8657) +- _lehnberg:_ β†’ has anyone been able to verify this happened? +- _antiochp:_ Impossible to verify, but he did tell multiple people +- _joltz:_ it is a risky precedent. what happens if an exchange loses more than our fund? are we expected to pay for every ecosystem loss? what if blame is not as straightforward etc +-_quentinlesceller:_ Seems like there is no proof right now and no demand from TO +-_pyhro:_ it's an unfortunate situation, but I'm not convinced the grin fund should be used for such compensations. Those that use TO could help with donations +-_lehnberg:_ okay - so there seems to be no strong support in favour of this. is that correct? + - πŸ‘: _joltz, _quentinlesceller, _dburkett, _geneferneau, _antiochp + +### 6. Community Funding +- _lehnberg:_ with AlexGSG's recent application I count 9 applicants in total +would be great to see some more + - _mcmmike:_ let see if we can motivate a few more people , but 9 is not bad for now . As this would be a long-term comitment if someone will join in. + +- _lehnberg:_ okay so what will happen is: +1. council reviews applications +2. council agrees on a proposal +3. council selects mu-sig participants based on applicants? +did I get that right? +where is all this happening? are we supposed to discuss this in open? I'd rather not evaluate candidates in public + - _antiochp:_ seeing as people ended up getting banned from various communication channels last time I suggested discussing in private we should decide up front if this will indeed be private + - _dburkett:_ No need for public discussion of candidates, but I would expect an explanation of why a particular proposal was chosen? + - πŸ‘: _mcmike, antiochp_ + - _lehnberg:_ that definitely sounds fair + - πŸ‘: _dburkett, _anynomous, _mcmmike, _geneferneau + +- lehnberg:_ okay! council members, let's try to be reasonably fast for once and get this wrapped up in two weeks. + +### 5. RFC Update +- lehnberg:_ since there's no RFC updates, this is then an excellent segue into our first other question, which is... that I'm planning to take a bit of a break, and have asked @joltz to lead the governance meetings moving forward, which he's kindly agreed to. + +### 6. Other questions +_None._ + + + + +**Meeting adjourned.** diff --git a/notes/20210406-meeting-development.md b/notes/20210406-meeting-development.md new file mode 100644 index 0000000..2bd3f16 --- /dev/null +++ b/notes/20210406-meeting-development.md @@ -0,0 +1,44 @@ +# Meeting Notes: Development, Apr 06 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#dev channel on Keybase](https://keybase.io/team/grincoin). Meeting lasted ~ 45 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 +- geneferneau +- trevyn +- joltz +- tromp + + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + +## Agenda points & Actions +### 1. Retrospective +- _antiochp:_ effort has been focused on work post emergency HF +and in parallel the secp256k1-zkp rebase + +### 2. Agenda review +The [proposed agenda](https://github.com/mimblewimble/grin-pm/issues/412) was accepted without changes. + +### 3. Action point follow ups from previous meetings + +### 3. "fixpastfees" RFC -> FCP +- _antiochp:_ FCP is 2 weeks and then assuming no big changes the PRs are basically ready to go immediately after that + +### 4. 5.1.0 release +- _antiochp:_ the known big changes for 5.1.0 are summarized [here -](https://github.com/mimblewimble/grin/issues/3605) (all post HF improvements etc.) +still a little bit of work to do on cleaning up this - (https://github.com/mimblewimble/grin/pull/3618) +if anyone wants to play around with it then please feel free +so 5.1.0 is still tentative, no hard deadline +but its not far off, maybe a couple of weeks (plus some testing) + +### 6. Other questions +_None._ + + + + +**Meeting adjourned.** diff --git a/notes/20210413-meeting-governance.md b/notes/20210413-meeting-governance.md new file mode 100644 index 0000000..67b6854 --- /dev/null +++ b/notes/20210413-meeting-governance.md @@ -0,0 +1,81 @@ +# Meeting Notes: Governance, Apr 13 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#general channel on Keybase](https://keybase.io/team/grincoin). Meeting lasted ~ 50 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:** +- cekickafa +- phyro +- quentinlesceller +- mcmmike +- antiochp + + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions + +### 1. Retrospective +- _joltz:_ status of spending log updates? + - _antiochp:_ no blockers that I know of - just need to spend some time on it + + + +### 2. Agenda review +The [proposed agenda](link::here) was accepted without changes. + +### 3. Action point follow ups from previous meetings + - Spending log// + + +### 4. Bounty Statuses @ quentinleseceller +- _quentinlesceller:_ Latest update I got from @mark_hollis is the following: +"I'm currently looking at the default lifecycle provider. I think I need a custom implementation for the hardware wallet. +The main task I'm now looking into is how grin-wallet could initialize a wallet using a device. I've added a CLI subcommand." - Last tuesday. Will ping him today. + +- _quentinlesceller:_ Update regarding Ledger bounty (https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/5?u=quentinlesceller) + + +### 5. Community Fund +- _joltz:_ My understanding of current state of community fund decision making: + - "Split Fund" proposal seems to come closest to council's preferences + - 4 strong candidates have council consensus, the remaining 2 seats do not have clear support + - Asking community for 1 more week for candidates to come forward for remaining 2 seats in "split fund" proposal + - After 1 week, a forum member vote (accounts must have been made before initial candidate announcement) will be held to indicate preference between 2 remaining candidates + - Hope that we have enough viable candidates for the "split fund" proposal to move forward + +- Not a major update, the decision making process is still ongoing. + + +### 5.1 Community Fund Announcement +- _mcmmike:_ I would like, once we agreed on the candidates to have a public announcment where we (or you as a council) descibe what we have done and what the community fund will be used for. This is more like a "press release" because I am getting a lot of questions regarding the history of this community-funds on why it exists, etc. its important to put it into context I think for the public + - πŸ‘: _renzokuken, _goyle, _defistalker, _ollx2070, _quentinlesceller + +- _joltz:_ I think it would be a good idea to have a high-level post describing this change in context of community, ecosystem, technology etc. Feel free to start on that post and I am happy to help as you go. Then maybe we can open it up to more feedback before posting it etc It is such a big change it will be nice to explain the changes and benefits clearly for both new and existing community members +If anyone else would like to contribute to that please ping @mcmmike + + + +### 6. RFC Update (https://github.com/mimblewimble/grin-rfcs/pull/77) + +- It is in Final Comment Period so please review and make any comments if you have not already. Barring anything unforseen it will likely be accepted and merged April 20 + + + + + +### 7. Funding Request @ antiochp +[here](https://forum.grin.mw/t/request-for-funding-antioch-apr-jun-q2-2021/871) +- Consensus to approve @ antiochp funding request for q2 2021 passed: + - πŸ‘:_dburkett, _renzokuken, _goyle, _defistalker, _ollx2070, _quentinlesceller, _mcmmike, _cekickafa, _geneferneau, _phyro, _tromp, _defistalker, _dtavarez, _unpourtous + +### 7. Other Questions + + + + +**Meeting adjourned.** diff --git a/notes/20210420-meeting-development.md b/notes/20210420-meeting-development.md new file mode 100644 index 0000000..6366a43 --- /dev/null +++ b/notes/20210420-meeting-development.md @@ -0,0 +1,59 @@ +# Meeting Notes: Development, Apr 20 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#dev channel on Keybase](https://keybase.io/team/grincoin). Meeting lasted ~ 50 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 +- geneferneau +- trevyn +- joltz +- tromp +- defistaker +- quentinlesceller +- deeev + + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions +### 1. Retrospective +- _antiochp:_ effort has been focused on work post emergency HF +and in parallel the secp256k1-zkp rebase + +### 2. Agenda review +The [proposed agenda](agenda for dev meeting later today - https://github.com/mimblewimble/grin-pm/issues/416) was accepted without changes. + +### 3. Action point follow ups from previous meetings +- Triage / GitHub cleaning is is ongoing with @ phyro. + - _phyro:_ I would like to add that we need more people looking at the grin-wallet. Right now we ping quentin for most things, but it's quite a lot and things. We may be moving a bit slow on that repo imo + +- "fixpastfees" RFC -> FCP + - _joltz:_ fee_shift RFC should be out of FCP today and ready to accept (with a minor review last minute by me) (https://github.com/mimblewimble/grin-rfcs/pull/77) + +- _antiochp:_ @quentinlesceller; how's the libsecp work looking? + - _quentinlesceller:_ going well. Still need to figure out one test. I think i'll do another branch closer to upstream based on the reviews I got so far. +No ETA but the biggest part is done. + +- _antiochp:_ I still want to get https://github.com/mimblewimble/grin/pull/3618 in for 5.1.0 but other than that i don't think there is anything blocking it right now so I think we can probably aim for later this week to at least cut an initial build for 5.1.0 +(if anybody wants to test/review said PR then please) + +### 4. 5.1.0 release +- _antiochp:_ Are there any other PRs outstanding for 5.1.0? + - _quentinlesceller_ The wallet side there is (https://github.com/mimblewimble/grin-wallet/pull/593) - Which need more testing. I can do some extensive tests during the week. + - _antiochp:_ I owe you a review on that one. + +### 5 Bounty Updates +- _quentinlesceller:_ next week bounty updates will be provided. + +### 6. Other questions +_None._ + + + + +**Meeting adjourned.** diff --git a/notes/20210427-meeting-governance.md b/notes/20210427-meeting-governance.md new file mode 100644 index 0000000..b942e2b --- /dev/null +++ b/notes/20210427-meeting-governance.md @@ -0,0 +1,85 @@ +# Meeting Notes: Governance, Apr 27 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#general channel on Keybase](https://keybase.io/team/grincoin). 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 +- geneferneau +- trevyn +- joltz +- tromp +- phyro +- quentinlesceller +- mcmmike +- mark_hollis +- vegycslol +- hendi +- goyle +- cekickafa +- defistaker +- renzokuken + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions +### 1. Retrospective +- _joltz:_ Action points have been followed up on from last time. Anything new in Bounty Status? + - _mark_hollis:_ I've looked how Monero and BeamMW approached certain technical issues, like opening an existing wallet, which data the wallet needs for signing during different transaction types etc. I did mostly some research the last weeks. No blockers at the moment. + +https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/5 + +### 2. Agenda review +The [proposed agenda](agenda for dev meeting later today - https://github.com/mimblewimble/grin-pm/issues/418) was accepted without changes. + +### 4. Bounty Update + - _mark_hollis:_ I've looked how Monero and BeamMW approached certain technical issues, like opening an existing wallet, which data the wallet needs for signing during different transaction types etc. I did mostly some research the last weeks. No blockers at the moment. +(https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/5) + +### 5. RFC Update +- _joltz:_ Fix past fees RFC (https://github.com/mimblewimble/grin-rfcs/pull/77) should be ready to be merged and accepted as an RFC. Does anyone here with commit access mind wrapping up last steps there? + - _antiochp:_ I can take a look at getting this merged. + +### 6. Community Funding Update +(https://forum.grin.mw/t/call-for-grin-community-candidates-for-additional-fund-granting-control/8521/4 ) + +- _joltz:_ The community is voting on each candidate by liking their forum post. If you are a candidate and have not made a post, please do so now +There is no anonymous voting, otherwise the process would not be sound. + +### 7. Request for funding @davidtavarez: one-time use slatepack addresses RFC + grin++ impl +(https://forum.grin.mw/t/withdrewed-request-for-funding-davidtavarez-one-time-use-slatepack-addresses-for-wallet-rfc-and-grin-implementation/8707/19) + +- _quentinlescellar:_ Are you going to PR it into grin-wallet? + - _dtavarez:_ I could, extend the scope sure; problem is that I'm not a skillful Rust developer so I can't estimate. + +- _joltz:_ I have somewhat mixed feelings. First of all @dtavarez crushes it and I want to do everyting I can to encourage the great work to continue. However, it seems like the rust impl only gets an RFC for this, which to me is not worth 10k eur. What would you need to extend scope to support grin-wallet? Otherwise it seems like maybe it is a better fit for the community fund? + - _dtavarez:_ I totally get it. Yes, I could extend the scope, but it will be hard for me to estimate time. + +- _phyro:_ I was under the impression this proposal is a bit like the previous proposals which were grin++ related, but with the RFC added to this one +which is why the work is on the grin++ side. But yeah, the grin-wallet would need this RFC implemented as well at some point + - _joltz:_ Which is why I think since there is no rust work it is a better fit for community fund. But we do not yet have that set up and I don't want logistics to get in the way of @dtavarez's work to continue + +- _joltz:_ I am open to supporting the proposal with an inclusion of a "best effort" attempt to implement in grin-wallet. I don't expect magic to happen but maybe your energy could help support the implementation on rust side if you include it as part of your goals +And I'll work with you on the RFC if you want. + +- _quentinlesceller:_ I think grin-wallet should stay as close as possible to all the RFCs. So I'd say integration in grin-wallet is a must for this. + +- _phyro:_ Perhaps we can even split this into two parts? RFC + Implementation after the RFC, maybe even someone else volunteers for funding to bring it to grin-wallet? + +- _joltz:_ @dtavarez do you want to move forward to get a decision on your proposal as is today or do you prefer to take some time to reflect, adjust it a bit and propose again? + +- _dtavarez:_ I can use this RFC to start contributing to the grin-wallet repo, for me it is a good opportunity. I would like to take some time to reflect, adjust it a bit and propose again. + +###Other Questions +_none_ + + + + + + +**Meeting adjourned.** diff --git a/notes/20210504-meeting-development.md b/notes/20210504-meeting-development.md new file mode 100644 index 0000000..5764a1a --- /dev/null +++ b/notes/20210504-meeting-development.md @@ -0,0 +1,62 @@ +# Meeting Notes: Development, May 04 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#dev channel on Keybase](https://keybase.io/team/grincoin). Meeting lasted ~ 30 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 +- geneferneau +- joltz +- tromp +- phyro +- quentinlesceller +- defistaker + + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions +### 1. Antiochp Update +- 5.1.0 beta is out for node + - _joltz:_ I think we are in a position to tag wallet also? + - + + + +### 2. Agenda review +The [proposed agenda](agenda for dev meeting later today - https://github.com/mimblewimble/grin-pm/issues/419) was accepted without changes. + +### 3. Action point follow ups from previous meetings +- Triage/ Github cleaning update @phyro + - github triage is ongoing + +- "fixpastfees" RFC & PR + - _antiochp:_ "fixpastfees" RFC was accepted and merged last week; PR is in review [and approved](https://github.com/mimblewimble/grin/pull/3629) - so I think we are in a position to merge that shortly +(and 5.1.0 will be tagged off current 5.1.0-beta tag so as not to include this right now as its a large-ish PR) + + +### 4. 5.1.0 release +- _antiochp:_ we should be able to release this sometime this week +on my todo list to get release notes together (mainly cleanup of the list etc.) anything else 5.1.0 related? + + +### 5. Bounty Update +- _quentinlescellar:_ Got some updates from @mark_hollis, still working on it. I think he is getting deeper into it based on the questions I got. + + + + +###Other Questions +_none_ + + + + + + + +**Meeting adjourned.** diff --git a/notes/20210511-meeting-governance.md b/notes/20210511-meeting-governance.md new file mode 100644 index 0000000..eb52fbf --- /dev/null +++ b/notes/20210511-meeting-governance.md @@ -0,0 +1,92 @@ +# Meeting Notes: Governance, May 11 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#general channel on Keybase](https://keybase.io/team/grincoin). 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:** +- joltz +- defistaker +- antiochp +- geneferneau +- deev +- mark_hollis +- cekickafa +- phyro +- tromp +- quentinlesceller + + + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions +### 1. Agenda review +The [proposed agenda](agenda for dev meeting later today - https://github.com/mimblewimble/grin-pm/issues/420) was accepted without changes. + + +### 2. Action point followups from previous meetings +- [fixpastfees-Merged](https://github.com/mimblewimble/grin-rfcs/pull/77) + - _joltz:_ Thanks for taking care of that @antiochp + + +### 3. Bounty statuses +- _joltz:_ Next to bounty statuses: it looks like @mark_hollis gave us a nice new [update](https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/10) Anything to add there? + -_mark_hollis:_ Not directly + - _joltz:_ thanks for your continued efforts on the ledger integration work + + +### 4. RFC updates +- _joltz:_ There don't seem to be any fresh/active published RFC drafts currently but I think there are maybe a couple in the pipeline from a few people + +### 5. Community funding status + +- _joltz:_ Community input is still coming in for community candidates it looks like it will be up for just under two more weeks, please make sure you give your input in the thread if you have not yet had a chance +- [Call-For-Votes](https://forum.grin.mw/t/call-for-grin-community-candidates-for-additional-fund-granting-control/8521/4) + +### 6. @geneferneau Atomic-Swap funding status [https://forum.grin.mw/t/grin-bitcoin-adaptor-signature-atomic-swap-update-thread/8689/9] + +- _joltz:_ I think the agreement was to go on a month-to-month basis with funding. April was funded but is now over by almost two weeks. Now we need to decide if we want to move forward with these efforts and pay for work for May. The floor is open for questions/concerns etc regarding the work/progress/direction with @geneferneau's efforts. Feel free to add anything else you'd like as well @geneferneau + - _dburkett:_ Do we have an estimated timeline for when atomic swaps will be ready? + - _geneferneau:_ I have the RPC basically ready, just need to do a test on localnet, then full test on Grin and Bitcoin testnet + - _dburkett:_ So by the end of the original 3 month period, it will be finished or close to finished? + - _geneferneau:_ That sounds reasonable for the grin-wallet implementation. The transaction flow currently takes 4 communication rounds each for the refund and main transaction. It would be nice to reduce that to 3, probably impossible to reduce further: I also need to impl a bloom filter or other mechanism for ensuring no re-use of atomic nonces. Re-use would result in loss of funds for the party that re-uses + - _dburkett:_ Sorry, I realized you said "RPC", not "RFC". Will there be an RFC for this? + - _geneferneau:_ Definitely, I planned to spend the last week of this month (or after testnet TX done) to write the RFC + +- _antiochp:_ Was April funded in advance or did we agree to fund post-April? I forget. + - _joltz:_ I think we funded April in advance but will wait for @geneferneau to confirm + - _geneferneau:_ no, I haven't received any funds + - _joltz:_ yikes, so this decision is for funding April and May? + - _dburkett:_ maybe we did agree to pay after the monthly update. + - _quentinlesceller:_ Yeah the decision was to do post payment + - _antiochp:_ yeah - we owe @geneferneau for April, then we decide on May @geneferneau sound about right? + - _geneferneau:_ sounds right to me πŸ‘ + + - _joltz:_ Do we want to take the May decision today or are we wanting to stick with post payment? + - _dburkett:_ I think post-payment makes sense still. It's my preferred approach, since it ensures we get solid updates for the final month. + - _quentinlesceller:_ πŸ‘ on may also same post payment + +- _joltz:_ Ok, if we stick with post payment, let's stay on top of payments as best as we can so we don't have contributors in limbo waiting on governance meetings to align to release if we can (I'll try to stay on top of it better myself, clearly I was out of the loop on this one) + + So it sounds like we are πŸ‘ on releasing April payment following this meeting and then we will review May payment at the end of May? + + Does all of the above sounds ok for you @geneferneau ? + - _geneferneau:_ Absolutely, I really appreciate the support. ❀️ + +- _joltz:_ Ok, I think we can consider this carried + +### 7. Council asset audit +- _tromp:_ fund candidate announcement: AlexGSG has finally replied in the voting thread. so all 5 candidates are now present there for you to Like + +- _joltz:_ council asset audit. I think @quentinlesceller was working on a tracking document at some point? Do we have any blockers for getting that done? Do we need to make a new draft to share publicly somewhere? + - _quentinlesceller:_ I have the tracking document which is not up to date. I could give it a few minutes today to update and release it. I'd need someone from the council to check it before + - _joltz:_ That would be great, I'm happy to help review it as well. I don't think there is a super impending rush to publish though. Maybe council can review and update as needed over the next week or so and plan to publish by next governance meeting? It will be nice to have public though so we can keep it updated and track things like domain expiry etc + +###Other Questions +_none_ + +**Meeting adjourned.** diff --git a/notes/20210518-meeting-development.md b/notes/20210518-meeting-development.md new file mode 100644 index 0000000..a0f82ea --- /dev/null +++ b/notes/20210518-meeting-development.md @@ -0,0 +1,62 @@ +# Meeting Notes: Development, May 18 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#dev channel on Keybase](https://keybase.io/team/grincoin). Meeting lasted ~ 45 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:** +- joltz +- geneferneau +- phyro +- quentinlesceller +- vegycslol +- + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions +### 1. Retrospectiv +- _joltz:_ Action points have been followed up on from last time. + + +### 2. Agenda review +The [proposed agenda](agenda for dev meeting later today - https://github.com/mimblewimble/grin-pm/issues/419) was accepted without changes. + +### 4. Atomic-Swaps bounty update with @geneferneau +- _geneferneau:_ I haven't tested the RPC/sync workflow, yet (still syncing testnet chain). There are tests for the command line / manual flow, though @deeev was kind enough to donate some testnet coins, so I should be able to do a testnet tx when the chain syncs. If people want to try out the wallet commands, I can write up a basic tutorial but, my tree is based on a fork of `grin` that doesn't include fixpastfees (waiting to update after `grin-wallet` gets it so, I think I'll be spending the rest of this week testing + writing docs and RFC; I'll be making my atomic swap PR pretty soon. next for the RFC to communicate the design, then the PR for review + - _joltz:_ Any known blocks to merge the PR? Just needs more review? + - _tromp:_ need 2 more reviews ideally. can you review, @dburkett and @quentinlesceller ? (https://github.com/mimblewimble/grin-wallet/pull/602) + - _quentinlesceller:_ yes absolutely can review that + - _dburkett:_ It looked fairly straightforward, so I should be able to fit that in today; I will also try to get to gene's grin-wallet PR later today. + +- _joltz:_ Thanks for the review Quentin and David πŸ™ @geneferneau please continue to keep everyone updated, especially as things come up that may slow you down πŸ‘ + +### 5. 5.1.0 release +- _joltz:_ On to 5.1.0 release, was pushed out after last meeting and seems to have gone fine. Anything worth mentioning there? + - _bladedoyle:_ Im running 5.1.0 without issues. +- _phyro:_ (https://github.com/mimblewimble/grin/issues/3641) there seems to be an issue on some distros. It might have to do with deforking croaring + - _joltz:_ hm yes that definitely needs to be tracked down and solved + +- _bladedoyle:_ Did we build in the avx2 instruction? Thats what was causing "illegal instruction" on old hardware (shitty vps).the commit claims to have been careful about avx2 ... I'll download the official build and double check + - _joltz:_ Thanks @bladedoyle please use the issue (https://github.com/mimblewimble/grin/issues/3641) to help track your progress (and anyone else who wants to take a look). I'll throw a few minutes at it as well. + +### 6. Github triage updated +- _phyro:_ the status there is similar to the previous week. I'm hoping antiochp can hop over to the wallet side for some time. I know he wanted to tackle late locking so perhaps in the scope of that + - _joltz:_ Thanks @phyro πŸ™ + +### 7. ledger hardware bounty update with @mark_hollis (https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/9) +- _mark_hollis:_ I'm now working on said items: initiation and sending. Vladislav from the Beam project is willing to share the Ledger code of Beam. I was looking at the rangeproof generation earlier this week. That is something I don't have an idea how to begin with at the moment. Beam uses an multi-party computation for this. I remember there were github issues at Grin about using bulletproof mpc. I don't have particular support needed for now. There are some things I need to research more before asking support. + +- _joltz:_ Let's do our collective best to followup on the (https://github.com/mimblewimble/grin/issues/3641) issue and help with the bulletproof building in #dev this week + + +###Other Questions +_none_ + + + + +**Meeting adjourned.** diff --git a/notes/20210525-meeting-governance.md b/notes/20210525-meeting-governance.md new file mode 100644 index 0000000..885e449 --- /dev/null +++ b/notes/20210525-meeting-governance.md @@ -0,0 +1,117 @@ +# Meeting Notes: Governance, May 25 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#dev channel on Keybase](https://keybase.io/team/grincoin). Meeting lasted ~ 45 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:** +- joltz +- geneferneau +- mark_hollis +- tromp +- mcmmike +- dtavarez +- phyro +- quentinlesceller + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions + +### 1. Agenda review +The [proposed agenda](agenda for dev meeting later today - https://github.com/mimblewimble/grin-pm/issues/422) was accepted without changes. + +### 2. Bounty statuses + - _joltz:_ Getting started with bounty statuses it looks like @mark_hollis has recently made an update https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/13 + - _mark_hollis:_ hello there + - _joltz:_ Anything to add from a governance/process perspective? and thanks for keeping the updates coming! + - _mark_hollis:_ Not at the moment. + - _joltz:_ I think this is the only active bounty currently? + - _quentinlesceller:_ yes + - _dtavarez:_ @mark_hollis, you said that you started looking grin++ is there any blockers or something? + - _mark_hollis:_ I had some problem which I created a github issue for. (issue #174) + - _joltz:_ πŸ‘ sounds like you can continue the technical details of the conversation there then? + - _mark_hollis:_ Yes + - _dtavarez:_ I will answer the issue :) - Cool + - _joltz:_ Great, thanks again @mark_hollis is great having you here. As always feel free to ask for anything you need (repeatedly if needed) and I'm sure everyone will do their best. + +### 3. RFC Update +- _joltz:_ @geneferneau has published a draft RFC for atomic swaps https://github.com/mimblewimble/grin-rfcs/pull/80 Please give it a read if you get a chance, am looking forward to reading myself soon. Already some good discussion with tromp and phyro + +### 4. Community funding status +- _joltz:_ https://forum.grin.mw/t/call-for-grin-community-candidates-for-additional-fund-granting-control/8521/13 voting is over and it looks like Mac and @anynomous are the two newst members (pending council approval which I think might be there?) +So next steps per the proposal at https://forum.grin.mw/t/fund-alternative-a-split-fund-proposal/8476 would be +1. Signers announce their spending guidelines +2. Wallet is created, tested, and then funds are transferred +Is there anything else that we want to address/discuss, or is it now up to the new group to discuss and share their spending guidelines? + - _mcmmike:_ I think it is up to us know to brainstorm and come up with some spending guidelines and build some structure around the new formed group. + - _phyro:_ would it make sense to routinely check that 6/6 is possible? or is this entirely up to them now? I'd like to avoid not having funding requests for 4 months and then figuring out multiple people lost their keys + - _dtavarez:_ I raised a question on #community_fund but I don't think this is the right moment to discuss; I would like to read more comments about it my question is: how the Community Council could prevent becoming another centralized front for Grin and avoid having 2 centralized fronts fighting each other? for example, what will happen when one side wants to make a change that requires an RFC and the other side disagrees? + - _mcmmike:_ I have not yet answered this question in detail publicly on the forum, but once we organise and stuctured, we can answere these question. From what I did understand, the current council is in favor of RUST implementations and supporting RUST improvments. So we need to figure out how we work together if we want to + - _dburkett:_ @mcmmike - I had a proposal that allocated funds to rust vs everything else. But that was not chosen. This merely splits the funds into 2 councils, each with the same goal, though with a different set of eyes. Both funds are for RUST and for community projects. + - _dburkett:_ @dtavarez - They presumably wouldn't spend funds on implementation unless there was already rough consensus for the change. + - _dtavarez:_ but what if the community council decides to support with funds something that requires a protocol change? + - _phyro:_ It's good that this is not possible imo. Otherwise you can throw money at protocol changes. + - _joltz:_ Ok,so it sounds like the new council needs to get together to come up with their spending guidelines? + - _mcmmike:_ as this was a requirement for splitting, I would say "yes" we have to sit down and agree on guidelines. + - _joltz:_ Ok then, we will all follow up together in the next governance meeting to check progress? + - _mcmmike:_ not sure if we can come up with a final version in 2 weeks but we will at least start. next few days, I will contact all new members and ask for a communication basis , where we will publish and discuss our progress. + - _dtavarez:_ but this is a good start:-> [presumably wouldn't spend funds on implementation unless there was already rough consensus for the change.] + - _joltz:_ Don't mean to derail the above convo. I think there is no clear answer there and variations have been discussed quite extensively. I think we can only all act in good faith and hope that the new model brings the improvements we all wanted to see. It won't be perfect but hopefully it gives us some new tools to continue to make the improvements we all want to see. It also touches on a particular point that has never happened before that I think is a cause for a lot of discomfort. What happens when the community funds and implements a change that the old council isn't happy with? Does it get merged or not? I think the aim here is to move culture in the direction of bitcoin but it's hard for us since we are so small. I think it will be an ongoing discussion + +### 5. Council asset audit + - _joltz:_ Thanks Quentin for putting together [Grin Access Rights] https://github.com/mimblewimble/grin-pm/pull/426 ; it looks like there is already some discussion, maintenance on making the document more accurate. Hopefully we can keep it relatively up to date. + - _quentinlesceller:_ We can add the list of current council members. But this list was more on "who has access to what" + - _dburkett:_ Why are the council keyholders private, but the community council's keyholders are not? keyholders for funds, that is + - _quentinlesceller:_ Some of them are anonymous too no? + - _dburkett:_ Pseudonymous, but their names will be in the list. I'm not asking for KYC- I think there's a real danger of losing access to council funds, considering the past history of members disappearing without handing things off. And we're down to just 3 or 4 members. + - _mcmmike:_ this is true, as this is a long-term commitment + - _dburkett:_ It was mentioned before that it was a 3 of 5 fund IIRC (I'd have to check gitter). So ideally, we would have 5 keyholders still active. That's clearly not the case, since we don't have 5 council members active. So is it time to move those funds to a new 3 of 5 (maybe picking up an additional council member to bring us up to 5) + - _joltz:_ That is not the requirement. The requirement is funds held in 4/6 + - _joltz:_ My personal take is that it is up to the council to secure council funds as it is up to the community to secure community funds. Transperency and accountability ar important but personally if I were a key holder I would not want to have that as public information. + + - _quentinlesceller:_ Do you feel like a public list of key holders would be the solution? + - _dburkett:_ A public list of key holders would allow the community to audit access and recognize when we're at risk of not meeting the threshold. + - _joltz:_ Yes and the community fund can decide to do that. Personally, for me, for the council fund I am not comfortable doing that myself and I don't see why it should be required especially with the fund now being split + - _phyro:_ would a sig from the council fund be enough to prove people have access to the fund? + - _joltz:_ Yes I would be fine with a regular "proof of key ownership" + - _quentinlesceller:_ This is a good idea, we can do a monthly or quarterly update with a proof of ownership + - _mcmmike:_ like we did in the past with the Canaries + - _tromp:_ that would be more convincing if you could sign as 5/5 but we can't AFAIK + + - _joltz:_ @_dburkett - Is that acceptable for you? + - _dburkett:_ The council isn't exactly overly active these days. I don't blame anyone for that, most are volunteers, but I have little faith in their ability to manage those assets without others monitoring. We've lost many assets before, the grin wallet has been inaccessible for nearly a year with no public effort to restore access to those, etc. Having a public key list allows the more active members of the community to monitor and alert when there's a problem. Because if it's a 3 of 5 but only 3 of those keyholders remain, I will call attention to that and ask for key rotation. Honestly, I think we're down to 3 at most now, so this is already a problem. + - _phyro:_ the only way to prove we have access is with a signature. People being around doesn't prove they have not lost their keys, so periodical signing makes sense in any case imo + - _quentinlesceller:_ I agree with @dburkett that this is a concern. I disagree with the idea of publishing the name of the keyholders online though. + - _dburkett:_ Why? If security is a concern, a single rubber hose attack on any one of the council members will be enough to get the rest of the names. + - _vegycslol:_ can't we just publicly announce public keys and then every quarter each member signs something individually? + - _joltz:_ Both councils are free to take this up internally and hopefully reach a transparent, accountable and resilient solution. + - _phyro:_ if we can't do a 5/5, we should start moving in that direction. + - _dburkett:_ Right now, the active council members are:[joltz, tromp, quentin, antioch (inactive for weeks)] Even with a 3 of 5, I think we are at a real risk of losing access to those funds now. Yet it wouldn't even be discussed if I hadn't brought it up. That doesn't instill a lot of confidence. + - _joltz:_ Your concern has been heard @dburkett + - _quentinlesceller:_ Give us time to think about a solution. I propose we re-discuss this at the next governance meeting with hopefully a concrete solution. + _dburkett:_ sounds good. Thanks + +###6.new funding request for some general pm duties https://forum.grin.mw/t/request-for-funding-newjack777/8893 + - _dtavarez:_ I think the role (Grin Groundskeeper) is needed; but I would like to see someone more familiar doing this + - _dburkett:_ It's a very modest request, so I believe if @jankie1800 continues to contribute to the community and make themselves more well known, I see no reason it wouldn't be approved in the future. + - _dtavarez:_ would like to more contributions as Grin Groundskeeper from @jankie1800 I think the role is needed actually + - _quentinlesceller:_ Also, I'd like people to start contributing directly to Grin as a regular open source project instead of directly asking for funding. Funding can come after once you have proven yourself useful- (regarding funding not bounty) + - _joltz:_ To their credit I suggested that as well and they have started https://github.com/mimblewimble/grin-pm/pull/425 which is nice to see. Hopefully they can continue adding value and if this is really what they want to do, find a nice home here after getting to know the community better. So it sounds like this request will not be approved for now but we are happy to see their contributions and hope that they can evolve into something longer term? + - _tromp:_ perhaps bringing out a new Newsletter will further boost his profile + +###7.Other questions + - _mcmmike:_ I would love to see the Newsletter get activated again, this was a very popular way of communicating for GRIN + - _joltz:_ What is needed to reactivate it? + - _mcmmike:_ good question, do we want to use the old account again or start with a new one ? + - _dburkett:_ Mac has been trying to get in contact with lehnberg to take over the newsletter, but no response yet. It would be ideal to continue the old one, since so many people see it.But we're at Lehnberg's mercy, since it is his newsletter and list. + - _joltz:_ Maybe we can collaborate on the newsletter in #community and hopefully have an opportunity for anyone interested to get involved + - _phyro:_ also writing your own blog posts or similar would be much appreciated. We have a lot of people in the community but very little content made + + +- _joltz:_ Ok, thanks for your time today everyone, we got through a lot. Some big points to follow up for next meeting. See you all there! + +**Meeting adjourned.** diff --git a/notes/20210601-meeting-development.md b/notes/20210601-meeting-development.md new file mode 100644 index 0000000..1d27ec4 --- /dev/null +++ b/notes/20210601-meeting-development.md @@ -0,0 +1,73 @@ +# Meeting Notes: Development, June 01 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#dev channel on Keybase](https://keybase.io/team/grincoin). Meeting lasted ~ 45 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:** +- joltz +- geneferneau +- phyro +- quentinlesceller +- mark_hollis +- tromp +- dburkett + + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions +### Action follow-up +- _joltz:_ I trust @phyro is still chugging along on the never ending triage For "fixpastfees" I know the RFC got merged, were the code PRs merged as well? Yep, looks like it https://github.com/mimblewimble/grin/pull/3629 + +### 2. Agenda review +The [proposed agenda](agenda for dev meeting later today - https://github.com/mimblewimble/grin-pm/issues/424) was accepted without changes. + +### 4. 5.1.0 release +- _joltz:_ For 5.1.0 release we had an issue with launching in certain environments https://github.com/mimblewimble/grin/issues/3641 +It looks like there was maybe some progress since last dev meeting, but I'm not sure we have landed on anything actionable? Or maybe we have with the build process +- _geneferneau:_ afaiu, the problem doesn't occur with source build + - _joltz:_ Right, it is an optimization in how the binary is generated by us? +- _tromp:_ croaring builds use avx2 instructions unless prohibited with ROARING_DISABLE_AVX + - _geneferneau:_ don't know if its fixed on the build machines + - _quentinlesceller:_ Yes disabling avx should do + - _tromp:_ or with -mno-avx flag to gcc - we need someone familiar with build scripts to try these options and test on a machine with no avx support + - _quentinlesceller:_ it's here: https://github.com/mimblewimble/grin/blob/master/.ci/release.yml#L7 I could potentially try and fix it. + - _joltz:_ That would be great @quentinlesceller if it is a quick fix for you. If not let me know and I'll try to find someone to work on it πŸ™ + - _quentinlesceller:_ tbh that's a quick fix for me, I'll do it + +### 5. Review atomic swap RFC/PR https://github.com/mimblewimble/grin-rfcs/pull/80 && https://github.com/mimblewimble/grin/pull/3643 +- _joltz:_ It sounds like there is some active ongoing discussion there shame on me for not having engaged much there yet It is an exciting and important area though and will certainly benefit from more engagement Is there anything in those discussions or processes worth highlighting here? + - _geneferneau:_ definitely, going to make a forum post suggesting a modification to SAS. hopefully, get some feedback from Ruben Somsen- need to implement multiparty outputs in grin-wallet which requires exposing multiparty bulletproofs (already present in secp256k1-zkp) to Rust and grin-wallet- side benefit: Grin multiparty outputs should be generally available after + - _joltz:_ yes, and multiparty is long overdue for grin imo, glad to see it is being picked up- definitely one of the most exciting things going on in the grin ecosystem right now, thanks @geneferneau! + - _geneferneau:_ you're welcome πŸ™ + +### 6. Bounty updates +- _joltz:_ Anything to add for the bounty update @mark_hollis? We got a nice update a week ago https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/13 + - _mark_hollis:_ This week I had some troubles building grin++, this is solved now. +Now I am at back grin-walle,t focusing on how to serialize the data to send to the device. Thinking about something like Partially Signed Bitcoin Transactions, but for Grin. It's a format for serializing transactions. The Ledger firmware should expect the data to come in a certain format. This should be uniform for both grin-wallet and grin++ and possible other wallets. thanks to @geneferneau for mentioning psbt's. +- _quentinlesceller:_ very nice @mark_hollis +- _joltz:_ thanks @mark_hollis it's great following your progress on this, thanks for your strong efforts πŸ™ +- _geneferneau:_ great work @mark_hollis + +### 7. Grin wallet PR to add Tor bridge support. https://github.com/mimblewimble/grin-wallet/pull/617 +- _joltz:_ This will be an important update for users located in places where Tor is blocked. Thanks to @deeev I made a few comments, would be great for others to weigh in as some decisions need to be made about how to handle this extension Nothing too involved though Mostly just wanted to bring the PR on everyone's radar to give any feedback they may have, and to highlight @deeev's contribution + +###Other Questions +- _joltz:_ it looks like there is a suggestion about a CHANGELOG.md. I think it's a great idea if we can find someone willing to consistently put one together without adding more to the plates of existing contributors + - _geneferneau:_ is there a way to script/automate the changelog? + - _joltz:_ It's possible. The usefulness would probably depend on the descriptiveness of PR titles, commit messages etc + - _geneferneau:_ I could spend some cycles looking into it + - _joltz:_ IMO, I wouldn't worry too much about it and stay focused on your current work. But if you need a break and want to look at something else for a bit.. + - _geneferneau:_ definitely + +- _joltz:_ I noticed there was a comment about a funding request made to the meeting issue, but it is more appropriate for the next governance meeting + - _dburkett:_ Does it even make sense to separate governance and dev meetings anymore? we get roughly the same attendance regardless of which meeting it is. + - _joltz:_ I plan to add this as a point in the next governance meeting + - _quentinlesceller:_ I'd vote for a bi weekly dev + gov meeting. and return to "normal" once there is more activity + + +**Meeting adjourned.** diff --git a/notes/20210609-meeting-governance.md b/notes/20210609-meeting-governance.md new file mode 100644 index 0000000..6b804a3 --- /dev/null +++ b/notes/20210609-meeting-governance.md @@ -0,0 +1,113 @@ +# Meeting Notes: Development, June 01 2021 + +Governance meeting held @ 3PM [UTC](http://www.timebie.com/std/utc.php) in [grincoin#general channel on Keybase](https://keybase.io/team/grincoin). Meeting lasted ~ 50min. + +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:** +- joltz +- geneferneau +- defistaker +- mcmmike +- hendi +- vegycslol +- jankie1800 +- cekickafa +- phyro +- quentinlesceller +- mark_hollis +- tromp +- dburkett + + + +_(apologies if I missed someone - submit a PR or contact @lehnberg to add)_ + + + +## Agenda points & Actions +### 1. Action follow-up +- _joltz:_ + +### 2. Agenda review +The [proposed agenda](agenda for dev meeting later today - https://github.com/mimblewimble/grin-pm/issues/427) was accepted without changes. + +### 3. Bounty statuses / status update from mark_hollis +- _joltz:_ First up we have bounty statuses. @mark_hollis has been working on ledger support. His latest update is https://forum.grin.mw/t/grin-ledger-hardware-wallet-progress-thread-by-markhollis/8670/17 Not a ton to note there, looking forward to seeing how the next couple of weeks go- Anything you want to call out there @geneferneau ? + +### 4.RFC update +- _joltz:_ For RFCs it looks like we currently only have one active https://github.com/mimblewimble/grin-rfcs/pull/80 Succinct Atomic Swaps +seems like lots of good discussion is going on there and progress is continuing +- _geneferneau:_ Just working on multiparty outputs. Still discussing some corner cases with SAS transactions. +- _joltz:_ sounds good, excited to see what kind of multiparty we end up wit +- _geneferneau:_ yeah, the multiparty part should be the same regardless. discussion is over whether to add adaptor signature to the Grin Timeout transaction + +### 5. Community funding status for @geneferneau & @mwgrin-fr https://forum.grin.mw/t/request-for-funding-gene-adaptor-signature-atomic-swaps-grn-btc/8632/13 +- _joltz:_ This brings us to community funding status for @geneferneau. I think you are owed payment for May and you are now seeking a continuation for June? Does anyone have any opposition or concern related to Gene's request that they'd like to share here? +- _phyro:_ I'd like him to continue to contribute πŸ‘ +- _dburkett:_ It's good to have @geneferneau around. I've been reading his updates, but haven't been following the RFCs & code as closely as @tromp and @phyro. If they are happy with his progress, then I am on board with continuing his funding πŸ‘ +- _tromp:_ i'm ok with continued funding but do want to see more work on the RFC that are still lacking in detail- for instance, are all the prepared txs done with multiple separate slatepacks (and if so how ,exactly are these communicated back and forth) or will there be a multi-tx slatepack. finally, i'm not a fan of the "atomic nonce" terminolog- just "secret" as in S.A.S. was fine. + - _geneferneau:_ I definitely plan to add more detail to the RFC, including changes to Slate-currently, the setup I have coded uses multiple slates +if everything was with one slate, it would take many rounds (16?) the flow is somewhat non-linear, too +- _joltz:_ Ok it sounds like we will complete Gene's payment for May and continue funding for June πŸ‘ We can continue the technical conversation in the RFC. + +- _joltz:_ Moving on, there is another funding request https://forum.grin.mw/t/request-for-funding-mwgrin-fr/8888 to make onboarding videos for Grin +Personally, I think it's a better idea for the community fund. +- _hendi:_ I agree, and also second Anynomous' post from 4w ago (example first, then funding) +- _tromp:_ i'd be happy to consider funding if we see some good example videos first + - _pyro:_ I think an example video was uploaded btw + - _mcmmike:_ yes, https://streamable.com/mzayob - I recomend zooming into the terminal a bit more, but these are details we can discuss later. +- _cekickafa:_ he done some vids.i seen.He fits for thisπŸ‘ +- _jankie1800:_ It looks like tech documentation. Is this more effective than the github install instructions? Only issue with video tech documentation is that it doesn't age well with updates that may change the terminal cmds + - _grindoggo:_ Just have to keep updating the videos honestly, and tag the videos with (2021 documentation) or something like that +- _tromp:_ but there's no accompaying narrative. i'd like to see an example with audio explanation as well +- _geneferneau:_ if the videos are CC-BY-SA, another community member could add audio, too + +- _joltz:_ Great it sounds like we have some good feedback and interest for supporting their work,Ok, it sounds like the feedback is to share some examples with the community before pursuing funding, regardless of the approach let's see the next round goes and hopefully we can get some quality videos for Grin πŸš€ + +### 6. Council asset audit (followup) +- _joltz:_ Next we have council asset followup. To take things a bit further I've made a proposal and some clarifications at https://forum.grin.mw/t/council-evolution-clarification/9021 +The main takeaways: +- council updates fund key holders to ensure everyone is active +- council provides regular proofs of spendability +- community takes over meetings +I think this helps provide some clarity and certainty around the majority of the concerns and hopefully helps give us a clean way forward as a community while we try to have less and less reliance on council as a point of failure +Will give us a bit to take a look and digest +- _jankie1800:_ question on point 3: Will core be taking future donations? and how will core/rust continue operations + - _joltz:_ the council may take future donations if they want. the council itself is only responsible for operations related to the fund. the repo/rust operations continue as they have since RFC0016, when the operations became responsibility of individual contributor teams and not "core" +- _defistaker:_ who are community Individual Contributors (ICs)? Contributors like mark_hollis, or community council members? + - _joltz:_ all of us are IC's + - _geneferneau:_ I like being an integrated circuit + +- _dburkett:_ How will funding requests to the OC be handled? also, the decision process in particular. Will that be public? + - _joltz:_ In the forum as per the funding guidelines RFC (which is probably due an update) but my hope is to improve the process at some point to make it even more clear, efficient and transparent. Maybe all in a dedicated github repo? As I'm proposing yes it would just happen all in the forum thread- + - _vegycslol:_ Is proof of spendability enough? If it's a 4 of 6, then that means that even if you are only 4 left it's going to seem like everything is fine when the reality is that someone could randomly lose key (i avoided die :D) + - _joltz:_ The proof itself can take many forms, I think that is still open + +- _joltz:_ It might feel like these are big changes, but I think zoomed out, it just makes the process around council funds more reliable and transparent and brings the community council and original council to as equal footing as possible by giving ownership of the meeting time/space over to the community +And hopefully the clarifications around how repos work etc will help us stay on the same page as a community going forward + - _phyro:_ so there will be no scheduled meetings unless someone creates an issue on the github? +as in, the current format dies unless someone picks it up + - _joltz:_ correct, it's just no longer responsibility of "council". it's now our responsibility as a community. but any one of us here can pick it up + - _geneferneau:_ I thought there was discussion about switching to one bi-weekly meeting? or is this only about community meetings? + - _phyro:_ there was, if I recall correctly, we wanted to merge both gov/dev meetings into a single bi-weekly. This is changed with this and suggests that this will take place if someone steps up and organizes and leads them + +- _mcmmike:_ its time for us now to organize and help with meetings,agenda, transcripts etc - I would suggest to keep the same timetable for gov-meetings and we from the CC agreed to attend the gov meetings at least one of us "all" the time. if there are no OC topics we have the bi-weekly CC meetings then +I would suggest to keep the same timetable for gov-meetings and we from the CC agreed to attend the gov meetings at least one of us "all" the time. + - πŸ‘: _grindoggo, _cekickafa, _geneferneau, _defistaker, _jankie1800 + +- _joltz:_ So in some ways this is a bittersweet meeting. Have been here every tuesday since we moved to keybase and hope to continue to see everyone on tuesdays. But sometimes you have to give up some control to have the right outcomes, and I think this is an example of that- I'm looking forward to seeing what we can accomplish together as one of the only truly community-driven project πŸš€ Thanks to everyone for participating in these over the last couple of years, I'm really excited to be a part of our continued evolution + + +###Other Questions +- _joltz:_ With that, are there any other questions that we want to bring up today?:) + +- _grindoggo:_ I'm not sure if this is my place but I wanted to mention Renzokuken's suggestion: keybase://chat/grincoin#community_fund/1582 / In short, he suggested a negligible funding to test the communication of the funding council. + - _joltz:_ Yes I totally forgot to highlight that, Slatepacks marketplace looks amazing! Kudos to everyone working on it + - _grindoggo:_ Well it doesn't necessarily need to have to be with that marketplace, it can be anything negligible probably + +- _phyro:_ decentralize the newsletters πŸš€ + +- _joltz:_ Ok, meeting over. Thanks again everyone for your energy and time today. Hope to see you all in the first meeting we put together as a community! + +**Meeting adjourned.**