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

Links to third-party content on nodejs.org – what should be included? #1971

Closed
fhemberger opened this issue Jan 1, 2019 · 4 comments
Closed

Comments

@fhemberger
Copy link
Contributor

Extracted from #1923: We're were already discussing more broadly in #1932, #1963, #1964 and #1965 what kind of third party content should be collected on the Node.js website at all (also making sure that it doesn't mean this content is promoted/endorsed by the Node.js Foundation in any way).

/cc'ing @Trott (who rose two of the issues mentioned above) and @amiller-gh (as this is also relevant for @nodejs/website-redesign).

@aymen94
Copy link
Member

aymen94 commented Feb 17, 2019

I think to should include on Node.js website every free no profit content.

@Trott
Copy link
Member

Trott commented Feb 17, 2019

I think to should include on Node.js website every free no profit content.

I think you're saying to include any content if it is free and not-for-profit. If so, I disagree strongly. There is plenty of free non-profit content that is also of extremely low quality. This approach would serve the content-providers, but that's not who we should be serving. We should be serving users.

@aymen94
Copy link
Member

aymen94 commented Feb 17, 2019

I think to should include on Node.js website every free no profit content.

I think you're saying to include any content if it is free and not-for-profit. If so, I disagree strongly. There is plenty of free non-profit content that is also of extremely low quality. This approach would serve the content-providers, but that's not who we should be serving. We should be serving users.

Obviously, the content must be approved by the Node.js Foundation.
It must be free and accessible to anyone

@ovflowd
Copy link
Member

ovflowd commented Aug 15, 2022

Closing as a stale issue. If any parties still feel that this subject is relevant, please feel free to reopen the issue 🙇

@ovflowd ovflowd closed this as completed Aug 15, 2022
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

4 participants