[archived] On GPL without contributor licenses, the App Store, and future of Pulse

Development
1

Hey folks,

We have a problem.

As you know, Syncthing is currently GPL licensed and yet has no contributor license agreements in place. This means, among other things, that no one can put a Syncthing-based app (or Pulse-based, as Pulse is a fork of Syncthing) in the App Store (or any app store, most likely). It also means that no one entity can defend it against license violations, etc.

For Ind.ie, it means that we do not currently have control over a component that we are using as a core element of our platform and that’s unacceptable for us, going forward. (If we are to compete with proprietary software vendors who have 100% control, we must also.) We already have the disadvantage that we are four people (two developers) with $100K+ in crowdfunding vs. thousands of developers with billions in venture capital. (We’ve structured Ind.ie so we cannot take venture capital even if we wanted to because there are no shares — we’re a social enterprise limited by guarantee.)

Anyway: going GPL without contributor license agreements was a mistake. It was a mistake on my part as I didn’t think about it and assumed they would be in place (live and learn).

So, the question is, what are going to do about it?

The easiest way out of this mess would be to revert to MIT.

I’ve talked to Jakob about this and he does not seem to favour this option.

If that’s the case, it leaves us with two options — neither of which are fun but one (or both) of which are necessary for Ind.ie, going forward:

  • Re-fork from the MIT version and continue from there
  • Re-implement from scratch

Of course, ideally, the easiest option is to revert to MIT and then we solve the app store issue also.

Would love to hear your thoughts on this.

2

Why would it mean this? Having to sign over copyright with a contributor license agreement is a fairly recent development, driven by corporations, and nothing that’s inherent to using GPL or part of it’s history. The only reason for doing it is to be able to distribute the software under non-GPL terms for whatever reason (usually economic). Are you referring to the fact that I would have limited funds to pay layers to mount a litigation against some violation, while if copyright was signed over to some entity with a lot of cash this would not be a problem? Are you offering your $100k as a legal defense fund? :wink:

I’m not really sure what control you are lacking, but I guess you mean the ability to sell it as is? If so, yeah, I guess. It’s free software, so you have the same control you have over Linux, the rest of the GNU toolchain, etc.

Well, yes and no. Can we clarify what exactly it is you want to accomplish once the license is changed? Obviously, the legal defense part is a red herring since going MIT doesn’t accomplish anything remotely useful on that front, so I’m assuming this is all about putting Pulse (Syncthing) on the app store? Under what terms, for whose financial benefit, etc?

The part where I’ve said I’m not super impressed by MIT (in email) is for the case where someone just grabs a blob of code and sells it on the app store, without the original authors getting a dime. This is in the spirit of the MIT license, and generally it’s something I haven’t worried about in the past because it’s usually not worth it while the original project is out there for free.

But the app stores changes this dynamic in that all you need is a little marketing and you can easily drown out the “genuine” project, even if that is also available for free on the same store… I don’t want to see fifteen clones like “Syncthing Pro”, “Pulse HD” and so on out there that random people are selling and marketing on our behalf…

2 Likes
3

There is the option of using ‘weak’ copyleft licenses such as the LGPLv2.1 or MPLv2, the latter can even be edited in such a way that the compatible ‘secondary licenses’ can be defined by an external authority such as the Ind.ie project.

Any modifications to the library would have to be distributed under the same license, so in effect if a company tried to add their own sauce to the Syncthing library, it would have to be redistributed under the LGPL or MPL.

1 Like
4

There might be a useful middle ground here, yes. I’ve heard good things about MPLv2 here and there.

This is tricky by the way, since you need to ensure that you are not influenced by the GPL code that came afterwards. That means not fixing the same bugs in remotely the same way, not implementing the same features, etc or it’s a derived work of the GPL code again. GPL is called viral for a reason. :slight_smile:

1 Like
5

If I understand this part of the MPLv2 correctly,

3.2. Distribution of Executable Form

If You distribute Covered Software in Executable Form then:

such Covered Software must also be made available in Source Code Form, as described in Section 3.1, and You must inform recipients of the Executable Form how they can obtain a copy of such Source Code Form by reasonable means in a timely manner, at a charge no more than the cost of distribution to the recipient; and

You may distribute such Executable Form under the terms of this License, or sublicense it under different terms, provided that the license for the Executable Form does not attempt to limit or alter the recipients’ rights in the Source Code Form under this License.

It basically says “if you distribute a binary, you must make source available and let people know where to find it” and “distribute the binary under whatever license you like, as long as the source is available as above”.

