Hi Ian, > Would there be a consensus that your version is the one to start from?
As Aaron outlines, Waldek's stuff is an "overlay" for the full Birmingham distro. > Migrate https://www.cs.bham.ac.uk/research/projects/poplog/V16/AREADME.html > <https://www.cs.bham.ac.uk/research/projects/poplog/V16/AREADME.html> to a > top-level README.md (in the "master" github), remove duplication and add > decent markdown formatting Makes sense, and makes me wonder if we should add a markdown renderer as a Pop-11 library. (I would have fun writing one.) > Create a Dockerfile instance that works from a known base and with all the > libraries, Motif etc. sorted so there's a good exemplar baseline at least Absolutely - this is critical to stabilising development. > Create/add a unittest library, preferably one that produces either > https://en.wikipedia.org/wiki/Test_Anything_Protocol > <https://en.wikipedia.org/wiki/Test_Anything_Protocol> or jUnit or some such > so we can use Jenkins / circleci etc. Agreed in principle - although TAP is far from pretty. > Fix the Motif thing Yes. > Create .deb/.rpm packages Tested in Docker. > Create/add a library/package mechanism so 3rd parties can extend the base > easily (installing a library by copying files into the source is so old hat) Yes, completely right. This is the central purpose of POPGOSPL by the way. The idea is that POPGOSPL provides packages that are basically a folder with the familiar auto/, lib/, help/, doc/, teach/, ref/ etc subfolders. When you add the package, it automatically handles all the path extensions so that the package seamlessly extends the system. So this might be a good place to start. Steve
