This section is not legal advice (legal advice comes from your counsel).
This section is intended to help you as you consider using Featherweight: Application Framework for LabVIEW™ code,
or referencing the documentation in
Using the Framework
The code itself aims to be as accessible as possible, both for
learning and enterprise, to promote the success of applications
designed and developed using graphical programming.
For this reason, the MIT license below was chosen at the time of
writing for best suiting these goals and being widely recognized
and accepted: [#featherweight-framework-license]
Bottom line: it’s likely OK for you to use the code for your application, even
as a proprietary fork or for-profit business endeavor, and you only must
include with your distributable the original license: [#featherweight-framework-license]
Ask your counsel if you are unsure or have additional questions.
Referencing the Documentation
The online documentation and ideas expressed on this site have a
different license than the codebase: [#ftw-docs-license]
The spirit is to allow contributors to Featherweight to retain
individual attribution to neat ideas while still freely contributing.
If you are preparing a presentation or writing a forum response, it is
sufficient attribution to provide a fully-qualified URL and anchored
link to the referenced documentation. You might consider crediting
the authors by name where appropriate.
When referencing content, one is encouraged to provide a direct URI
to the original documentation (either online, or a URI to an offline
clone of the repository) rather than copy-and-pasting portions.
Redistribution of Documentation
Extensive adoption (beyond a just few references) for closed-source business
use is against the spirit of the documentation license. Examples of prohibited
redistribution include but are not limited to:
forking the documentation or site for internal use
creating for-profit, closed-source training material or courses based on FTW documentation
If you create something using Featherweight, then give that thing to
somebody, give them this license at the same time: [#ftw-framework-license]
Include the license as appropriate to your distributable and accessible
to the end-user, such as inside a /legal or /licenses directory
alongside the distributable, or as text in an “About” dialogue.
It is permissible to modify CRLF whitespace to fit word-wrapping boundaries
of text containers, but the license must remain otherwise unmodified.
This website is based on the generous and most excellent work of
the people who made Jekyll.
Featherweight has no connection to National Instruments, owner of
the NI LabVIEW™ trademark, and many worldwide patents on their
contributions to graphical programming.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the “Software”), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN