Add reports for April

- Improve C++ API documentation
- Improve User Experience VarSets
- OCCT liaison

Author: pieterhijma

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

@@ -0,0 +1,51 @@
+## Summary of Activities - Improve C++ API Documentation - April 2025
+
+### CMake issues for generating documentation
+
+Last month, I created the PR below which was still open.  This has been merged
+now and needed some fixing as well.
+
+- [#20479 (merged)](https://github.com/FreeCAD/FreeCAD/pull/20479)
+- [#20709 (merged)](https://github.com/FreeCAD/FreeCAD/pull/20709)
+
+### Fixing unassociated doc strings
+
+Some doc strings were not associated with a specific piece of code and would
+appear randomly:
+
+- [#20737 (merged)](https://github.com/FreeCAD/FreeCAD/pull/20737)
+
+### PropertyContainer
+
+The documentation of PropertyContainer was improved.  Based on community
+feedback on the forum, I changed the assignment of this project slightly.  I
+defined the project as having the scope by just fixing the doc comments of
+classes, functions, etc.  However, it was clear that the community wanted to
+have improved overview texts as well, that would provide developers context.
+So, I decided that I will not document all of the App package, but just the
+most important things but I will add overview texts as well.  For this work, I
+created such an overview text for the Property Framework where the most
+important object is PropertyContainer.  This came in two PRs:
+
+- [#20781 (merged)](https://github.com/FreeCAD/FreeCAD/pull/20781)
+- [#21065 (merged)](https://github.com/FreeCAD/FreeCAD/pull/21065)
+
+### Discussion on how to document
+
+Based on the above PR, a [discussion on
+Discord](https://discord.com/channels/870877411049357352/1354091480393842799)
+was started to establish how documentation can be done in FreeCAD.  This can
+eventually lead to guidelines in the developer guide.
+
+### Property
+
+I've started working on improving the documentation of Property but this is not
+yet finished.
+
+### ObjectIdentifier
+
+The same is true for ObjectIdentifier.
+
+
+
+

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

@@ -0,0 +1,44 @@
+## Summary of Activities - VarSet User Experience - April 2025
+
+### Update the project page
+
+I've updated the [project page](https://github.com/orgs/FreeCAD/projects/30/views/1).
+
+### Visibility icon for VarSet
+
+Last month I couldn't find a satisfactory solution.  This month I have:
+- [#20649 (merged)](https://github.com/FreeCAD/FreeCAD/pull/20649)
+- [#20573 (closed)](https://github.com/FreeCAD/FreeCAD/pull/20573)
+
+### Units in the VarSet dialog
+
+Last month, I worked on units in the VarSet dialog, but I couldn't make them
+work properly.  This month I have:
+- [#20570 (merged)](https://github.com/FreeCAD/FreeCAD/pull/20570).
+
+### Frame around the value field in the VarSet dialog
+
+The value field lacked a frame.  This has been fixed in:
+- [#20582 (merged)](https://github.com/FreeCAD/FreeCAD/pull/20582)
+
+### Immediate access to value field VarSet dialog
+
+In the VarSet dialog, it was necessary to first define a name and type, and
+only then the value field would appear, leading to a strange user experience.
+This has been fixed in:
+
+- [#20824 (merged)](https://github.com/FreeCAD/FreeCAD/pull/20824)
+
+### Add multiple properties VarSet dialog
+
+In [issue #20637](https://github.com/FreeCAD/FreeCAD/issues/20637) there are
+different opinions on how the user flow should be when adding multiple
+properties in the VarSet dialog.  I started a discussion with the Design
+Working Group, but there does not seem to be much consensus either.
+
+### Refactoring properties
+
+A larger task in the project is allowing users to refactor properties in
+VarSets or other document objects.  I've started thinking about how this should
+happen and the concrete action I'm now working on is renaming as I announced in
+[issue #16222](https://github.com/FreeCAD/FreeCAD/issues/16222).

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

@@ -0,0 +1,64 @@
+## Summary of Activities - OCCT Liaison - April 2025
+
+### Contact with Dmitrii: Data Exchange
+
+In the last report, I wrote that this needed follow up, which I haven't done
+yet.  I will do that in May.
+
+### Discussion on OCCT bug reporting and versions
+
+Last month, I wrote that this needed follow up and I did.  Oursland writes this:
+
+> It's not a genuine compatibility issue as some other build systems are using OCCT 7.9.0, but the conda-forge smesh still needs to be updated.
+
+So, I'm waiting for that.
+
+### Suggest a process for a 10 year roadmap
+
+I've had a meeting with Brad in which we discussed the idea.  I've also had a
+meeting with Hyarion and Kadet1090 on which I reported in the FPA meeting.
+Some interesting points that came out of this meeting:
+- It would be good if FreeCAD could work with a company that uses FreeCAD in industry.
+- It would be nice to have a label "AdoptionBlocker" similar to the "Blocker"
+  label for 1.0.  The new label indicates that these issues are blockers for
+  widespread adoption of FreeCAD.
+- Idea from Kadet1090: make a document with 100 problems for the next 10 years.
+- Hold another meeting with a slightly larger group of people.
+
+### Check forum on OCCT issues
+
+I wrote last month that I wanted to participate on the forum.  I announced
+myself there, but it was an old post.  I haven't had any reactions.
+
+### Update the project
+
+The [OCCT Liaison project](https://github.com/orgs/FreeCAD/projects/32/views/1?layout=table) has
+received continuous updates on issues.
+
+### Draw Test Harness
+
+I've investigated creating Draw Test Harnesses.  I studied the Draw Test
+Harness that bgbsww created in
+[#9760](https://github.com/FreeCAD/FreeCAD/issues/9760).
+
+Given the results of this study, I focused my attention to
+[#10760](https://github.com/FreeCAD/FreeCAD/issues/10760), a fillet with a
+crash.  I could confirm the crash.  The process was:
+
+- make a minimal example, finding out the (in this case) two features that cause the problem
+- make a Draw test case that mimics the minimal example
+- verify the stack traces to confirm that the test case is indeed the same problem
+- report it to OCCT ([#501](https://github.com/Open-Cascade-SAS/OCCT/issues/501).
+
+Please note, that this was a fairly complicated test case to create.
+
+### Part Design / Part interaction
+
+I studied [#19702](https://github.com/FreeCAD/FreeCAD/issues/19702) and came to
+the conclusion that this may be an OCCT problem, but there is also a problem
+with the interaction between Part and Part Design.
+
+I have created [#](https://github.com/FreeCAD/FreeCAD/issues/20735) for that
+problem and I have raised this in the DEV meeting of 19 April.  Unfortunately,
+this was a meeting without many developers, so we could not make progress on
+this matter.  I will put this back on the agenda at a next meeting.