Seeking Core Maintainers for @CRXJS/vite-plugin #959
Replies: 3 comments 10 replies
-
Hello, My name is Tim. I have experience developing Chrome Extensions and have recently started exploring integrating built-in models within them. Over the past 8 years, I’ve worked as a developer across various projects, which has equipped me with the ability to quickly learn and adapt to new technologies. I'm interested in maintaining this project because it aligns with my skill set and allows me to contribute to an area I find both technically exciting and impactful. I can commit approximately 8 hours per week, distributed flexibly throughout the week, as this would be a side project for me. You can review my work on GitHub. While not all projects directly showcase extension development, they demonstrate my technical expertise and problem-solving capabilities. Looking forward to contributing! |
Beta Was this translation helpful? Give feedback.
-
Hello @CRXJS/vite-plugin community! I'm excited about the opportunity to contribute to this fantastic project. Here's a bit about my background and why I'm interested in becoming a maintainer: Experience with Vite Plugin Development:I have a solid understanding of Vite plugin development and am familiar with the Vite ecosystem. My experience with Vite's architecture and plugin system has allowed me to create efficient and useful plugins that enhance the development workflow. Experience with Chrome Extensions:While my primary expertise lies in Vite plugin development, I have also developed several Chrome Extensions using @CRXJS/vite-plugin. This experience has given me a good understanding of the unique challenges and requirements of Chrome Extension development. Why I'm Interested:Open-source has always been a passion of mine. I believe in the power of community-driven projects and the impact they can have on the developer ecosystem. Contributing to @CRXJS/vite-plugin as a maintainer would be a fantastic opportunity to give back to the community, help shape the future of Chrome Extension development, and collaborate with like-minded developers. Time Commitment:I can commit to dedicating 8 hours per week to this project. This time will be spent on PR reviews, issue triage, participating in GitHub Discussions, and collaborating with other maintainers to ensure the project's success. |
Beta Was this translation helpful? Give feedback.
-
🎉 Discord Community Launch!Hey everyone! Quick update on the maintainer search and some exciting news. First off, I'm happy to welcome @timsankara and @FliPPeDround as our new core maintainers! They've already jumped in to help with issue triage and community support. To better support our growing community, we've just launched the official CRXJS Discord server! This will be a space for:
Join us at: https://discord.gg/rEpNHh6t We're still looking for one more maintainer to round out the team. If you're interested, check out the requirements above and drop a comment! Looking forward to seeing you all in Discord! 🚀 |
Beta Was this translation helpful? Give feedback.
-
Hello @CRXJS/vite-plugin community!
Since its launch in 2022, this project has grown beyond my expectations, now helping thousands of developers build Chrome Extensions with modern tools. While the library is feature-complete and stable for most use cases, its growing adoption means it needs more active maintenance than I can provide alone.
The Current State
The Path Forward
I'm looking to form a small team of core maintainers (3 positions) to help ensure the long-term sustainability of the project. This is an opportunity to:
What We Need
We're seeking 3 maintainers who can commit to:
Required Experience
How to Apply
If you're interested in becoming a maintainer:
Applications will be reviewed on an ongoing basis and I'll respond to each candidate individually.
Next Steps
Once we have our maintainer team in place, we'll:
Looking forward to working with the new maintenance team to ensure @CRXJS/vite-plugin continues to serve the developer community effectively!
Questions? Feel free to ask in the comments below.
Beta Was this translation helpful? Give feedback.
All reactions