Here’s why we are going open source
citizenlab.co
Here’s why we are going open source
1–10 of 26 posts
Re: Here’s why we are going open source
#2Not 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.
Re: Here’s why we are going open source
#3I worked in the same co-working space as Wietse, Aline and Koen, the three co-founders of Citizenlab, when they were launching their service. They're a super competent team with a fantastic vision and execution - I'm excited to see this new step in their story.
Re: Here’s why we are going open source
#4Not 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.
Re: Here’s why we are going open source
#5For those interested, here is the GitHub repo: https://github.com/CitizenLabDotCo/citizenlab!
Re: Here’s why we are going open source
#6Not 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.
I really hope they change the name. Citizenlab.ca is quite well established and doing important work.
Re: Here’s why we are going open source
#7How 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 big brain play, or some just sloppy oversight.
[EDIT] Clarification.
Re: Here’s why we are going open source
#8How 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.
Re: Here’s why we are going open source
#9They'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.
Re: Here’s why we are going open source
#10They'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.
This is important, +1.
If you want an example of what successful OSS looks like for over 10 years now, https://github.com/artsy, MIT license.