Define a) āpersonal dataā, b) āshare a build anonymouslyā, oh and c) integrity 
a) There are some scripts that add the username/host/timezone/dates to the build (ādefault.propā)
b) Depends, eh?
c) Complicated to do, but possible if you set it up correctly and if supported a bit by FP.
Data which might identify me clearly. Clearly enough to get sued by the rightsholders.
Upload it via VPN to an OCH (mega,zippy,etcā¦)ā¦
No manipulations, changes of the official source code.
I guess thatās a major problem. While it started to sound very interesting, and publishing fposos is indeed a cool idea, IMHO, all that fuss about legalese for the blobs kills this idea, nobody will look for other ROMs, like cm or omnirom or whatever. This leads to the situation you described above, people turn to Samsung et al, even though their hacker friendliness is not that great eitherā¦ But look at e.g. the Samsung S3, many people still are using it, because it still gets an official cm, for example. So, in terms of sustainability, itās not that bad eitherā¦
Are you saying you donāt need blobs to get CM on Samsung devices? I donāt know whether this is true but have a hard time believing it.
What I have seen so far with (almost?) all devices that get CM is: Binaries are copied from the device itself and then used to build CM. There is no ālegaleseā which you have to agree to. However, this does not make it better for you. It probably just means that what you do is not covered legally. Having this ālegaleseā is actually an improvement in my understanding because we get the blobs without having to hunt for them first and we may officially use them.
In most other cases we donāt have this freedom but people are just grabbing and distributing the blobs without asking whether they are allowed to do so. If you think Samsung devices give you enough freedom to distribute CM for their devices, then you can also go forward and distribute builds for Fairphone 2. The only thing stopping you is your conscience which apparently doesnāt stop you in case of Samsung devices 
No, āof courseā cm has to use binary blobs, they way you describe it. But for other devices there is no legalese, so nobody is hindering you putting the blobs on cm. The FP blobs explicitly are forbidden to be distributed that way in a room not provided by Fairphone so, we would need a bare cm where we could install the blobs afterwards. Thereās a lengthy discussion wether thatās possible at all, and probably it isnāt. So no ROM not provided by Fairphone, except for something like replicant. But then lots of things probably wonāt workā¦
And thatās exactly my point: This is just not true. When you buy another device (say from Samsung), you implicitly agree to their terms. The thing is, nobody reads those terms, but Iām 99.9% sure they include a clause prohibiting you from extracting the binaries and distributing them to other people. Developers just donāt care.
The difference with Fairphone is that they explicitly allow you to get the binaries and even present them to you. The caveat is that they also shove the terms under which you may use them up your face and that makes people aware of them and ā¦ voila, their consciousness kicks in.
Well, I donāt follow you 100%. For me, itās a grey area. You are normally and also explicitely hindered to reverse engineer the software or otherwise modify it. Thereās no writing (with the samsung I had) to prohibit this propagation. Not up to now. Samsung especially goes at great lengths to hinder you unlocking the bootloader, with Knox and Flash counters and all that, but they donāt follow up on the simple copying for all those official and inofficial CMs, OmniROMS, SlimRoms and what else on third party ROMs. Thereās virtually no manufacturer I know of that went against this praxis (except for Google and itās (in)famous action with gapps, so these are not distributed with CM and the likes)
Do you think Fairphone would?
Good question. Qualcomm would, I guess. But Fairphone might be forced to, even if they donāt want toā¦ At least they wrote it down explicitly, so you are supposed to expect it
I do not understand:
a) Who wrote that licence (clearly not a lawyer)
b) The licence (see above)
c) What the difference between a file everybody can download and sharing the same file in a ROM is.
Itās totally okay to put in a statement ādo not decompile our secret sauceā, but if you do so and offer it as a download for everybody, you can also just use it in a ROM.
I think this was written by FP or the ODM, but not by Qualcomm.
Iād say this one was written by lawyersā¦
And they do explicitly forbid the sharing of the blobs as long as itās not Fairphone distributing them
The decompile stuff just comes on top, but this you get with other devices also.
I did not check the license lately, but it is well possible that this license is Fairphoneās, whether written by them or dictated by the software owner behind them, I donāt know. In the end, it doesnāt matter for usā¦
The EULAs looks like copy and pasted together, maybe it was Google Anyway, all I want to say that it does not make a lot of sense. It looks like it was copy and pasted together from different EULAs. It would be nice if FP could explain who wrote the EULA.
The last time I saw āYou must not take any actions that may result in the fragmentation of Android.ā was in the old Android EULA. Itās not even in there anymore.
Also itās from the Google SDK, it has nothing to with bin blobs from companies that build cameras or gps receivers. They couldnāt care less.
Google SDK Terms
FP2 Binary Blobs Download Page, Special License Agreement, April 2016
I was just about to order a Fairphone and discovered both the License Aggrement for the binary blobs and this thread afterwards. I wonder if it is even legal to force a customer to aggree to license that claims to make the seller able to force you to delete the drivers on your phone and thus basically make it unusable after it has become your property.
Really bad thing, basically a curseā¦
http://code.fairphone.com/projects/fp-osos/dev/fp2-blobs-download-page.html
This Agreement applies from the first date you download the Software and
you may terminate it at any time by permanently destroying, the
Software, all backup copies, and all related materials. This Agreement
can be terminated in writing by Fairphone, at any time, without prior
notice. Upon termination, you must destroy the Software, all backup
copies, and all related material.
I guess it just a standard text that Google sends around for Android. But I never got an official answer on this. Iām not sure if this text was even ever read by a lawyer. Fun fact: code.fairphone is not even including the google services, itās just plain Android. So they protect the āIPā of the OEMs and not so much Google.
I read through the entire thread but still not sure if I get this right:
Is this special license term I cited above only for installing Fairphone OS myself and I could thereby order a Fairphone and would not be āboundā to this term as long as I do not switch to Fairphone OS (but remove Google Services manually?)? As, to me it means Fairphone (respectively the OEM behind) can permanently disable my 500ā¬ phone whenever they want by disallowing me to use those, sadly neccessary, binary blobs.
Did you ever read EULAs from different manufacturers? Everybody reserves the right to withdraw the license. What they wonāt do, because it would render the product useless and land them in court, I could imagine. Same thing by the way if you buy DRM protected media. Here this happens all the time
I usually donāt buy any DRM protected media, so I never got in touch with such licenses I guess. 
I think they definitely would withdraw the license, else there would be no reason why they should add this paragraph to the license.
So this license is the same when I just buy a Fairphone but donāt change to Fairphone OS?
And really, how could I ever sue them if what they did is actually covered by a EULA i aggreed to. Not mentioning I might not be able to cover the financial risk of sueing a big company in another countryā¦
I would think that the license is in place, regardless of what (Fairphone provided) OS you have on your phone. But IANAL.
I donāt think they are planning to withdraw that license, as this template is in place in lots of comparable EULAs. They might get a too big a backlash doing this.
And yes, on person probably would not be able to sufficiently sue them, but then, many would be able (think Verbraucherschutz in Germany)ā¦
But still, I think this is very hypothetical, and yes, I donāt like that EULA not at all and maybe not fitting for a product of a company called āFairPhoneāā¦ But who knows what happened in the background to be able to use that particular hardware and software(-blobs)
It would be nice to know. Wasnāt one of the reasons for the whole FP project to get some more transparency into the inner dealings of the whole phone business? I think it would be interesting to understand where this text comes from. Because these licences also drive what kind of other hardware/software is chosen.
I still think this is a Google ācatch it allā text for ānothing is allowedā to make the different manufacturers happy and work together.
But does it make sense? No.
Iām still interested to figure out how Mozilla managed to get a bin-blob free build.