Which seems both app store and common sense compatible to me…

1 Like
6

Hey Jakob,

A contributor agreement doesn’t mean signing over copyright. Look at how Canonical do it with a license assignment. I’m not a fan of having people sign over their copyright or waive their moral rights. At Ind.ie we will be using an agreement based on http://contributoragreements.org

Yes, exactly: we need to be able to distribute on App Stores. We need to distribute on App Stores if we are to compete with the ease of proprietary solutions that distribute on App Stores. And yes, we will be asking for payment for App Store versions of Heartbeat to keep Ind.ie going because we do not work for spyware/malware companies during the day to fund our hobby of working on open source projects in the evening. Instead, we are trying to create viable, sustainable alternatives.

No, I’m referring to the fact that you do not have the legal right to defend anyone else’s copyright.

We can then include Pulse as part of Heartbeat and potentially on the App Store in the future. Regardless, it will mean that we don’t spend our limited resources contributing to a code base that we do not have control over.

This isn’t for Pulse — Pulse is a component of Heartbeat. As is, Pulse/Syncthing wouldn’t make sense on an app store. That’s not what its for (at least not how I see it). It’s a component, not a product.

GPL isn’t a patent :slight_smile: Last I checked, you cannot license ideas under GPL, just code. Unless we copy code, we are free to reimplement or implement new functionality on an MIT codebase as we see fit. Are you saying that anyone who implements the Block Exchange Protocol must do so in GPL? That any other language implementation must be in GPL? If so, you should make that very clear in the protocol license so that people know not to use it.

1 Like
7

Why do you need this? What is GPL not providing to you with that you need to satisfy your goals:

I want technology that protects our freedoms, human rights, and democracy, not technology that erodes them. I want technology that I own and control, not technology owned and controlled by corporations.

1 Like
8

I don’t need to. Defending the majority of the project I still have copyright on is enough to defend the project.

Now you’re just being disingenuous and spreading FUD. Algorithms and ideas are not copyrightable, at all. The protocol is public domain, of course there are no restrictions on the license of implementations. I’ve said previously that even if an implementation in another language were similar enough to somehow constitute a derived work by some lawyerly definition, I’d never “go after” that because there’s absolutely no reason to. I want there to be multiple implementations.

But reading a patch, then implementing that same feature on the same codebase in a similar manner is generally considered a derived work. This prevents idiocy like following a project commit for commit and reimplementing each step slightly differently with a different license and copyright. Or getting a patch, saying “thanks, i’ll just reimplement it myself slightly differently” and not giving credit where it’s due.

But let’s not go further down this discussion, because it’s stupidity.

You want to use Syncthing/Pulse as a component in Heartbeat. That’s awesome, it’s what we discussed at the start of our venture, and I suggested then “just do it man, it’s MIT”. :wink: Now it isn’t anymore, and ironically it was you who convinced me to be OK with GPL by the reasoning of not letting evil corporations steal and sell the code.

So how about something like MPLv2 above? It lets you use Syncthing as a component, it requires source to be released for modifications, win-win? You’ve said Pulse isn’t going to be sold as a standalone app by Ind.ie, and I’m fine with that. My nebulous “app store gold diggers” should be somewhat deterred by having to release source, and if they aren’t, whatever. Are there any downsides I don’t see here (from either camp, GPL-preferrers and MIT-preferrers)?

9

So, I was trying to steer this back to something constructive, but then I reread this and see the dig against me in the second sentence and get fucking angry. Yes, I work for a company you don’t approve of during the day, producing something in the evenings for the benefit of all, that I’m not selling.

You want to take that and sell it, with an as yet unspecified layer of functionality on top. So you barge in and declare “we have a problem”, insult me, and want license changes so you can sell the software? The software that you and your company have so far contributed zero lines of code back to? That’s a bit of a crappy attitude, to be frank, and not the way towards whatever goal you have…

Perhaps if we lay off the personal attacks, define the goals, and define what you intend to contribute back to Syncthing, we can get somewhere?

3 Likes
10

Our ability to compete on UX with proprietary solutions that are available on App Stores. Also the competing on unequal ground with proprietary software companies that control 100% of their codebase.

I don’t think that’s hard to understand and I’m not sure how to make it any clearer so I’ll stop trying.

11

It wasn’t a dig at you specifically but at “open source” in general. Working at (e.g.) Facebook, Google, etc., and, with the privilege afforded from that, working on open source projects as a hobby is quite common. And no doubt a lot of value is created that can be used by independents as well as proprietary silos. But what’s not created are alternatives.

