CG Meeting agenda 2024-03-06

[hzbarcea]

Draft agenda for the 03/06 CG meeting

[TallTed]

(@hzbarcea — Please change PR title from CG Meeging to CG Meeting!)

[TallTed]

Repeating inline comment, so it's more persistent/visible after change suggestions are applied.
Note that #555 still looks alive. Someone coming back to it, to see the latest addition to the bottom of the table, won't necessarily see the top-posted notice that it's been closed with new info being posted at . I suggest adding <strike> or similar to make clear what is no longer valid. https://github.com/orgs/solid/projects/16 requires more thinking, parsing the date column which is no longer in ISO-numerics, figuring out that "status — done" means the meeting has been held... and now, it's even more challenging, because the last dated entry is March 5 (which is now in the past) and shows status "discussed" instead of "done" or at least "scheduled" which seems to make more sense for a date in the past....

[TallTed]

(Repeating inline comment here, where it will be more visible and persist after change suggestions are acted on...)

Note that #555 still looks alive. Someone coming back to it, to see the latest addition to the bottom of the table, won't necessarily see the top-posted notice that it's been closed with new info being posted at https://github.com/orgs/solid/projects/16. I suggest adding <strike> or similar to make clear what is no longer valid.

Also note that https://github.com/orgs/solid/projects/16 requires more thinking, parsing the date column which is no longer in ISO-numerics, figuring out that "status — done" means the meeting has been held... and now, it's even more challenging, because the last dated entry is March 5 (which is now in the past) and shows status "discussed" instead of "done" or at least "scheduled" which seem to make more sense for a date in the past....

[csarven]

@hzbarcea , you can batch the suggestions from the "Files changed" tab ( https://github.com/solid/specification/pull/633/files ) and then make a single commit. That way, only a single (email) notification is sent out where individually accepting the suggestions sends out separate notifications. The former would be less annoying and would be sufficient for something like the minutes I think.

Also... when you finally merge the minutes, please Squash them.

[csarven]

Suggested change

	* Status: Draft
	* Status: Published

[hzbarcea]

Thanks @csarven, I already made this change yesterday: 7dff115. Noted the squashing request.

[TallTed]

Still titled "Meeging"...

Should be titled "Meeting"...

[michielbdejong]

I'm seeing:

Merging is blocked
The base branch restricts merging to authorized users.

@VirginiaBalseiro can you see if you can fix that?

[csarven]

@michielbdejong , you (and other chairs) have access to merge PRs even without approvals. (PRs on this repo require one approval, and there is already one here.) So I'm not sure why you can't squash merge or bypass?

[VirginiaBalseiro]

@michielbdejong can you check now? I updated one rule that might be related. If not, then I am not sure what is wrong.

[michielbdejong]

That worked apparently, thanks @VirginiaBalseiro!