We're a developer group that is now writing a server library. We plan to use it for commercial projects by putting all the code into the library and creating a thin proprietary wrapper to keep clients happy.

It's a strategic move to use the LGPL, as if we used GPL then we'd have to sell proprietary licenses. Proprietary people would choose to either:

• Re-implement their own closed-source version of the software.
• Buy a proprietary license from us and then not make the changes public.

This way (by using LGPL) we get to extract as much free source-code from them as possible.

The problem now comes with the fact that our library can be used for web services. People could make changes to our library, use them in their commercial service and not make changes public.

I was searching the net and found these links:

http://stackoverflow.com/questions/731246/lgpl-for-php-applications http://mohammed.morsi.org/blog/?q=node/270

The 2nd link claims you can just include an affero clause in the LGPLv3? What is your word on this?

Many thanks to the FSF. I love your work.

Bitcoins are not money.

You can fill up the gas tank in about a minute. You cant really do that with a battery pack.

That's 1 million USD split 75 ways for roughly 4 months of work.

Congratulations you're making $50/hour.

Does Strain 121 survive outside of extreme heat?

Is that a joke? How is the state government requiring businesses licensed in the state to do something like this unconstitutional?

They dont need to last for 12 hours, just long enough to make the transition to grid power.

Solar power is a perfect match for data centers. Their power demand is basically constant and they already have large batteries on site. So the main drawback of solar power isn't a problem for them (mostly).

NTFS is only writable on linux though NTFS-3G, the write support in the kernel only works if the file size doesn't change.

You'd run this in a project directory which you have built from source, try it.

That will tell you the packages for which an already build (in the current directory) depends as configured. The step of generating the ebuild is trivial from there.

And in case anybody doubts the lameness of this specific project, behold

find . -type f -executable -exec ldd {} \; | grep -vF "not a dynamic executable" | cut -f 1 -d " " | xargs equery belongs

can i haz stipend?

For example this one is lame

ldd + equery belongs and some bash glue would do that.

http://en.wikipedia.org/wiki/Jevons_paradox something most people spouting off about efficiency dont understand, congratulations on being smarter than those people.

Didn't you get the memo? Racism is O.K. as long as you're not white.