On 3/21/18 6:59 PM, Victor Manuel Romero Rodriguez wrote:
> Hi Myrle,
>
> Thank you for your response. I'm looking for information too, and
> I would like to contribute in this point, right now customers in
> Mexico, which are now looking at the OSS projects like Fineract
> have this questions and if we can help, would be great.
>
> I will come back with our 2 bucks.

Thanks, Victor!

Good places to start looking are [1] and  the page you posted below [2].

IANAL, but I think the key thing to determine first is does Fineract
include any crypto code of its own or bundle any third party
libraries including crypto?  If so, we need to follow the process
described in [1].

Does anyone know if fineract sources include crypto code or if there
is any bundled dependency that includes this?

If you have questions about what counts as crypto, etc, you can
subscribe and post questions to [3]

Phil
[1] http://www.apache.org/dev/crypto.html
[2] http://www.apache.org/licenses/exports/
[3] http://www.apache.org/foundation/mailinglists.html#foundation-legal


>
> Victor
>
>
> El 21/03/18 a las 01:31, Myrle Krantz escribió:
>> Hi Victor,
>>
>> To my knowledge, no committer or contributor has tried to figure
>> out what
>> we need to do here. If you want to step in here, your
>> contributions are
>> welcome!
>>
>> I’m not sure how to find out the next steps, but I’d start by
>> searching
>> through the mailing lists of projects that are in the incubator
>> and on the
>> list you sent us.
>>
>> Best Regards,
>> Myrle
>>
>> On Tue 20. Mar 2018 at 20:36 Victor Manuel Romero Rodriguez <
>> [email protected]> wrote:
>>
>>> Hello Fineract Team,
>>>
>>> Recently in Mexico as part of the FinTECH regulations our
>>> customers ask
>>> us about the licenses I have the link of ASF about export
>>> licenses, but
>>> I am unable to locate Fineract
>>>
>>> http://www.apache.org/licenses/exports/
>>>
>>> Is there any link/information related to the Export Authorization
>>> License/compliance of Apache Fineract ?
>>>
>>> Regards
>>>
>>> Victor
>>>
>
>

Reply via email to