On 21/03/13 07:51, Alan Whiteman wrote: > Well put John. If two years of inactivity isn't a sign of neglect or > abandonment- I don't know what is. I think that devs of skill ought to > put their efforts into a project that shows signs of life. From this > perspective (I know I'm going to get ultra-flamed for saying this) devs > perhaps ought to see what Steve needs over at scidvspc. >
I started this as a response to Alan, but diverged so far from the topic I thought it better to start a fresh thread. This morning I have been doing some investigations into the project. I've looked at the git summary and, later, shortlog. SCID has four developers. One, pgeorges, no longer has a sourceforge account. Another has done nothing at all that I can see. Oh, the shortlog says he has, but not since October 2011. I'm looking at a list of commits to the official git repo. All of them are made by Alexander or Fulvio. The go back to January 2012, and I think they represent all the changes to SCID since 4.3. There are 16 of them. One fixes a problem which I reported to the list, and for which I created (but since there was no apparent interest didn't offer) a patch. It should have been released. A bug I read about here yesterday and commented on (I think I had the problem too) is listed in tracker as fixed but not closed. Alexander made a commit which might be the fix. It should have been fixed. The most recent two changes were made by Fulvio and are for the merger of SCID and scidvspc, so I expect the merger will proceed. So far as I can see, Steven has made no changes. The project has bug tracker. There are 26 open bugs going back to May 2009. Nobody has been assigned to take care of them, although one has been fixed. I presume "open" and "fixed" mean it's not been released to users yet. Someone needs to deal with them, and for the moment Fulvio's the person. Of course, anyone can join as a developer and ask to join the program and adopt any of these bugs. Or, since there's so many willing to fix them, quietly work up a patch and offer it to the project. There are 17 open feature requests, going back to July 2002. Someone needs to deal with those too, and my first candidate for that is Fulvio, although perhaps Steven could take a look too. Some might be dismissed, that's find if it's shown they have been properly considered. There are four patches for goodness sake, going back to January 2004. Surely those are easily considered and, probably, easily tested. It might be a little late to consult with their authors though, they're probably using something that is supported. There are two support requests, those have been completely ignored. It's hard to relate the git commit history to the tracker. This should not be, it would be useful to use the tracker to track all changes to SCID (and its websites). Doing so would help future developers to see what past developers did, and for interested users to see that things are happening. At the moment there is little incentive for people to report bugs or to request improvements. A good start to change that is to attend matters raised in tracker, to be present on the user's list, and to document every change in tracker so people see there is activity. And make it really easy for people to check out git source code, make the instructions easy to find. I did it yesterday, after some difficulty, but wanted to do it again today and searched all over the place and didn't find them. Eventually, I resorted to google. Additionally, the build process is in sore need of repair. I recommend using the Free Software Foundations autoconf tools (but I don't know how to). -- Santa -- Santa ------------------------------------------------------------------------------ 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