Shareaza

Just noticed that the development of Shareaza has slowed dramatically. Is there a reason?

Vacation... lack of developers... many other things you can imagine

SourceForge is rejecting my SSH key for some reason right now so the build from 2011-09-02 has not been uploaded.

How about you code in "send feedback" feature within shareaza so its easier and faster to send feedback for beta builds?

How about sending them to a mailing list where anyone interested can read the messages sent...

Or you could just post your comment on the forum? It is not really useful to be more accessible and responsive unless you actually can make the responses useful... Getting more feedback is not that valuable if you already have more things on your TO DO list than you can handle.

Well, the size of the TODO list is probably due to a tendency to ignore the TODO list completely, just as well as to a tendency to discourage new developers etc. To make a long story short: I don't see the point in doing any coding work if my code is not even included in the debug builds for testing. Currently, all of my 3 code commits (among which are two fixes for bug reports on the tracker, as well as one major performance update) are "on hold" in the code commits forum with no progress since more than one month.

My point was that having a send feedback button linked to a mailing list would not help. At all.

IMHO, the main reason is that Raspopov didn't put enough (if any) effort to encourage developers to join the project and learn it. He is a powerful programmer and has a good grasp of Shareaza internals (maybe more than anyone else). Shareaza is a complex and big project. The code is not documented so understanding whole of it would take years without help of someone already dominant. I even don't know which parts of internals does he know about. So now nobody really knows the internals.

Not true. Patches are very outdated and questionable.

I sense a flamewar coming on...
A word of caution: Lets try and keep this civil and keep our criticisms constructive.

@raspopov: if you could check out the developers section of the forum once a day it would go a long way. If we have something for you then we, as moderators, will do our best to put it where it belongs - in the dev and code submissions section. If you see that someone is working on the same bit ofcode as you then maybe hold off on your commits for a couple days so they can fix up there code. You are our projects primary dev and probably the one with the best understanding of the code, so it is much easier for you to update your patches then it would be for a newbie to keep up with you

Please excuse my intrusion. Perhaps a move to Github might be helpful. It seems to have been designed specifically to sidestep these types of issues.

Actually, sourceforge has git support and OldDeath has no problems creating branches in other projects that have git.. Why not try switching to git?

How an svn user sees git workflow.

Funny picture.