On Thu, Oct 29, 2020, 10:48 PM Denis Cheremisov <[email protected]>
wrote:

> Well, as usual I wrote something in the way, not the real thing.
>
> The case is:
>
> - At my company we are using errgroup from that sync repo in one project,
>   sync/errgroup in fact mostly.
> - It proved to be error prone with its context shadowing on
> errgroup.WithContext
>   so we took the original and adds context in the group itself via
> eg.Ctx() +
>   a couple of additional functionality.
>
> Yesterday our attorney wrote us "we can't use sync because of this patents
> note" as it works like a virus, and can't use our modification too for the
> same
> reason. It turned out the stdlib is under the same note too, so we will
> have
> fun times :)
>


That makes no sense to me.  And I'm not aware of any other company that
sees any problem at all with the patent grant.

But I am not a lawyer, and you will have to make your own decisions.

Ian


четверг, 29 октября 2020 г. в 20:09:59 UTC+3, ohir:
>
>> Dnia 2020-10-29, o godz. 06:52:17
>> Denis Cheremisov <[email protected]> napisał(a):
>>
>> > Hi!
>> > At my job we found these additional patents
>> > limitatations https://github.com/golang/sync/blob/master/PATENTS
>> > They makes us impossible to use errgroup (which is, to say, turned to
>> have
>> > pretty poor choice of WithContext signature, so our one is different),
>> so
>> > we have our custom implementation of it with additonal functionality
>> > (errors collector, concurrency limitation), but it is derived from the
>> > original implementation.
>>
>> This list is not a proper venue to gather 'common-sense' legal advice, as
>> such
>> advice will likely be at odds with your real legal standing regarding
>> your software
>> under each next jurisdiction.
>>
>> To be clear and a bit assured about your real situation you should hire a
>> good attorneys
>> in each country of interest or hire a top-tier international law agency
>> then make sure to
>> be very frank with them about what you did, what you do, and what you
>> plan to do with
>> your implementation.
>>
>> Hope this helps,
>>
>> --
>> Wojciech S. Czarnecki
>> << ^oo^ >> OHIR-RIPE
>>
>> P.S. My "Common-sense" advice is this: as whole Go ecosystem is under
>> this grant,
>> if it is stands against your planned deeds, you certainly should abandon
>> Go right now
>> and switch to Java or Swift ASAP. There you'll be covered by Oracle's or
>> Apple's
>> voluminouos license agreements that will make the "very close to" problem
>> disappear, as it will be clearly forbidden ;).
>>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/1db53b86-32fd-4a43-9bf4-d39fde9ed96dn%40googlegroups.com
> <https://groups.google.com/d/msgid/golang-nuts/1db53b86-32fd-4a43-9bf4-d39fde9ed96dn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAOyqgcVZ33JoLE-8U%3DVhHX2LDQkYjkyEJreVrSs%2BptVxK2HC0g%40mail.gmail.com.

Reply via email to