Alexander Wagner a écrit : > Hi! > > First of all I did not manage to subscribe for this list for > whatever reason till now (was always refused or did not get > any answers from the listrobot but now it seems to work) so > I was not able to follow the discussion (still I've not > found a way to access the archives <grrr>)... > > >>>> Excuse me for asking a curious - but for sure a naive - >>>> question. I did not follow this discussion previously ! >>>> What is the problem with making a fork of Scid and have >>>> that fork hosted by SF ? Wouldn't that solve your needs >>>> here ? >>>> >>>> >>> First I don't like "forks". If one day someone manages to >>> continue Scid, there is no interest in any fork for me. >>> Regarding another project at Sourceforge, what name to >>> choose ? I don't want to rename Scid to "xxxx" and change >>> all occurences of Scid in source code. This would make >>> change tracking difficult. >>> >> I see. If I had to start a fork project, I would probably >> refrain from renaming any source code. At least as long as >> there still was any meaning in diff-ing the source trees. >> > > As far as I can see you're discussing wether the scid > 3.6.x-Forks of Pascal should go to sf. For me as a user here > I'd strongly support this! > > I could only encourage Pascal here. He did some really great > work and I did find it only by chance yesterday cause I was > recompiling my chess software and was searching for the > b2-patches that where once upon a time found on > http://scid.skjoldebrand.org/ I did not find them but > Pascals code and I'm really impressed. (So actually I stoped > searching the old patches ;) And his stuff is good, it would > be a pitty if it would be lost again. > > >> But of course I agree with you that it would be much >> better to just work on the existing project. A pity if >> someone is blocking you out... :-( >> > > This would be the best, indeed. Anyway even registring a new > project as something like scid2 or whatever stating clearly > on the page that it is a subsequent development of > <...link...> as the original author is not reachable and > that it might fuse again with scid would be very helpfull > for the users community. Just to find the project... Really > I did just find the new code by pure chance after quite some > research for the patches I knew that they once existed. > > So, Pascal, put it to SF! For me and others to be able to > find it. It could merge again to scid if possible at some > day. But unfortunatley the last message from scids webpage > did not even make me expect that there is new development. > So I was really suprised. > >
There are 3 options here : 1. Someone (not me !) asks for a take over of Scid at Sourceforge ; 2. Someone (not me !) sets up a new project at SF (Scid2 is a good name for me) and opens CVS to developpers; 3. *I* set up a new project at SF (Scid2) and opens CVS to developpers. I don't vote for option 3 because : - if someone takes on administrative task, this would give more free time for me; - I like to have an external eye looking at what I am doing and other advices/opinions are a good thing; - I don't like designing web sites, and everybody noticed my lack of skills ;-) Pascal ------------------------------------------------------------------------- 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
