You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our project rigorously enforces code quality using `ruff`. The definitive configuration (including line length, target version, and active rule sets) is maintained centrally in `pyproject.toml`. Please refer to the `[tool.ruff.lint]` section in that file for the current active and ignored rules.
313
311
314
312
### Pre-commit Hooks
315
313
@@ -372,7 +370,7 @@ Use conventional commits:
372
370
LinkForge uses **Release Please** to automate versioning and changelogs.
373
371
374
372
1.**Automation**: When code is merged into `main`, Release Please will automatically create (or update) a "Release PR".
375
-
2.**Versioning**: This PR will contain a version bump in `blender_manifest.toml`, `CITATION.cff`, and an updated `CHANGELOG.md` based on your commit messages.
373
+
2.**Versioning**: This PR will contain a version bump in `pyproject.toml`, `blender_manifest.toml`, `CITATION.cff`, and an updated `CHANGELOG.md` based on your commit messages.
376
374
3.**Merging**: Once a maintainer merges this Release PR, a GitHub Tag and Release are automatically created.
377
375
4.**Distribution**: The `release-please.yml` workflow will then build the extension `.zip` and attach it to the GitHub Release.
378
376
@@ -392,7 +390,7 @@ To maintain LinkForge's status as a professional-grade **Linter & Bridge**, we p
392
390
393
391
### 1. The Blender Bridge (Foundation)
394
392
LinkForge must remain compatible with the latest Blender LTS (Long Term Support) and the current stable release.
395
-
-**Vigilance**: When a new Blender version (e.g., 5.0) enters Beta, we prioritize testing our `export_ops.py` to ensure no API breaking changes affect our users.
393
+
-**Vigilance**: When a new Blender version (e.g., 6.0) enters Beta, we prioritize testing our Blender integration to ensure no API breaking changes affect our users.
396
394
397
395
### 2. URDF/XACRO Fidelity (Core)
398
396
Our primary goal is 100% compliance with official specifications.
@@ -459,6 +457,8 @@ If you've contributed (code, docs, ideas, etc.), you can ask the bot to add you
459
457
Replace `<contribution-type>` with one of the [valid contribution types](https://allcontributors.org/docs/en/emoji-key) (e.g., `code`, `doc`, `bug`, etc.).
460
458
461
459
### Academic Recognition
462
-
For significant core contributions (new sensor systems, physics engine refinements, major architectural changes), we may invite you to be listed as a co-author in the `CITATION.cff` file and the official documentation, ensuring your work is properly attributed in academic research using LinkForge.
460
+
For profound core contributions (e.g., advanced mathematical noise models, novel simulator integrations, or deep physics engine refinements), we may invite you to be listed as a co-author in the `CITATION.cff` file and the official documentation. This ensures your high-level domain expertise is properly attributed in future academic research using LinkForge.
461
+
462
+
*(Note: Standard features, basic sensor additions, and bug fixes are highly valued and will be celebrated via our standard Open Source contributors framework, but they do not automatically qualify for academic co-authorship).*
For a deep dive into our long-term strategy, the **Digital Twin** philosophy, and our technical roadmap for AI and Kinematics, please read our [Project Vision](VISION.md).
192
-
193
162
## 🤝 Contributing
194
163
195
164
We welcome contributions! LinkForge is a community-driven project.
- 🏗️ Check our [Architecture](ARCHITECTURE.md) to understand the internals.
198
167
- 💬 Join the conversation on [GitHub Discussions](https://github.com/arounamounchili/linkforge/discussions).
199
168
169
+
## 📝 Citing LinkForge
170
+
171
+
If you use LinkForge in academic research, please cite it using the provided `CITATION.cff` file. You can find the citation format in the "Cite this repository" button on GitHub's sidebar.
172
+
200
173
## 📄 License
201
174
202
175
LinkForge follows a **Split-License Model** designed for both community-driven innovation and industrial-scale integration:
0 commit comments