We had agreed on meeting again this Saturday at 2PM central but I just realized that’s going to overlap with a wedding I’m going to. Could we reschedule for the same time Sunday?
That works for me.
OK, by me.
What’s our agenda?
I was successful in compiling FreeCAD on my Windows 10 machine. Here is the information regarding my build:
OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.16821 (Git)
Build type: Release
Branch: master
Hash: 73c1a9c9a75f1703d79d41d8670f5e073c72c7b5
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United States (en_US)
There were a few bumps along the way, and I made some mistakes, but sgrogan and kkremitzki got me through smoothly. I can now build and run FreeCAD on both Ubuntu and Windows 10!
Besides a general check-in, one main item on the agenda is to collectively pick the first Debian/Ubuntu packaging bug for FreeCAD which we’d like Zach to work on once the coding period begins Monday.
Maybe this one: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084
I’ve updated my blog with a post for yesterday. Today I’m having an in-person meeting with kkremitzki and we have one planned for this weekend as well. I’ll be updating my blog with today’s progress later tonight.
I updated my blog with some info about my upcoming coding work. A detailed plan on how to improve the OpenCamLib installation with FreeCAD will follow.
@zach awesome. A favor: can you post the permalink to said update with each update you make, please 
thanks
Hey @zach
Hows it going? How is the progress going?
Also, please put your blog address in you signature
The progress is going well. I have added my blog to my signature.
My last contribution was adding a dependency to the packaging build for FreeCAD. My blog post https://zachgummow.github.io/Control/ has the link to the merge request and https://zachgummow.github.io/Changelog/ covers my experiences working on it.
Thank you 
Apologies for the poor communication on my project. I have updated my blog on my current progress.
The last three changes to the Linux packaging I’m adding are just finishing up. This is behind schedule by a lot. I will be putting in extra hours to get up to speed on my second phase Windows development.
I have been in contact with sgrogan about the Windows development. We’ve settled on smoothing out issues with building FreeCAD on Windows with a focus on allowing developers that aren’t well versed in packaging to easily contribute. We are looking to find a more streamlined solution to the libpack directory.
Howdy!
I have finished the procedure for submitting my bug fixes as a patch for the Debian packaging of FreeCAD. The bugs can be found here and here.
In the mean time I’ve been working with sgrogan on the Windows configuration. We found some improvements that could be made to the Libpack and a summary can be found here.
I have also updated my blog with this information.
I have finished my changes to the CMakeLists.txt file. It will now only copy the necessary files from the Libpack and set a path for FreeCAD to know where to find the compressed python archive. More details available in my blog.
Howdy!
I have been in communication with my mentors about my current Libpack project. I have had a few meetings (with one in-person with kkremitzki) discussing the libpack project I will be working on.
However, the first thing is to finalize my CMakeLists.txt changes. Previously I had switched the binary copying function to a function that would create a batch file which would refer to the Libpack directory. sgrogan informed me that there is still a use for copying the binaries and that I should give an option to do so.
The second task is to have the CMakeLists.txt file cause CMake to stop early while configuring if the Libpack is not detected. This should eliminate false negatives when it searches for dependencies that are located in the Libpack. This early stopping will be able to be turned off if the user wishes to have their own directories for the library.
The third task is to have CMake search for the Libpack in some likely directories such as the base directory, one directory up, the C:/ drive, etc. This should allow the user to place the Libpack in a logical location and CMake will be able to auto-detect it’s location.
The final task for the last coding period is developing a Powershell tool to manage the Libpack for the user. The tool will search for updated versions and allow them to be downloaded independently from other packages. I will be using the debian/watch file as a reference for version regex.
Why no August updates?
Not trying to make excuses but I just seem to lose track of updating the forum/my blog. Neither has been in common usage for me before this project. Mostly my communication and updates have been direct to my mentors.
All CMake objectives have been completed. PowerShell development is going well and I will be able to have a proof of concept ready before the deadline.