<cb> 👋
<bkardell_> scribe nick: bkardell_
<bkardell_> scribenick: bkardell_
<joyee> scribenick: joyee
<bkardell_> scribenick: bkardell_
jorydotcom: this came from an idea - the open js foundation has been a w3c member for a long time ...
recently merged with nodejs foundation ..
wanted to talk about and coordinate efforts and we thought it would be great to have a session where we could talk to members of w3c, our members in wgs, our projects
scribe: not a really formal session, we wanted to do conversation and brainstorming
where do we see opportunities to do more coordination/involvment/partnerships
<jory presents slides>
32 projects - some of them are in emeritus stage
5 impact projects
the rest are at large/growth projects
they represent a diverse set of concerns
actually - let's do introductions...
<introductions>
returning to the projects... as you can see they are diverse, we're looking for how we can coordinate more and particpate more in standards
the structure of the open js foundation...
board of directors board, cross project council, impact, growth, at large and emeritus projects
the CPC is the group of people in the community who are very active in helping make sure the community can help drive the activity of the foundation ...
one of the programs that we want to do is a standards working group - we just started meeting bi-weekly a month or two ago ...
we w to be talking with and working with the w3c, what can we do to strengthen this
torgo: what are the outcomes we would like to see happen that aren't happening now
cb: for people who build standards, they miss use cases - I think that's one part where projects can really help...
the projects can help provide feedback and make sure we are helping improve that
torgo: I just heard about the webxr community providing a spec and a javacript library that is a companion -- not officially part of the spec but I think will be published with the w3c license...
is this something that we can do better
tobie: isn't there related rtc stuff?
torgo: I am just saying this one because I think it is one I just heard - but I think there are other examples like this that could use a center of gravity
tobie: it would be intersting to have a governance model around a project like this because it would be a lot for a small thing, but I wonder if they could all fall under one sort of unbrella thing in the open jsf or something
jory: interesting idea
wseltzer: question because I am relatively new to the open js foundation ... what does it add here?
jory: I think there are some things - discoverability, perhaps less accessible to the broader audience. They might not even realize as easily that they could _contribute_, but if it is an open js foundation thing, they do expect that
tobie: lifecycles are also very different
sangwhan: it would be great if polyfills could be that way
bkardell_: thanks for saying that, I was trying to bring that up in between typing
tobie: I wrote a polyfill when I was doing geolocation, and I had this problem, it got out of sync quickly and I couldn't maintain it.. I dont think people knew they could help
sangwhan: also licensing issues apply to the spec, not the library
wseltzer: we could fix that
sangwhan: there are specs
happening in w3c that don't need a browser techincally, but we
built it so that it does require a browser. Example: service
workers rulesets - could be useful for building routers for
example, but it requires service workers
... it would be good to get feedback as soon as possible
jorydotcom: bkardell_ and
littledan have been working on some outreach to do this, and
we've been thinking about how to do this recently and integrate
it
... we have people in open js foundation who are involved in
other tc too - tc-53, for resource constrained devices
https://twitter.com/StandardsIn2Min
torgo: I find this frustrating - like even with mdn, you find all of this extremely detailed infromation but the thing you often want is just the high level "what even is this?" - I wonder if there is opportunity for collaboration of 2 minute standards with mdn, for example
bkardell_: I think yes
wseltzer: this is very
interesting for thinking about the ecosystem and
collaboration... it seems like code is where we could do more
for the ongoing maintenance
... are there things that go in the other directions
bkardell_: a lot of examples of that already I think , so yes
tobie: lots of examples of things that span, like modules
wseltzer: are there things w3c could be doing to be a better partner here?
joyee: we are already working
with whatwg and node but only in the form of writing code... it
would be great if the foundation could help facilitate the
communication. People who implement and test, work together -
and that helps... but sometimes in node-core for example, we
ask for a justification, we can't make changes ...
... i would hope the foundation could help facilitate
jorydotcom: I think we have
examples of projects that were designed to solve... we've had
fair success in getting feedback, there's not as many recent
examples I can think of and I think that should change. We have
projects that are working to solve things like
internationalization or accessibility
... and we should be working with standards there
... if you go to the website, there is a slack link and a
standards channel there that you can join... it is open to
anyone in our project community - we take a pretty liberal view
to what that means, we would love to have any of you as
participants
torgo: what are the action items?
bkardell_: we can open an issue
torgo: where?
github openjs-foundation/standards
jorydotcom: we can also just go ttalk to some we know about if you know them... we could talk to the xr folks
torgo: go talk to ada while here - we can use it as a case study
jorydotcom: we can ask other
groups
... do we know that or something?
wseltzer: no.. we don't
... especially if we had some benefits to describe to them, it
would help for that
tobie: knowing the process to create a project - i worry that if we make it super complicated, it will be very uncompelling. You want to create a thing just for this basically
torgo: you want to talk to them though and figure out what that looks like... some kind of space that is jointly branded/held
bkardell_: asks about the stuff w3c historically developed
(nothing really interesting discussed)
tobie: hmmm now that you mention it, we have a whole lot of tools -- a whole bunch of tools, they could live here?
respec? bikeshed? I have stuff... for a lot of that though, you have to make it easy to not disincentivize it
jorydotcom: we have that meeting mentioned before next tues - the 24th, at 18:00 UTC, you can find the invite on the site, or slack and ask
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/rrsagent make logs public// Succeeded: s/sandwhan/sangwhan/ Present: cb jorydotcom joyee wseltzer bkardell_ Dan Appelquist tobie Found ScribeNick: bkardell_ WARNING: No scribe lines found matching ScribeNick pattern: <bkardell_> ... Found ScribeNick: joyee WARNING: No scribe lines found matching ScribeNick pattern: <joyee> ... Found ScribeNick: bkardell_ Inferring Scribes: bkardell_, joyee Scribes: bkardell_, joyee ScribeNicks: bkardell_, joyee WARNING: No "Topic:" lines found. 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: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report 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]