On 01/03/13 09:20, Matthias Luckhardt wrote:
I disagree on your approach. The developers should focus on the advancement
of the code and other volunteers should be sought out to flesh out the
documentation.
Well, we could discuss this issue forever, and I tend to disagree on
this matter: To me, proper documentation is just as important as
bug-free code, and as a developer, I feel responsible for providing
it. After all, if I wrote (most of) the software, who could be in a
better position to describe its functions? Asking for volunteers to
step in will, in most cases, result in exactly what you're seeing with
Scid, namely insufficient documentation, at least for smaller
projects.

Of course, here I agree with you all the way. But as matters stand, there are priorities. The developers feel that there's not enough manpower/time to address both code and documentation. If I were to pay 100 for a piece of software I would definitely expect to have completeness and consistency: A program with no bugs and lots of documentation. Scid is a program available for free, developed by a small dedicated group of developers, and driven by a passion for chess. With that said, there's a lot of praise for scid: An excellent, fully functional, full featured alternative to expensive programs such as Chessbase.

      
I recommend that you select the fork that is most active, start rolling your
sleeves up, and make a great program even better.
Like I said, I would like the forks to join forces first and decide on
a way forward. If Steven is complaining about inactivity about some of
the core developers, shouldn't these matters be resolved first?

In a perfect world, there would be one branch- much like the Linux core is developed. However, there are many distros that cater to different tastes. This is an advantage in the OS world but not for a single application. However this does not take away to the fact that scid is an exceptional program worthy of the attention of talented developers.

As an outsider to step in now and fix the issues previously addressed
(both by me and what Steven wrote), I feel I would have to invest way
too much time. Spending € 100,- on Hiarcs would be the much more
sensible and saner option, I'm afraid.

Sorry, but if Scid wants to attract more developers, the people most
involved in the project need to step up and join forces first, and
make the barrier to entry much, much lower.

I disagree with you here about barriers. I think developers can join the community and contribute to the project if they really want to. If you can't afford the time and rather pay for a program, then that's the way to go. But why complain?

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to