Thank you for raising this question.
I had a discussion along those lines with Jan a while ago and, if i recall correctly, he indicated that there are a number of organizations who have developed internally the skills to work with the source code.
However, I also felt that its time to have commercial organizations working with SWI-Prolog to support swi-prolog by helping increasing the number of people in the community understanding the source code and even have the knowledge of maintaining and improving it.
To this end, and as a first step, I thought that swi-prolog should be documented – quite like those Linux kernel books that annotate the code and have chapters explaining the OS design approach.
There is, for example, a company called SWIMM, who create a git based tool to document open source code, as well as help sync between documentation and source based on gits source code tracking capabilities.
There is also a tool called CodeStory, which i have been using for some time now to document own code, which however, isn’t git based in the version i have – there is a git version in the working.
What if commercial organization could crowd raise fund for Jan so he can dedicate time towards documenting the source, writing technical chapters and perhaps even educating individuals in the community about internal workings through online (and recorded) webinars.
Do you think this could work – assuming of course that Jan would be interested in something like that.