Was a failure to stop what happened, no doubt about that.
No need to move to a proprietary hosting service like Github.
I wrote about this previously: http://www.fsf.org/blogs/community/savannah
The new GnuPG website will bring bullet-proof privacy to the general public, provide a friendly face of Free Software cryptography, and allow the project to sustainably fund maintenance and development into the future. The new GnuPG.org will be mobile and desktop ready with a fresh design, built for internationalisation, provide non-technical guidance for new users, and have built in management for future subscription donations."
Link to Original Source
Link to Original Source
They've done dozens of events at Apple Stores, including the huge Apple store about 100 metres from this Microsoft store.
"free enough to be distributed with the Linux kernel sources"
the firmware files are typically under a license that prohibits modification and even redistribution.
> A desktop os needs a browser (Firefox), text editor (vim), office suite (OpenOffice), PDF reader (evince), window manager (kde), etc
Browser: GNU Icecat, text editor: emacs, office suite: GNOME Office, PDF reader: GNU PDF, window manager: GNOME.
I found its actually hard to get a machine that's decent these days, unless you're prepared to put up with a bit of crap.
The solution is to build your own custom laptop -- http://www.avadirect.com/gaming-laptop-configurator.asp?PRID=25095
If you go for the "VISIONTEK Killer" wireless card, it has an Atheros chipset, so you can distro-hop to your hearts content. They also ship it with no OS if you like.
Rip it all and then use something like beats to figure out the audio fingerprinting and correctly tag things for you.
If you press stop twice, then hit play, you can generally skip that stuff.
Thanks for the breakdown on work for hire -- and I 100% agree, regarding hiring a lawyer to look at contracts.
(background: I've been freelancing for about twelve years, with several engagements that have resulted in open source contributions)
If you're freelancing, the general rule is that the customer owns everything you produce within the scope of the contract. This means you do not own the copyright, and therefore you can't open source the code. The specific phrase you look for in your contracts is "work for hire"
It's very difficult to get around that rule, or to outline specific exceptions ahead of time -- but you can change the incentives to encourage your client to contribute code to the open source community.
I offer to reduce my rates for any work we mutually agree to release as open source. I benefit by getting my name and work in broader distribution, my clients benefit by paying less for the work, and the open source world grows a little bit. It's a reasonable trade off for all parties, and even if most clients don't exercise that option, they appreciate the spirit of such an offer.
Where it gets hairy is when you're making changes to code that has been open sourced under a "viral" license, like the GPL. If that is the case, then you should inform your client that they are bound by the terms of that license -- that those changes *necessarily* become open source. Keep a copy of those emails. If your client decides that they're going to skip out on that obligation, you'll want to make sure your ass is covered if/when your client gets in trouble