Translate

docs/0.3/general/licensing
I mentioned earlier, that there is application specific data in form of code and in form of data. These two cases have to be distinguished:
SourceTranslationState
527
To tell BOLTS about this and things like the available selection of locations
available. This is done by a additional field in the base file. The entries are
selfexplanatory, so here is the content of the base file with the connector
infos:
528
This is a good time to test again. You can use the utility script like shown
[earlier]({{ doc(openscad,basemodule) }}). Make sure all
connectors are where they should be and that this remains the case when you use
a range of parameters.
529
The final thing to do is create drawings for the connectors to visually show
their location for easy reference. The utility script can do most of the heavy
lifting, by creating OpenSCAD scripts for each location that shows the part
together with the connector there.
530
You might want to [contribute]({{ doc(general,development) }}) this
part to BOLTS, so that every user can profit from your efforts.
531
* the backend specific data is specific to the CAD application (FreeCAD or OpenSCAD at the moment), and can come in two forms: as code (OpenSCAD modules or FreeCAD python functions) or as data (stl files for OpenSCAD or fcstd files for FreeCAD. Its license is chosen by the creator.
532
I mentioned earlier, that there is application specific data in form of code and in form of data. These two cases have to be distinguished:
533
#### Backend specific data in form of data
534
In this case on has to consider the final design as a combined work between the part (in form of a FreeCAD fcstd file or a STL file) and the rest of the design that the user created. If the BOLTS part were licensed under a fairly restrictive license like GPL, the whole design would need to be licensed under the GPL.
535
As this is undesireable, BOLTS must not contain backend specific data in form of data that causes such restrictions. This means, that such data must be placed in the public domain, or better yet, the author must waive all rights on this content using [CC0](http://creativecommons.org/about/cc0). The latter is a legally more sound procedure, as the public domain is a legal concept that does not exist in all legislations.
536

537
One can also regenerate the HTML output, which is useful when creating drawings
or adding new collections

Loading…

Glossary

Source Translation
No related strings were found in the glossary.

Source information

Comments
docs/0.3/general/licensing
Source string age
3 years ago
Translation file
translations/fr/LC_MESSAGES/docs.po, translation unit 532
String priority
Medium