DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

DQMH License Term

Solved!
Go to solution

Hi,

 

I have been google searching this morning to try and find any information on the License terms for using DQMH, I know it is freely provided and supported, but I assume there is some form of GNU License or equivalent somewhere ?

 

cheers 

 

Danny 

Danny Thomson AshVire Ltd
0 Kudos
Message 1 of 11
(3,134 Views)
Solution
Accepted by topic author danny_t

Go to VIPM, select DQMH from the list, and then select License Agreement:

 

Ozfarmboy_0-1632219591278.png

 

 

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

Message 2 of 11
(3,130 Views)

Yep obvious, why did I forget that 🤔, thank you

Danny Thomson AshVire Ltd
0 Kudos
Message 3 of 11
(3,124 Views)

Yep!  Although the vipm.io page says License "Not Specified":

 

DQMH Toolkit for LabVIEW - Download - VIPM by JKI

 

That should probably have the license info in there @Joerg!

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

0 Kudos
Message 4 of 11
(3,116 Views)

@ChrisFarmerWIS wrote:

Yep!  Although the vipm.io page says License "Not Specified":

That should probably have the license info in there @Joerg


Thanks for pointing that out!

 

Seeing as DQMH's license is not one of the generic open-source licenses (like BSD etc.), that field probably won't have much use - but it still should not say "not specified".

 

I can't edit the value directly via the web interface, so I'll have to check with the VIPM team. 




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )


0 Kudos
Message 5 of 11
(3,083 Views)

I'll second that it would be nice to have the license text available somewhere without having to start the package installation process. Even if it's just a small link in the footer of the dqmh.org website

--------------------------------------
Message 6 of 11
(2,995 Views)

I've added the license agreement to the wiki while we're working on a more permanent solution for both vipm.io and DQMH.org.




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )


0 Kudos
Message 7 of 11
(2,981 Views)

The license is now linked to both on vipm.io and DQMH.org (in the "Install" section).




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )


0 Kudos
Message 8 of 11
(2,970 Views)

Hello everyone,

 

I have a very basic question: I am developing an application to perform automated testing using teststand. The main VI (i.e. the only application the operator will actually run) is not implemented using DQMH, but I would like to implement several modules as DQMH (DAQ-Module, single test control, ...).

 

Is it enough to mention the use of DQMH in the documentation/about window of the main application (which is not dqmh-based)? (many submodules are headless, so there won't be any interface for the user to see an "about" section)

 

Thank you in advance,

Juan

0 Kudos
Message 9 of 11
(194 Views)

Hi Juan,

 

We have provided the following VIs on the function palette:

FabiolaDelaCueva_0-1736895130996.png

If you place the About DQMH VI on your block diagram and run it, you will see that it displays the text that the other three VIs provide: DQMH Version, DQMH Legal information, and the DQMH End User License Agreement URL. 

 

You can use the About DQMH VI as is, or save it and make your own version with other information relevant to your application and use it as the About VI for your application. Or if you already have an About VI, call in that VI the DQMH Legal Info and DQMH EULA URL and you will be complying with the license.

 

You don't need an about section per DQMH module in your project, just an acknowledgment that your application is using DQMH.

 

Thanks for your interest in DQMH and your trust in us.

 

Happy wiring,

Fab

For an opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
Check out DSH Pragmatic Software Development Workshop!

DQMH Lead Architect * DQMH Trusted Advisor * Certified LabVIEW Architect * Certified LabVIEW Embedded Developer * Certified Professional Instructor * LabVIEW Champion * Code Janitor

Have you been nice to future you?
0 Kudos
Message 10 of 11
(156 Views)