Nice to hear that! I hope you will make it easier to open up servers! That's bothering me for a while.

No i think we don't need a better system at the moment...
other thinks are more important!

I really respect u catpaw for ur technical knowledge and im almost sure u want to help but maybe criticizing the people who do all their best to code the game we all love is not the best thing u could do. I see u mentioned a lot of things that can be improved but u could have done the same in a lot calmer way :>. Those people are working hard for our entertainment and even if they do some things wrong instead of putting them down try to help and show them the right path ( incase u know it ).

Constructive critizism is the best thing which can happen. And a discussion is to get one step further. If all ppl just said yes, we still would be in the middleages. And writing posts in a forum in a not-native-language will sometimes sound more rude, than in your mother tongue.
btw: No one doubts that "those people" do work hard.

And again, there will be mechanics in place for that, not just until we can properly maintain that workflow. Nothing about collaboration is automatic, and the only thing worse than not accepting community patches is saying you do, but then not taking the time to review and implement them.

I believe we're more or less on the same page here.

I think that was the opening discussion. What kind of system do you need where there isn't one suitable out there? And what kind of "workflow maintance" do you need to implent? yet another teeworlds sepecific thing, where a standard tool doesn't sufficide? Btw. AFAIK creative work and "workflow", usually that contradict each other.... And the opening suggestion. If you are going the invest 30 minutes a day, start investing them on reviewing patches...

I believe we're more or less on the same page here.

I would say the criticism of why we keep the code under strict scrutiny and the criticism of the code itself should cancel each other out. The codebase is still very much a work-in-progress, and while many of your points may be valid, I must urge patience. The major reason we still keep our code under "dictatorial rule" is because we're not done with even a third of the things we want to do, and there are still improvements to be made to all the areas you addressed.

We'll hopefully get some community development features off the docks pretty soon, which I hope can stimulate these kinds of conversations in a more constructive manner.

As said, nothing speaks against keeping strict control over your copy. But it shouldn't rule others out. Just stricly review what people send to you, but give them an option to send... Okies? Take a look at Linus Torvalds, he has strict control of his copy "the vanilla tree", but still there is a vivid and active developing community around it. So code under strict scrutiny and the criticism of the code does not cancel each other not.

SDL is under GPL which matricks don't really like. Besides, it's very big for the little things Teeworlds uses.

I know about the GPL "issue", but technically speaking SDL would be the better choice IMHO. I mean the GPL doesn't hurt you, if you have a compatible license (that is all "free as in beer without omnimous restrictions)

I didn't talk about GPL, I said X11/MIT, I don't see where the current (in SVN) "teeworlds license" is in effects any different than X11/MIT, except worded differently, and have to be rechecked with every other license out there if compatible or not. So why not use the standard license X11/MIT to keep the jungle a little smaller. Just because we were talking about using "standard tools".

Its not so difficult to enable TCP and UDP of the same port number. Other games/applicatios have this too, some since decades (speaking e.g. of DNS). And it works.

No, on what system I would ever want to implement an own mem_copy routine? There are standards out there. And memcpy is a pretty strong standard, which machine/OS hasn't got that? Its part of the C standard!

Well windows has gcc/glibc available for it. Google for "gnuwin32"

Honestly no, The linker will either just pick out the routines used. So why not use a standard bazoka, if it does the job pretty well already?

Yes, but at least as far as I've seen there are quite some teeworlds specific stuff in engine as well...

Well wherre would you read this. How about reading you should look into the file game/server/server.cpp. Path and prefix is IMHO unnecessary duplication of data.

As I've wrote, you don't need detailed documentations in every detail. But 1 little sentence per function is not thaaaat much a work, and would do wonders.

As I explained, if you keep the naminig convention of header files being named after the classes, and classes having the first letter a capital letter, you can easily destinguish c from c++ headers.

We'll hopefully get some community development features off the docks pretty soon, which I hope can stimulate these kinds of conversations in a more constructive manner.

SDL is under GPL which matricks don't really like. Besides, it's very big for the little things Teeworlds uses.

Yes, we need another license. matricks have spent a LONG time (like 3 months) on choosing a license for Teeworlds, including talk with an Ubuntu license expert (if I don't remember wrong). There are reasons why he didn't choose GPL. What's the problem with the current license?

The TCP thing matricks has though of, but it would be better if everything went through the same socket. That makes it easier to configure the firewall.

The reason for mem_copy and such functions is that on specific platforms you'll want to implement an own. The io-functions exist to clean up and fix the crap that happens on some systems when you forget the b-flag.

The reason for implementing this is to do heap checking on platforms that don't have gcc/glibc, for example Windows.

Vector libraries often are too big for the little usage Teeworlds has. "It's stupid to kill flies with bazokas" to quote matricks.

The difference is that you can make a completely other game by changing the files in the game-dir and keeping the engine (simplified). The file prefix is really helpful when you for example read that it's the file gs_server.cpp you should look in. By using these letters anyone can find the file directly, and that makes working with multiple files much easier.

Documentation is on its way. Since Teeworlds is in alpha state right now, it would be a waste of time to document everything, especially the network part, since it changes a lot from version to version. There already are a documentation in the trunk (for 0.5), feel free to check it out.

The reason of the renaming is that Teeworlds use both C and C++ files and that's a simple way of separating them.

Thanks for suggesting stuff and such, but please don't expect too much this early in the game's developing.
/Somerunce