STEP:Guide-Development Workflow

STEP Community Member Roles

STEP is a community-driven project. This means that the community at large is the mechanism by which STEP evolves. There are several "levels" of voluntary STEP-community membership:

• Administrators - STEP website maintenance and update management
• Anthologists - Senior community members trusted with maintaining the STEP Mandate
• Developers - Users assisting on particular development projects relating to STEP or the STEP websites
• Editors - These users have special wiki privileges
• Members - Registered site users
• Mod Testers - Committed to testing and/or validating at least one mod per STEP release
• Mod Authors - Members that are authors of any Skyrim mod
• Moderators - Site moderation and general administrative assistance
• Site Founders - Members of the original founding group of the STEP Community no longer active on the project

STEP Development

Synopsis

The STEP forums serve as the vehicle for STEP release development. Any registered site members may post a new thread in the Mod Suggestions (MS) Forum (posting instructions are displayed on the forum). These threads serve as the "catch-all" for information and feedback relating to the mod. Mods being actively considered for STEP will be stickied within the MS Forum. If a givem mod "passes", then its MS thread will be moved to the STEP Anthology Forum. Each mod withing the Anthology also has a corresponding STEP Wiki Page. The wiki pages directly feed the official STEP Guide via our custom Semantic Mediawiki infrastructure.

Thus, in order for the STEP Guide to remain current, it is imperative that this generalized workflow be maintained by the community. Certain parts of the current workflow are restricted to Administrators; however, most of the workflow is exposed to community Members. It is this functionality that is presented here along with the linear breakdown of the update workflow. Given that STEP is currently on a biweekly release schedule, it is important that the community help drive the process, as a few part-time administrators cannot maintain the entire workflow and all of the quality assurance that goes along with it.

Workflow Details

1. • This is a continuous process, and many mods currently exist in MS, so please search before posting!
   • Any mod can be posted in MS, but they must be of sufficient quality in order to be considered for STEP.
   • These threads contain community feedback pertaining to the mod.
2. • These mods should be fairly well researched by the poster.
   • Anyone posting in the Development Thread should be prepared to act as a Mod Tester for any mods being advocated or disavowed.
3. Administrators determine which mods in MS will be called out for testing based largely on mods called out by members on the Devel Thread.
   • Admin will sticky these mods in MS, appending the [ TESTING ] tag
   • Admin and knowledgeable community members will post some minimum criteria for testing on each testing thread OP.
   • It is expected that the community provide the mod testing detail that is requested in the OP (particularly the Devel Thread advocates).
   • A mod will remain in the testing phase until the minimum testing criteria have been met.
4. • Once tagged, each mod thread will remain stickied under MS until the scheduled release date.
   • Mod Testers or other advocates of [ ACCEPTED ] mods must CREATE THE CORRESPONDING MOD PAGE on the STEP Wiki PRIOR TO RELEASE.
   • Administrators will move mods that have completed testing either to the STEP Anthology or back into the general MS thread pool, depending on status.
   • These threads will continue to be used for posting as per usual.