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

future of this github org #294

Open
ashleygwilliams opened this issue Oct 25, 2020 · 4 comments
Open

future of this github org #294

ashleygwilliams opened this issue Oct 25, 2020 · 4 comments

Comments

@ashleygwilliams
Copy link
Member

@fitzgen @alexcrichton it seems like we need to talk about the future of this GitHub org. it's obviously really overdue but with comments like rustwasm/wasm-bindgen#2337 (comment), it doesn't seem that our continued collaboration in this org is desired.

i'm currently in the process of collecting folks who are interested in maintaining and developing wasm-pack as well as the book and other documentation. it'd be worth figuring out if we should be officially sunsetting this working group and retiring this org. i was hoping that this group of people i'm gathering could reignite the working group, but that requires input from ya'll. let me know if you'd like to chat in another venue.

@alexcrichton
Copy link
Contributor

I'm busy this week starting a new job, but I will respond more fully next week.

@alexcrichton
Copy link
Contributor

Ok I’ve had a chance to talk with @fitzgen about this and I’m gonna write this for both of us. Unfortunately we don’t have the time right now to help maintain the Rust and WebAssembly working group as a whole. We largely consider the working group as successful and have shifted our focus from the specific tooling we’ve created here towards standardizing it upstream and what that might look like. I will personally continue to keep up with maintenance on wasm-bindgen, however, to ensure it gets any bug fixes and such (although I won’t have a ton of time for new features).

As for where that leaves this organization, we’re ok leaving that up to you. We're interested to see what exciting projects people might bring to this group and don’t want to see the efforts in the rustwasm organization go away. We also see a lot of value in community involvement, ownership, and governance in making Rust and WebAssembly a best-in-class story. It feels like we may be in a lull now but that’s just temporary.

For what this means about the Rust and WebAssembly working group we’re also not sure. So long as there’s folks willing to work on it then it seems prudent to have an agreed upon location of where to work, though!

@AlexEne
Copy link

AlexEne commented Aug 6, 2021

Hi, @ashleygwilliams, @alexcrichton and @fitzgen - too as they are one of the most active contributors on twiggy.

As I understand this github org's future is unclear (for some time :D), but as i've pinged in the discord room and other various channels, until there's a path forward and plan on what to do with some of the repos, I'd gladly share some of the mainenance burden of twiggy.

There are a bunch PRs, some that I think are really good PRs waiting in the queue, e.g.: rustwasm/twiggy#576

Would it be possible for me to be added as a maintainer of the twiggy repo? I can try sort some of them out regardless where twiggy or some other repos eventually land (other orgs, etc.)

@fitzgen
Copy link
Member

fitzgen commented Aug 6, 2021

Hi @AlexEne, I've invited you to the twiggy repo and sent an owner invite on crates.io as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants