Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propose this list to the aggregators after its completion #6

Open
amivanoff opened this issue Sep 23, 2024 · 5 comments
Open

Propose this list to the aggregators after its completion #6

amivanoff opened this issue Sep 23, 2024 · 5 comments

Comments

@amivanoff
Copy link
Contributor

Let's track interesting awesome lists aggregators here

@VladimirAlexiev
Copy link
Collaborator

VladimirAlexiev commented Dec 2, 2024

@VladimirAlexiev
Copy link
Collaborator

@amivanoff We should not delay this. Please first comment on #28

@amivanoff
Copy link
Contributor Author

amivanoff commented Jan 3, 2025

I think we should insert in https://github.com/sindresorhus/awesome#computer-science, right after "Data science"

According to the https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md:

"Your entry should be added at the bottom of the appropriate category".

So, no after "Data science" for us, just the bottom of the Computer Science, pun intended :)

"Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file."

Our "obsolete software" may be an issue. Due to the "community-based" reviewing process (new submitters should review two other new submissions) it is an easy target for the novice reviewers.

"All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents."

I'll make a PR for this one.

"Does not use hard-wrapping."

Semantic Line Breaks could be a problem.

@amivanoff do you know how trackawesomelist is collected? Do they use sindresorhus/awesome, or have own submission method, or do their own crawling?

They have their own awesomes list in a Yaml config and their own categories. https://www.trackawesomelist.com/#contribution

@TallTed
Copy link
Contributor

TallTed commented Jan 6, 2025

"Your entry should be added at the bottom of the appropriate category".

I strongly disagree with this. It effectively results in a random ordering, which typically makes such lists difficult to consume.

I think the entries within a given category should have a definite ordering, which I suggest be alpha-numeric by name/title. (I don't think there are any categories listing people, but if they should ever exist, I suggest these be ordered by family name.)

@amivanoff
Copy link
Contributor Author

https://awesome.ecosyste.ms -- another indexing service, this time with API

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants