Development meeting held @ 3PM UTC in grincoin#general channel on Keybase. Meeting lasted ~ 40 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
- bladedoyle
- jaspervdm
- joltz
- lehnberg
- mcmmike
- phyro
- quentinlesceller
(apologies if I missed someone - submit a PR or contact @lehnberg to add)
-
lehnberg: Proposed agenda.
- jaspervdm: Lgtm.
-
quentinlesceller: David funding request will be considered at the next governance meeting I guess?
-
antiochp: Just want to add that I totally dropped the ball on funding (my funding), forgetting it was jan next month... I'm looking to put a funding request together early next year to cover q1 (just a heads up, nothing to discuss today).
- 👍: quentinlesceller, jaspervdm, lehnberg, joltz
- lehnberg: Yeah I almost did the same. And had to rush to put it in.
-
lehnberg: So let's maybe add a meeting point about "holiday schedule".
- 👍: antiochp
-
lehnberg: And yeah dunno - we have a policy that we are to give one week notice for these requests, but who knows when the next gov meeting is. Maybe we could also agree to do it next week as part of the dev meeting? For both you and david? Assuming you submit a request today @antiochp Seems a bit silly to have you both wait until jan before we agree.
- antiochp: I actually want to defer until jan to give it some thought and a bit of planning. And either do it retroactively from jan 1 or happy to just do it from mid jan, whatever works best.
- lehnberg: Ah fair enough.
-
quentinlesceller: Tuesday 29 dec is next governance meeting.
- lehnberg: Yeah - not sure this will happen:)
-
lehnberg: Okay so maybe let's slide into the "holiday schedule" right away now and settle this.
-
antiochp: Yeah next realistic governance meeting is likely in jan?
-
jaspervdm: I'd be in favor of disussing David's proposal next week during the dev meeting.
-
quentinlesceller: @antiochp december 29.
- antiochp: "realistic".
-
lehnberg:
- Tue dec 22 - dev meeting
- Tue dec 29 - gov meeting
- Tue jan 05 - dev meeting
- Tue jan 12 - gov meeting
I'd imagine the 29th one maybe should be postponed?
-
lehnberg: Or we do a dec 22 gov + dev meeting bonanza. And then come back on 5th for the dev meeting again?
- jaspervdm: Yes sounds good @lehnberg. Don't think we will have a huge list of items anyway so we could do both meetings net week.
- lehnberg: Could also do a jan 05 gov + dev meeting bonanza again? And then from the 12th we can do it regularly again.
- quentinlesceller: I'd be in favor of doing both next week.
- 👍: antiochp
-
lehnberg: How's this?
- tue dec 22 - dev & gov meeting
- tue jan 05 - dev & gov meeting
- tue jan 12 - dev meeting.
- 👍: joltz, jaspervdm, antiochp, quentinlesceller
-
lehnberg: Sweet - so david's we can handle on 22nd, and antioch if you like we can take yours on 22nd or 5th whatever you prefer.
-
antiochp: Yeah sounds good.
-
lehnberg: Nothing new to update really, David shared that tradeogre seems to be working now with text at least?
- antiochp: Yeah that's awesome news about tradeogre.
-
lehnberg: @jaspervdm that tokio fix, is that going into 5.0.0?
- jaspervdm: Thats the plan yes.
- lehnberg: Very nice, might get that other exchange up and running soon again.
-
antiochp: Is the tokio runtime pr ready to go or still needing review?
- jaspervdm: Me and quentin tested it, but more testing can never hurt.
- quentinlesceller: Yep tested and looking good.
- 👍: antiochp
-
jaspervdm: (I also opened another small bugfix pr on the wallet today). We could get both fixes merged and release a new beta.
-
lehnberg: Cool - let's not derail into dev meeting.
-
jaspervdm: Yeah sorry lol.
-
lehnberg: Np. But we could continue dev discussions in #dev after this meeting?
- 👍: bladedoyle, quentinlesceller, antiochp
3. Lehnberg request for funding Q1 2021
-
lehnberg: Happy to answer any relevant questions. @antiochp please can you run this part?
- antiochp: Sure thing.
-
lehnberg: I think next quarter will be a lot about figuring out how work on grin will be post 5.0.0.
- 👍: joltz
- antiochp: Agree strongly on this.
-
antiochp: Hopefully everyone has read the forum post for the request.
- quentinlesceller: Just did.
- antiochp: Shall we give everyone a few minutes to (re)read it?
- quentinlesceller: Can we just pre approve daniel for like a year or so lol.
-
lehnberg: Tl;dr of funding request is
more of the same, q1 2020, 3 x £2,500. -
jaspervdm: @lehnberg's work is very valuable and the amount of funding he is requesting for it is modest. Of course I am in favor of approving this one. :)
-
antiochp: Is anybody against this or wants to raise any concerns or questions?
-
quentinlesceller: Same very much in favor.
-
joltz: 👍 from me without hesitation. Thanks for keeping us on the rails through another hardfork, looking forward to seeing what comes after v5:)
- quentinlesceller: Kinda excited for that.
- 💯: phyro
- antiochp: Yeah maybe we come out of q1 with some kind of (gasp) roadmap. At least directionally.
- 👍: joltz
- quentinlesceller: Kinda excited for that.
-
antiochp: (also very much in favor here)
-
phyro: +1
- 👍: bladedoyle
-
antiochp: Going to wait a couple of minutes for anyone to ask questions.
-
antiochp: Ok couple of minutes is up - I'm going to propose we approve this? Anything else to add?
- 👍: jaspervdm, joltz, phyro, quentinlesceller
-
antiochp: Approved!
- 🚀: jaspervdm, quentinlesceller, antiochp
- lehnberg: Thanks all!
- antiochp: Thank you!
4. RFC update
- lehnberg: FCP of PIBD ends today. Please anyone who has any opinions on this, raise a comment in the next hour or so, as it will be merged soon!
- 👍: antiochp
- lehnberg: To me, it reads very well, really nice work on this @jaspervdm and @antiochp.
- 👍: bladedoyle, joltz
- jaspervdm: Thanks!
5.1 Grinnode.live Winter Bug Bash Challenge
-
lehnberg: Really nice to see this initiative come together, I was wondering if there's anything we can do to support it?
-
quentinlesceller: I think this is an awesome initiative @mcmmike.
- 🚀: antiochp
- jaspervdm: Indeed.
-
bladedoyle: Support it by working to fix the bugs:)
- lehnberg: Yes, this too:)
- bladedoyle: Probably some effort needed to evaluate the testing results, prioritize, and then fix.
-
lehnberg: > we have approx. 0.75 btc + 2500 grin ready to distribute and we need your help with that!
Should we offer some grin from the general fund as well? Idk does that make a difference? Or btc for that matter, but 0.75 is already quite a lot.
- quentinlesceller: I think right now @mcmmike did not ask for funding. He is free to ask but I like the fact that we are not involved in this.
- 👍: joltz, mcmmike
- lehnberg: Yes indeed, so do I.
- antiochp: Yes @quentinlesceller agreed. I think this gives us a good opportunity to see what bubbles up in terms of community priorities.
- joltz: I think this is a positive decentralizing force for the community. It's nice to see work getting done from others and this seems like a good way to bring even more people in.
- bladedoyle: Everybody who writes or runs a testcase learns more about grin. finding a bug is a bonus.
- lehnberg: Cool - so I understand our position to be that we think it's a great initiative, while we we won't offer anything unless asked for it.
- joltz: And hopefully try to keep some bandwidth available to prioritize and address various things that may come in as a result.
- quentinlesceller: I think right now @mcmmike did not ask for funding. He is free to ask but I like the fact that we are not involved in this.
-
mcmmike: I would like to know, if we should test in areas which we haven't thought about? any input is good, as we will write test-cases for the community even when we start on the 19.12.
- 👍: lehnberg
- quentinlesceller: I'll have a look.
Meeting adjourned.