Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
111 lines (76 sloc) 6.58 KB

Meeting Notes: Governance, Dec 17 2019

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

3. Yeastplume funding request

  • lehnberg: Request for funding link here. Proposal is to support yeast with 3 x EUR 10,000 for Q12020. Floor is open for people to discuss. Does anyone have any questions or comments to yeastplume? Or about the request?
    • antiochp: none here
    • quentinlesceller: me neither
    • lehnberg: Yeah you lot probably wouldn’t have that many questions but maybe there are some lurkers that want to query/challenge this a bit. Or give a show of support for the (humble) yeast.
    • tromp: I support the yeast

five minutes of silence followed

Decision: Approve yeastplume Q12020 funding request

  • lehnberg: Okay so that’s at least five minutes of silence. Are we approving? I think there are no objections in 3... 2.... 1....
    • quentinlesceller: well deserved
    • antiochp: 🚀
    • lehnberg: 🥳
    • yeastplume: The yeast humbly thanks everyone for their support in allowing him to continue serving the community!

4. Site & Forum

  • lehnberg: So financials link not been put up, I will get to it but probably roadmap is higher prio.

  • lehnberg: Regarding I reached out to @madwax who’s just now got back to me. Not sure if they are here? In any case they will research VPS hosts for reverse proxy, and I hope we’ll be able to move forward fairly seamlessly, let’s see. Anyone who wants to help out can hit us up.

  • lehnberg: Regarding the domain, @0xb100d came through as always and now wants to know who to hand the Samir share’s of the domain login to. So wanted to ask today who should have the shares? To be put together in case 0x disappears and we need to renew the domain. I suppose it shouldn’t be a nym.

    • quentinlesceller: Don't mind to be involved.
    • yeastplume: Heh, me as well unless there are no other takers.
    • lehnberg: Could we do a 2 of 3 Samir’s secret share of @quentinlesceller @yeastplume and... @jaspervdm? I don’t mind to be involved but wouldn’t want to propose myself either.
    • tromp: 3 of 5 is safer.
    • lehnberg: Okay let’s add me and @tromp then?
    • tromp: Unless some non-council members want to volunteer.
    • lehnberg: Yeah sure they could take my spot. Is there any non-nym person up for this responsibility?Would anyone reading this like to safekeep a share of the login of the domain?

No takers

Decision: Shares to the domain login

  • lehnberg: Okay shall we just go with these five people (Quentin yeast tromp jasper lehnberg) and hope jasper is okay with that? And then come back to it if not?

No disagreement, support from tromp.

5. Switch meeting location from gitter to Keybase?

  • lehnberg: Shall we move both governance and dev meetings to keybase? Pros: Keybase sucks way less than gitter. Cons: We have way fewer people on keybase and there’s no IRC relay bot for lurkers etc.
    • yeastplume: I vote for yes.. honestly I use gitter less and less these days
    • tromp: I don't mind. As long as we leave message here saying: "Dev/Gov meeting in progress at keybase channel such and such".
    • quentinlesceller: I think we should figure out a way to give more visibility to keybase. There is significantly less people on those channels.
      • lehnberg: Agreed. Let's add keybase visibility as an action point to track?
    • yeastplume: That is true... but gitter is particularly bad and featureless in comparison. And I would very much like to reduce the number of chat clients that need to be monitored.
    • quentinlesceller: Yep definitely agree with moving everything to keybase.

Decision: Switch location for dev & governance meetings

  • lehnberg: Okay, and @DavidBurkett and @JosephGoulden we’re in favor as well. So no objections - let’s try that next meeting then and see how things go? Can’t be more quiet than here in any case. Any late readers of this chat feel free to object after meeting etc.

6. RFC & Sub-teams update

6.1 Moderation team

  • lehnberg: Moderation team is moving again @energyburn is a trooper and has picked up the task to help. So maybe after the holidays we’ll have sth. If there are community mods/admins that would like their particular community to be part of this, hit either of us up!

6.2 RFC status review

  • lehnberg: I notice both Enable faster sync and TOR are still not merged. Anyone got an update?
    • antiochp: I pinged @DavidBurkett last week about the "enable faster sync" RFC and he's aware of it (he's the shepherd for it).
    • yeastplume: Yes, will merge TOR rfc.

7. Dev & Governance meetings during holiday period

  • lehnberg: I note that the next dev meeting is set for the 24th of December. And next gov meeting for 31st... As much as we all know how committed we are to Grin, perhaps we should move those meetings?
    • yeastplume: I would propose moving the next official dev meeting until the week after the holidays and going from there and we'll sync up as needed to mind the HF, release and issues separately from meetings.
    • lehnberg: Okay so... dev meeting on 7th of Jan? Governance on 14th?
    • yeastplume: yeah, think I'm okay sticking to 7th and 14th unless there an urgent need otherwise
    • quentinlesceller: I'm good with these dates too
    • tromp: We can always schedule an extra emergency meeting if need be

8. Other questions


Meeting adjourned.

You can’t perform that action at this time.