Technical board membership and processes about ircv3.github.io HOT 4 CLOSED

Proposal to have a meeting, and possibly to regularly schedule ones in the future. Can't magically bring everyone back into activity, but can motivate people into doing things (like our informal meetup at #live a few years ago did). It can also unstick decisions where everyone's just waiting for someone else to say something, and to get quick reads over everyone's thoughts on specific proposals/PRs/etc.

We could make them TB-only or require TB members to be there, but that'd make the meetings an extra responsibility that may put people off (seems counter to the 'get more diverse range of opinions in the WG/TB' idea above). We could go for voice/video meetings, but given our membership that probably wouldn't work too well. So I think just something along the lines of "Meeting will happen in the IRCv3 channel at XYZ time" would work best. We'll probably want some basic rules to follow, just simple things so we can stay on-task, run through all the agenda items we want to, and finish in an appropriate amount of time.

We may use Doodle or framedate.org to organize it - in the past I've found https://www.worldtimebuddy.com/ pretty useful for working out timezones with different people but yeah, whatever works. Might want to collect email addresses of TB members to send details out if we schedule more meetings in future? And/or of parties interested in meetings generally? Or maybe we can just announce it here and in the channel and worry about all that later on.

Rough agenda:

• Go through the roadmap, check where we are on each issue.
  • See any issues/blockers/future work on issues.
  • Go through specs that've been kicking around for ages without any resolution, decide on how to resolve them or what work needs to be done to resolve them one way or another.
• Discuss how to fix the technical board to make people feel better about the WG process (I suspect this might be a more abstract discussion, but any concrete proposals from this issue could probably be discussed in particular).

edit:

• We definitely need someone to take a condensed list of minutes after the fact and post it somewhere on github where it's easily digestible and other people who weren't in the discussion can respond to it.

from ircv3.github.io.

I'd like to suggest we look at reinstating meetings with set times and agendas

from ircv3.github.io.

Regarding processes, ircv3/ircv3-specifications#215 and ircv3/ircv3-specifications#214 are I think the last places we explicitly discussed our processes around things getting ratified.

from ircv3.github.io.

opened #353 to plan times

from ircv3.github.io.