awesomejs.dev

awesomejs.dev copied to clipboard

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.

@Akryum Hi, can I be added to the moderators for checking contributions?

Awesome! I don't have contributing documentation available yet though.

At the expense of the criteria, you can stick to the current list from CONTRIBUTING

This could help migrating data from awesome-vue

In relation to this, I realized that it is necessary to develop api for the possibility of adding contributions.

I could make adding contributions directly from PR

@Akryum Hi, can I be added to the moderators for checking contributions?

Sure! What's is the email and username you have on awesomejs.dev?

At the expense of the criteria, you can stick to the current list from CONTRIBUTING

Yeah, but for example we need guidelines for handling tags. (Max 2-3 tags, use existing tags whenever possible...)

In relation to this, I realized that it is necessary to develop api for the possibility of adding contributions.

There is an API here but authentication-wise it's using cookies so a bit harder to use for editing purposes.

@Akryum Hi

Sure! What's is the email and username you have on awesomejs.dev?

username: Ivan Demidov email: [email protected]

Yeah, but for example we need guidelines for handling tags. (Max 2-3 tags, use existing tags whenever possible...)

Did you mean at least 3 tags? I will make the necessary adjustments in CONTRIBUTING I will sketch and do you PR

There is an API here but authentication-wise it's using cookies so a bit harder to use for editing purposes.

I'm still trying to figure out the current ecosystem. I will ask a more specific question as soon as I figure it out.

I don't think it's useful to have more than 3 tags on a package. Keep in mind it's used in the filters so we don't want to have the likes of vue-plugin, vue, vue-extension.

Basically this are the dos and don'ts for tags:

• Don't: too many tags on a single package
• Don't: redundant tags or variations of existing tags
• Don't: tags describing the project type that the package is already attached to, for example vue, react, node
• Do: explicit and concise
• Do: reuse existing tags as much as possible

@Akryum Have a nice day, I made a list of criteria by which a package can be rejected

• [ ] git: should be the link of the github repository
• [ ] tag: over max 2-3
• [ ] tag: used existing
• [ ] tag: describing the project type
• [ ] tag: very long
• [ ] pkg: doublicate (fork)
• [ ] time: not updated for more than 6 months
• [ ] category: not in its category
• [ ] docs: no documentation
• [ ] docs: non-english documentation
• [ ] project: dead project

Let me know if you have any other ideas.

Sure! What's is the email and username you have on awesomejs.dev?

Unfortunately I did not receive a notification; are there any other actions I need from me?

Unfortunately I did not receive a notification; are there any other actions I need from me?

Just added you to Vue and Vue CLI. You should be able to see moderation actions on those packages now. You can also add packages to other projects types, for example Vue + Nuxt if a Vue package contains a Nuxt module too.

@Akryum Cool! Thank you

I saw in Issue there are tasks for adding projects, tell me how I can add a project there posthtml whose maintainer I am, this is an analogue of PostCSS but only html

I added one more criterion

• [ ] git: should be the link of the github repository

because many do not have a link to the github repository