Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
96 lines (64 sloc) 5 KB

Meeting Notes: Governance, Oct 22 2019

Governance meeting held @ 3PM UTC in grin/Lobby on Gitter, full chat transcript here. 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
  • hashmap
  • jaspervdm
  • j01tz
  • lehnberg
  • quentinlesceller
  • tromp
  • yeastplume

(apologies if I missed someone - open a PR or contact @lehnberg to add)

Agenda points & Actions

1. Agenda review

Proposed agenda accepted.

2. Action point follow ups from previous meetings

2.1 Site redesign

  • lehnberg: @nijynot design is live, feels like a good improvement.

    • quentinlesceller: Very nice improvement indeed. Again good job!
    • jaspervdm: Definitely.
  • lehnberg: Displaying grin budget and creating a simple onboarding flow with binaries action points have now been unblocked. There's still more work to be done, those who feel up for some web design, there are areas where your services would be valued. See here for example:

2.2 Lehnberg funding

Actioned.

2.3 Grincon call for presenters

Actioned.

  • lehnberg: Do we want to post on the mailing list on that?
    • quentinlesceller: Yeah that'd be great.
    • lehnberg: Wanna take that one?
    • quentinlesceller: Sure.

2.4 List of crypto problems

  • quentinlesceller: Here is a list of 7 research problems https://github.com/mimblewimble/docs/wiki/Grin-Open-Research-Problems. There are some more simple problems such as implementations problems and also wider problem such as the accumulator one or the one about reducing linkability of outputs on chain. To be clear, this is just to be considered as a starting point, feel free to edit and add problems.
    • yeastplume: Very nice, very good to have all of these in the one place.
    • lehnberg: Indeed. So let’s all take until next gov meeting to review / improve / comment etc and see if we get to sth stable that we can put on the website alongside of a call for people interested working on any of these to get in touch?
    • quentinlesceller: Yes, you can make changes by just editing the wiki.
    • lehnberg: Cool - let's give Quentin the right to revert changes and keep document in order and avoid wiki chaos.

3. Website

Covered as part of section 2.1 above.

4. Security

4.1 Audit

5. grincon1

  • lehnberg: We have:

    • Venue secured
    • Call for speakers announced, submissions closes Oct 30, we’ve received 1 application so far. Eight days left to nail down a speaker schedule - if anyone here wants to give a talk, apply now.
    • Very ugly website up https://grincon.org
    • An anonymous donor that might be willing to cover part of the bar tab
    • Registration to the event is now open.

    We don’t have much more than that at this stage I think.

6. RFC & Sub-teams update

  • lehnberg:
    • RFCs: No update.
    • Sub-teams: Still no moderation team announcement but expecting that to move forward soon. Some documentation has been produced. Aspiring moderators willing to take an active part in reviewing, please reach out.

8. Other questions

8.1 Grin 2020 Roadmap

  • lehnberg: I’ve not fully thought it through but would like to propose some kind of canvassing effort to solicit ideas and directions that can be put into a Grin 2020 Roadmap doc. Where some X focus areas are prioritized for the year, with some motivation. Will try to formalize some thoughts asap. If anyone wants to be involved, give me a shout.
    • antiochp: To be clear - is the idea to canvas in terms of proposing ideas with an intent to also implement them or just ideas for Grin to implement? i.e. is this a wishlist? Or things people have an interest in contributing to?
    • lehnberg: I see it as a bit of both, it’s “what Grin should focus on achieving in the next year”. I’m thinking there’s some communal effort where anyone is free to propose ideas, that then gets condensed into a core approved (tm) doc. Obviously if a proposal also includes how it is delivered, it strengthens the rationale for us focusing on it.

Meeting adjourned.

You can’t perform that action at this time.