Community and Governance

[syrusakbary]

We want to welcome as many developers and companies joining and participating in WASIX.
This is a project that aims to be governed by many entities, not just one.

Wazero, Zig, and AssemblyScript could be great additions to the governance team, but any others will be more than welcome.
As long as you want to move WASIX forward you will be welcome to chime in and participate in its progress.

The aim of WASIX is to allow any kind of app to be compileable to Wasm: supporting POSIX apps seems like the best way to accomplish this without recreating the world.

Would you like to participate in the future of WASIX?

If so, please chime into this discussion and let us know your preferences:

• When would be a good day for the meeting: weekdays (Mon-Fri), or weekends (Sat-Sun)
• What should be the cadence for these meetings: every two weeks, once per month, or once per quarter

[codefromthecrypt]

TL;DR; Do you think that it is reasonable to have these meetings one way to participate as opposed to the authoritative way?

My opinion is we should try to be as async as possible and not rely heavily on meetings. One thing I haven't really enjoyed about WASI, is that basically meetings win, so if you are out of timezone etc and don't attend a meeting, you aren't prioritized regardless of async elaboration vs meetings. So, culturally, I would love for meetings to be a convenience and less of a prioritization system. For example, a feature doesn't magically become priority because someone hangs out on a call. Also, votes in the call don't override votes on an issue. Sync calls are bad for ESL and out of timezone, as well easy to game. However, I think calls serve a purpose and are helpful, this in mind. I think a cadence of max once per month forces people to primarily work async, and I can do Europe morning (my afternoon Malaysia time), if it helps.

[jcchavezs]

+1 on async meetings. Sync meetings are usually unfair for those in non popular TZ gives an advantage on those with louder voices and ignores past work. None of those features are great for OSS projects.

[fanweixiao]

agree with for meetings to be a convenience and less of a prioritization system, prefer once a month to force progress async.

[dynamite-bud]

This seems good, and I believe everyone agrees with the async meetings. @syrusakbary

[syrusakbary]

Yeah, fully agree on async communication and have a regular monthly meeting just for those who want-to/can join.

Would 4pm CET work for you @codefromthecrypt @fanweixiao @jcchavezs? (it would be 4pm in Barcelona, 10pm in Malaysia and Singapore)
Proposing this time in case people from the US want to join... it will be early (7am in SF), but I believe could be workable.

Also, would Thursdays work?

[codefromthecrypt]

I'll be honest, I'm very unlikely to attend especially regular meetings that start late. Another way is to run twice and assume there are a quorum as particularly Europe overlaps.

Also, I think the industry often over-optimizes for SF to the point of fault. Unless there is someone who says they would join from SF, we shouldn't make everyone else suffer.

[fanweixiao]

@syrusakbary I am OK for 4pm CET

[codefromthecrypt]

ps I had private feedback that if we believe the sync meeting is a convenience, not making it shouldn't matter too much. just someone remembers to click record and ideally take notes. then we can have a async chat about it on slack. glad to have a meeting, but yeah we shouldn't need to perfect the meeting time if we are optimizing for async.

[evacchi]

fwiw: 4pm CET should usually work for me :) +1 to optimize for async anyway

[Raymond90328]

Hello all,
I am new to WebAssembly, I installed wasi-sdk as

https://github.com/WebAssembly/wasi-sdk

instructed, but how can I install WASIX-libc ?
I would be more than happy if someone tells me the details of the installation.

[dynamite-bud]

@Raymond90328 please ask help related questions on Discord.

[Raymond90328]

Thank you so much

[syrusakbary]

Thanks everyone! We want to move this forward, so here are next steps:

We have created a poll in Calendly so we can select the most convenient time for doing the first WASIX meeting:
https://calendly.com/d/255-rhy-s97/first-wasix-meeting

In this meeting we will define the governance rules for WASIX and next steps on how to advance things technically.

In a nutshell, here are the goals that I believe would benefit to have in the WASIX Governance:

• Fast iteration
• Enable most use cases
• No breaking changes (v2 prefixes over replacing behavior)
• Minimize process (iteration time over process)

[syrusakbary]

We have just reviewed most of the times, and the only two days/times where everyone is available are on:

• Tuesday July 25, 7am PDT
• Thursday July 27, 7am PDT

Since we are now a bit close to Tuesday, we have decided to do the first meeting on Thursday July 27, at 7am PDT.

For anyone reading this, feel free to chime in into the Zoom as well on July 27th 2023, at 7am PDT:
https://us02web.zoom.us/j/89969434135

Looking forward chatting with you in a few days!