mark meeting as happening sporadically

[elf-pavlik]

we can add this correction while #322 stays open

[TallTed]

Suggested change

	Online panel meetings occur sporadically on Wednesday, 14:00 UTC at https://meet.jit.si/solid-authorization.
	Online panel meetings occur sporadically on Wednesday, 14:00 UTC at https://meet.jit.si/solid-authorization.
	For now, a meeting may be requested by raising an issue on the
	[`authorization-panel` repo](https://github.com/solid/authorization-panel/issues/)
	or posting to the [Solid CG mailing list](mailto:[email protected]).

[elf-pavlik]

SGTM, @matthieubosquet ?

[matthieubosquet]

I would rather keep issues to their current and primary use and I don't follow the Solid CG mailing list.

Links to HackMD and discussions about occurence of meetings have always taken place on Gitter until now, I don't see a very compelling reason to change the way things have worked until now. Especially for a temporary measure.

[elf-pavlik]

I honestly doubt that anyone will request the meeting, especially since we want to resolve the stable schedule ASAP.

I suggest merging the PR as it is and if @TallTed feels strongly about this amendment it could be proposed in a separate PR.

[matthieubosquet]

Sounds good to me @elf-pavlik .

[TallTed]

Links to HackMD and discussions about occurence of meetings have always taken place on Gitter until now, I don't see a very compelling reason to change the way things have worked until now. Especially for a temporary measure.

This does a very effective job of limiting meeting attendees to those who monitor Gitter 24/7, which does not include me, and you may have noticed my typical failure to attend.

This is far from a lowest-common-denominator invitation mechanism, and I do not consider it friendly to those who have not yet been involved with Solid and/or Solid-AuthZ efforts. In fact, I feel it is decidedly unfriendly to new involvement, and is not in keeping with the expressed basic ethos of the Solid project.

[elf-pavlik]

I think any discussion related to organizing meetings should follow in #325 including recommendations for announcing agendas and any upcoming meetings if the schedule is not fixed.

The purpose of this PR was just to amend incorrect information in README. If there is a need for more amendments before #325 gets resolved I think a small PR would be the fastest way to get it in.

[matthieubosquet]

I agree with you @TallTed that it is unintuitive and difficult to navigate the schedule of meetings (as you mentioned in response to #325.

I would suggest trying to address the calendar issue holistically on the CG level (in addition to addressing the specific need of AuthZ meetings in #325).