Coh3n
2011-05-23 23:26:58
This is just going to be here as a reminder of the responsibilities/duties of an MSI Scripting Leader. It's more for new people that are brought in, but it'll always be here as a reference to who'd here now. :)
Forum-side
Programming-side
Cheers,
Coh3n
Forum-side
- The most important part: When you make (i.e. push to the main repository) create a new thread here! People like to know about the updates. Just look at previous threads to see how I did them. Of course they don't have to be like that, but they should outline what was changed. :)
- Promote MSI! Do whatever you can to get people involved. Whether it be using/testing or developing. I think the best advertising method for us is to have something in our signatures.
- Threads in the Bugs and Suggestions forums should always have a prefix, so be sure to check them and keep them updated.
- Remember, you're a representative of MSI. You're looked at as elite scripters, but don't let it go to your head. Be humble and helpful. :)
Programming-side
- Currently, only a few people (you know who you are) are able to push to the main MSI git repository. This means that everyone else needs to fork it and send pull requests when you feel your repository is ready to be merged (after testing of course).
- If you have access, you should keep up with current pull requests and merge them if you feel they're ready. I HIGHLY suggest merging the pull request locally and make sure it compiles before merging on github (i.e. don't click the "Automatically merge" button on github unless you're 200% sure).
- You're expected to do some coding at one time or another. You aren't expected to do a lot as we know everyone has lives, so don't feel obliged to write a ton of code. There is always a list of small things that can be done. Spending 10 minutes here and there to add something in the progress report goes a long way.
- You're also expected to give your opinion on any active discussions within MSI about things that may be added or changed.
- You should always keep up with bug reports as best as possible, and it's probably a good idea to periodically check the Public Scripts threads (I subscribed to them) because often people post bug reports there as well.
- And of course, the MSI Core TO-DO List.
Cheers,
Coh3n