On 03/14/2013 07:34 AM, Fulvio wrote:
Mario Lacunza wrote:
Hi,

I was following the discussion in silence, Im a scid user (now a 
scidvspc user) in Ubuntu linux for years and Im a dev myself and 
opensource fan (and off course I play chess since 12 years old... some 
time ago ;) )

Fulvio: I dont understand your idea about the add more features to the 
scid line (I think a death line right now no updates in a long time) 
with the only idea to put scid at the scidvspc level or with the same 
features (anyways you are free to donate your time), thats not a wasted 
of time? efforts? and hands? for me is better idea add more code to the 
latest and more developed code version... and after that (for me and if 
the hands are there) add the scid code to the scidvspc (the portion not 
used in the last one) Steve said he will going to port the dock option 
(I nice option for me) so?
  
This is obvious to me and maybe is a technical thing so i would like 
Steven to confirm it so there will be no confusion:
- Steven don't want to merge the two projects because is too much work 
(no problem with this)
- Four years ago Steven started is fork of Scid (no problem with this) 
and after that he taked all the code he liked from scid mainline (no 
problem with this, i don't know if he give credit back, but scid files 
are unfortunately missing the required copyright statements anyway)
- He added a few features like Engine Chess Tournaments but didn't send 
back to scid his code (this is understandable for big features, but if 
you find a bug or do a small improvement like "Clickable Variation 
Arrows" or "Tri-coloured Tree Bar-Graphs" you should be nice enough to 
send it back to the mainline from which you usually take code, but no 
problem with this anyway)
- He didn't take a lot of code he didn't liked, expecially tcl/tk code, 
because he have different ideas on usability and how the UI should be 
(no problem with this)

Now scidvspc is a separate open source project, with his happy users 
(like you, if i understand correctly) and all will be good.
But now, for no reason i can understand, Steve (with Alex complicity) is 
trying to delete the 4 years of code that people contributed to scid and 
Steven didn't liked.
THIS IS NOT ACCEPTABLE, expecially considering that this is a GPL 
project, you don't kill and delete concurrent projects to force people 
to use your program.

As i have already said neither Alex neither Steven has the right to do 
this and I WILL NOT ALLOW THIS (i'll report the issue to sourceforge and 
free software foundation if i have to).
I hope i'm clear and there are no misunderstandings.
Bye,
Fulvio

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users



After the merge the old scid code can reside in the archives for anyone who wishes to access it.

From a user's point of view, it does not make sense to have two scid branches. One is hardly maintained while the other is actively developed, with bugs and new features addressed. Many users made the switch to scidvspc just for that reason. Eventually, most all scid users would have abandoned the scid branch for scidvspc.

Scid's lead developer (Alex, I think) thought, very prudently, that it was a good idea to have Steve's code be a continuation of scid.

All this talk about not "allowing" old code be deleted is really counterproductive.




------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to