2 ms·
Yes, that is exactly what I'm proposing. You're talking about a library of markdown files for your own personal use to practice writing some code, posted to gi
by stackghost 9mo ago
Yes, that is exactly what I'm proposing.
You're talking about a library of markdown files for your own personal use to practice writing some code, posted to github, and includes a bunch of language about how to contribute, explicit instructions to fork it, etc.
Imagine giving a flying shit about the lack of a license, in that context. Couldn't be me.
The lack of a license file is by several orders of magnitude the least interesting thing about this repo.
- antonvs 9mo agoSo it's the nature of the repo for you, then. Presumably you wouldn't take the same position if the repo contained a substantial software system. > Imagine giving a flying shit about the lack of a license, in that context. Couldn't be me. Some of us are accountable to other people for these kinds of things. One comment mentioned possibly using this for a team transitioning to Go. In that context, license can matter. Having explicit authorization to use it changes it from an open question that can raise concerns, to something you don't have to worry about. Btw well done on adding to the "perennial complaining about the license". The top comment made a perfectly reasonable request, that may have been useful to the OP author. It wasn't a complaint. You could have just not commented. And flagging was an obnoxious choice.
- stackghost 9mo ago[flagged]