sp1915 wrote: It should be done automatically after the first post, like Payment Proof section.

Quote:
1..............Increase membership , no T.O.S ,reason topic was closed , fight of 2 Mods,
that is wrong

2 ........Close forum, in feature requests , no T.O.S , closed and no info why
Some mods did not liked

Marcel-R6 wrote:
Wouldn't that be too harsh?

Quote:It is a well-known fact that those people who must want to rule people are, ipso facto, those least suited to do it... anyone who is capable of getting themselves made moderator President should on no account be allowed to do the job.

Quote:Blackmail is such an ugly word. I prefer extortion. The ‘x’ makes it sound cool.

I wrote:There are no shortcuts. You learn to program the same way you learn anything else - take things apart, and put them back together. Find some software you like, some software you use. Join their support forum or mailing list, answer questions from newbies. When you can't answer a question, read the answers so you can answer it next time. Subscribe to the git RSS feed, and read every commit. You won't understand most of it at first, but if the commit notes are good, you'll pick it up as you go along. As you find minor bugs - typos, display issues, etc, fix them. Finding your way around the code is an important part of learning it. If you can't fix them, file GOOD bug reports - figure out how to reproduce it, that also helps you figure out the program flow, figure out where it's breaking, figure out what works, and what doesn't. If you can create a good bug report, you can sometimes even fix for something you didn't even understand at the start of the process. Keep this up for a couple of years and you'll be Lord High Fixer before you know it. It'll also give you a good git history to show employers, and handling support will earn you a good reputation with better developers who will, in turn, help you more.

Basically, you just have to get your hands dirty until you damn well can do it.