Collaboration with upstream FreeCAD

As a company that creates added value for FreeCAD users, we are committed to staying a positive force in the FreeCAD ecosystem and thus being true to our values. This puts a number or requirements on our operation. Here is how we comply with those requirements.

1. The company should be contributing their changes back to the upstream project.

Over the course of v0.21 development cycle, Ondsel submitted over 20 pull requests, all were merged by respective maintainers after code review. For v1.0, Ondsel has already contributed an integrated assembly workbench (work in progress) and a kinematic solver, as well as various quality-of-life improvements.

2. The company shouldn't get a special treatment when contributing to FreeCAD.

Patches by Ondsel land into the same pull request queue as patches by other contributors. These patches go through the same review process and, after further improvements where applicable, are merged by respective maintainers who are not Ondsel employees. The only patches that the Ondsel team merges are the ones for the Path workbench where Brad Collette is the maintainer.

3. None of the Ondsel employees should have a conflict of interest between Ondsel, FreeCAD, and the FreeCAD Project Association.

Multiple Ondsel employees are FreeCAD developers. However only one Ondsel employee, Brad Collette, is also a FreeCAD maintainer and a board member of the FreeCAD Project Association. While he has voting rights in the FPA, he represents a minority whose voting can be easily overturned. As a FreeCAD maintainer, he provides code review for patches outside of his personal scope of interest, but ultimately only merges patches to the Path workbench.

4. Ondsel shouldn't be able to make unilateral decisions on the rules of participation at the FreeCAD project.

While the initial revision of CONTRIBUTING.md comes from Brad Collette, that document was created prior to launching Ondsel and receieved further revisions from contributors who are not Ondsel employees.