PGP has failed to provide "encryption for the masses".

PGP fills a niche that OTR and Axolotl do not. It provides a bunch of operations that are not supported by OTR (anything that requires signatures that are verifiable by third parties). PGP is used by the masses (package signatures and similar functions), it's just that they don't use PGP for communication.

Try Phabricator (http://phabricator.org/), you can point it at a remote repository without hosting it.

> Phabricator is nice, but it's more of a full-featured replacement for GitHub as a whole. Some people want to keep most of GitHub and just improve on the code review aspects.

That's the nice thing about Phabricator, you can switch off all features you don't need, and it integrates with GitHub. You can definitely use it just for code reviews, with users logging in using their GitHub accounts and the repositories being hosted by GitHub.

> You can also deploy Review Ninja (and soon Reviewable) on-premises, though of course that means you're on the hook for administrating the system again.

That would work! Third party SaaS probably includes Github.

One of the nice things about Phabricator is its performance. It originated at Facebook, and they are using massive, monolithic monorepos.

This is exactly what the GPLv3 protects against.

Which government regulation overrides.

What does that even mean? If regulators say it's illegal to comply with the license terms, you can't use products released under those terms. It's not like the GPL'd components fall into the public domain.

There's a legal order of compliance. You don't get to break the law because you agree to a contract that stipulates you're going to break the law.

In this case, I bet the interpretation would be that if a piece of software requires you to break FCC law if sold as part of a Wifi router, then that software cannot be sold as part of a Wifi router.

Back to VxWorks in other words.

> It means you can't license the baseband under the GPL, nor release it the public

...within the jurisdiction of the US Government. Have a look at libdvdcss for guidance on how such a baseband might be developed and distributed.

It doesn't override anything, if vendors must lock down their firmware, then they cannot use GPLv3'd software.

In a clause is contrary to public policy, it may be unenforceable in that jurisdiction and thus they could use the code without violating the license. The unenforceable clause will be skipped over by the courts. It is a nullity.

IANAL, but GPLv3 requires software to be modifiable by an user.

> If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information.

However, it can be still followed by not letting even Wi-Fi router vendor update the firmware on a device.

> But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

Otherwise, you cannot provide the program at all. It's intentional, it's supposed to provide pressure on regulations like FCC regulations, at least in theory (vendors who already use GPLv3 software, could complain to FCC that they cannot use free software licensed under GPLv3).

> If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all.

Nope nope nope. My license can say "cannot distribute in places where law x exists." My license can say "no one can distribute. period."

No, they couldn't. The GPL is a grany of rights, not a restriction of them - if you can't fulfil the criteria then you do not get the grant, regardless of public policy.

While I agree with you, if they don't have to release it, you'll never know unless you can successfully decompile the firmware.

This could already be the case with closed source firmwares, which could be using unlicensed non-FOSS blobs too for all you know.

If we're ignoring licences now then this is a different argument.

Nope nope nope. Gpl is a binary decision whether you are in compliance and can distribute or not. So, in this case, it would be negative, not allowed to distribute. Unless the law requires someone to distribute gpl software, which it doesn't, there is no conflict here.

This is one of the finest pieces of open source software that I've ever seen. The documentation is very good and even succeeds at making LaTeX accessible to non-technical people.

I've been using it for years for pretty much everything that other people would use LibreOffice or Office for.

Not many pieces of OSS are on my list of "would continue to use even if all competing commercial offerings were open-sourced". LyX is on that list, beside Inkscape and Postgres.

Try DigiKam - it's open source and its photo management features work very well.

> Does anyone have a web or desktop alternative that supports tagging on individual and multiple photos?

DigiKam!

Fantastic feature set, but on Windows importing from USB cameras doesn't seem to work and it also isn't stable, so a deal breaker. As Picasa hasn't had any love in years, it's future demise was obvious, and my hope is that this creates a whole lot more attention for DigiKam on Windows as it seems to work well on Linux.

Thanks for the recommendation. Works well on both Windows and Linux. Problem solved!