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

awesome manifesto #212

Closed
wants to merge 9 commits into from
Closed

awesome manifesto #212

wants to merge 9 commits into from

Conversation

n1trux
Copy link
Contributor

@n1trux n1trux commented Jun 27, 2015

as stated in #207, we should discuss the guidelines about what is awesome here.

@@ -0,0 +1,54 @@
# The awesome manifesto

If you want your list to be included on `awesome`, you should really
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want your list to be included on awesome, you should really just include awesome stuff.

This makes me think this is a list of rules to be included in the list. It should just be a list of tips/guidelines about how to make your lists more awesome.


## Include contribution guidelines

People who are contributing to your list should have a clear understanding how they should do so. You could copy a contributing.md from another awesome repository you like.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This also needs to explain what the contributing guidelines should guide about: formatting of the list, order, ...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what else?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could copy a contributing.md from another awesome repository you like.

Isn't this enough?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay but then link up a good one (ours, for example)

@n1trux n1trux mentioned this pull request Jun 27, 2015
@sindresorhus
Copy link
Owner

// @Aleksandar-Todorovic @h4cc


## Choose an appropriate license

See [Choose a License](http://choosealicense.com/no-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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the link target correct? "no-license" looks like the wrong target.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@h4cc Yup, you're right, it should link to the homepage. I originally wanted to explain what happens when you don't select a license and I forgot to change it once I paraphrased the paragraph.


But **what is awesome?**

## Only awesome is awesome.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The period at the end of this title is inconsistent.

@n1trux
Copy link
Contributor Author

n1trux commented Jul 2, 2015

so, does it look finished for the moment? Should we merge it?

@h4cc @Aleksandar-Todorovic @sindresorhus @arthurvr

@inputsh
Copy link

inputsh commented Jul 2, 2015

One small suggestion:

You could just copy a contributing.md from another awesome repository you like if you don't feel like writing a new one from scratch.

I bolded the words I think should be added. In my opinion, by leaving it like this, we're kind of encouraging people to just copy that file. In my opinion, that file should be a bit more descriptive and kind of depends on the topic of the list.

@h4cc
Copy link

h4cc commented Jul 2, 2015

I am kind of confused about the explanation "what is awesome". Should the list itself be awesome, or the linked content?
In my case the awesome-elixir list is the current only resource for easy finding any elixir/erlang library out there - thats what makes itself awesome, not every linked content is awesome too. So i have even duplicate entries in there.

A focus on the awesomeness of the list itself would be a better fit, i think.

@inputsh
Copy link

inputsh commented Jul 2, 2015

Should the list itself be awesome, or the linked content?

Both. It should link only to awesome resources and the list itself needs to be awesome (basically to follow everything from this pull request).

@@ -0,0 +1,40 @@
# The awesome manifesto

If you want your list to be included on `awesome`, you should really just include awesome stuff.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want your list to be included on awesome, try to only include awesome stuff in your list. After all, it's a curation, not a collection.

@n1trux
Copy link
Contributor Author

n1trux commented Jul 9, 2015

@strugee because it highlights the dangers of choosing no license.

@sindresorhus incorporated your suggestions.

@sindresorhus sindresorhus changed the title [discussion needed] awesome manifesto awesome manifesto Jul 9, 2015
@n1trux n1trux closed this in f8e6c22 Jul 9, 2015
@sindresorhus sindresorhus deleted the awesome-guidelines branch July 9, 2015 13:08
@sindresorhus
Copy link
Owner

Thanks @n1trux :)

amsharma91 added a commit to amsharma91/awesome that referenced this pull request Sep 27, 2016
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

Successfully merging this pull request may close these issues.

6 participants