I am interested in finding someone that would be interested in serving as our Macros Czar. This person should be 100% fluent in the macro language of MQ2 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 macros. This person must be a VIP member in order to have access to those macros. 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 macros what Wassup is for the readme.
The purpose of this is that I would like to have someone in charge of deciding which macros should be included in the release of MQ2 and keep them constantly updated both with what's new and with bug fixes. I think that the zip file should contain ALL of the most useful and bugfree macros in a directory structure that makes sense. I also would want this person to write up documentation for all the macros that are included in the zip and work with Wassup (our master of the readme/documentation) on how best to organize said documentation.
New Macros Czar: PhoenixZorn!
Moderator: MacroQuest Developers
New Macros Czar: PhoenixZorn!
Last edited by Amadeus on Sat Sep 04, 2004 12:07 pm, edited 4 times in total.
PhoenixZorn will now serve the role on the MQ project as the Macro 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 macro 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 macros so that it is easy to figure out the usage of a macro by simply reading the macro file itself. (This will most likely be done via comments). (Note: I also would like macros to have version numbers or dates.)
2a. Come up with a scheme for thread subject lines in the macro depot. I want to be able to know the name of the macro, the version or date it was last updated, etc.. at the least. There are a couple of really good examples already in the forum -- let's just make them all that way.
3. Determine which macros should be included in the zip file and keep those updated for me.
4. Regularly patrol the macro help boards and make sure that bugs, etc.. are fixed in the released macros in the zip file.
5. Work with wassup to make sure that there is enough documentation related to macros and/or macro writing in the readme. (It might be nice to have a couple macro 'walkthroughs' in the readme.)
6. Go through the "Macros - Pre Data (Params)" boards and move the shit that's outdated to the 'outdated macros' boards ...and delete the threads/macros that have already been converted and are now listed in the "Macro Depot 3.0" forum. I would like to be able to get rid of the "Macros - Pre Data (Params)" boards within the next month....it's cluttering the main page.
I would like to have new macros in the zip by the oow patch day, etc...
Some of the things I've asked of him:
1. Go through the macro 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 macros so that it is easy to figure out the usage of a macro by simply reading the macro file itself. (This will most likely be done via comments). (Note: I also would like macros to have version numbers or dates.)
2a. Come up with a scheme for thread subject lines in the macro depot. I want to be able to know the name of the macro, the version or date it was last updated, etc.. at the least. There are a couple of really good examples already in the forum -- let's just make them all that way.
3. Determine which macros should be included in the zip file and keep those updated for me.
4. Regularly patrol the macro help boards and make sure that bugs, etc.. are fixed in the released macros in the zip file.
5. Work with wassup to make sure that there is enough documentation related to macros and/or macro writing in the readme. (It might be nice to have a couple macro 'walkthroughs' in the readme.)
6. Go through the "Macros - Pre Data (Params)" boards and move the shit that's outdated to the 'outdated macros' boards ...and delete the threads/macros that have already been converted and are now listed in the "Macro Depot 3.0" forum. I would like to be able to get rid of the "Macros - Pre Data (Params)" boards within the next month....it's cluttering the main page.
I would like to have new macros in the zip by the oow patch day, etc...