Inclusion to the "Awesomeverse" #9
Comments
|
Good idea + totally open to changing the license to creative commons! I am less clear what the repository topics change would mean, but open to that as well. |
In order to be included in the "Awesomeverse", the license must be a CC license. Creative Commons Attribution 4.0 International is the nearest match to the Apache License 2.0 used previously. The only major difference is the patent grant clause. However, this repository is only documentational, hence no code, nor patents thereof used. Part of #9.
|
@sblackshear Great! 🎉 The repository topics are listed below the repository description, and can be modified only by project admins. For example, https://github.com/diem/move/ has the following topics: "smart-contracts", "blockchain", "verification". |
Following major Awesome style guidelines and committing early, so the next additions could adhere to the Awesome style guidelines from this point onwards. This commit is mostly about formatting, and the content itself is mostly intact at this point. Part of #9.
Following major Awesome style guidelines and committing early, so the next additions could adhere to the Awesome style guidelines from this point onwards. This commit is mostly about formatting, and the content itself is mostly intact at this point. Part of #9.
Copied widely accepted guidelines from https://github.com/sindresorhus/awesome-nodejs. Dropped the strictest requirements, ending up with a list of reasonable guidelines, while still being awesome compliant. Part of #9.
Copied widely accepted guidelines from https://github.com/sindresorhus/awesome-nodejs. Dropped the strictest requirements, ending up with a list of reasonable guidelines, while still being awesome compliant. Part of #9.
Copied widely accepted guidelines from https://github.com/sindresorhus/awesome-nodejs. Dropped the strictest requirements, ending up with a list of reasonable guidelines, while still being awesome compliant. Part of #9.
The list now passes "npx awesome-lint". Part of #9.
|
@sblackshear This list is almost compliant: after PR #14 the only major change needed is adding the GitHub topics |
|
Done! |
Hello everyone!
Awesome lists are aggregated to the "main" awesome repository.
If included,
awesome-movewould be accessible from tools using theawesomerepository, such as Awesome Indexed, awesomelists.top, and others.However, inclusion requirements are quite strict, but not impossible to meet.
I can work out most of the stuff (such as style, content, structure, etc.) and open a PR, but unfortunately there are a few things I can't do alone. Some of these are:
awesome-list&awesome)I am opening this issue for general discussion on the idea of inclusion, and will link the PRs to this issue.
Feel free to close this issue if inclusion to the list is not desired 🙂
The text was updated successfully, but these errors were encountered: