Having documentation 'on-request' for an Open Source project is very weird. In fact it's a big no-no for Open Source.
Lots of developers dump their code on the internet and say it's 'Open Source', while in fact making something Open Source means
work. You need to provide documentation, answer questions, review patches/pull requests and generally maintain your code. It's work, and for some projects it's a LOT of work.
If you don't have the bandwidth to do all this then don't open source your code.
Servoy has over 100 public repositories. But, to be honest, the documentation on it is very poor. Source code alone is no substitute for documentation and still that is what we mostly have to resort to to be able to understand what it does and can do.
As I understand Servoy is working on consolidating the documentation and hopefully make it more complete, perhaps they can then also update the documentation for the Servoy code and make it publicly available again.
ptalbot wrote:If the only problem is to find a place that is not to be found by accident and confuse users, I suppose (and Robert Ivens will be able to confirm this) that a good place to put this information would be on ServoyForge.
We could open a specific project with a wiki that could be used to document the steps needed to run Servoy from the sources.
Yes, we will be happy to create a project for it on ServoyForge.