Here’s the agenda for the meeting on 2022-03-23T18:30:00Z.
This meeting will be about our backlog. We will go through our oldest tickets, and provide an update for each of them.
Announcements
F36 Beta (NO-GO, next target date is Mar 29, next Go/No-Go meeting is Mar 24 17:00 UTC)
Minutes and logs from today’s meeting are available.
@bcotton since you were not there, we took the opportunity to assign you an action
If you could take a look at #65 about release date in release notes, it’s an old one, but we think it’s still a good idea. @py0xc3 we quickly looked at #189, and we think it would be a good idea to write the list of final members in this ticket, just to be sure not to forget anyone. Then start the cleaning next week.
What do you think?
It’s not clear from the logs or the ticket what you want me to look at. We could certainly add the release date to the release notes, but that’s something anyone contributing to the release notes can do.
If I remember correctly, the idea was there would be someone, either a human or a script, taking care of the release notes. And you might know who that someone is and ask them to systematically include the release date, e.g. on the first page.
I do not think I need such access at the moment.
The reason I am involved in these discussion is because I am slowly updating the Package Maintainer Docs.
I do not see myself contributing to other docs in the foreseeable future.
So, my interest lies in what is needed for writing team documentation:
tooling and documentation contributor docs.
Contributions from my side will be single fixes for particular problems I run into.
I think the pull request workflow is the most suitable for such contributions.