A specific case: when I worked at Adobe, we could not use any open source
library whose license was not one of a standard set of pre-approved licenses.
During a license audit (oh joy!) I had to approach a couple of OSS projects we
had started to use in order to persuade them to change their lice
I've never seen synthread. I'll investigate in probably a few days.
On Sat, May 3, 2014 at 9:52 AM, Jozef Wagner wrote:
> Thanks for releasing this library. How does it compare to the synthread
> library [1] [2] ? Seems like both libraries have the same goal.
>
> Jozef
>
> [1] https://github.c
Thanks for releasing this library. How does it compare to the synthread
library [1] [2] ? Seems like both libraries have the same goal.
Jozef
[1] https://github.com/LonoCloud/synthread
[2] http://www.infoq.com/presentations/Macros-Monads
--
You received this message because you are subscribed
Some software companies, particularly larger ones, are careful about the
licenses of software they use in their products. With a standard open
source license it's often easy to get approval, because licenses like MIT
are very common.
Software with a custom license is trickier, because it's not a c
Hi!
I'm pretty familiar with legal license stuff (though IANAL). I wouldn't
mind considering changing it at the point where someone wants to use it but
can't - because that would carry with it a specific reason we can think
about.
-Jason
On Fri, May 2, 2014 at 3:03 PM, James Reeves wrote:
>
The non-standard license might make using this library difficult to use for
some companies. You may want to consider using an existing open source
license that's broadly similar, such as MIT.
- James
On 2 May 2014 09:00, Fabien Todescato wrote:
> Thanks for that great work ! Reminds me of simi
Thanks for that great work ! Reminds me of similar techniques in the
context of logic programming : http://www.info.ucl.ac.be/~pvr/edcg.html :)
>
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegro
