---
# System prepended metadata

title: 'SwiftWasm Maintainers Meetup #1'
tags: [' swiftwasm-meeting', SwiftWasm]

---

---
lang: en
tags: SwiftWasm, swiftwasm-meeting
---

# SwiftWasm Maintainers Meetup #1

- Where: [SwiftWasm Discord](https://discord.com/invite/ashJW8T8yp)
- When: 2022-03-29 2pm BST

## Topics

Please list up topics you would like to discuss in the meeting :+1: 

### Upstreaming

#### Pull bot not working

Latest PR was submitted by the bot ~5 days ago.

#### Relative Pointer patch

[We finally got concensus about how to upstream relative pointer things from John McCall](https://forums.swift.org/t/wasm-support/16087/49)


#### Swift for WebAssembly Working Group?

This will likely require some commitment for regular workgroup meetings from those participating. It would potentially require some monthly or quarterly workgroup meetings, depending on the workload? The main hope is that people from the Swift team can participate in it, which should greatly simplify upstreaming efforts.

#### Pushing `swiftwasm` branch to Apple's repository

This is something that could help us with upstreaming, more details to be discussed during the meetup.

### Bare metal support?

The main blocker is [uSwift](https://github.com/compnerd/uswift) support. While it had some great progress, we need to pointers support for basic memory allocations to work. It also doesn't support runtime metadata and unspecialized generics yet. Driver code needs some updates as well, draft PR is open on SwiftWasm repo. 

Max had a discussion with @compnerd who developed [the original PR (currently unmerged)](https://github.com/apple/swift/pull/35970). We need to handle `swiftrt.o` before the driver PR can be reviewed upstream. Max is looking for documentation on `swiftrt.o` to understand how to correctly handle it.

### 5.6 release blockers

- Known issues are currently tracked in [the corresponding GitHub ticket](https://github.com/swiftwasm/swift/issues/4378).
- Consider requiring swift tools version 5.5 for all related projects for avoiding Swift Concurrency issues.

### Google Workspace and email setup

Do any of our co-maintainters need an email on swiftwasm.org domain? We currently have conduct@swiftwasm.org group that redirects to other emails within that domain, same for hello@swiftwasm.org. 

Max is open to transferring swiftwasm.org and carton.dev domains to a shared SwiftWasm organization account (still needs to be created). Not sure if Google Domains supports some shared ownership with Google Workgroups, could transfer there if that works.

### Code of Conduct

Is there a concensus that we should adopt Swift.org code of conduct or are there any other suggestions? The only change compared to the original is that email specified is conduct@swiftwasm.org.

### SwiftWasm maintainers policy

There are at least two inactive members who have maintainers permissions on Discord and GitHub. There is a suggestion that we should get in touch with them and ask if they're willing to become active in the future.

Has anyone been in touch with Carson? Need to clarify with him if he'd like to participate in our SwiftWasm meetups, or is he focused on Tokamak exclusively?

### DocC generation on CI

Is this ready to be adopted in our repositories instead of `swift-doc`?

### DOMKit status

Should we prioritize this after 5.6 release? There are more and more questions about Web APIs on Discord. Having DOMKit ready will likely make it easier for people to interact with Web APIs.

### In-browser debugger

Potentially built on top of WAKit?

### Community involvement

#### Public SwiftWasm meetups?

Could be quite beneficial for outreach, but requires a time commitment from people organizing meetups. The long-term benefit is that we can get more people involved and understand what are the most pressing concerns for our users.

#### SwiftWasm logo and swiftwasm.org redesign contest?

Something we could announce at some point if we have time. We could even set up a monetary reward from our OpenCollective fund for contest winners. [Here's an example](https://github.com/xmonad/xmonad/discussions/359) of how the XMonad community have done it in public.

## Action items

- [x] Watcher fix in `carton` - candidate libraries are available, need someone to try
- [ ] 5.6 release - Max to document the release process.
- [ ] Swift for WebAssembly Workgroup - for Max to follow up with Swift team
- [x] ~~Google Workspace~~ Using Fastmail instead - Max to add Jed and John for separate email accounts
- [ ] ESLint redesign as a model for swiftwasm.org redesign?
- [x] Upstreaming relative pointers patch - Yuta is working on it
- [ ] Future ideas: DOMKit/webidl2swift, debugger, DocC, SwiftPM plugins - post on Discord/GitHub as a potential roadmap
- [x] Mid April - share available time and schedule next meetup, potentially for early May
