There is still quite some amount of hubris in this. If A writes software under L0 and gives it to B and is “nice enough” to allow B to use it privately for free, there’s some entitlement to the software., You’re…
It’s misleading because it pretends that you need zero licences for it.
Nor is it Ⓕ Copyfree compatible, and none of the BSDs would ever touch it either. So that leaves you with adaption by unwashed unorganised masses who wouldn’t care about licence terms at all.
Just find something that brings bread on the table. Doesn’t even have to be software-related, could be, idfk, gardening.
Eh, you can use a fixed-width font in GUI apps, too. In Kontact, for example, you just press “x”. FixedMisc is still the best font
meh, give me ed over vi and emacs any day “modern” seems to be a curse word these days, all the time I find it being used it’s used to describe something despicable like the systemd ecosystem.
Slack? Ugh. When my employer turned off the company-internal Jabber server in favour of, out of all things, Hipchat, I moved my team mates to IRC. (They also seem to all know at least some vi, even the trainee.)
I am the author. And I am not an academic interested in bringing out a lengthy article with explaining the interpretations and all. I am, in this instance, pragmatic: explaining what’s bad, why it’s bad, what we need to…
Sorry about that, I was more concerned with getting the explanation into more than 140 chars and out to both people and GitHub and getting in touch with GitHub than with writing a lengthy article. And all this besides…
The licence per se is not disallowed. If you create a work from scratch and decide to put it under GPL and upload it to GitHub (thus granting extra rights), that’s just fine. It’s only you cannot currently upload…
True. But CC0 is deprecated by CC themselves and CC requested the OSI to not approve it. It is unclear whether there will be a successor. But any of the BSD/MIT-ish licences should be close enough to a “gift” for this…
“how these rules came to be and what they try to achieve” That’s not my point here. The intent behind the rules and what they’re trying to achieve is GOOD and A STEP UP from the previous ToS. HOWEVER, they have language…
Someone intelligently (hah) decided to link to the (1 MiB) page with the entire wlog posts of the last decade (plus CSS, webfonts, …) instead of to the permalink of the one article (15K), and then over https. The…
But, thanks to the new ToS becoming effective immediately (as of 28½ hours ago), you do have to act. Basically, starting March 2017, uploading anything (new) like that is not allowed. Removing repositories and/or the…
BSD/MIT/etc. only require the licence text to be present, usually by retaining it in the source code or accompanying documentation. Yes, it’s close. No, I don’t want to go there and discuss this detail.
Github doesn’t, it just requires that of its users (that, or to not upload any copylefted works, or works under licences requiring attribution, which contain work from people who have not agreed to waive those…
Both the AGPL (“anciliary transmission”) and the law have exceptions for ISPs and other such scenarios.
Yes, that’s actually what GitHub and I are talking about now. Any OSS licence already grants way enough rights for a hosting platform to operate, period. Anything else can be solved technically and does not need to…
They actually had a review period, and did some good changes. But then, they took a week to look at the reviews (ostensibly; I, as well as others, never got any response to them), went and made some minor changes (which…
No, don’t use JIRA for developing OSS: https://mako.cc/copyrighteous/free-software-needs-free-tools
I’m in contact with them, as I wrote in the updated post.
Yes.
Any OSS licence fulfils the requirements EXCEPT for GitHub’s requirement to not add any requirements to the grant. See my updated post.
just ssh, git and gitweb will do. Or self-hosted FusionForge if you need more fancy stuff.
As far as I can tell: no, unless GitHub takes taking excerpts from works too far and redistributing them without the licence attached. But nobody else is allowed to deal in those excerpts then, except via the original…
There is still quite some amount of hubris in this. If A writes software under L0 and gives it to B and is “nice enough” to allow B to use it privately for free, there’s some entitlement to the software., You’re…
It’s misleading because it pretends that you need zero licences for it.
Nor is it Ⓕ Copyfree compatible, and none of the BSDs would ever touch it either. So that leaves you with adaption by unwashed unorganised masses who wouldn’t care about licence terms at all.
Just find something that brings bread on the table. Doesn’t even have to be software-related, could be, idfk, gardening.
Eh, you can use a fixed-width font in GUI apps, too. In Kontact, for example, you just press “x”. FixedMisc is still the best font
meh, give me ed over vi and emacs any day “modern” seems to be a curse word these days, all the time I find it being used it’s used to describe something despicable like the systemd ecosystem.
Slack? Ugh. When my employer turned off the company-internal Jabber server in favour of, out of all things, Hipchat, I moved my team mates to IRC. (They also seem to all know at least some vi, even the trainee.)
I am the author. And I am not an academic interested in bringing out a lengthy article with explaining the interpretations and all. I am, in this instance, pragmatic: explaining what’s bad, why it’s bad, what we need to…
Sorry about that, I was more concerned with getting the explanation into more than 140 chars and out to both people and GitHub and getting in touch with GitHub than with writing a lengthy article. And all this besides…
The licence per se is not disallowed. If you create a work from scratch and decide to put it under GPL and upload it to GitHub (thus granting extra rights), that’s just fine. It’s only you cannot currently upload…
True. But CC0 is deprecated by CC themselves and CC requested the OSI to not approve it. It is unclear whether there will be a successor. But any of the BSD/MIT-ish licences should be close enough to a “gift” for this…
“how these rules came to be and what they try to achieve” That’s not my point here. The intent behind the rules and what they’re trying to achieve is GOOD and A STEP UP from the previous ToS. HOWEVER, they have language…
Someone intelligently (hah) decided to link to the (1 MiB) page with the entire wlog posts of the last decade (plus CSS, webfonts, …) instead of to the permalink of the one article (15K), and then over https. The…
But, thanks to the new ToS becoming effective immediately (as of 28½ hours ago), you do have to act. Basically, starting March 2017, uploading anything (new) like that is not allowed. Removing repositories and/or the…
BSD/MIT/etc. only require the licence text to be present, usually by retaining it in the source code or accompanying documentation. Yes, it’s close. No, I don’t want to go there and discuss this detail.
Github doesn’t, it just requires that of its users (that, or to not upload any copylefted works, or works under licences requiring attribution, which contain work from people who have not agreed to waive those…
Both the AGPL (“anciliary transmission”) and the law have exceptions for ISPs and other such scenarios.
Yes, that’s actually what GitHub and I are talking about now. Any OSS licence already grants way enough rights for a hosting platform to operate, period. Anything else can be solved technically and does not need to…
They actually had a review period, and did some good changes. But then, they took a week to look at the reviews (ostensibly; I, as well as others, never got any response to them), went and made some minor changes (which…
No, don’t use JIRA for developing OSS: https://mako.cc/copyrighteous/free-software-needs-free-tools
I’m in contact with them, as I wrote in the updated post.
Yes.
Any OSS licence fulfils the requirements EXCEPT for GitHub’s requirement to not add any requirements to the grant. See my updated post.
just ssh, git and gitweb will do. Or self-hosted FusionForge if you need more fancy stuff.
As far as I can tell: no, unless GitHub takes taking excerpts from works too far and redistributing them without the licence attached. But nobody else is allowed to deal in those excerpts then, except via the original…