3 ms·
Some bizarre hair-splitting here. Besides, even if a beginner somehow wanders into the project, mis-IDs the project, and uses on their beginner server, then it
by hombre_fatal 7y ago
Some bizarre hair-splitting here.
Besides, even if a beginner somehow wanders into the project, mis-IDs the project, and uses on their beginner server, then it sounds like a good learning experience for them even though the README didn't give them permission to learn by neglecting to include the word "educational", god forbid.
Is this the catastrophic scenario you have in mind?
- AdieuToLogic 7y ago> Some bizarre hair-splitting here. I was trying to be explicit as to my reasoning. If that came across as "hair-splitting" then I suppose I failed to adequately do so. The whole point I was trying to make is that people find code in all sorts of ways. And my opinion is that if a public repo, such as GitHub, has a project which could easily be both desired (due to need) and misused (due to intent), then it might be a good idea to put a simple declaration in the project's README. Given all the blow-back this concept has incurred, I would think the concept is either wholly immaterial or now proven as needed.
- grepthisab 7y agoRelevant username? This seems to be a strange hill to die on. For all intents and purposes there is a declaration in the readme. And anyone who knows enough to want to operate with this will see that it's fairly basic. Others will likely just reach for a more generic or battle tested solution. In any case, people should be able to do what they want with their repos and code, assuming legality of course.