mirror of
https://github.com/sindresorhus/awesome.git
synced 2026-07-25 06:44:12 -05:00
Improve the awesome list ecoystem #26
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/awesome-sindresorhus#26
Reference in New Issue
Block a user
Originally created by @sindresorhus on GitHub (Jun 24, 2015).
A lot of lists are missing important things or just too low of quality. We could be nice internet citizens and help out those lists.
Common things I open issues about in lists:
Having all lists follow this would improve the quality considerably.
Maybe we could come up with some guidelines on what's a
awesome"certified" list?Anything I missed?
Anyone care to help out opening issues on lists? Both lists included here and not.
@sindresorhus commented on GitHub (Jun 24, 2015):
@n1trux
@arthurvr commented on GitHub (Jun 24, 2015):
Neat idea. Just going through some of the lists. If a list looks unmaintained, should I open an issue to discuss removal and/or finding an alternative?
@sindresorhus commented on GitHub (Jun 24, 2015):
Yes, though unmaintained should be a bit loose, meaning not updated in many months.
@arthurvr commented on GitHub (Jun 24, 2015):
@sindresorhus Well, WDYT? https://github.com/dypsilon/frontend-dev-bookmarks. The 54 open PRs...
@sindresorhus commented on GitHub (Jun 24, 2015):
@arthurvr Would be happy to change the link to an alternative high quality fork, but don't want to remove it as it's a good resource as is.
@inputsh commented on GitHub (Jun 24, 2015):
@sindresorhus Maybe creating a new file called something like
guidelines.mdthat will explain this process?@sindresorhus commented on GitHub (Jun 24, 2015):
@aleksandar-todorovic Yes, that's the idea. Just need to decide on what it should contain first.
@inputsh commented on GitHub (Jun 25, 2015):
Here's my idea. Of course, you could improve the order a bit.
Only link to awesome content.
Don't link to everything people suggest you to link. Research it, find out if it's really awesome and include it if it is.
Request a personal comment on why something is awesome
It's not enough to just suggest something. You also have to say why do you suggest it and how will the potential users benefit from consuming it.
Make it clear on what the list is about
Make sure your list covers a certain scope and nothing else.
Pay attention to the grammar
Please be sure that you do your best to keep the list grammatically correct.
Choose an appropriate license
See Choose a License for more details. Keep in mind that if you haven't selected a license, it basically means the people are not allowed to reproduce, distribute or create derivative works.
NOTE: I did an interview with a GitHub representative about licenses that could be a perfect addition to this section. It'll be online in a couple of days.
Stylize your list properly
Create table of content, put a picture or two, organize the content into different categories.
Accept other people's opinion
If you're an owner of the list, respect other people's opinion. If there are plenty of users not agreeing to your decision, give it a second thought!
@n1trux commented on GitHub (Jun 27, 2015):
Nice idea, I think we should continue our efforts in making the lists better.
I'll start with my own one and then open issues on other lists. Should we mark "certified awesome" lists which adhere to the awesome guidelines with ☑ or ❤ or another symbol to distinguish them from the ones needing work?
Should we create an "awesome.md" with a "check list" or merge the guidelines into contributing.md?
Kind of like an "awesome manifesto"?
@arthurvr commented on GitHub (Jun 27, 2015):
I opened quite a bit of issues on lists last week too.
@sindresorhus commented on GitHub (Jun 27, 2015):
I'd rather we just help everyone get there when the guidelines are decided on. We can remove entries that are non-responsive.
awesome.md file in this repo that is referred to from the readme and contributing.md
@h4cc commented on GitHub (Jun 27, 2015):
I think such a community should be based on standards and choosen membership. A role model or overall inspiration could be these guys: https://thephpleague.com/
Just replace "PHP Packages" with "Awesome Lists/Content".
@sindresorhus commented on GitHub (Jun 27, 2015):
What does that even mean? Elaborate?
@n1trux commented on GitHub (Jun 27, 2015):
Fair enough.
Okay, I'm doing just that. Should I create a PR or push directly and we discuss later?
@sindresorhus commented on GitHub (Jun 27, 2015):
You can usually just push directly, but I think it would be helpful to do a PR so we can discuss directly there.
@h4cc commented on GitHub (Jun 27, 2015):
@sindresorhus Its a term i used for the "we" in your previous sentence:
Defining what is "certified" needs to be a rfc-style decission needed a group of people.
Also calling it "certified" might be counterproductive by scaring maintainers and producing competition. A open and friendly group that could be joined on free will seems way more friendly to me.
@n1trux commented on GitHub (Jun 27, 2015):
Fair enough.
Okay, I'm doing just that. Should I create a PR or push directly and we discuss later?
@arthurvr commented on GitHub (Jun 27, 2015):
Create a PR so we can discuss it first.
@arthurvr commented on GitHub (Jun 27, 2015):
Also worth checking some lists for broken links. Found quite a bunch of them.
@h4cc commented on GitHub (Jun 27, 2015):
That could be offered as a service. Or every list would have to integrate that into its own CI with travis or such (what i already did).
@n1trux commented on GitHub (Jun 27, 2015):
oh fuck. Accidentally uploaded it before branching :/
https://github.com/sindresorhus/awesome/blob/master/awesome.md
er, should I remove it again or should we just discuss it now? facepalm
@sindresorhus commented on GitHub (Jun 27, 2015):
@n1trux Fixed it for you. Just click the green pull request button in the repo ;)
@dypsilon commented on GitHub (Jun 29, 2015):
@sindresorhus I will go through your list and improve the quality of frontend-dev-bookmarks asap. Thank you for your contributions to the community.
@gothburz commented on GitHub (Jul 7, 2015):
You know what would be awesome but a long process? adding the logos to each link or just the big ones.
@sindresorhus commented on GitHub (Jul 7, 2015):
@xPetrus It's a nice idea, but I honestly don't think it's worth the effort. And it will look weird when only some have graphics.
@strugee commented on GitHub (Jul 8, 2015):
I think this could be solved by putting a placeholder (e.g. blank circle or something) next to any list that doesn't have a graphic... shrugs
@sindresorhus commented on GitHub (Jul 8, 2015):
Yeah, I just prefer the simplicity of text. Logos are all different. In my mind, it would look kinda noisy.
@sindresorhus commented on GitHub (Jul 9, 2015):
The awesome manifesto is now live: https://github.com/sindresorhus/awesome/blob/master/awesome.md
We're still very much open to improvements and additions. I'm sure there's things we've missed.