<stakagi> I am fine!
<krit> Zoom usage at W3C: https://www.w3.org/Guide/meetings/zoom.html
<krit> New Slack channels at W3C forward email to internal WG mail soon.
<Tavmjong> Having trouble connecting.
<krit> Join by phone :+1-617-324-0000 US Toll Number
<krit> Scribe
<krit> ScribeNick: AmeliaBR
<scribe> Scribe: AmeliaBR
Dirk: There's a new W3C slack
channel you can sign up for; forwarded the email to the group
list, but this is public info, can invite others.
... The W3C is also exploring using Zoom as an alternative to
WebEx, see link above. Given our connection issues, might be
worth trying out.
Amelia: We could ask Chris to set us up with a Zoom meeting to see if it works better than WebEx.
Dirk: Slightly different issue: we've had trouble getting everyone on at the same time. Maybe partly with summer time shift. But do ask if there's a need for a different time.
<krit> ScribeNick: krit
AmeliaBR: when we talked 4 weeks
ago, main focus was on getting more contributors... especially
on testing. Targets would be implementers, especially browser
implementers. Idea was to sign up a special meeting or time
where ppl could call in for virtual work sessions. Start would
be to assign tasks for the test suite.
... More than 1.5 years ago I went through each chapters and
change logs to see what needs testing. Will get back with the
list. Hopefully this month.
krit: an idea how to reach out to browser implementers?
AmeliaBR: Myles was on the call and supportive. Unsure how to get others on the call.
krit: let me take the task to contact google and Mozilla folks.
Tavmjong: we get comments on issues.
AmeliaBR: Limited way to reach out to ppl in private.
krit: Why reach out in private?
AmeliaBR: To ask if they would be
interested in contributing to tests, specs...
... there are ppl who have the skills and interest. We ned to
get that organised.
krit: Would it help to publicly ask on www-svg?
AmeliaBR: probably. We could always link to the archived email for questions in private
nzimmermann: or having a crowd funding compain.
AmeliaBR: Or get some funding in general
krit: Will follow up with
plh
... It seems like many ppl do not even have the time to look
into SVG2. Just an incorrect observation?
AmeliaBR: certainly the case for
me
... lower on priority if there are no comments or
contributions
Tavmjong: busy with InkScape
nzimmermann: similar situation
AmeliaBR: Would it be helpful to set a side a virtual editing session on the calendar?
Tavmjong: might be helpful after 9PM CET
krit: sadly not much time till June from my side.
nzimmermann: principally yes. I'd
prefer regular working hours. Early in the morning or late at
night :)
... but not in the short term
... If there is a proposal for a time I'd decide case by
case
AmeliaBR: Ok, lets start with an email to ww-svg to see who else is interested.
krit: would you concentrate on testing or spec editing?
AmeliaBR: seems most likely to get testing first
<AmeliaBR> https://github.com/w3c/svgwg/issues?q=is%3Aopen+is%3Aissue+label%3A%22Test+suite%22
nzimmermann: would we have a public list of specs sections that lack testing. Then we could ask ppl who are NOT familiar with spec editing to look at it and write tests for it.
<AmeliaBR> https://github.com/w3c/svgwg/issues/487
AmeliaBR: Started with a master issue
nzimmermann: perfect. We need a
public relation compain
... ... on Twitter that SVG2 needs your help
AmeliaBR: It would definitely
help to have a core group of ppl, (For instance on regular
calls), to work on tests and write a guidance page how to write
a a good SVG test based on WPT
... 1. look up what needs to get tested 2. here is how you can
do it
... we want to do it in steps. Especially get attention in an
organised way
... Lets follow up with the few of us at the end of the
month.
<AmeliaBR> https://web-platform-tests.org/
AmeliaBR: We should all read up on things and come with our own thoughts and questions. We should follow up with ppl who just recently created tests to know what needs to get included into posts and tutorials for other contributors.
krit: Just a reminder to think about switching from a "stable" recommendation to a living standard.
AmeliaBR: We still need to clean
up the spec. This work is the same.
... No features are up for the spec anyway and if they may get
into own models (we need to decide)
nzimmermann: what are the general feelings of WG members? Haven't thought about it much.
AmeliaBR: for the immediate
future we need to make the spec better and align more to
browser implementation. To what happens after wards? In a
module approach, all implementers are supposed to match the
living standard and keep up to data with it as opposed to a
fixed spec that can get implemented by other parties.
... The modular approach might make sections look options. But
maybe this is appropriate. I don't know.
krit: My point of view, neither fixes the lack of contributions.
AmeliaBR: We haven't been
meanting in calls for some times. We didn't review new issues
and some don't have any comments at all. Please review the
issues and comment or at least tag them.
... we can mentioned the community group but nothing happened
in it either.
krit: Good call. Look at issues
and provide feedback.
... seems like we all have work for the next call to do
<nzimmermann> AmeliaBR: I had fun with a codepen from you btw
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) Succeeded: s/sag/svg/ Default Present: AmeliaBR, krit, stakagi, nzimmermann, Tavmjong Present: AmeliaBR krit stakagi nzimmermann Tavmjong Regrets: Sairus Myles Found ScribeNick: AmeliaBR Found Scribe: AmeliaBR Inferring ScribeNick: AmeliaBR Found ScribeNick: krit ScribeNicks: AmeliaBR, krit WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: 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.)[End of scribe.perl diagnostic output]