Wait a sec... "Instead of nitpicking, fix the apps so that they do not rely on anything outside what is covered within the promise and ECMA spec." - it's nitpicking to say JOB DONE in the case of the SPECIFICALLY NAMED APP?
Posted Jul 19, 2009 19:40 UTC (Sun) by rahulsundaram (subscriber, #21946)
[Link]
Fixing it one single app hardly solves the problem being mentioned. Tomboy is just one example and probably the smallest. The list is longer and includes other popular applications. Fix the rest of them and then say you have addressed the entire class of problems. In fact, Mono applications developers should have done this long back since it hardly the first time this problem is being raised. Till then, FSF's point remains valid.
The FSF warns (again) against Mono
Posted Jul 19, 2009 21:10 UTC (Sun) by directhex (subscriber, #58519)
[Link]
Which leaves only one real sticking point - ADO.NET, the System.Data namespace.
So. In your considered legal opinion, what needs to be done to make SQlite access "safe"? Which specific details of System.Data make it dangerous? What do apps need to do? Is renaming it to "Panda.Data" enough for all legal risk to suddenly vanish, in your mind? If not, what do you suggest instead?
The FSF warns (again) against Mono
Posted Jul 20, 2009 7:40 UTC (Mon) by rahulsundaram (subscriber, #21946)
[Link]
I suggest contacting SFLC if you must continue using Mono