Hi all,<br><br>We had a good meeting on IRC #blenderwiki today. Brecht posted the log earlier. <br>Next scrum will be Sunday morning/afternoon at the close of #blendercoders scrum (10 am CST?).<br><br>First of all, a big thanks to the old guard of reviewers for getting a lot of the required infrastructure and procedures developed. I hope there is no perception that we are undermining those efforts. What we are here to do is come up with a workable temporary solution while we are in a situation of a large backlog of un-reviewed contributions and no experienced reviewers.<br>
<br>We're not going to fix all problems at once. Today's scrum was just to set some 1-week goals to get the ball rolling.<br><br><i><b>We will be putting out a hit-list to docboard and blenderartists of a fraction of the un-reviewed pages each week. First one will be published tomorrow for us to devour.</b></i> <br>
Post a link to your un-reviewed contribution to have it added to the hopper.<br><br>Distilled from the IRC chat is a new trial procedure for contributing and reviewing:<br><br>(a) small changes are allowed by anyone <br>(b) bigger changes are allowed when reviewed by one other wiki contributor (admin or not)<br>
b.1 New contributors/reviewers can start by creating an account. <br> b.2 Terry Wallwork will hand-approve new accounts to avoid spam<br> b.3 For big changes, a small fraction of pages can be reviewed to ensure basic style compliance. <br>
The rest of the pages can be pushed to the manual with a box saying "This page has not been reviewed. Please help us make it better. Do not use this page to copy style for new pages."<br> with a link to style guide and how to get involved / in touch. <br>
b.4 If not admin, reviewer should at least have recently reviewed <a href=" http://wiki.blender.org/index.php/Meta:Guides/Style_Guide ">Style Guidelines</a><br> and are familiar with <a href="http://wiki.blender.org/index.php/Meta:Guides/Templates">templates</a> for formatting. We will try to have everyone's first review<br>
re-reviewed to ensure consistency.<br> b.5 Reviewers can use the Discussion tab to post review comments. Post to docboard when your review is done for re-review :) <br> b.6 We are going to try and organize a couple of week-long review-sprints to clear out the backlog. If we aren't making good progress by end of sept, then we'll have to open the doors to push live according to b.3. Changes can be reverted through the History tab available when you are logged in.<br>
(c) a few people pledge to look at recent changes and answer questions on bf-docdoard<br> c.1 We'd like to work towards having head reviewers for each section to keep the workloads light. However, it's not required. <br>
So far we have Jim doing BGE, meta-androcto doing addons, brecht and myself at large. We need at least another 4 core reviewers willing to contrib 2 hrs/wk at first to make this fly.<br><br><b><br>Optional Reading:</b><br>
<br>Fweeb mentioned that in addition to the style guide, we should have some templates of best practices to further promote a solid look-and-feel.<br>The current style-guide gives the form. This new guide might be more focused on content, pedagogy etc. I'd like to see a discussion on this get distilled and added as a link to the style-guide. Some general suggestions I'd make:<br>
<br>Use action phrases. Assume the user is following along with blender. Give activities that can be checked for results when possible.<br><br>Get to the punchline as quickly as possible, with a picture or <a href="http://wiki.blender.org/index.php/File:Animated_editing_particles_in_particle_mode.gif ">animation </a><br>
Show what the user will be able to do. Then go through the steps to get there.<br><br>Aim your page at a beginner level. This is especially important if you want your work reviewed quickly. If you provide procedures with high level descriptions of how to do things without following it with the sequence of UI steps to get there, your reviewer may get stuck or give up. Please provide a link to another part of the manual if it exists or supply the steps in detail yourself.<br>
<br clear="all"><br>-- <br><br>Kesten Broughton<br>President and Technology Director, <br>Solar Mobile Trailers<br><a href="http://www.sunfarmkitchens.ca" target="_blank">kesten@solarmobiletrailers.com<br>www.sunfarmkitchens.ca</a><br>
512 701 4209<br><div style="display:inline"></div><br>