<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Hi All,<BR>First a big thanks to mindrones and the other team members for proposing what (I think) is <br>essentially a sound and useful structure for updating the Blender wiki.<BR> <BR>I would like to suggest a couple of changes (mostly simplifications) to the structure proposed<BR>in <a href="http://wiki.blender.org/index.php/Meta:Wiki_Tasks/Review_2.6_Manual">http://wiki.blender.org/index.php/Meta:Wiki_Tasks/Review_2.6_Manual</a>:<BR> <BR>1) Writers:<br> Include a column for "Writers", and ask anyone who is writing edits for a particular chapter to<br>enter their name in the list (this will make it clear to everyone on the team who is working<br>on what chapters).<BR> <BR>2) Swap the names "Editor" and "Reviewer".<br>I suggest that the Editor for a given chapter is the person who is responsible to the core team <BR>for this chapter. He/she can delegate some of the reviewing to other Reviewers who have<br>specialist knowledge of this Blender area; but always (as you propose) the named<br>Editor has ultimate responsibility for this chapter. I think this name-change would be more<BR>in tune with other organisations, and so simplify both control structure and workflow.<BR> <BR>3) Developers.<br>I dont quite understand the role of Developers in updating the wiki. Although they can (and <br>frequently do) help writers in documenting Blender, usually they only provide a <br>supporting role in wiki construction. They should NOT be able to make changes without asking<br>permission from the reviewer (but of course they would be welcome to work as writers, or<BR>review-team members and so suggest changes to the Editor!) <BR> <BR>I would therefore suggest removing the column on Developers, but add a note linking to<br>the Development module owners list <a href="http://wiki.blender.org/index.php/Template:ModulesOwners">http://wiki.blender.org/index.php/Template:ModulesOwners</a>.<BR> <BR>I hope this is seen as constructive criticism of a basically very useful document.<BR> <BR>Regards, Jim<BR> <BR><br> <BR><div>> From: bf-docboard-request@blender.org<br>> Subject: Bf-docboard Digest, Vol 85, Issue 2<br>> To: bf-docboard@blender.org<br>> Date: Fri, 16 Mar 2012 12:00:01 +0100<br>> <br>> Send Bf-docboard mailing list submissions to<br>> bf-docboard@blender.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://lists.blender.org/mailman/listinfo/bf-docboard<br>> or, via email, send a message with subject or body 'help' to<br>> bf-docboard-request@blender.org<br>> <br>> You can reach the person managing the list at<br>> bf-docboard-owner@blender.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Bf-docboard digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Manual Wiki Team Call (mindrones)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Thu, 15 Mar 2012 20:59:24 +0100<br>> From: mindrones <mindrones@gmail.com><br>> Subject: [Bf-docboard] Manual Wiki Team Call<br>> To: Blender Documentation Project <bf-docboard@blender.org><br>> Message-ID: <4F624A1C.9060300@gmail.com><br>> Content-Type: text/plain; charset=ISO-8859-1<br>> <br>> Hi all,<br>> <br>> after some discussions in #blenderwiki, we want to propose the workflow<br>> described below and make a call to build a proper Manual Wiki Team.<br>> <br>> We need to see if we have enough people in each different role to start<br>> publishing proposed pages at<br>> http://wiki.blender.org/index.php/Meta:Wiki_Tasks/Review_2.6_Manual<br>> <br>> So for those that are interested to partecipate, please just propose<br>> yourself here or in #blenderwiki :)<br>> <br>> <br>> ROLES<br>> =====<br>> <br>> For each chapter, we would like to cover the roles explained below.<br>> <br>> * Reviewers<br>> These people have to have good understanding of Blender and<br>> of the Wiki. They can edit, review and decide when a proposed<br>> page is ready to go public. The decision should be based on<br>> the quality of:<br>> - contents<br>> - formatting<br>> - language<br>> <br>> Apart from doing big changes in the Manual structure, a Reviewer<br>> can work without asking permission about his actions, but he/she<br>> takes responsibility for the manged chapter.<br>> <br>> He has to keep good communication with the core of admins,<br>> possibly in #blenderwiki, see<br>> http://wiki.blender.org/index.php/Meta:Wiki_Team#Core<br>> <br>> Right now the only Reviewers we have are the ones listed at:<br>> http://wiki.blender.org/index.php/Meta:Wiki_Team#Main_Reviewers<br>> <br>> We need to find more, but these will eventually come with time.<br>> <br>> If someone with good wiki + blender skills is reading, just head up!<br>> Roger and past wiki contributors come to mind, but feel free to talk.<br>> <br>> * Editors<br>> These people can edit proposed pages and review them<br>> but have to ask the reviewer for publishing.<br>> <br>> * Developers<br>> These people can give good advice to editors and reviewers<br>> on technical aspects of the documented features.<br>> Developers can edit Manual pages without asking permission,<br>> but if they prefer to do so, they can ask Reviewers or<br>> Editors for help.<br>> <br>> Modules owners and members are defined at:<br>> http://wiki.blender.org/index.php/Template:ModulesOwners<br>> <br>> * Writers<br>> Everyone can be a wiki writer, but if not an editor or more,<br>> he/she can write in own User space and suggest own edits as<br>> we do now.<br>> <br>> * (Skilled Artists)<br>> Also, it would fantastic to have skilled artists mentoring<br>> editors and reviewers and giving suggestions about missing<br>> parts and possible enhancements (probably too much to ask).<br>> <br>> <br>> WORKFLOW<br>> ========<br>> <br>> - Basically everyone is a Writer and can suggest edits in his/her own<br>> user page<br>> <br>> - After some good work in wiki, a Writer can become an Editor, so that<br>> he can review other people work, and help Reviewers to get pages published<br>> <br>> - After some good work, Editors can become Reviewers.<br>> <br>> - Reviewers can help Developers when these don't have time or enough<br>> wiki skills to document own feature.<br>> <br>> - Ideally a Reviewer manages his/her own chapter-team and can<br>> potentially assign tasks to editors if he find some.<br>> <br>> Basically we believe that establishing a good hierarchy and using<br>> delegation well, we can distribute work and keep the Manual up to date<br>> with less effort.<br>> <br>> <br>> <br>> Regards,<br>> Luca<br>> <br>> _____________________________<br>> <br>> http://wiki.blender.org/index.php/User:Mindrones<br>> http://www.mindrones.com<br>> <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> Bf-docboard mailing list<br>> Bf-docboard@blender.org<br>> http://lists.blender.org/mailman/listinfo/bf-docboard<br>> <br>> <br>> End of Bf-docboard Digest, Vol 85, Issue 2<br>> ******************************************<br></div> </div></body>
</html>