Open brillout opened 7 years ago
To avoid duplicated work of two people reviewing the same entries, we can divide the work into chunks. Where one chunk = one section. And a chunk is assigned to one person.
E.g. I'd be up for reviewing the libraries of the sections Component Collections
and UI Components
.
Cleaning the Awesome Vue.js is a great idea and I would be happy to help. I can review the Projects Using Vue.js section.
👍 Collaborator invite sent and I've assigned you to it at https://github.com/brillout/awesome-vue/issues/3
Reviewing one library entry could be done as following.
1. Replace the description of the entry in the markdown with
good
orrejection reason
e.g.no v2
for libraries that don't have a v2 compatible version. E.g. I've started with theComponent Collections
section: https://github.com/brillout/awesome-vue#component-collections.2. If not rejected, add the enty to https://github.com/brillout/awesome-vue/blob/master/README_CLEANED.md using the format
- [npm-package-name](https://github.com/org/repo)
. (After we processed all entries I will use a script I wrote for devarchy to automatically add the GitHub description to all entries)