Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call for co-maintainers #102

Closed
thedodd opened this issue Dec 17, 2020 · 9 comments
Closed

Call for co-maintainers #102

thedodd opened this issue Dec 17, 2020 · 9 comments
Labels
discussion This item needs some discussion help wanted Extra attention is needed

Comments

@thedodd
Copy link
Member

thedodd commented Dec 17, 2020

Hello friends! TL;DR: I'm looking for co-maintainers.

When originally setting out to build Trunk, my objective was to fill a gap I perceived in the Rust WASM ecosystem, and to provide a generally useful tool for myself and others to address that gap. After building Trunk, I was able to use it to successfully build and ship an app, and then move on. The move on part is problematic for Trunk, given that there is MUCH more awesome work to be done, and lots of community interest in developing tools like this.

As such, I would like to begin the process of chatting with at least one or two individuals interested in being a co-maintainer of Trunk. My primary expectations for such an individual:

  • able to help drive the design and development of Trunk
  • review PRs in a meaningful and constructive way, always first prioritizing mutual respect and constructive communication within the community, and secondly looking out for the health of the Trunk project / code base overall
  • cut code releases
  • participate along with me (Dodd) and other co-maintainers in design and planning
  • (EDIT) also, my other project which is pertinent to this space (thedodd/ybc) will also be lumped into this effort

Co-maintainers will not be alone in this effort. I will still be here and involved. This is primarily a call for help due to having too much on my plate. I am genuinely excited about working with other co-maintainers on this project!

IF YOU ARE INTERESTED, just drop a note here on this issue, and then we can sync up on Discord or elsewhere to proceed with more in-depth discussion. Cheers!

@thedodd thedodd added discussion This item needs some discussion help wanted Extra attention is needed labels Dec 17, 2020
@jkelleyrtp
Copy link

jkelleyrtp commented Dec 18, 2020

Hey there.

I've been working on https://github.com/jkelleyrtp/yew-projects/tree/master/packages/yew-pack recently, and it seems that trunk and yew-pack super close in goals/scope and structure. I've also helped with yew's worker support and would enjoy adding that in.

I'd love to help maintain / build out trunk, and maybe even spruce up Yew as well so they work well together.

Also, I see that you're working on ybc. I've been working on adding hooks, selectors, Redux, and Recoil to Yew - which you can see in my YewProjects repo! Over the winter though, I really want to separate Yew's backend so we can do pre-renderer, which was the ultimate goal for yew-pack.

@kud1ing
Copy link

kud1ing commented Dec 18, 2020

Not sure whether this is the case, but there might also be an overlap with @cecton's https://github.com/IMI-eRnD-Be/wasm-run

@cecton
Copy link

cecton commented Dec 18, 2020

We are all very close to each other! ❤️ 🦀

  • wasm-run tries to be minimalist, highly customizable and specialized in web apps (not npm libraries). It also doesn't specialize to any framework. The only thing it doesn't share with trunk is that wasm-run is a tooling library (not an external binary tool).
  • yew-pack is also very similar to trunk (maybe even more!) except that it specializes to yew.

I do intend to make a "yew+yewprint template" based on the wasm-run-template. (I'm waiting for the 0.18 release of yew to release the first release of https://yewprint.rm.rs). (More help on yewprint would actually be welcome, it's pretty dead at the moment.)

I might take some inspiration from trunk with the sass-scss and turns it into an optional feature flag as I want to keep things very generic.

There is also substrate-wasm-builder which is intended to be used in a build.rs script. This is useful if you want to include the WASM binary in another project.

I will continue my work on wasm-run because my need (for a customer) is more into the customization of the build (my build needs to have as few files as possible which I can achieve with wasm-run). But I'm open to any proposition to share common work together.

cc @fstephany

@rakshith-ravi
Copy link
Contributor

I've always been excited to see something like trunk for the wasm community. I have worked on the rust compiler (here and there), and lead a team that handles web development in my company. I have a personal interest in bringing the rust web dev situation to be more production-ready, since I've wanted my team to switch over to rust for web dev ASAP. With that as my motivation, I would love to be a part of this and help bring it up to speed. Do let me know if you'd like any help whatsoever.

PS, you can find me on Discord as BlackJackHack#2355

@rakshith-ravi
Copy link
Contributor

@jkelleyrtp just saw yewpack and love the approach you're taking! We've been dabbling with redux on rust ourselves internally and would love to contribute. Do let me know if you'd be interested in exchanging notes and working on something together. 😄

@philip-peterson
Copy link
Contributor

philip-peterson commented Dec 18, 2020

Would love to get involved! Though I only have a couple of hours a week, I am very interested in helping get the Rust frontend ecosystem up and running, and have been actively developing Yew SSR. I'm ironmagma#8437 on Discord.

@thedodd
Copy link
Member Author

thedodd commented Dec 30, 2020

@rakshith-ravi welcome aboard! Great talking with you.

@thedodd
Copy link
Member Author

thedodd commented Dec 30, 2020

@philip-peterson && @jkelleyrtp sounds like you guys may be interested in helping out as well. I'd love to jump on a video chat on Discord. @philip-peterson I sent you a message. @jkelleyrtp if you would like to reach out to me, my username is Doddzilla#3116.

@thedodd
Copy link
Member Author

thedodd commented Jan 7, 2021

@thedodd thedodd closed this as completed Jan 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion This item needs some discussion help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

6 participants