So here we are, a tiny group of people, who are working for comparatively little pay (everyone gets a little over £2K a month expect me, I just put money in and don’t draw a salary; I subsist currently on professional speaking fees) who are trying to make an alternative. I don’t mention this because “hey, we’re holier than thou” but because I’m sick of the allegations that somehow we’re some sort of corporate entity in it to make money. If I was in it to make money, I’d be working at a cushy job at a malware/spyware company instead of setting up a social enterprise that doesn’t even have shares so that it cannot be sold or accept venture capital. So that’s quite enough of that, to be honest.

I think it’s clear that we have very different cultures and I’m done responding to “why can’t you do it our way” questions. We’re not doing it your way because we don’t have or want the privilege of working at malware companies for high 5/6 figure salaries during the day while we work on open source in the evenings. And we have absolutely no reason to justify our actions to people who are.

Please feel free to do whatever you like with the license of Syncthing going forward. It’s your hobby project and you have every right to run it as you see fit. At this point, I’m done wasting our limited resources on this farce.

We will continue to use the fork, with whatever restrictions are present in the license, until we have our own implementation of something that solves the same problem.

It was my mistake in thinking that open source culture could evolve to be compatible with independent technology. It’s not. We won’t make that same mistake again.

1 Like
12

This is a textbook example of where the GPL can unintentionally lead, and one more reason I stick to the most minimalistic permissive licenses (MIT and BSD) for my own open source projects.

IIRC, back when the Syncthing license was MIT the lead developer was cool with a company of some sort doing a friendly fork.

Then - who knows why - said company suggested relicensing under the GPL, soon to find out they had shoot themselves in their feet.

Now, no matter how much goodwill may have been there from both sides, it sounds like the Pulse fork is not going to be that friendly anymore, and chances of cooperation and mutual benefit for the two projects appear slim.

No individual or small company can really afford the legal costs of enforcing whatever license terms they set against some ‘big evil corporate code thief’ anyways, so why bother with pages of licensing legalese? If I MIT/BSD license something and somebody takes it and makes millions, good or them - they found a business case I wasn’t aware of and wouldn’t pursue myself. If I code something specifically for my own financial gain, I simply do not open source it. I can always license it for free to whomever/whatever use I may wish.

But hey, to each his own, and thanks a bunch for giving us Syncthing and any offsprings may come. Please take my post as well meant, from a user who appreciates what great tool Syncthing is :o)

2 Likes
13

@aral cut the personal attacks please, it’s helping nobody.

14

I’ve read through your posts and find it hard for you to achieve anything with that sort of attitude. You class both Pulse and Syncthing as a component and not a product but I definitely don’t see how you get to this conclusion, Syncthing is far from a component even at this early stage.

At any rate all I’ve ever seen since finding Syncthing in November are constant posts from you not getting on with something or nitpicking instead of spending your time doing what you say you intend to do.

15

So @aral, why isn’t the MPLv2 a viable option for you? You haven’t said anything about it, when it seems like the obvious solution.

2 Likes
16

Hey only a few words from me to this conversation. Beside Hyperboria, Syncthing is the first Project I’ve seen that does realy something against the intended restrictions of the Internet from states or others and for more privacy. So I’m following Syncthing just since some weeks but I’m impressed what allready have been done! And I think it should keep up in this manner and that includes also that every product, that says, it uses Syncthing should be open as well. Under MIT-license an other product could use Syncthing and brand it as a safe and secure product but oneself coud be closed source. I think thats not honest and undermine the fight against restricting the freedom of the internet! Who knows, what a product like that could do beside, when itself is not opensource? The only and most important thing ist to suport projects like this one, so that they can keep up! Discussions like this waste useful energy! I’m a poor electroingenieur-student, but when I can suport projects like this, it would be a pleasure for me :wink:

17

I’m not sure that the goal of Syncthing is really to go against restrictions of the internet from states. I simply see it like an open-source alternative to BittorentSync. Other projects such as Freenet, I2P, RetroShare, OneSwarm or Waste are more intended to build a communication network “spying proof”.

18

Because I hadn’t had a chance to read through it. Now that I have, it seems like a viable fit. As I understand it:

  • Any changes to the source code must be shared back

  • You can do what you like with binaries (as long as you share back)

Is there anything else I’m missing?

1 Like
Syncthing is going to be relicensed as MPLv2
19

