Right now there is a lot happening - I'm being absolutely flooded with messages, and I appreciate all of them! Thank you for all the support. It is taking me a while to sort through them though, so if I miss you out I sincerely apologise!
By far the most common question is, how can I help? So I'm going to address this here:
1) Keep pushing the message. Tell anyone and everyone. Get your favourite server owners in here, get your friends and clans on board. The biggest danger is that while we are riding high right now things will calm down and return to the old status-quo. Thus while we sort through everything and get organised we need to keep that pressure up.
2) Very similar to the above - use these forums. Post pictures of your cats (post pictures of your dogs too I guess, if you're in to that sort of thing), ask scripting questions, re-release your scripts and includes, post screenshots and videos (you can even use you(them)tube). Basically normalise using these forums for anything you used the official SA:MP forums for before. But most importantly - post pictures of your cats!
3) Don't insult anyone. We may have issues with the way things had been run before, but that doesn't mean we go after the people themselves.
4) We need a list of SA:MP bugs, a nice thorough one. Start compiling them, or how will we know if we've fixed them? I'll get my bugtracker up (or that's something else someone could work on - fiixing this bugzilla error:
I'm sure it's not hard, it's just 2am here.
5) Related to above - tests. So we can prove bugs are gone. Consider using https://github.com/pawn-lang/YSI-Include...testing.md to write them (look up unit tests), and see here for examples: https://github.com/pawn-lang/YSI-Include...#L218-L227
6) The other big thing, the one we've been working hard on, is the code. This is where we will need the most help, though it is already well under way. However, right this minute it is not in a state suitable for general opening. If you are interested in this, and know C, tell us and we can move that forward.
7) I'm bad at graphics. We have some already, but more for promotion would be good.
8) Small modes. The examples that get bundled with a server. We need our own ones of those.
As I say, these are all little jobs that can be got on with while we sort out and organise the larger ones over the next few days.
By far the most common question is, how can I help? So I'm going to address this here:
1) Keep pushing the message. Tell anyone and everyone. Get your favourite server owners in here, get your friends and clans on board. The biggest danger is that while we are riding high right now things will calm down and return to the old status-quo. Thus while we sort through everything and get organised we need to keep that pressure up.
2) Very similar to the above - use these forums. Post pictures of your cats (post pictures of your dogs too I guess, if you're in to that sort of thing), ask scripting questions, re-release your scripts and includes, post screenshots and videos (you can even use you(them)tube). Basically normalise using these forums for anything you used the official SA:MP forums for before. But most importantly - post pictures of your cats!
3) Don't insult anyone. We may have issues with the way things had been run before, but that doesn't mean we go after the people themselves.
4) We need a list of SA:MP bugs, a nice thorough one. Start compiling them, or how will we know if we've fixed them? I'll get my bugtracker up (or that's something else someone could work on - fiixing this bugzilla error:
Code:
Encode version 2.87 required--this is only version 2.60 at /usr/share/perl5/Email/MIME/ContentType.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Email/MIME/ContentType.pm line 7.
Compilation failed in require at /usr/share/perl5/Email/MIME.pm line 13.
BEGIN failed--compilation aborted at /usr/share/perl5/Email/MIME.pm line 13.
Compilation failed in require at /usr/share/perl/5.20/parent.pm line 20.
BEGIN failed--compilation aborted at Bugzilla/MIME.pm line 14.
Compilation failed in require at Bugzilla/Mailer.pm line 20.
BEGIN failed--compilation aborted at Bugzilla/Mailer.pm line 20.
Compilation failed in require at Bugzilla/Auth.pm line 22.
BEGIN failed--compilation aborted at Bugzilla/Auth.pm line 22.
Compilation failed in require at Bugzilla.pm line 23.
BEGIN failed--compilation aborted at Bugzilla.pm line 23.
Compilation failed in require at /var/www/bugs.y-less.com/index.cgi line 15.
BEGIN failed--compilation aborted at /var/www/bugs.y-less.com/index.cgi line 15.
I'm sure it's not hard, it's just 2am here.
5) Related to above - tests. So we can prove bugs are gone. Consider using https://github.com/pawn-lang/YSI-Include...testing.md to write them (look up unit tests), and see here for examples: https://github.com/pawn-lang/YSI-Include...#L218-L227
6) The other big thing, the one we've been working hard on, is the code. This is where we will need the most help, though it is already well under way. However, right this minute it is not in a state suitable for general opening. If you are interested in this, and know C, tell us and we can move that forward.
7) I'm bad at graphics. We have some already, but more for promotion would be good.
8) Small modes. The examples that get bundled with a server. We need our own ones of those.
As I say, these are all little jobs that can be got on with while we sort out and organise the larger ones over the next few days.