Shareaza

How about posting advertisement on public places to hire devs for our Project?
More than one of us is going to university, for example, and there are places where everyone can post announcements etc. How about printing out some pages and posting them on black boards etc.? Even if we get only one dev more, this would be a great success.

Since when was Shareaza hiring developers?

Don't turn me my own words in my mouth :p

It was thought to mean "get more devs working for free in their free time on our project".

I believe the word is "recruit".

OK^^ Now that the English language problem has been solved, back to the idea...?

I have some known to me coders who could be interested eventually. What I would need and would like to propose is that helpfull would be a "dev pack starter" so sth what could be burned onto CD like basic code and what i could give them and said have a look if you would like to helo with work on it.

Anyway I have done sth like this already about 1,5 years ago with a kind of posters but I don't know if there was any effect, well I have no way to verify this. I ll do it again. A starter, introduction for new devs is needed. And perhaps also a list of simple task they could start with. Just an idea.

Wow, now we're getting somewhere. These tasks could be added to the bug tracker as feature requests, BTW.
Probably you should do this yourself, as you know more about the respective things needed to be done...

I am sure our sole active developer (although ivan and mojo posted some neat code lately...) already has all the low priority no time to do stuff he wants in his head without me pushing more on him. Probably lots of high priority no time to do stuff as well. But if we are talking about projects to offer to new developers not familiar enough with Shareaza to do those higher priority things... I have lots of those, and most other long time users probably do as well.

Well, then how about a complete list of such tasks for new devs in the development forum? Divided into "easy", "difficult" and "horrible to code" ?

Because it makes some features that didn't exist at the time Shareaza became a multi-network client more difficult or less efficient to implement. Specifically obfuscation. Since obfuscation is designed to make recognizing the type of connection more difficult for the ISP, it probably will end up increasing the overhead of recognizing the protocol by Shareaza. Using separate ports for protocols would allow simply assuming any unclear connections protocol. Obviously you can just make it so that Shareaza uses multiple ports if obfuscation is enabled. Also I have no idea if the actual obfuscation implementations really cause a problem, but eventually one will. Another problem is that it limits the degree of separation between different protocols, although unless we start wanting pluggable protocols that is an aesthetic concern rather than a real problem.

I think I mostly meant "problem" in the sense of "not the way the books say it should be done," tbh.

Sorry to turn the topic to a negative atmosphere, but our first and great challenge is to convince the new requiters that Shareaza is/(will be) alive prior the Discodia-Rhythm-bulling and that they have not to be afraid for the trademark-issues...