3 ms·
I do it for attribution, partly out of respect to the original authors, and partly to help resolve any licensing issues that may arrive - e.g. "This code was ta
by jestar_jokin 10y ago
I do it for attribution, partly out of respect to the original authors, and partly to help resolve any licensing issues that may arrive - e.g. "This code was taken from a site with no clear license on its use, so we may need to replace it at some point."
- exodust 10y agoLicensing issues? I'm not talking about entire plugins, and I didn't think others were talking about that either. I thought we were talking about Stack Overflow, where we learn the best way to iterate an array backwards or something that amounts to a small component of what you're doing. In that circumstance (which is what Stack Overflow is mainly used for) links would not be necessary in your comments.
- JdeBP 10y ago> Licensing issues? [...] I thought we were talking about Stack Overflow Xe probably was. * https://meta.stackexchange.com/questions/272956/ https://meta.stackexchange.com/questions/272956/ * https://meta.stackexchange.com/questions/271080/ https://meta.stackexchange.com/questions/271080/ * https://meta.stackexchange.com/questions/25956/ https://meta.stackexchange.com/questions/25956/ * https://news.ycombinator.com/item?id=10905009 https://news.ycombinator.com/item?id=10905009
- exodust 10y agoThat's quite sad. Most of the time SO is a source of learning a new technique rather than copying code snippets letter for letter. We are shown a cool way of doing something with fewer lines of code for example, and we apply that method to our own projects. If someone wants attribution for code, it better be something self-contained with its own home on github or at least a blog somewhere with a unique name: "my awesome plugin v1.0".