2,244 karma · joined April 25, 2012
Catch you next time.
It's great to see Stoke-on-Trent represented in the startup arena.
As I'm really keen to see more local jobs and affluence, my comment would be, there's nothing about how the project will be sustained financially, no payment plans or premium support.
Look forward to seeing more about this at Staffs Web Meetup.
By essentially saying that, if you don't use cloud technology your precious photos and documents might be unaccessible in years to come.
It sounds like you need to manage them by breaking their tasks down into more bite sized chunks if you don't want them to go off task.
I'm aware that they are possible, but they appear to be unlikely, especially when using md5 correctly, even then most people have already migrated to sha1 or sha256...
It seems to read that he is basically going around systematically "upsetting the applecart".
Now, whether he's doing that technically or otherwise, it's still having an effect on the ecosystem. You can't detach yourself from that.
https://en.wikipedia.org/wiki/Lennart_Poettering#Controversi...
"The "Poettering effect" is now sometimes used as a negative term for presumed damage his mindset is doing to opensource communities."
https://groups.google.com/forum/#!msg/comp.sys.raspberry-pi/...
I guess there's two sides to every story...
What a strange situation.
When you're weighing up what to implement, it certainly helps when there is an agreed upon technical specification.
https://translate.google.com/#auto/fr/a%20great%20man a great man => un grand homme
https://translate.google.com/#auto/fr/a%20tall%20man a tall man => un grand homme
In both of these examples, the ordering is the same as English.
So yes by that logic, you're right, French is equal to or worse than English.
For example, “Black box”:
In French this would be called a “boîte noire” or literally a “box black”. This seems more logical as first you identify that it is a box you are looking for, secondly that it is black.
Try 2014->08->2014-08-06.md
So I ask, what big problem does this solve?
It all comes down to semantics of what linking means. The PHP license is pretty much identical to the Apache license and you could indeed make a case for not allowing any GPL'ed software to be "linked to" from Apache either.
See http://www.apache.org/licenses/LICENSE-1.1.
The PHP license was chosen to match the Apache license because Apache and PHP are tied so closely to each other.
This hair splitting over linking, derivation and aggregation has been going on since the beginning of time. My stance is that you can indeed ship PHP licensed PEAR components on the same cd or in the same tarball as GPL'ed code because I see it as an aggregate work. This changes if you take PEAR code, modify it and copy-paste it directly into your own work. Then it moves from aggregate to derived. But the intent of the PEAR components is to be used in aggregate form. The PHP license allows you to use it in derived form as well, of course, but then you should be choosing a license other than the GPL for the derived work.
The FSF has a FAQ on aggregation here: http://www.fsf.org/licensing/licenses/gpl-faq.html#MereAggre...
That text is heavily biased towards compiled software and they talk about executables and memory spaces which don't really apply in this case. If you don't consider using a PEAR component as aggregation then it logically follows that you also cannot have Apache call your code so you will have to stipulate that nobody can use your code from Apache. I think this is an extreme interpretation that pretty much nobody out there shares.
In short, I don't see an issue here. Move along.
For PECL extensions that are linked into PHP, the license must be compatible with the PHP license. That means you can not GPL a PECL extension or you would be violating the GPL. Note also that if you write an extension that links against a GPL'ed library you will be violating the GPL. If you need to link against a GPL'ed library, get permission from the author of the library to use the library under a compatible license.
The license of any PEAR/PECL package can be found in the head of all source code files, inside the <license> tag of the package description file (package.xml) and also on the package homepage.
http://wayback.archive.org/web/20120522154154/http://archive...
The outgoing or upload are nouns that don't mean share either.
The Google Android - three dots approach seems to be the simplest, most logical, where one becomes two (or more).