sldkit 0.2.0__tar.gz

sldkit-0.2.0/CLA.md

@@ -0,0 +1,51 @@
+# sldkit Contributor License Agreement
+
+Version 1.0, 2026-09-16. Recipient: **UnRobotics Inc.** (the Company).
+
+This agreement applies only to contributions identified in your explicit
+acceptance record. Merely using the software, reporting a problem or opening a
+pull request does not constitute acceptance. The acceptance process is in
+[CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Your contribution and authority
+
+You are the individual or legal entity identified in the acceptance record.
+The Contribution consists of the code, documentation or other original material
+you identify and intentionally submit for inclusion in sldkit.
+
+You confirm that you own the rights you grant, or are authorized by their owner
+to grant them. When an employer or another entity holds those rights, your
+acceptance must identify that entity and your authority to act for it. Disclose
+third-party material and its applicable terms; this agreement does not grant
+rights to someone else's material that you cannot license.
+
+## Copyright grant
+
+You retain ownership of your Contribution. You grant the Company a perpetual,
+worldwide, nonexclusive, royalty-free, irrevocable copyright license to use,
+copy, modify, prepare derivative works from, display, perform and distribute
+the Contribution in source and other forms, and to sublicense those rights.
+This includes licensing it under PolyForm Noncommercial and under separate
+commercial terms, and charging for commercial licenses.
+
+## Patent grant
+
+You grant the Company and recipients of software it distributes a perpetual,
+worldwide, nonexclusive, royalty-free patent license to make, have made, use,
+offer for sale, sell and import your Contribution, with rights to sublicense.
+This grant covers only patent claims you can license that are necessarily
+infringed by your Contribution alone or by its combination with the sldkit
+version to which you submitted it. It does not cover unrelated combinations.
+
+## Scope and assurances
+
+No copyright assignment, exclusive rights, trademark rights, employment
+relationship, obligation to pay you, or obligation to accept your Contribution
+is created by this agreement. You may continue using and licensing your work.
+The Company may distribute the Contribution under different licenses without
+requiring a further signature for each distribution.
+
+Apart from your statements about authority and third-party material above, you
+provide the Contribution as is, without warranties to the extent permitted by
+law. You have no obligation to provide maintenance or support. Notify the
+Company if you discover that the rights information you supplied was incorrect.

sldkit-0.2.0/COMMERCIAL-LICENSE.md

@@ -0,0 +1,83 @@
+# Commercial licensing
+
+This document describes available licensing arrangements. **It does not grant
+any license.** Rights arise only under a written agreement accepted by
+UnRobotics Inc. and the customer, subject to that agreement's payment terms.
+
+The licensor and commercial contracting entity is **UnRobotics Inc.**
+Use the [commercial contact form](https://www.un-robotics.com/#contact) to
+describe your organization, application, target platforms and distribution needs.
+
+## Plans
+
+| Plan | Intended scope | Pricing basis |
+| --- | --- | --- |
+| Internal | A named legal entity's internal business use, applications, development, modification, testing, CI and backups | Annual fee per legal entity |
+| OEM | Internal rights for that entity, plus integration into a named product, distribution of its runtime and end-user execution rights | Annual base fee per product and agreed distribution band |
+
+Affiliates and additional products must be named in the agreement. Contractors
+may act for the licensed entity under the agreed conditions. Internal includes
+human-operated contract analysis that delivers outputs only;
+delivering executable software requires OEM scope or an agreed redistribution
+addendum. Customer-operated hosted
+services or APIs require a SaaS addendum.
+
+An OEM runtime can include the native extension, required Python modules and
+viewer assets. End users need not purchase individual licenses from us when
+their execution rights are covered by the OEM agreement. Providing a development
+SDK for other organizations to build and redistribute their own products
+requires an SDK redistribution addendum; ordinary OEM execution rights do not
+include that grant. SaaS and further sublicensing are agreed separately.
+
+## Standalone HTML viewers and data outputs
+
+`sldkit view` embeds executable viewer code and Three.js alongside the user's
+data in one HTML file. Internal covers generation and viewing within the
+licensed entity. Business delivery of executable HTML outside that entity
+requires OEM scope or a viewer-output addendum specifying redistribution and
+recipient execution rights. This does not restrict distribution or use already
+permitted by PolyForm, earlier MIT permissions or third-party licenses.
+Preserve the accompanying notices when redistributing viewer code.
+
+We claim no additional ownership or output-based royalties in extracted JSON,
+properties, images or geometry data. Embedding data in an HTML viewer does not
+change ownership of that data; the bundled software retains its own terms.
+
+## Term, evaluation and support
+
+The standard commercial term is 12 months; prices are quoted individually.
+OEM includes Internal use for the same entity, without a second Internal fee.
+An Internal-to-OEM upgrade credits the remaining Internal term as specified in
+the quotation. We do not meter parsed files or require online activation.
+
+Internal and SaaS commercial use ends at expiry unless renewed or separately
+licensed. OEM end users may continue running products lawfully distributed
+during the term. New shipments and update distribution end at expiry unless
+the agreement grants surviving maintenance distribution rights. Fixed-version
+perpetual use and long-term runtime distribution are separately quoted.
+
+Companies can request a separate, normally free 30-day evaluation license
+before evaluation begins. It covers internal feasibility testing, not production
+or customer delivery. Downloading the public package does not create that
+evaluation license or an automatic commercial trial.
+
+Standard updates and ordinary technical inquiries are included as agreed.
+Custom format support, customer-specific fixes, response-time commitments and
+vendor-system validation require separate scope and fees. Validate representative
+files against the [supported profiles](docs/compatibility.md) before contracting;
+payment does not imply support for all SolidWorks files, complete geometry, feature history or
+drawing rendering.
+
+## Independent rights
+
+The agreement covers only rights the licensor can grant. Third-party conditions
+and existing MIT permissions remain in effect, including after expiry of a
+commercial agreement. Customers retain their rights in their data and outputs;
+we do not claim additional ownership or output-based royalties in converted
+geometry data, images or extracted properties. Rights in the input data and any
+third-party material remain the customer's responsibility.
+
+Use already permitted by the [PolyForm terms](LICENSES/PolyForm-Noncommercial-1.0.0.md)
+does not require a commercial contract. This document does not narrow those
+permissions. The signed agreement defines the precise scope, fees, warranties,
+liability limits, termination provisions and governing law.

sldkit-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Contributing
+
+Read the [development instructions](README.md#development), [parser provenance](docs/parser-provenance.md)
+and [supported scope](docs/compatibility.md).
+Keep changes bounded, preserve source values and include evidence for newly
+supported file profiles. Update both language versions of the licensing documentation together. Do not submit confidential CAD files or samples without redistribution
+permission.
+
+## Contribution licensing
+
+sldkit offers new material under PolyForm Noncommercial 1.0.0 and separate
+commercial agreements with UnRobotics Inc. To allow both forms of distribution,
+new external code and documentation contributions require explicit acceptance
+of [CLA version 1.0](CLA.md). Contributors retain copyright; the agreement grants
+nonexclusive rights including commercial sublicensing and specified patents.
+This does not retroactively change earlier MIT contributions.
+
+On the pull request, identify the contribution and post the following acceptance
+statement, filling in the identity and scope. Reference the immutable Git
+revision of CLA.md that you reviewed, not just a moving branch URL:
+
+> I accept the sldkit Contributor License Agreement version 1.0 at
+> [full commit SHA / immutable CLA URL] for my contributions in [PR and commit
+> range]. I am [individual or legal entity], and I have authority to grant the
+> rights stated in that agreement. Third-party material: [none, or list and terms].
+
+If your employer or another entity owns the contribution, obtain authorized
+acceptance on behalf of that entity. Contact
+[UnRobotics Inc.](https://www.un-robotics.com/#contact) for a private signature
+record rather than posting personal addresses or confidential documents.
+
+Maintainers must verify acceptance before merging an external contribution.
+Record the contributor/entity, authority, covered commits, CLA revision,
+acceptance date and link or private record reference. If a PR gains contributions
+from another rights holder, obtain their acceptance as well. This is a manual
+review requirement; no CLA bot is currently configured. A DCO sign-off alone
+does not record acceptance of this agreement.
+
+Issue reports and suggestions do not require the CLA unless they include
+material proposed for incorporation that requires a license grant.
+
+## License and packaging changes
+
+Preserve earlier MIT and third-party notices. After changing legal files, run
+`python scripts/sync_license_notices.py`, then rebuild the viewer with
+`npm run build --prefix viewer`. Check `python scripts/check_license.py` and
+the [distribution gates](docs/releasing.md). Generated Rust and viewer notices
+must match the canonical files; do not edit those copies by hand.