Add more maintainers

[visnaut]

It's evident by the many PRs that there's great enthusiasm in adding to this list. The current maintainers have done a great job, as this list has been a great resource that myself and many others turn to, again and again.

However, the long backlog, and lack of merges (only 1 in the past month) is also a sign that the current maintainers need a hand, and as such, I'd like to propose that more be added to spread the workload.

I recently attended VueConf Toronto, and the core team that was present really encouraged the community to contribute and participate. In the spirit of doing so, I'd like to volunteer to be a maintainer here, as have others. I would happily lend a few hours a week to assisting this project.

Please let us know how the community can help @kazupon @LinusBorg.

[ajtruex]

I'd also like to volunteer to help maintain this repo as @visnaut already suggested.

Let me know if there is anything I can do to help @LinusBorg @kazupon.

[Akryum]

Hi! You can also help with either adding packages to https://awesomejs.dev/ or contributing to https://github.com/Akryum/awesomejs.dev (which replaces vue-curated).

[DannyFeliz]

I would like to help with the maintenance of this project.

[Scrum]

@Akryum Hi, I would like to help

[heygambo]

I can make some time to go over PRs as well

[Jogai]

Who are the maintainers? It looks like no pr's are merged anymore, and I think some are closed by contributors due to lack of response , example: #3123

[Scrum]

@LinusBorg @kazupon @Akryum ping ping ping

[LinusBorg]

Okay, so here's the deal:

• We don't really have the capacity to track this repo reliably anymore - obviously.
• We realize we need some suport from y'all to make this go forward.
• At the same time we are not comfortable giving merge privileges to people who we don't know well enough, yet.

So here's what we propose:

• Those wanting to help moderate this, please speak up here again.
• Start reviewing PRs, check wether they fulfill the criteria for being on the list (laid on here).
• Kindly ask contributors whose PRs don't match those criteria to update them accordingly.
• Approve PRs that do match the criteria
• Ping us in said PRs and we will merge them.

Once you have shown yourself to be a nicer and reliable person we will give you merge permission so you can continue to do this work on your own.

---

At the same time we want to make something clear: We think the usefulness of this form of "awesome-list" declines after a certain scale of the ecosystem has been reached, and we think we are there already, pretty much.

So we think that in the future, such a list might be better handled on e.g. https://awesomejs.dev - we could put you there as moderators checking contributions as well.

But we aren't sure when and how we should deprecate this list right here in favour of said other tool, so options are welcome.

[Scrum]

Those wanting to help moderate this, please speak up here again.

I am ready to help.

[Jogai]

I strongly disagree with some of your statements.

We think the usefulness of this form of "awesome-list" declines after a certain scale of the ecosystem has been reached, and we think we are there already, pretty much.

As the ecosystem grows its more important to have an awesome list to be able to quickly get an overview of real good content in the community

So we think that in the future, such a list might be better handled on e.g. https://www.awesomejs.dev - we could put you there as moderators checking contributions as well.

I think the audience is mostly the open source community and developers in general. Those are familiar with github and the https://github.com/sindresorhus/awesome list. I think its important to keep it this way (for reasons discussed enough in the awesome repo) and not make it external. (point in case, the external link gives a 404 right now).

edit: external services exist that use aweseme lists as a base dataset, see https://github.com/sindresorhus/awesome#related

[visnaut]

Thank you for the thoughtful response, @LinusBorg

At the same time we want to make something clear: We think the usefulness of this form of "awesome-list" declines after a certain scale of the ecosystem has been reached, and we think we are there already, pretty much.

So we think that in the future, such a list might be better handled on e.g. https://www.awesomejs.dev - we could put you there as moderators checking contributions as well.

But we aren't sure when and how we should deprecate this list right here in favour of said other tool, so options are welcome.

If this is how the maintainers feel, I'd be more in favour of just ripping off the band-aid, placing a deprecation notice on this repo, and moving all efforts to AwesomeJS.

However, I'd like to point out that of the three main categories in this list, Resources, Projects Using Vue.js, and Components & Libraries, AwesomeJS only covers the latter. And in that, it excels.

But I would argue that this list is very important for gauging the overall health of the ecosystem; not just the availability of packages, but for the training available, and for name-checking other successful uses of Vue in the real world; information that is hard to come by otherwise.

With that in mind, perhaps we can consider deprecating the Components & Libraries list, point people to AwesomeJS instead, and focus on the other sections of this list. I think that would provide a good balance of pointing people to the best resources available, and not duplicating maintainers' efforts.

Those wanting to help moderate this, please speak up here again.

Yes, I'm in 🙋🏻‍♂️

[visnaut]

(point in case, the external link gives a 404 right now).

@Jogai Try https://awesomejs.dev without the www.. Though I would agree that it should just work or redirect regardless.

[Scrum]

@LinusBorg sketched a sample checklist of criteria by which PR can be closed.

Checklist

• git: pull request template structure not broken
• git: empty commit
• git: link not to repository
• git: broken PR
• git: no conflicts resolved
• git: doublicate
• time: not updated for more than 6 months
• category: not in its category
• lists: not the last on the list
• docs: no documentation
• docs: non-english documentation
• project: commercial product
• project: dead project
• project: does not accept donat
• site: no link to the site
• site: site with errors
• site: not actively using vuejs
• site: not original

Follow the rules CONTRIBUTING

It seems to me that you can give a chance for old PR sizes of 1 week, after which you can close the task if there is no movement on it.

It would be great to be able to put labels in order to mark already viewed or pending PR decisions.

[Scrum]

@LinusBorg In relation to PR, we can use templates with checklist as I have done in the project https://github.com/post/post-static/blob/master/.github/pull_request_template.md

Regarding issue you can make blanks as in https://github.com/Scrum/slims/issues/new/choose