Comments (3)
I see where you're coming from for all of this, and I appreciate it. I ultimately started this just as a list of lists - not as in an arbiter. It's hard for me to imagine shifting to that. "Tips" is better, but it's still vaguely preachy. I just wanted to link to knowledge repos. I don't have the energy to do more than that.
My thought process was, trying to discourage the sharing of pirated content and adhering to Github's Terms of Service.
If GitHub has an issue with a repo, they can take it down. I don't think linking to those repos is an issue. I'm not interested in being the police around what repositories are valid or not. It sounds like effort.
As for contributing, isn't putting these notebooks publicly on GitHub already a statement of intent for it to be shared?
I think a single line: "If you want to link back to this repo, do so!" would work well for me, in a PR. I don't know if I want anything more than that.
from meta-knowledge.
I've come across a couple that contain PDF versions of books that are not open-source or in the public domain.
Are those the only things in those lists? Why should we avoid that?
Regarding licenses: If there is a license in the top level, that should be fine. I'm not too worried about that. I also am not sure about contribution guidelines. This is mainly for notebooks that people have, and I don't mind if they don't accept contributions.
Happy to suggest a link back. Want to PR this particular change?
from meta-knowledge.
Are those the only things in those lists? Why should we avoid that?
My thought process was, trying to discourage the sharing of pirated content and adhering to Github's Terms of Service.
Licenses and Contribution Guidelines
I suggested these as part of a "rules" section to encourage people to think/talk about sharing their knowledge further. Even if they don't want contributions to their repositories, I believe there's benefit in suggesting that people share their thoughts around how they want their repositories to be used.
I think that "licenses" was most likely an unnecessary addition to the list, and calling the section "rules" might have been misguided.
Calling it "tips" or "suggestions" might better reflect what I was trying to say.
I can PR the 'link back' change for sure! What are your thoughts regarding what I said above? I hope I did a better job explaining my point, which, by the way, is just a suggestion, of course.
from meta-knowledge.
Related Issues (4)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from meta-knowledge.