Inquiry Regarding Source Code Disclosure Requirements Under the AGPL for OpenMVS

[Matsuda，Takuya (HCM) / 松田卓弥]

Dear OpenMVS Team,

I hope this message finds you well.
We are writing to inquire about the required scope of source code disclosure under the AGPL license when using OpenMVS in our Android application.

We plan to use OpenMVS in an Android application.
I am contacting you to confirm the scope of the OpenMVS source code disclosure under the AGPL.
We are preparing to release our source code in accordance with the AGPL.
The source code we plan to release is summarized below:
- All OpenMVS source code
- Source code for C++ libraries other than OpenMVS used in the Android application
- Source code for the Android application itself

We also plan to make it possible to call the above application from another application using Android Intents.
In this case, we believe that the calling application will not be obligated to disclose its source code under the AGPL.
Is the scope of the source code we will release sufficient?

We look forward to your reply.

Regards,
************************************************************************
Takuya Matsuda
IoT Business Development Sec.
ConSite Development Promotion Dept.
?
Hitachi Construction Machinery Co.,Ltd.
************************************************************************

[cDc Seacave]

Dear Mr. Matsuda,

Thank you for your interest and for outlining your intended usage of OpenMVS.

Please note that I am not a legal or licensing expert, and therefore I cannot provide an authoritative interpretation of the AGPL license. That said, based on your explanation, I understand the proposed plan and approach as you described it, and I agree with it.

From my perspective, the scope of source code disclosure you outlined appears reasonable and consistent with my intended use of OpenMVS. I have no objections to the license being applied and complied with in the manner you proposed, including your understanding regarding the use of Android Intents and the separation of the calling application.

I do not foresee raising any objections related to licensing, provided that OpenMVS is used and distributed as described in your message and in accordance with the AGPL.

Kind regards,

Dan

--
You received this message because you are subscribed to the Google Groups "openMVS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openmvs+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/openmvs/TY4PR01MB12765AB2DD8135CF8E787727B8591A%40TY4PR01MB12765.jpnprd01.prod.outlook.com.

[Matsuda，Takuya (HCM) / 松田卓弥]

Dear Mr.Dan

 

Thank you for your quick response and for sharing your thoughts on the OpenMVS license.

Your comments were extremely helpful to our team.

We will continue to develop our app while ensuring compliance with the AGPL license.

 

Regards,

************************************************************************

Takuya Matsuda

IoT Business Development Sec.

ConSite Development Promotion Dept.

 

Hitachi Construction Machinery Co.,Ltd.

************************************************************************

[cDc Seacave]

Pls send me a link to the new app when it is released!

Good luck!

PS: if you need new functionality or customization for the library, I could allocate some time and help