GWGI brought it up at HWC last night as an example of how we did smaller geographic events at concurrent times in the past, as a possible option for the future
[tantek]GWG, I feel that depends a lot on what the goals are for that session, because it could be so many different things, and some things depend on other things
GWGWe could go macro or micro. Big picture... discussing the change control challenges so we can close off other issues outside of the meeting, or picking a few big ticket items
[tantek]I feel the most important thing is making the change control more efficiently usable to more folks to help increase the number of folks that can help nudge issues along
[tantek]So to that extent, maybe we could start by trying to gather challenges / obstacles that folks have encountered when they've tried to work through change control, or in anyway move an issue forward.
[tantek]right. the change control steps are all supposed to be able to work asynchronously so the overall question should be why is that not happening?
gRegorI think a lot of it happens async in the github issues, but it's been convenient at an indieweb meetup with several people in the room to make the final resolution.
gRegorUsing the github issues is still kinda new, too. I think it was 2017 Portland when we finally cleared out old issues still on the wiki and put the notice for new issues to go on github
[tantek]GWG, I'm looking for feedback on are the steps in change control understandable (if not, what questions?), reasonable (if not, what feels too burdensome/heavy?), and sufficient (if not, what else seems necessary to add?)