11–20 of 26 posts
They're asking contributors to sign a CLA which assigns copyright for your changes to them. Quick reminder: do not sign this kind of agreement. It's deliberately designed for them to pull the rug out from under you and make this proprietary again after a period of enjoying the benefits of community contributions. Shame on them for asking in the first place.
Not to be confused with citizenlab.ca, a research lab of University of Toronto that deals with high profile civil right violations using OSINT and tech analysis.
That's gotta be deeply frustrating for the original Citizen Lab who was founded 15 years before this company. It makes me wonder how much of their income has come from the good work and reputation of the original Citizen Lab.
How does the choice for AGPL influence third-party consumers of governments deployments the citizenlab platform? I understand this license closes the network loophole in GPL by forcing all calling code to be released under the AGPL, so I be interested to know if I can call apis and download data of my government website without sharing it or talking to citizenlab. Maybe I am a little paranoid but this feels like a bi…
The loophole is someone hosting a modified instance without publishing their source code changes. I don't think it affects data or APIs at all.
They're asking contributors to sign a CLA which assigns copyright for your changes to them. Quick reminder: do not sign this kind of agreement. It's deliberately designed for them to pull the rug out from under you and make this proprietary again after a period of enjoying the benefits of community contributions. Shame on them for asking in the first place.
What do you mean "pull rug out of you"? If they decide to discontinue GPL edition, you are free to pick it up from where they left.
Not to be confused with citizenlab.ca, a research lab of University of Toronto that deals with high profile civil right violations using OSINT and tech analysis.
Especially since the domain (including TLD) is only a single letter off
They're asking contributors to sign a CLA which assigns copyright for your changes to them. Quick reminder: do not sign this kind of agreement. It's deliberately designed for them to pull the rug out from under you and make this proprietary again after a period of enjoying the benefits of community contributions. Shame on them for asking in the first place.
Earlier quoted context omitted.
The loophole is someone hosting a modified instance without publishing their source code changes. I don't think it affects data or APIs at all.
Oh so I can basically do a SaaS and as long as I don't change the codebase without charing the changes its ok
Earlier quoted context omitted.
What do you mean "pull rug out of you"? If they decide to discontinue GPL edition, you are free to pick it up from where they left.
It signals that they're not making a long-term committment to open source. When they pull the rug out from under you, the community will have to scramble to put together a viable fork. It is a highly disruptive event that we've seen happen many times. Some communities never recover.
Even Firefox had one or two until recently.