Meeting minutes
Minutes
<kaz> Oct-18
Ege: minutes are approved
agenda wiki cleanup
Ege: I have created subpages, I would like to delete the main page content
Daniel: how does this work?
Ege: they are available at https://
Ege: you can create any page there
Daniel: how is the table of contents generated?
Ege: it is automatic but you can manually disable it
Ege: there are some tutorials at https://
Daniel: we should not do it manually then
Kaz: you can follow the tutorial as well
Ege: I would like to delete them now
Ege: (deletes the wiki pages)
New Timeslot?
Ege: we have less people lately, should we change the timeslot?
Daniel: it is a bit problematic but I can manage
Daniel: also people might think that we have quite a lot already, so less importance on this
Kaz: changing the timeslot is fine but we should clarify the remaining tasks of the TF
Kaz: and who is needed for the work
Ege: I will create an issue and we can comment here until next week
remaining tasks
Ege: (lists the tasks in the github issue)
Kaz: I'm not sure if the Marketing TF needs to generate explainer documents. Probably each spec TF and the moderator should generate an Explainer document for their spec.
Ege: I will create the issue, as there are no objections to this initial list
Ege: we should not generate explainers, just integrate them to this page style. So a copy-paste work
JSON Schema Case Study
Ege: it is tracked at https://
Ege: it is public now at https://
Ege: I have tweeted it from our account too: https://
Daniel: It would be nice to get some statistics about it
Ege: I will reach out to them. Our tweet got the usual amount of likes
Ege: their tweet has more interactions than ours, which is nice
Ege: closing the issue
Issues
Issue 353
https://
Daniel: my machine picks the html, gh takes the md version
Kaz: the width, it is not an issue from our point but from accesibility point of view would have issues with the text in the iamge
Daniel: we also have two images
Ege: are svgs fine?
Kaz: we should simply split the image into the guy with the question and simple text
Kaz: or use alt text worst case
Ege: we should split it, also problematic for font size
Ege: we should have 1.1 only
… we should merge issues 353 and 340
Kaz: it is not clear why we need the detailed explainer here
Kaz: we can have an abstract text here and point to the td
… repository
Ege: it is better that people stay on this page
… and writing something new would mean more work to us
Kaz: I am objecting copying the existing resources to the marketing area
Daniel: I think we should have a single place
… we can remove from one or the other
Ege: we cannot remove from the TD repository
Kaz: it is problematic since the resource is generated by the TD TF
Cristiano: is it fine if we link to the resource?
Kaz: we should clarify who is responsible for which resource
Ege: can you symlink to the td explainer and let jekyll render it still?
Ege: we should avoid problems. Let's link to it
Ege: can I close issue 353?
Daniel: yes sure, I was not aware of 340
Daniel: what is the decision now?
Ege: if we can let jekyll render it from a link it would be nice
Cristiano: We should link to the source in any case
Kaz: It would not be really useful to the readers to provide a copy of the existing explainer. It would be more useful to provide some abstract description under the Marketing area and links to the existing explainer document and the spec itself than that.
Ege: in order to avoid problems, we should simply link to it. I will document it in the issue
Daniel: why do you want to link to branch?
Ege: so that we can have a static link
Daniel: but then, we need to track the changes all the time
Ege: true, we can simply link the main branch then
Ege: aob?
Ege: meeting is adjourned