I am interested in finding someone that would be interested in serving as our Plugins Czar. This person should be 100% fluent in how plugins work with MQ, should have a working knowledge of C++ and the MQ code in general, and should have contributions on the boards in the past that can verifiy this fact. This person must also be a frequent peruser of the message boards and be willing to keep up with what's new and what's changed with plugins. This person must be a VIP member in order to have access to those plugins as well. I would also like this person to be on the MQ irc channel regularly. In other words, I'm looking for someone to be for plugins what Wassup is for the readme.
The purpose of this is that I would like to have someone in charge of the plugin forums here on the messageboards and be a 'goto' for me when I have questions about ANY plugins. This person would be a moderator of the plugin forums and would insure that there is a uniform way that plugins are posted (ie, date/names/versions all the same in the subject lines) and possibly a 'sticky' system for plugins that are working vs. plugins that are not working. This person would also talk to me when they believe there are plugins that should definately be included in the MQ2 zip file (no plugin is guaranteed that right) ..and, if so, they will be in charge of making sure that all MQ released plugins are updated regularly by sending me new files for cvs. This person will, in essense, be a leader in the realm of plugins and be the pipeline between me as a dev, and the general MQ community (and those that submit plugins in specific). I also would want this person to make sure that all plugins are sufficiently documented by their authors and work with Wassup (our master of the readme/documentation) on how best to organize said documentation.
New Plugins Czar: koad!
Moderator: MacroQuest Developers
New Plugins Czar: koad!
Last edited by Amadeus on Sat Sep 04, 2004 12:07 pm, edited 6 times in total.
koad will now serve the role on the MQ project as the Plugins Czar (ie, one of Amadeus' assistants). This is a 'hire' on my part; therefore, any future comments/complaints/etc.. should go to ME.
Some of the things I've asked of him:
1. Go through the plugin boards and clean them the hell up. Sticky the good stuff so that we can find it.
2. Come up with a documentation scheme for all plugins that will include documentation within the source as well as a special document (ie, readme.txt or readme.html) that will be included with each plugin that will describe it's usage, etc..
2a. Come up with a scheme for thread subject lines in the plugins forums. I want to be able to know the name of the plugin, the version or date it was last updated, etc.. at the least.
3. Determine which plugins should be included in the zip file and keep those updated for me.
4. Regularly patrol the plugins boards and make sure that bugs, etc.. are fixed in the released plugins in the zip file.
5. Work with wassup to make sure that there is enough documentation related to plugins and/or plugin writing in the readme. (It might be nice to have a couple plugin 'walkthroughs' in the readme.)
My email to him was a lot more specific and included a few more items..however, I'm sure you get the idea :)
Some of the things I've asked of him:
1. Go through the plugin boards and clean them the hell up. Sticky the good stuff so that we can find it.
2. Come up with a documentation scheme for all plugins that will include documentation within the source as well as a special document (ie, readme.txt or readme.html) that will be included with each plugin that will describe it's usage, etc..
2a. Come up with a scheme for thread subject lines in the plugins forums. I want to be able to know the name of the plugin, the version or date it was last updated, etc.. at the least.
3. Determine which plugins should be included in the zip file and keep those updated for me.
4. Regularly patrol the plugins boards and make sure that bugs, etc.. are fixed in the released plugins in the zip file.
5. Work with wassup to make sure that there is enough documentation related to plugins and/or plugin writing in the readme. (It might be nice to have a couple plugin 'walkthroughs' in the readme.)
My email to him was a lot more specific and included a few more items..however, I'm sure you get the idea :)