Well this whole debate/conversation dates all the way back to at least February of last year, and some of the earlier requests were from early April 2009, I saw some posts about XCP source throughout 2009 and 2010, and even some of your own posts date as far back as at least April or May of this year, so that's been well over 15-18+ months of requests for the XCP source code from Carsten Wiedmann (from "mell1ej"), and I even saw some earlier posts that proceeded even that.
Here is a request on April 7, 2009 from "mell1ej" asking for the XCP source code (which is over 15+ months ago) asking for the XCP source code:viewtopic.php?f=16&t=34411&p=147205p147205#p139958
Nat32support was kind enough to even post all of the source for his XCP 2.3, 2.4, and 2.5 here:viewtopic.php?f=16&t=36680&p=147200#p147200
Chris has been extremely nice about posting his own source code (which "Carsten Wiedmann" seems to have based "his" derivative works on).
Even that earlier post above (dated August 13, 2009) from Chris (the original author of the source code) had asked "Carsten Wiedmann" to PLEASE post/publish his own source as well. That seemed to have fallen upon deaf ears (for at least over the past year and a half). Even since Chris' request (from the original author of the XCP source code), asking " Carsten Wiedmann " to post the updates to the source code and 11+ months is a long time to wait for someone to post/publish their source code. That last request was made on August 13, 2009 by Chris (almost a year ago).viewtopic.php?f=16&t=36680&p=147200#p147200
So there have been requests for over a year and a half ago (dating back to at least "mell1ej" in April of 2009) asking for the source code for the XCP.
I do agree that the whole point of an "Open Source" project is so that the source can be made available, so that if minor changes (or customizations) need to be made, the source is readily available.
The whole point of making source available, is so that patches/fixes/customizations can be made without bothering the core developers. We all have jobs, and we all get busy in life. But that's the whole point of having an SVN, and storing the latest versions of code on the SVN.
If "Heir Weidmann" (Carsten Wiedmann) can't "play nice" with the Open Source Community then maybe another developer can just maintain the code (and make the fixes/updates), or maybe you (or possibly even myself) can help with just maintaining it (as needed).
But that's just ridiculous selfish for ONE person to make changes to Chris' source code and then not share the changes/updates or make them available, or update the SVN and then for Carsten Wiedmann to just horde the code updates all to himself.
It seems to defeat the whole purpose of an Open Source project, and seems to go against everything that Open Source communities and Open Source projects stand for.
Plus it puts a project at jeopardy, because what happens when ONE person "gets busy" (such as the case with Mr Heir Weidmann), or ONE person chooses to leave the project (for personal reasons) or just gets "sloppy" and never commits the updates to SVN.
Either way, it creates problems, and the releases should always be 100% based off of the latest SVN. If anyone wants to submit code (that will be used in a release) then ALL the source should be made available and the latest source should ALWAYS be stored in the SVN as well.
It makes it extremely difficult to make minor changes, updates, or even post code snippets (for patches) or customizations when source code is not even available.
Seems to go against everything that "Open Source" stands for. I have only one word for it "Selfish".
I had been searching for the source code myself, and stumbled upon one of your threads (and a few other threads) looking for the source, and all fingers seem to point at this mysterious Mr. "Heir Wiedmann" ( Carsten Wiedmann ).
At least a simple response from Heir Weidmann ( Carsten Wiedmann ) would be appreciated, even if it was a simple "Go suck donkey nuts, because I'm a selfish gnome that eats my own source code and doesn't share it with anyone else.
But at least we'd have a response.