Andrew Brown (Sep 14 2023 at 15:41): Andrew Brown (Sep 14 2023 at 15:41):I am proposing we set up a group to evolve the wasi-nn specification together--what do you think? At WasmCon, I was amazed at how many people were using wasi-nn in one way or another. I have been holding back on certain changes I would like to make to the specification (see the issues) out of concern that we leave some implementation behind or break some use case. If we create a group to communicate the changes, discuss them, and propose new ones, we can move the specification forward with a bit more consensus.
Andrew Brown (Sep 14 2023 at 15:41):@fitzgen (he/him), @Bailey Hayes is this something that makes sense as a BA SIG? Can non-member groups attend?
Andrew Brown (Sep 14 2023 at 15:43):cc: @Ralph, @David Justice, @Radu Matei, @Angel M, @Wang Xin, @Matthew Tamayo-Rios... (searching for other people I talked to about this)
Ralph (Sep 14 2023 at 15:45):Well, SOME group is required to discuss it and make more progress....
Mingqiu Sun (Sep 14 2023 at 16:11):wasi subgroup is also an option, and maybe more appropriate? there is wasi-crypto as a precedent. BA's SIG is intended for incubating new projects.
Andrew Brown (Sep 14 2023 at 16:30):cc: @Till Schneidereit
Pat Hickey (Sep 14 2023 at 16:55):If you want to schedule and hold wasi-nn meetings as a champion of the proposal you don’t need anyone’s permission, just go for it
Bailey Hayes (Sep 14 2023 at 17:41):I think if it's a group focused on implementation then it totally makes sense as a SIG in the BA. Growing the standards within the WebAssembly org should continue in GitHub issues of wasi-nn and community updates in the WASI SG.
Andrew Brown (Sep 14 2023 at 18:38):Just to put all the discussion in one place: in the Wasmtime meeting, @fitzgen (he/him) made some comments about how if it's spec-related it could be a W3C meeting and implementation-related it could be a SIG. @Till Schneidereit made a good case for it being a BA SIG, IIRC saying that would fit the "gather users, implementors, designers" goal better.
Andrew Brown (Sep 14 2023 at 18:39):But @Pat Hickey is right in that this can just be informal as well. I guess one thing I'm looking for here is: who is truly interested in participating?
Andrew Brown (Sep 14 2023 at 18:40):(one other @Till Schneidereit thought: if it is a SIG, it would be a "machine learning SIG," not exclusively focused on wasi-nn as it exists today)
Pat Hickey (Sep 14 2023 at 18:40):No less informal to have it be under the WASI subgroup, just puts it in WASI instead of BA. Doesn’t matter to me though
Justin J. Janes (Sep 14 2023 at 18:51):I would like to be included in whatever form the group takes.
Steve Schoettler (Sep 14 2023 at 19:59):@Andrew Brown count me in!
Angel M (Sep 14 2023 at 21:36):+1 for having a group to discuss and work on WASI-NN. I'm not familiar with the differences between WASI group, BA SIG or informal group, so +1 to any option. Really happy to participate on it and thank you @Andrew Brown for pinging me on the thread :smile:
cc @Rafael Fernández López
Rafael Fernández López (Sep 14 2023 at 22:20):Interested as well, thanks for the initiative @Andrew Brown :)
Wang Xin (Sep 15 2023 at 02:09):+1 for a WASI-NN SIG.
Ralph (Sep 18 2023 at 11:24):Finally coming back to this. Def SIG, as the wasi-nn proposal itself does not encompass all the NN usage we expect to and some of us want to see. Whether ONLY wasi-nn evolves or other "nn" proposals appear -- all of that would be good fodder for the SIG, I would think!
Matthew Tamayo-Rios (Sep 19 2023 at 06:48):I will participate in whatever form it takes. I think having a SIG and W3C/GitHub split as Andrew suggested would be ideal as not all SIG topics may impact spec and spec discussions tend to have their own idiosyncratic concerns.
Andrew Brown (Sep 19 2023 at 17:48):Sounds like there is interest so let's meet: if you're interested in being involved, please fill in your availability: https://whenisgood.net/igx7z3a. I am predisposed to scheduling this on Tuesday, Oct. 3rd at 9am Pacific but let me know what works for you (message me if the slots don't work for you, e.g., timezone issues).
Andrew Brown (Sep 19 2023 at 17:50):At that meeting I will have (a) more of this SIG process figured out and (b) some key issues to discuss re: wasi-nn. Please bring any questions, focus areas, implementation updates, etc. and we can try to fit things in. At that meeting we'll also decide on a cadence for the meeting but I'm currently thinking every two weeks.
Andrew Brown (Sep 29 2023 at 23:22):Ok, I sent out invites for the first meeting on Tuesday, Oct. 3rd at 9am Pacific. If you didn't receive an invite but want one, please message me your e-mail address.
Andrew Brown (Oct 03 2023 at 15:56):Just a reminder that this first meeting is kicking off in 5 minutes
Ralph (Oct 03 2023 at 15:59):grabbing headset
Andrew Brown (Oct 04 2023 at 22:24):Thanks to all for the participation at the working group: I created a new repository to house the meeting details and notes — https://github.com/bytecodealliance/wasm-ml-meetings.
Andrew Brown (Oct 04 2023 at 22:26):I did realize after the fact that a 3 week cadence would conflict on certain weeks with the WebAssembly CG meeting; to avoid that, I propose we meet every two weeks (at least initially) so the next meeting would be on Oct. 17th. Let me know what you think of this change.
Justin J. Janes (Oct 16 2023 at 22:51):Are these meetings recorded by chance? Would be nice to catch up on them async.
Andrew Brown (Oct 17 2023 at 15:55):@Justin J. Janes, I think you should be able to see the transcripts if you were invited to the meeting (they're embedded in the Teams stream).
Andrew Brown (Oct 17 2023 at 15:56):Just a reminder for everyone else: this meeting is kicking off in 5 minutes
Ralph (Oct 17 2023 at 15:59):I'm overbooked today. Apologies all around, but commanded by management and all that....
Andrew Brown (Nov 14 2023 at 16:44):Heads up: we're meeting today in 15 minutes!
Andrew Brown (Nov 28 2023 at 16:13):We are meeting today in ~45 minutes. Some last minute agenda items: a couple of issues raised by Stuart and a discussion about changing the meeting time due to a conflict with the Wasm CG.
Andrew Brown (Nov 28 2023 at 18:05):Ok, for those who did not attend today: we need to find a new time slot for the meeting to avoid a conflict with the new Wasm threads subgroup. Please indicate your preference in this poll: https://whenisgood.net/g255z5j
Justin J. Janes (Dec 14 2023 at 21:53):Not WASM specifically but an approach taken by Mozilla to navigate mutli-OS/ARCH for llama inferences https://github.com/Mozilla-Ocho/llamafile
Last updated: Dec 23 2024 at 12:05 UTC