J. Varsoke a écrit : > Perhaps it is once again time to revisit the issue of the great Scid > fork, and taking over this abandoned project. > > Since Feb 2007 nothing has transpired on the Scid project. No new > releases. No code committed. No return of our beloved Shane. > Yes, no public return. > Where once there was one, now there are two forks of this program we all > love so dearly. Both ChessDB and Scid-pg > > Since this issue got ridiculous political, why don't we take an > objective glimpse at how far these two projects have come: > > http://chessdb.sourceforge.net/changes/ > Download games from ICC > Much improved connectivity to The Week In Chess (TWIC) web site. > all language files have been split into 4. $lang-basic.tcl (w > A new logo > Improved method of annotating a game, which still detects blunders, > but ignores minor differences of score. > Minor fixes > > > http://prolinux.free.fr/scid/scid_newfeatures.html > Play a game against an opponent with a defined ELO > Play a game against an UCI engine > Search for blunders in a game (auto-annotation) > Add markers directly on the board > Opening trainer > Easy game navigation > Tactical exercises > Multi-variations display (N best lines) > UCI engines support > Opening book > EPD support > Minor updates > > >From the looks of there was a lot more work put into Scid-pg. > > Now, there have been a lot of valuable Open Source projects that have > been killed by egos. Let's not let this be one of them. > > Shane is gone. Maybe deceased. No, he's not (fortunately !). > But in any case has no interest in > Scid. He knows its out there. He knows people love and use it. But > he's expressed no interest that I know of in the last 4 years. > It is not as simple about Shane's willingness to continue Scid's development or not (he wrote to me in Feb 2007 about his plans to come back, but we saw nothing). So, you're right, and the apparent result is the same. > While there are rumors he didn't like people futzing with his code, he > also made it open source and hosted it on SourceForge. SF has a policy > of allowing future development on abandoned project under the flag of > the original project once the author has lost interest. > You are certainly right on SF's policy, but they don't want to enter endless battles. So if someone, that has strictly no right on a project makes a "formal opposition" to a take over and starts a FUD war, they will freeze things. It is obvious that Scid is abandonned now at SF, but some people denied it (D Kirkby), with the idea to leave Scid in its current state, and to prevent others to revive it. So what to do ? If anybody manages to revive Scid, I am sure many people (and I am among them) will want to contribute to it. But the question is : how to achieve this ? If you ask for a take over at SF, and warn people about it before doing so, be sure D Kirkby will make a "formal objection", because he wants Scid to vanish (or what are his motivations about ?). I would personaly be happy if someone could make Scid up again, even if only on the administrative part (mailing list maintenance, CVS access, announcements, etc.). > It seems right that Scid should continue to flourish -- certainly its > userbase would enjoy new features. For some of us, Scid is the only > reason not to buy Chessbase (I own two versions and still prefer Scid). > To be honest, Chessbase products are not bad at all ;-). But they lack features that can easily be put in Scid with a few hours of coding. I usually find Scid more efficient than Chessbase (faster searches for example), but Scid's user interface needs some refreshing / revamping (better integration, better graphics, more intuitive). > So let's put differences aside and breath life into this wonderful > project. Let the most active fork become the official main branch. Let > the userbase win with a new version of a product they've known and > loved. > > Let's let Scid-pg take over the Scid project at SourceForge and end this > silly feud. > I agree things gone really silly here, and if anybody could take over the project at SF, I think it would be great (I tried one year ago, and it failed because I underestimated nuisance capacity of some people). And me (and others), would follow him. The problem is that some people have other "interests" than reviving Scid, so what to do ? From my point of view, the best solution would be that someone (not me ...) takes over Scid at SF, and by opening CVS access to contributors, I think Scid will quicky move forward again.
Pascal > -jason > (author of ICTK, hosted on SourceForge) > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