That’s pretty much it. Only thing is, if you want to allow this work to be combined with (L/A)GPL code i.e. compatible with those licenses, you need to remove the ‘Incompatible with secondary licenses’ clause at the bottom of the license file, otherwise users won’t be allowed to proliferate to those licenses.

20

I wrote a huge rant in response to the Oct-Nov discussions about my dismay of switching to GPL, and now I am very pleasantly surprised to come across this more recent discussion and see that Aral / ind.ie came to the realization of the limitations of the GPL!! I’m all for a Stallmanian utopia where all software is GPLv3, we all have Star Trek replicators so no programmers starve, but we aren’t there yet, and in today’s world, GPL is brutally impractical, (especially for something like syncthing that might be useful as a library,) and therefore repulsive to a huge chunk of developers.

I think SyncThing/Pulse looks awesome and set up a bunch of shares across 6 devices, but then was about to write it off as a user due to lack of app store compatibility. I want an open source bittorrent sync replacement, and I have that on iOS/Android but it looks like SyncThing can’t go on iOS, and new features/bugfixes can’t be brought over to the swift port since they are derived works of GPL software…problem!! And I was about to write it off as a potential developer who could contribute bugfixes/small features, because I work on mobile apps and games that get deployed to app stores (I’m actually considering a sync mechanism for a mobile and perhaps console game, as well as some eventually open sourced (MIT libraries) to support it), where GPL and LGPL are both no-go’s. When I see *GPL, my brain thinks “you’re dead to me” and moves on. It’s not a philosophical choice, it’s my reality. And I am not alone.

As much as I wanted to unload my beautiful unabridged rant against the anti-freedom GPL and LGPL (MPL is ok with me), it looks like peacemaking is needed now:

Guys, PLEASE don’t let petty misunderstandings undermine what could be a great synergistic relationship, or put the future of what should be a BitTorrent Sync killer (and eventually DropBox et al killer, and foundation for a facebook killer,) in jeopardy! So take a breath! 1) Aral makes the dig at spyware companies as part of his regular ind.ie schtick – it’s clear to me it wasn’t directed at Jakob. 2) Also, Aral wasn’t being disingenuous/FUDding about the GPL and derived works. Jakob has a very valid point about fixes being derived works of a GPL, but what constitutes “so inspired it is a derived work” is very much a fuzzy thing that is open to interpretation and Aral just didn’t seem to be as concerned. Why? First, he has a point that algorithms (such as trivial bug fixes?) can’t be copyrighted in their purest form, so that may eliminate the need to find alternative fixes in some cases, (albeit the person who reads GPL syncthing code to determine what is a trivial fix may be “tainted” and unable to contribute to a MIT codebase.) But perhaps Aral does not fully understand how being inspired by GPL bugfixes/commits may taint code as derived work of GPL and therefore be infected by the GPL virus. Or maybe he thinks he and his people have the resources to do clean-room implementations. In any case, there’s no reason for the discussion to get heated. 3) In the context of Aral’s grandiose vision of displacing Facebook, pulse/syncthing is just one small component, but to Jakob and users like me, syncthing is a pretty big deal right now as a standalone cross-platform application! We each have different perspectives about how it is useful to us – don’t get bent out of shape. Some of us think BTSync replacement is big potatoes, while others think that Facebook replacement is big potatoes (and anything else is small potatoes.) And I want to include some sort of peer to peer sharing/sync in apps I make – that could be the kind of thing Aral was referring to when he said it could be a component of something larger. 4) I would think it would be good to not resent ind.ie for not contributing back yet – I’m guessing they have a lot of software to write and adding v2.0 features to syncthing will come but it’s not the biggest bang for their limited buck at this point.

I have been waiting for years and downloaded tons of crappy closed source non-cross platform sync software over the years (one was so good, FreeFileSync, I put up with it even though it defaulted to install Conduit malware in its installer, and I accidentally installed it once. Holy cow! So much for my extreme disdain for malware purveyors.) SyncThing/Pulse/ind.ie is too good of an idea to blow up from misunderstanding in a few messages. BitTorrent Inc., closed a thread in their forums that was advertising SyncThing too much. That’s how I found out about it. You’re sticking it to the man! Keep it up!

You two appear to be prone to emotional overreaction, and hasty decision making (so don’t feel bad about changing your mind – making bad decisions is fine as long as you’re not too stubborn to fix them.) Realize these weaknesses and be prepared to gracefully deal with the consequences, (as you grow out of these weaknesses.) But neither of you guys is mean-spirited. You guys should be friends. Trust me.

So I say pick MIT (or MPLv2) and get on with making beautiful music together!

3 Likes