Meeting minutes
<wendyreid> date: 2025-02-07
<toshiakikoike> I use Loqui (linux)
Final discussion on WG Naming
wendyreid: Good news - charter passed! No votes against
… we are now official, BUT ...
… 2 responses included comments
… There is a feeling that "Publishing Maintenance Working Group" isn't really correct
… Do we prefer PMWG or PWG or what?
sueneu: Are we aligned with other groups on our name
mgarrish: It's a royal pain to switch names, have to change the mailing lists, etc
… How many times, and why?
<gpellegrino> +1 to Matt
AvneeshSingh: I wish Ivan was here, he is better at explaining this
… when we discussed with the team, some arguments were legacy of PWG (kind of failed), and why bother (echoing Matt), and 3rd what is the message to the community?
… specifically the publishing community, not w3c
… Don't want to worry people that we will make huge changes
wendyreid: Context - when we started we were PWG (which struggled), but that did not have epub
… then we were epubwg, and it was done
… so then we were pmwg
… So we are still maintaining but also expanding
… Other groups tend not to have maintenance
ivan: I check with Phillipe and we are not required to change the mailing list and identifier, so we can stay PMWG for internal details, but then change our publicly facing name
… Not saying we should, just that we are not required to
wendyreid: Feeling sounds like we keep the name, does anyone disagree?
ivan: We can have an official resolution and send it on to commenters
<wendyreid> Proposed: The working group will keep the name Publishing Maintenance Working Group
<ivan> +1
<gpellegrino> 0
<dhall> +1
<CharlesL> +1
<dlazin> +1
<sueneu> 1
<duga> +1
<mgarrish> +1
<wendyreid> +1
<toshiakikoike> +1
<AvneeshSingh> +1
<Dale> 0
<gautierchomel> +1
<shiestyle> +1
<MasakazuKitahara> +1
<ikkwong> 0
RESOLUTION: The working group will keep the name Publishing Maintenance Working Group
Meeting Timing
wendyreid: Poll results - we said Thursday at 9am Eastern
… But maybe people didn't consider the time change
… Was going to tie it to Japan time so it doesn't change. But that means it will be 10am this summer
duga: I don't care, but surprised people voted considering the time change, and probably they meant that time slot
ivan: I believe we are just used to the situation that we are set to Boston time
… Which is just the normal 2 week EU/US mess
… which is what I had in mind.
… But we decided to anchor this group in Japan time, so we are an exception
wendyreid: If I set this up as Eastern then it changes in Japan
shiestyle: [Translating for Japan folks]
… It is currently 11pm, we could move to midnight (it is acceptable)
wendyreid: Actually, I think it will be 10pm, not midnight
… it will now be Thursday, 9am Boston time, as is standard for w3c
<AvneeshSingh> It would be good for Asia. The qustion is more for Brady, every meeting will be at 6 AM!
wendyreid: Next meeting is Feb 13th
duga: Next meeting is first meeting?
wendyreid: Yes
duga: We have to rejoin?
Ivan: Yes, there are new deliverables
ivan: There will be a 45 day grace period, but then you have to rejoin
… By Tuesday we will be the new group
wendyreid: So AC reps have to do their thing (rejoin or approve)
Taskforces
wendyreid: Last meeting we started to discuss TFs, I would like to confirm this week
… Laurent isn't here, but he did volunteer last time for Annotations
hadrien: I will contact him to verify
wendyreid: I think you (hadrien) had agreed to comics
hadrien: Yes.
wendyreid: FL is still me
<ivan> pesent+ dale_rogers
Horizontal review experts
wendyreid: Other thing is to have other people lead horizontal review when the time comes
… We have clear people like i13n, a11y, etc
… Others are less obvious (e.g. Privacy and Security)
ivan: Just to remind you, if we get late to horizontal review, it creates a problem at the end
… We keep banging up against HR, then we can't publish, etc. Painful loop
… Better is to start as soon as possible, track all the issues, ping as needed, etc so we have no issues when we want to publish (or no surprises)
… You don't have to be a security expert, this is more for making sure the experts are pulled in as needed
wendyreid: Last review was long because we had never been through the review before, and we want to avoid that this time
… Just something to consider if you want to volunteer later, or if you know someone who wants to volunteer
Hadrien: we have been working with Brazil a lot on edu recently
… they are making epub books available to all students in Brazil
… There is an issue with access to the volume (e.g. just chapter 1)
… I wonder if this is something we can tackle with what we have in the spec now, or if there is a better group for it
wendyreid: For the sake of tracking, we should log this. But also, where do we log issues?
… We have PMWG, and we also have EPUBSPECS where the actual doc maintenance happens
… Maybe it should be PMWG?
ivan: pmwg can be used for whatever we want. Currently that repo is for admin only, but it can be used for whateve we want
… Opening a new one doesn't make sense
… We also have one for the publishing manifest and one for audiobooks
wendyreid: Hadrien, can you put an issue in the PMWG repo?
… I was thinking PMWG for broad issues, then the individual spec repos for specific items
F2F Meeting
AvneeshSingh: It would be helpful to understand the theme of the first face to face
… Just wondering if I should extend to cover those days
<duga> +1
wendyreid: I will create an issue for the f2f
… It will probably be a lot of brainstorming and hashing out the work, maybe starting work on some items
<ivan> B.t.w. Meeting practicalities
ivan: We should get some presentations on the big TF issues
… So what exactly is annotations now?
… The same for webtoons
… There are some things in a11y
… Then maybe discuss toHTML or not to HTML
… I have a page with all the practicalities [see above]
wendyreid: Anything else?