16:03:42 RRSAgent has joined #pbg 16:03:42 logging to https://www.w3.org/2018/02/13-pbg-irc 16:03:43 rrsagent, set log public 16:03:43 Meeting: Publishing Business Group Telco 16:03:43 Chair: liisa 16:03:43 Date: 2018-02-13 16:03:43 Regrets+ pbelfanti 16:03:43 Agenda: https://lists.w3.org/Archives/Public/public-publishingbg/2018Feb/0030.html 16:03:43 ivan has changed the topic to: Meeting Agenda 2018-02-13: https://lists.w3.org/Archives/Public/public-publishingbg/2018Feb/0030.html 16:14:38 Julian_Calderazi has joined #PBG 16:50:48 wolfgang has joined #pbg 16:51:36 jyoshii has joined #pbg 16:53:58 George has joined #pbg 16:56:23 Avneesh has joined #pbg 16:58:21 Brian has joined #pbg 17:00:21 rkwright has joined #pbg 17:00:33 liisamk has joined #pbg 17:00:35 present+ George 17:00:42 present + 17:00:43 Dan_Sanicola has joined #pbg 17:00:49 present+ 17:00:51 present+ dauwhe 17:00:54 present + rkwright 17:00:56 present+ 17:01:08 present+ 17:01:09 Rachel has joined #pbg 17:01:15 present+ liisamk 17:01:16 jkamata has joined #pbg 17:01:19 present+ 17:01:28 present+ 17:01:35 Hello everybody. Check mics are muted pls ;o) 17:01:50 laudrain has joined #pbg 17:01:52 will be mainly available on IRC due to unstable connection 17:01:58 Bill_Kasdorf has joined #pbg 17:02:00 present+ 17:02:00 present+ 17:02:08 present+ 17:02:16 present+ 17:02:21 present+ 17:02:35 present+ 17:03:17 scribenick: Rachel 17:03:20 present+ wolfgang 17:03:28 garth has joined #pbg 17:03:36 Topic: feedback for proposed charter 17:03:37 present+ Garth 17:03:43 present + 17:03:52 present+ Brian 17:03:55 https://docs.google.com/document/d/1OKmYjSGRx7ttipWTmngGHQkJmxnrH2tcePFOb-gQ7Pc/edit#heading=h.k3859or7msx 17:03:55 EDRLab summit prep is running long. What is the plan for conf call? 17:04:01 mateus has joined #pbg 17:04:02 BillM: looks okay to me 17:04:03 q? 17:04:13 q? 17:04:22 present+ Brian 17:04:45 George: clarification - the community group and their specifications would be approved by the CG and would no longer need the BG to approve? 17:04:50 present+ 17:05:19 q? 17:05:27 dauwhe: that's not what it says. it reflects BG approval of CG documents as was documented in the merger agreement. 17:05:54 ... it's unusual for W3C but it's also unusual for a CG to manage rec track work 17:06:11 ivan: it is not - we need to be careful about this 17:06:56 ivan: the w3c process for rec track work does not apply here 17:07:03 q? 17:07:32 George: having the PBG approve the CG may help in terms of IP 17:07:34 laurentlemeur has joined #pbg 17:07:40 What about renaming steering committee to coordination committee? 17:07:40 present+ 17:08:07 George: the sooner we get to epub4 the better 17:08:10 q? 17:08:18 present+ RickJ 17:08:37 rickJohnson: it might benefit all of us to explicitly state why we need to have this approval 17:08:43 zakim, who is here? 17:08:43 Present: George, ivan, dauwhe, Dan_Sanicola, Avneesh, liisamk, Rachel, BillM, Bill_Kasdorf, laudrain, tzviya, jkamata, Julian_Calderazi, jyoshii, wolfgang, Garth, Brian, mateus, 17:08:46 ... laurentlemeur, RickJ 17:08:46 On IRC I see laurentlemeur, mateus, garth, Bill_Kasdorf, laudrain, jkamata, Rachel, Dan_Sanicola, liisamk, rkwright, Brian, Avneesh, George, jyoshii, wolfgang, Julian_Calderazi, 17:08:46 ... RRSAgent, Zakim, BillM, tzviya, ivan, Karen, bigbluehat, dauwhe 17:08:54 q+ 17:08:54 present+ Karen 17:09:18 garth: it dates back to the merger - the BG was where all members could join without money but there are ongoing legal challenges with the merger and this protects our agreement moving into that space 17:09:54 ack BillM 17:09:57 RickJohnson: outside of the legal issue my understanding was the board approved spec releases in the IDPF and this is replacing that board 17:10:33 BillM: I think Garth explained this well, the w3c inherited this through some unspecified process and decided not to make this a rec through the standardized process 17:10:46 ... the BG will provide some formality to the CG 17:10:59 ...where CGs traditionally did not produce specs etc 17:11:03 +1 to BillM 17:11:18 q+ 17:11:27 q? 17:11:35 q+ 17:11:35 ...there is no real precedent to this at the w3c. You can see this as an expedient way to introduce changes 17:12:15 rickjohnson: of the fundamental issue is that there is a group outside the CG that sways the CG work then should that be managed within the CG instead 17:12:17 q+ 17:12:23 q+ 17:12:34 BillM: that was an explicit decision of the directors and TBL 17:12:49 ... there may be complaints 17:13:15 rickjohnson: if we can insert business oversight into the CG then that might be the solution we need 17:13:19 ack Bill_Kasdorf 17:13:38 Bill_Kasdorf: there is def a precedent for things deevloped in a CG and then headed to a rec track 17:13:50 ...the BG is not just involved with the CG but also the BG 17:13:56 s/deevloped/developed/ 17:14:06 q? 17:14:15 ...it is meant to provide a business perspective. It's reasonable to provide this kind of role 17:14:27 ack Brian 17:14:33 ...this work from the CG will inform the WG and epub4 17:14:53 Brian: does the CG in managing epub3 go away when epub4 is released? 17:14:56 ivan: yes 17:15:09 garth: upon the retirement of epub3, yes 17:15:31 Brian: there was some discussion of a 2 year window for the CG? 17:15:40 dauwhe: the CG has no expiration date 17:15:56 BillM: the BG has a 2 year charter 17:16:29 q+ 17:16:49 ... after 2 years the BG charter needs to be reissued, but the CG itself has indefinite life 17:17:08 JensKlingelhofer has joined #pbg 17:17:42 I don't think the PBG charter expires. It's undated, as are other BG charters. 17:18:02 ... every commitment can vary in length, but most are 2 years in length (like the BG) 17:18:58 Current PBG Charter: https://www.w3.org/2017/02/PublishingBGcharter 17:19:06 ...as garth indicated if epub3 is in maintenance mode and development has stopped, we likely won't need an epub3 community group but we are a long ways away from that time 17:19:50 ack liisamk 17:19:57 +1 to what Brian just said 17:20:07 Brian: I agree with RickJohnson and his perspective in integrating oversight in the CG but since the agreement is in place regarding the 2 year time period, I will respect that and reraise in one years time if necessary 17:20:24 q- as liisamk made my point :) 17:20:28 q? 17:20:31 liisamk: this charter is undated and there is no wording in the charter indicating the time limit 17:20:31 q- 17:20:33 ack garth 17:21:09 garth: I think we should continue as we are until the merger is formally closed. 17:21:19 q? 17:21:30 ... we've come a long way in resolving this with 25 +1s, 1 0, and 1 -1 17:21:57 "When the group discusses an issue on the mailing list and there is a call from the group for assessing consensus, after due consideration of different opinions, the Chairs should record a decision and any objections. " 17:21:59 liisamk: should we approve or put it out to a 72 hour vote 17:22:06 q+ 17:22:32 ivan: it's up to us how we manage ourselves. However, having a 72 cooling period for the vote may be a good idea. 17:22:38 ack BillM 17:23:02 s/25/something like 25/ 17:23:03 BillK: then we would have numerical documentation of the votes 17:23:26 Note that I've resolved all the comments on the Google Doc 17:23:33 BillM: theres no firm requirement one way or another but a vote would be beneficial 17:23:40 liisamk: sending out for vote 17:23:50 Topic: Revised slate 17:24:02 BillM: the adjustment mentioned in email 17:24:05 ...? 17:24:15 q+ 17:24:22 ...we had 2 folks offering to engage from the Japan side 17:24:31 ... ??? was willing to serve as colead 17:25:06 Rachel: it is Daihei Shiohama (Media Do) 17:25:13 s/???/Daihei/ 17:25:28 ... the two Japanese representatives have agreed to share responsibilities. 17:25:43 proposed additional co-chair is Junichi Yoshii (Kodansha) 17:25:46 ...this ensures representation from Japanese publishers 17:26:18 ...Daihei Shiohama and Junichi Yoshii would lead together in the external coordination task force 17:26:29 q+ 17:26:32 ack ivan 17:28:02 Ivan: w3c staff are ex-officio on these groups, for the record 17:29:06 Brian: this working group is meant to coordinate with other groups 17:29:15 ... I would want to hold at three 17:29:25 ...so the overhead doesn't out weigh the outcome 17:29:32 ...(task force) 17:29:51 PROPOSED: new Steering Committee slate (including co-chairs and BG task force leads as previously communicated, with addition of Junichi Yoshii of Kodansha who has been added as a co-chair of the External Coordination task force) is considered elected by consensus 17:30:05 q+ 17:30:23 ivan: should we reconsider the name of steering committee as it is a loaded term 17:30:41 George: we may need to until the merger agreement is fully in place 17:30:43 +1 17:30:54 q- 17:31:08 BillM: we need the name to remain in place since it is specified in the IDPF/W3C merger documents 17:31:12 ack Brian 17:31:14 q- 17:31:19 ack Brian 17:31:48 I think we agree. 17:31:56 liisamk: do we need to put this out along with the revised charter 17:32:05 +1 17:32:10 garth: I think we should put it out and just count the votes this time 17:32:33 q+ 17:33:07 ack Brian 17:33:35 Brian: the issue that is not easily addressed from daniel is being creator and evaulator 17:33:54 ...the resolution there is in resignation from one or the other groups 17:33:58 q+ 17:34:05 ...we should put to a vote 17:34:06 ack laudrain 17:34:15 s/evaulator/evaluator/ 17:34:16 Avneesh has joined #pbg 17:34:26 laudrain: I want to mention that of the people on the slate, we have no negative votes. Daniel didn't vote. 17:34:41 ...his objections was and are still with the charter 17:34:48 s/vote./vote against./ 17:35:07 +1 17:35:08 liisamk: can we move ahead? 17:35:10 +1 17:35:10 +1 17:35:10 +1 17:35:11 +1 17:35:11 +1 17:35:12 +1 17:35:14 +1 17:35:14 +1 17:35:16 +1 17:35:16 +1 17:35:17 +1 17:35:20 +1 17:35:20 +1 17:35:21 +1 17:35:21 +1 17:35:26 +1 17:35:34 +1 Rick Johnson 17:35:35 +1 17:35:55 RESOLVED: new Steering Committee slate (including co-chairs and BG task force leads as previously communicated, with addition of Junichi Yoshii of Kodansha who has been added as a co-chair of the External Coordination task force) is considered elected by consensus 17:36:00 liisamk: let's move forward 17:36:08 Topic: proposal for funding epubcheck 17:36:09 Topic: Epubcheck 17:36:48 rickjohnson: coresource is a sister company that sees lots of epubs flowing through 17:36:59 ...we asked who relies on epubcheck 17:37:25 ...there were 20-25 a level publishers and 5-6 key channels that are hurt by eubcheck not remaining current or functional 17:37:40 ...we can ask each of them for a $5000 donation for support 17:37:48 s/eubcheck/epubcheck/ 17:37:53 ...I've asked tzviya to help write a purpose statement 17:38:14 ...that is well over $100K that we could raise to hire a developer to do this work 17:38:20 laurentlemeur has joined #pbg 17:38:24 q+ 17:38:31 liisamk: essentially we would be talking about crowdsourcing funding 17:38:42 ... is there a plan for maintenance? 17:38:56 rickjohnson: this would be primarily for upating 17:39:07 q+ 17:39:10 liisamk: BillM? 17:39:16 q+ 17:39:20 s/upating/updating/ 17:40:07 BillM: bring epub up to snuff, track it to the latest version, deal with the languishing pull requests and technical debt - if that costs $100K then we should assume a fraction of that for support. 17:40:29 ... if someone funds $5K for updating, can they also pay $1K in maintenance fees a year? 17:40:40 ...is there a fee schedule that is reasonable for these players 17:41:52 ...we may need a more significant investment for epub4 17:42:00 ack tzviya 17:42:11 tzviya: there is a draft statement 17:43:10 ...there is a maintenance release, an update release, and a total rehaul. We need a discussion about who would work on this and how many hours this would take - including the hours needed for the tiers of development 17:43:17 ack rkwright 17:43:31 rkwright: I and readium would like to particupate 17:43:50 ...I did some work with Romain to spec out what needs to be done 17:43:53 s/particupate/participate/ 17:44:09 ...and I want to work with this group to see how it should be done etc 17:44:27 q? 17:44:33 ack laurentlemeur 17:44:54 laurentlemeur: it's great to have the BG sizing this and estimating needs 17:45:02 q+ 17:45:15 ...this is a good way to have an independent org managing this money and plans 17:45:23 q+ 17:45:26 liisamk: are you proposing readium manage the money 17:45:55 laurentlemeur: the BG has no bank account and readium is a technically focused company so this seems reasonable 17:45:56 q- 17:46:01 ack George 17:46:22 george: as long as DAISY and others can participate I think this would be terrific 17:46:31 ack billm 17:46:41 BillM: I agree with laurentlemeur 17:46:57 ...a low overhead, focused group will spend funds most efficiently 17:47:29 ... the first line of business is to see what the market will bear 17:47:45 ...we shouldn't rule out the w3c as managing the funds 17:48:09 ...let's start with a prospectus and maybe some quid pro quo 17:48:40 ...allowing contributers to work on the task force determining the future work to be done 17:49:15 liisamk: feelings about this as a fundraising method? 17:49:19 +1 17:49:23 +1 17:49:23 +1 17:49:23 garth: absolutely 17:49:24 q? 17:49:26 +1 17:49:30 +1 17:49:32 +1 17:49:37 +1 17:49:42 RickJohnson: I'm coming for all of you 17:50:01 q? 17:50:23 liisamk: let's get this compiled and distributed 17:50:26 +1 17:50:32 ...then we can follow up on the prospectus 17:50:43 present+ JensKlingelhofer 17:50:53 rickjohnson: I don't know if we can make the list from coresource public 17:50:54 hahah 17:51:11 ...so the source of the messaging might be Ingram rather than w3c 17:51:15 q+ 17:51:20 ... I need to make sure we have permission 17:51:22 ack tzviya 17:51:41 tzviya: we should not put the whole burden on coresource 17:51:55 like Amazon? 17:51:56 ...we should contact apple and other companies that rely on epubcheck 17:52:19 q? 17:52:44 Topic: Kicking off task forces 17:53:13 Hachette is so flush they can put two people on this call 17:53:16 liisamk: how should we move forward with these task forces 17:53:28 smaller task forces should be ok for me. 17:53:46 ivan: each task force will be unique. I'm not sure there's a universal role. 17:53:54 q+ 17:54:06 garth: maybe a document that each team can contribute to that will work to shame people into action 17:54:18 laurentlemeur has joined #pbg 17:54:27 q+ 17:54:32 ack la 17:54:36 laudrain: should we use the task force system 17:54:48 ivan: people are still afraid of github 17:54:56 ack laudrain 17:54:57 liisamk: so we should use google docs? 17:55:00 ack tzviya 17:55:23 tzviya: it might be helpful to feature different task forces on the call. 17:55:35 me/ Shame == Opportunity for Fame 17:55:55 liisamk: anything else 17:56:17 laudrain: I will put myself on the hook for the next call 17:56:50 George: can we send out a redlined and not redlined version? 17:57:00 q+ 17:57:02 liisamk: yes, we should do that 17:57:06 ack garth 17:57:28 +1 17:57:28 Liisa++++ 17:57:32 +1 17:57:33 garth: this is the first time in a while that this felt like we were moving in a positive direction 17:57:45 present+ karen 17:58:04 by all! 17:58:07 BillM has left #pbg 17:58:09 bye* 17:58:09 rrsagent, draft minutes 17:58:09 I have made the request to generate https://www.w3.org/2018/02/13-pbg-minutes.html ivan 17:58:43 rrsagent, bye 17:58:43 I see no action items