Lets face it, applying for tech takes time and effort from both the staff and the applicant. The server needs techs to fix bugs and help more people stay on the server by adding new features, but the position requires so much trust (since you could do tons of damage if you mess up as a tech). So I propose we form a "coders club" of meep. this would provide many benefits such as:
- a new way for people to meet each other or get to know each other in a new way
- a place for people who enjoy coding to discuss code and programming-related things
- a place where techs/high staff can go to request help or ask for bug fixes to be written to help the server (without giving everyone tech-level perms)
To elaborate on that third bullet: My primary intention for this "club" is mainly to get bug fixes and code edits done faster in meep and, while the final decision about what gets implemented is, as always, up to the high staff, i think this could be an interesting way to challenge new coders (ahem).
The way i envision it, techs or high staff would see a problem /bug and send it to the group with any small code snippets (i.e. here's the buggy code and what we need it to do). then either a) the group leader (prob me) could assign the task to someone, b) we could fight for it, first person to send back a working solution wins, or c) someone "claims" the task and is in charge of working on it/getting it done.
Then
- the techs/staff could get bugs fixed quickly,
- the club members would have a healthy supply of puzzles to solve,
- the server wouldn't need to spend time hiring or training (as many) new techs,
- club members could work on the problems on their own schedule and not have to worry about being demoted for inactivity (if thats even a thing) or being known as "that slacker"
If accepted, i would like to be the one to organize/spearhead this plan, but if a high staff member wants to take this on, i would be happy to just be a club member as all i want to do is code for meep (i think thats pretty obvious at this point).
This idea was partly inspired by @Khafra explaining to me that it was his code that fixed vshop (thanks matt if your reading this).
now i will tag some programming people who i think will be interested, ignore this bit... @Blendyz @lordusan @Shellcode @reggles44 (already tagged mattisaperson). apologies if i missed you...