Add reports for various projects

reports/improve-c++-api-docs/pieterhijma-2025-08.md

@@ -0,0 +1,4 @@
+## Summary of Activities - Improve C++ API Documentation - August 2025
+
+This project did not have activity due to holidays and a feature deadline for
+the new release.

reports/improve-c++-api-docs/pieterhijma-2025-09.md

@@ -0,0 +1,4 @@
+## Summary of Activities - Improve C++ API Documentation - September 2025
+
+This project did not have activity due to the feature freeze for
+the new release.

reports/improve-c++-api-docs/pieterhijma-2025-10.md

@@ -0,0 +1,41 @@
+## Summary of Activities - Improve C++ API Documentation - October 2025
+
+I picked up on this project after finishing the Improve UX VarSet project.
+Last progress on this project was halted on a [discussion on how to approach
+the
+documentation](https://github.com/FreeCAD/FreeCAD/pull/21494#issuecomment-2909471139).
+The discussion happened on Discord and after reviewing this discussion again, I
+came to the compromise in [this
+comment](https://github.com/FreeCAD/FreeCAD/pull/21494#issuecomment-3397022581)
+that was accepted.  This means that the [alternative
+PR](https://github.com/FreeCAD/FreeCAD/pull/21708) is not regarded as the way
+to go.
+
+This PR is awaiting conflict resolution and since we are waiting for a
+reformatting of the code, I decided to not update this PR.
+
+Other work that was done in this project:
+- Upgrade Doxygen to a new version
+- Document `App::Document`
+- Create a topic for Document
+- Document `App::Application`
+- Create a topic for Application
+- Document `App::Link`
+- Create a topic for Link
+- Document `App::Expression`
+- Create a topic for Expression
+- Document the classes for element mapping (toponaming) (unfinished)
+
+Since we are waiting for a big PR that reformats the C++ code and this is not
+for 1.1, I haven't created PRs for this work yet.
+
+With this effort, the project is nearing its end.  The things to do are:
+- Finish documenting the classes for element mapping
+- Create a topic for element mapping.
+- Improve the formatting of the website
+- Present the work at the developers meeting
+- Create the PRs for this work
+- Update the developer's guide
+
+
+

reports/improve-ux-varsets/pieterhijma-2025-09.md

@@ -0,0 +1,74 @@
+## Summary of Activities - VarSet User Experience - September 2025
+
+This project is almost finished.  The only implementation work necessary is
+copying properties to other objects.
+
+### Moving properties
+
+The following PR for moving properties was used as a base to discuss various
+issues, most notably with `theo-vt`.  This PR has been closed in favor of a new
+PR that has a satisfying solution, although I have some reservations because it
+pushes the transaction system to the limit.  I brought this PR to the attention
+of the CQWG.
+
+- [#22960 (closed)](https://github.com/FreeCAD/FreeCAD/pull/22960)
+- [#23841 (submitted)](https://github.com/FreeCAD/FreeCAD/pull/23841)
+
+
+### Presenting the project at the developer's meeting on 20 September
+
+[This project](https://github.com/orgs/FreeCAD/projects/30) is almost complete,
+with most issues done and merged and all but one a submitted PR.  The last one,
+copying properties, depends on a discussion with the CQWG that is planning on
+reviewing my solution on moving properties.  In the meeting, I tried to explain
+the different considerations for the implementation.  Although the
+implementation finds the limits of the transaction system, there was not strong
+resistence against the current path and merging it in the dev release after the
+1.1 release.
+
+Based on this, I conclude that it is worth to work on the last PR, copying
+properties, while understanding that a review of the "move property" PR may
+render the copying properties PR unnecessary.
+
+### Reconcile Add Property dialogs
+
+Remove the old Add Property dialog in favor of the one that is used for
+VarSets.
+
+- [#23426 (merged)](https://github.com/FreeCAD/FreeCAD/pull/23426)
+
+
+### Allow editing of a property tooltip in the Property View
+
+This PR has been merged.
+
+- [#23510 (merged)](https://github.com/FreeCAD/FreeCAD/pull/23510)
+
+### Expanding and collapsing properties in the Property View
+
+This PR has been merged after DWG discussion and approval.
+
+- [#23535 (merged)](https://github.com/FreeCAD/FreeCAD/pull/23535)
+
+### Add a binding for property removal
+
+This PR adds a binding to remove properties and takes into account Mac users as well.
+
+- [#23552 (merged)](https://github.com/FreeCAD/FreeCAD/pull/23552)
+
+### Various fixes for properties and the expression dialog
+
+These PRs solve several small issues with the Property View and the expression dialog.
+
+- [#23631 (merged)](https://github.com/FreeCAD/FreeCAD/pull/23631)
+- [#23648 (merged)](https://github.com/FreeCAD/FreeCAD/pull/23648)
+- [#23650 (merged)](https://github.com/FreeCAD/FreeCAD/pull/23650)
+- [#23991 (merged)](https://github.com/FreeCAD/FreeCAD/pull/23991)
+
+
+### Reporting where properties are being used
+
+This PR allows users to obtain a report where properties are used (referred to)
+in their designs.
+
+- [#23989 (submitted)](https://github.com/FreeCAD/FreeCAD/pull/23989)

reports/improve-ux-varsets/pieterhijma-2025-10.md

@@ -0,0 +1,51 @@
+## Summary of Activities - VarSet User Experience - October 2025
+
+With this report, I would like to finish this project.  Not all work has been
+merged yet, but this is mainly caused by FreeCAD's current attention to bug
+fixes for the 1.1 release.
+
+### Pending feature PRs
+
+#### Moving properties
+
+The PR below has a satisfying solution, although I have some reservations
+because it pushes the transaction system to the limit.  I brought this PR to
+the attention of the CQWG and I propose this to merge it into the main branch
+after the 1.1 release to validate the functionality before the next release.
+
+- [#23841 (submitted)](https://github.com/FreeCAD/FreeCAD/pull/23841)
+
+#### Copying properties
+
+Along the same line, the PR below supports copying properties from one object
+to another.
+
+- [#24443 (submitted)](https://github.com/FreeCAD/FreeCAD/pull/24443)
+
+#### Reporting where properties are being used
+
+This PR allows users to obtain a report where properties are used (referred to)
+in their designs.
+
+- [#23989 (submitted)](https://github.com/FreeCAD/FreeCAD/pull/23989)
+
+### Pending bug fixes
+
+There is only one PR for the 1.1 release that solves the issue of an overload
+of Python console messages:
+
+- [#24446 (submitted)](https://github.com/FreeCAD/FreeCAD/pull/24446)
+
+### Overview of performed tasks
+
+When starting the project, this was an overview of issues to handle:
+
+![Screenshot start Improve UX VarSets](res/start-improve-ux-varsets.png)
+
+Currently, the state of the project is the following:
+
+![Screenshot result Improve UX VarSets](res/result-improve-ux-varsets.png)
+
+Besides the pending PRs described above, there is one issue that has not been
+closed but is marked as done, because this issue needs wider discussion.  I
+notified the Design Working Group of the issue.

reports/occt-liaison/pieterhijma-2025-09.md

@@ -0,0 +1,47 @@
+## Summary of Activities - OCCT Liaison - September 2025
+
+### Update the project
+
+The [OCCT Liaison
+project](https://github.com/orgs/FreeCAD/projects/32/views/1?layout=table) has
+received extensive updates on issues.  Previous months I've mentioned each time
+that I was running behind, but now I'm up-to-date.
+
+Besides that, I focused mostly on OCCT issues with the regression label.
+
+### Regressions
+
+To prepare for release 1.2, the FreeCAD developers are trying to handle
+regressions.
+
+There are five issues that are both labeled regressions and OCCT in [FreeCAD's
+issue
+tracker](https://github.com/FreeCAD/FreeCAD/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Type%3A%20Regression%22%20label%3A%223rd%20party%3A%20OCC%22).
+I track those issues in the [For release
+view](https://github.com/orgs/FreeCAD/projects/32/views/15) in the [OCCT
+Liaision project](https://github.com/orgs/FreeCAD/projects/32).
+
+One of those five issues is no longer in the list because it has been marked as
+"Done" because the issue has been solved in OCCT 7.9.
+
+Two of the other four issues are submitted to OCCT, one of which causes a crash.
+
+One of the four issues, issue
+[#20889](https://github.com/FreeCAD/FreeCAD/issues/20889) is on Dmitrii's radar
+and I provided brep files for Dmitrii for various OCCT versions.
+
+The final issue awaits triage from Hyarion or the CAM team and may not be
+OCCT-related.
+
+### DRAW Test Harness
+
+DRAW tests submitted to OCCT:
+
+- [#15102](https://github.com/FreeCAD/FreeCAD/issues/15102)
+- [#6196](https://github.com/FreeCAD/FreeCAD/issues/6196)
+- [#24155](https://github.com/FreeCAD/FreeCAD/issues/24155)
+
+### Discussion on OCCT bug reporting and versions
+
+I contacted Adrian, but I don't have a reply yet.
+

reports/occt-liaison/pieterhijma-2025-10.md

@@ -0,0 +1,34 @@
+## Summary of Activities - OCCT Liaison - October 2025
+
+### Update the project
+
+The [OCCT Liaison
+project](https://github.com/orgs/FreeCAD/projects/32/views/1?layout=table) has
+received updates on issues.  There are still OCCT-related issues in the issue
+tracker that are not in the project, but I'm close to having captured all
+issues.
+
+### Discussion on OCCT bug reporting and versions
+
+I contacted Adrian last month, but I don't have a reply yet.  I will ping him
+again.
+
+### Verify an OCCT fix
+
+OCCT has fixed issue [#15102](https://github.com/FreeCAD/FreeCAD/issues/15102)
+that I submitted last month.  I verified that this fix has also the expected
+behavior in FreeCAD which it does.
+
+### DRAW Test Harness
+
+I focused on submitting a DRAW test harness for a crash in FreeCAD.  For this
+one, it was challenging to find out what exactly was the problematic geometry,
+but it has now been submitted to OCCT.
+
+- [#19403](https://github.com/FreeCAD/FreeCAD/issues/19403)
+
+### Contact with OCCT on FOSDEM
+
+I sent an email to OCCT inviting them to FOSDEM, the FreeCAD day, and the
+hackathon.  I also introduced Brad regarding the FreeCAD Professional Network.
+