<scribe> ScribeNick: myles

jpamental: my motivation is, since i'm starting to talk about it in conference talks, people are starting to asks. Rather than direct them to the Google team's demo, I wanted to be mindful of a few things so we can set the stage appropriately and set expectations. What are the problems we are trying to solve?
... I wanted to be sure to write this up from the point of view of how this will impact users on the web. Letting people look at this tool and see what it's doing. Or they can see the screenshots and explanations.
... I was hoping to get everyone's eyes on it. Am I getting the history right? What about context and expectations? I think I've been vague enough in certain areas that keeps us from getting put in a corner. My intent is to send this to my Web Typography Newsletter, and it will live on my website. Not really as a great place for this to live forever, but there's nowhere else better.
... What I've been doing is publishing things in a Web Typography publication on Medium as well. We can decide where we want this published. It doesn't matter much to me. And we can augment this with a link to additional materials if possible. Like issue trackers, etc. I didn't link to the existing one because it doesn't have any information about what we're working on.
... A few people have already looked at it. Please add comments corrections or additions.

Vlad: Thank you. It's a great opportunity to bring this work to some level of visibility in the public. I dont
... I don't know if anyone outside this group knows what's going on

jpamental: That's what I discovered last week at <inaudible> conference. The only people who knew anything about it were Rachel Andrew, and one or two other people. This is something that will have a lot of interest, especially in combination with the emergence of variable fonts. They are interesting hand-in-hand

Vlad: This is useful and important. We should have something out there that people can see that things are happening. My only concern is setting the level of expectations. I don't want publicity to drive the need for a solution... I don't want to publicize a half-baked solution. If we can balance those two, that would be great
... I don't want to say that this work will take as long as WOFF2 did, but it will take a while until it's optional, widely implemented, and well tested

jpamental: I don't want to time the "marketing" wrong, and get people too excited too soon. But it took a number of years for Rachel Andrew campaigning around grid, and it took a significant amount of attention to make sure it landed. I thought it would be a good idea to get the idea out there and get people talking about it, to plant a seen in people's mind. Then we can turn it up a notch as things become more concrete.

Vlad: Your immediate plan is to release this tomorrow in the next issue of the Web Typography Newsletter

jpamental: Yes, unless there are objections

Vlad: If anyone has any objection, please say now

myles: I'd like to spend some more time with it (hours, not days)

jpamental: sure

Vlad: for Adobe and Google, Jason speaks a little bit about priorities and existing solutions. TachyFont, unicode-range subsetting. Also it doesn't mention static subsetting

jpamental: I tried to describe it but I didn't do a very good job at it.

Garret: I can make a review after the meeting and give feedback.

Vlad: I think you provide just enough detail to say "this is not something that is completely new and unexpected"
... I just wanted to mention everyone who's company names are mentioned so they could have a chance to review

Garret: I don't see a problem with it

Vlad: It's just a historical reference "these companies did something, and now we're working to do it better"

Garret: Yes, that's the right message

jpamental: In the "Setting the Stage" section, I wanted to make sure I'm not missing anyone. If I forgot anyone, please let me know and I can rework it
... I wanted to distinguish people's efforts on behalf of the W3C as distinct from people's efforts on behalf of their organization. Rather than me making assumptions about what should be said in public, I would let people come to me

Vlad: Probably the right way to do it as far as company names are concerned
... Just to give this a defined state, would it be okay if we jointly make a group commitment to review this over the next hour and contact Jason?

jpamental: By the end of the day would be helpful
... Or if you have future plans, please let me know so I can include them

Vlad: Silence counts as approval
... Please let Jason know by the end of the day

jpamental: When this goes out, I'll send a note to the group as well

Vlad: Any other topics?

Garret: At the last meeting I was asked to add a VF and CFF font to the incremental transfer demo. I did it.
... There are two more fonts in the dropdown

jpamental: thank you!

Garret: I'll also add some Indic and Arabic fonts as well

jpamental: That would be awesome. I mentioned it but I don't have any way to talk about it. It would be great. Then I can ask someone to help me get some of those test things, so we can tease out more of this as we go

Garret: That's all I had.

ChristopherChapman: Can I recommend Noto Nastaliq for Arabic for its complexity

Garret: okay

Vlad: It's also beautiful

jpamental: yeah

Vlad: it will be noticeable

jfkthame: Can we have Noto Nastaliq and a more typical Arabic font? Noto Nastaliq is interesting but atypical

Garret: yep, got it. I can do that.

ned: While you're doing that can you also fix the font itself?

Garret: I can pass the message along

jfkthame: like Noto Naskh

Vlad: anything else?

<silence>

Vlad: Okay then. That was short and productive. Thank you jpamental!

jpamental: I'm excited to do this, and appreciate everyone being okay with my work

<goodbyes>

None

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: Vlad, ChristopherChapman, jpamental, Garret, jfkthame, myles
Present: Vlad ChristopherChapman jpamental Garret jfkthame myles
Found ScribeNick: myles
Inferring Scribes: myles
Found Date: 25 Apr 2019
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)