Change meeting time to avoid clash with Solid CG weekly #322
Conversation
|
I will not be able to participate given that change. I think we should look at the general reorganization of panels since the participation has been pretty low for a big part of this year. My counter-proposal would be to mark panel meetings as suspended, as well as add a link to a new tracking issue for deciding on the future of this panel and its meetings. |
|
-1 as 15:00 UTC conflicts with the W3C RCH WG weekly meeting. I submit that a change like this should start as an Issue, probably with a link to something like a Doodle poll, rather than going straight to a PR. |
|
Matthieu did a quick run of the proposal on Gitter chat in which this PR reflects. If people would like to attend meetings but can't for the proposed slot, then alternatives can be proposed. It is challenging to find a slot that works for everyone so unanimity shouldn't be the aim here. Reducing objections is key. Granted if participation is low or there are logistical issues, okay to omit the information about the weekly meeting and suggest that meetings can be held ad hoc to help move things forward. |
It would have been (would still be) helpful to link to that chat log. Also, I submit that Gitter is an insufficient forum for such proposals. I can't help but believe there are other involved and interested people like me who cannot monitor all relevant Gitter/IRC/Discord/Slack/etc. channels 24/7/365. If Wednesdays are a must, then I'll suggest the possibilities of 13:00 UTC, 17:00 UTC, or 18:00 UTC, which at least do not currently conflict with anything to which I'm committed. Clearly, I've no idea about anyone else's calendar. |
Conversation starting at https://gitter.im/solid/authorization-panel?at=63359f977ccf6b6d45fac9e7 . I try to funnel CG-wide (simple) discussions and coordination to Gitter solid/specification, and everything else into GitHub. I get your concern with monitoring / organising with so many mediums/channels. Hopefully we'll re-organise/visit panels/task forces through the CG weekly meeting or at least to draw more attention on the activities and how we can proceed. It'll sort out. We'll add the recurring meetings on W3C calendar. |
|
I think the change I suggested above, can be merged quickly we can take time to figure out when (and if) we want to hold panel meetings. As I said during the call today, AuthZ has to be taken into account in all the other parts of the solid ecosystem and I think it should be worked alongside the core protocol. |
|
Pavlik, are you objecting to updating the time of the weekly meeting? That's what this PR is about. Perhaps you can work with those that would be open to an alternative datetime? See how TallTed is being constructive on that front. Or are you objecting to others having a meeting? It'd be important to know why, and if that's something you don't want to share in public, you are welcome to ping me in private. And, as I've said during the CG weekly call, all work items (and their general categories) is of interest. I've emphasised that we have limited time. There are other work items and components that could just as well be central - I gave Identification/Profile as one example, and a whole topic on why Quality Assurance is arguably central to our work. There was even a dedicated Call for Editors to pick up the Authorization UCR today! In fact, the only topic in today's agenda that actually had to do with a specific issue that was about Authorization. Were you present during those discussions? Don't worry, no one overlooked the importance of authorization, and we'll make sure to keep things on track. I don't understand what your off-topic spamming with links has anything to do with the issue here but we don't have to "merge quickly". This PR is literally about re-initiating interest and deciding on time. |
Relax @csarven this was just a simple copy & paste mistake, I've fixed the link to point to my comment above.
Looking at https://github.com/solid/authorization-panel#participation
I see no reason to keep that incorrect information out there while we try to figure out a different schedule. We can also make separate PR to just remove the incorrect information and keep this one open for however long it takes. EDIT done in #324 ✅ Looking at https://github.com/solid/authorization-panel/tree/main/meetings There are 10 meetings recorded in 2022 so far. I see my name listed under Present all 10 times, while yours @csarven just once in April. Please keep in mind that you might not be very aware of this panel's activities in 2022. Last meeting only @matthieubosquet and I participated. I don't think that the problem is related to a specific schedule.
None of those hours would work for me on Wednesday, and anything after 20:00 UTC might not work for others. If there are fewer than 4 responses, I think this will signal that there is not enough interest in having a dedicated AuthZ panel meeting. I could look into setting up a such poll myself at the beginning of November, if someone has time to deal with it before that it would be great. |
|
Following your feedback and the CG meeting suggestions, I opened an issue to agree on a mutually convenient time for meetings focused on Authorization UCRs. The first step prior to that would be to have enough people expressing interest in giving attention to the authorization UCRs. I think that having a provisional day and time for sporadic meetings about authorization would be preferable to stating all panels as completely paused, which seems inaccurate as work on authorization, for example, keeps happening and is needed. Given that agreeing on a new mutually convenient time for now seems besides the point and controversial, I would propose that meeting times remain unchanged despite the clash for now and to simply update the frequency with a note of the current clash. @elf-pavlik I'll close this PR and follow-up on yours since they seem like duplicates of each other. |
The Solid CG Weekly will be happening at 14:00 UTC on Wednesdays which clashes with the current authz pannel meetings.
Pushing it by one hour would avoid the clash.