Open Call For Contributors

[sagalbot]

I'm actively looking for contributors to help triage issues, get pull requests merged, and help push out new releases. The project continues to gain interest, installs, and stars - and I no longer have the capacity to handle it all by myself.

The immediate need is to get v2.5.0 merged and released. I also have a vision for v3.0 that will solve most of the common issues.

If you're interested in getting involved, please drop a note here on this issue. Thanks so much your interest in the project!

[spacemudd]

Hey, I'd love to help around.

[kotarCreative]

Willing to help out where I can.

[stevenharman]

We've recently started using vue-select in our main app, in production. Hence the recent influx of PR comments, Issues, etc... 😄 I'd imagine I'll be rather interested in getting fixes in, changes through, etc... while keeping an eye on it not breaking things. So... I'd be game to help triage and get PRs in. And I'd be willing to do a release here and there, if you'll show me the ropes.

[beattyml1]

We use this at the startup I work at so I'd probably be down to review some PRs and triage depending on level of time you're looking for.

[jaapio]

For me the same applies as steven. We are using vue-select in our application. With lots of users, some of them are on a staging environment where we can break things. So I could provide some time to review and go through the issues.

I don't think I'm expirenced enough compared to you guys to contribute in code. But I can triage issues for sure.

[Aukhan]

same as @stevenharman and @jaapio
we are also using this plugin in a serious project and I would like to help out however I can,
thanks

[dannyrb]

@sagalbot 👋
FWIW, I help maintain:

• https://github.com/cornerstonejs/cornerstone and
• https://github.com/cornerstonejs/cornerstoneTools

So I have some experience at this. Would love to pitch in (:

[GiuMagnani]

I'm also using vue-select in a big project. I'd love to help!

Thanks!!

[eliurkis]

I would love to help @sagalbot

[sagalbot]

So glad to have some folks interested in helping out!

I have finally settled into some consistency after a turbulent year, so I'm really looking to get the release cycle back on track, and push forward to v3. The first step was getting v2.5.0 out, which had been backlogged for at least 6 months. There were a ton of changes in there, and I'm actually a bit surprised more issues haven't rolled in since the release.

v2.5.2

At the moment, there's a couple issues that I've tagged under the 2.5.2 milestone. If you're keen to take on any of those bug fixes, maybe post a note here so that no one else takes them on. There's a couple ugly bugs here so I'd like to get this release out pretty quickly.

---

Vue CLI 3 & VuePress

I've dumped a bunch of hours into the vue-cli-3 #615 branch and related vuepress #619 branches. The bump to cli3 cleans up the repo a lot, and improves the dev experience. The tests have all been rewritten with Jest and vue-test-utils, eliminating a ton of boilerplate that I had to write before test utils was a thing. It's much easier to add new tests and should encourage contributors to add coverage to PRs. It also adds linting which has been an issue, as well as netlify builds for pull requests so you can preview changes without having to checkout a branch. Overall it should be a big plus to the developer experience.

The Vuepress based docs have been overhauled significantly: all props, slots & events are documented, as well as guides for common use cases.

The main concern with the above branches are:

1. ensuring that the move to cli3 doesn't affect the UMD build. Some testing needs to be done there to determine how the updated /dist files need to be used (ex: loading from CDN vs npm package)

2. updating the 'splash' page for the updated website. I'd like the splash page to be a bit more interactive, and let you adjust the props of the select interactively so a visitor can get a sense of what it's capable of. I was thinking that this could also replace the default dev environment - right now there's about a dozen v-selects on the dev page and that's just going to continue to get harder to wrangle.

---

Write Access

Huge thanks to those of you that have contributed here already. I really appreciate the efforts.

If you're interested in having write access to the repo, I'm definitely open to that. It's hard to relinquish control over something I've spent so many hours on, but I really do think it's in the best interest of the library to let others contribute directly. Shoot me a note if that's something you're interested in and we can chat about it.

---

v3

Some quick bullets about where I'd like to head for v3:

• update all CSS classes to be prefixed with vs__ (or vs_)
• refactor CSS to use the least amount of specificity possible to encourage ease of customization
  • ideally, styles would actually be scoped, but I'm not sure of how to accomplish this while encouraging easy overrides
  • it'd also be great to include a version of the build with no CSS, or maybe some very light scaffolding
• Leverage multiple scoped slots that will allow for complete customization, with more variables and methods passed to the slots. Using a renderless approach (shoutout to @adamwathan 🙌) will be key

[bribar]

I'd be happy to help where I can! @sagalbot

[nickescobedo]

I'd be happy to help! @sagalbot 😄