<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Greg,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thanks for the welcome. I’m glad to see a project management tool like Phabricator in use—especially one with the ability to set priorities and create sub-tasks.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I’ll take the role of reviewing the submits on the commit page like you suggested, maybe at the end of each month for starters and adjust frequency depending on work-load.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I’ll also review what has been done already and who’s active to see if there is an area where I can lend some help, as well as catching up on past discussions to the docboard distro to get oriented to the team’s current mindset.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>v/r,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Michael Fink<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>BnBGobo99<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></a></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> bf-docboard-bounces@blender.org [mailto:bf-docboard-bounces@blender.org] <b>On Behalf Of </b>Greg Zaal<br><b>Sent:</b> Monday, January 19, 2015 4:06 AM<br><b>To:</b> Blender Documentation Project<br><b>Subject:</b> Re: [Bf-docboard] Being involved In documentation<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><div><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Hey Michael,<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>Thanks for putting that together! I'm glad there's someone with your experience willing to help us :)<br><br>I think for now it is best to keep using our current system of review and task management ('Phabricator', here's the <a href="https://developer.blender.org/project/view/53/" target="_blank">doc project</a>) - the only thing it doesn't currently do is keep track of the current status of the project - though this can easily be added in the project description per-chapter.<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>At the moment, Campbell, Francesco and I are handling project management - though Campbell and Francesco are also busy with all sorts of other Blender projects, and I've technically been appointed as 'documentation coordinator' which involves both writing documentation myself and helping/finding others to write with us.<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>As for the intent/goal of this project - my impression is that it is "make the manual less crappy" ;) We don't have the man power to rewrite the whole thing, but the idea is to have at least one person responsible for each chapter of the manual and let them do whatever they want in order to make it better (be it fixing and updating it, or rewriting it entirely). Personally I plan to fix and check the legacy parts of the Render chapter (the old render engine), but rewrite the subsection for Cycles mostly from scratch.<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>Any suggestions you have for how we/I can manage this project better would be much appreciated!<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>And if you'd like to check our spelling and grammar, the quickest way would be to watch the <a href="https://developer.blender.org/diffusion/BM/history/trunk/blender_docs">commit page</a>, click on the commit numbers on the left (e.g. <a href="https://developer.blender.org/rBM55">rBM55</a>) and add a comment at the bottom of the page. The author of the commit will get an email about your comment and then fix the problem in a new commit.<o:p></o:p></p></div><p class=MsoNormal>Cheers,<br>Greg<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 17 January 2015 at 03:57, Michael Fink <<a href="mailto:bunnie0515@yahoo.com" target="_blank">bunnie0515@yahoo.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>Hi team,<br><br>Sorry for jumping on my own email--after reading my message I fear it may have come off as "here is this tool you've never seen before that I think you should use but I don't want to be the one in charge of maintaining it." Especially since my name has never appeared in a discussion reply before.<br><br>If the review or a similar discussion-&-task-focusing-tool is implemented to help guide and facilitate project management, I'm more than happy to do the data entry and coordination with the task owners and project manager(s) for that tool.<br><br>I'm happy to mentor and asist the person (or persons) placed in a project manager position if we go that route (which I think would be wise). I just don't think I can do justice to you all 'the' project manager.<br><br>Also, for being involved in the documentation--since I do not use Blender much I am not much help in drafting new content, but I volunteer my services for:<br>1. QC'ing (quality control for grammar, spelling, etc.)<br>2. Screenshots/video grabs of certain functions or elements. (This could be useful for somebody who has written a good text article but needs somebody to take the time and do the associated screenshots or video grabs.<br><br>Just let me know what tasks and pages I can help with, or if the review (or similar process) is adopted how I can help modify it to work best with the team flow.<br><br>If you haven't had an opportunity to take a look at the review process proposal, the files can be accessed here:<br> PDF: <a href="https://www.dropbox.com/s/lwu6dhdn9hmcw63/Blender%20Documentation%20Project%20Review%20%28proposal%29.pdf?dl=0" target="_blank">https://www.dropbox.com/s/lwu6dhdn9hmcw63/Blender%20Documentation%20Project%20Review%20%28proposal%29.pdf?dl=0</a><br> PPTX: <a href="https://www.dropbox.com/s/pcorrecirwi9dos/Blender%20Documentation%20Project%20Review%20%28proposal%29.pptx?dl=0" target="_blank">https://www.dropbox.com/s/pcorrecirwi9dos/Blender%20Documentation%20Project%20Review%20%28proposal%29.pptx?dl=0</a><br><br><br>Thank you,<br>Michael Fink<br>BnBGobo99<br><br><br><br>--------------------------------------------<br>On Thu, 1/15/15, Michael Fink <<a href="mailto:bunnie0515@yahoo.com">bunnie0515@yahoo.com</a>> wrote:<br><br> Subject: Re: Being involved In documentation<br> To: "Blender Documentation Project" <<a href="mailto:bf-docboard@blender.org">bf-docboard@blender.org</a>><br> Date: Thursday, January 15, 2015, 7:26 PM<o:p></o:p></p><div><div><p class=MsoNormal><br> Hello team,<br><br> I know there has been a flurry of email traffic lately, so<br> I'll try to keep this one brief.<br><br> I was surprised that nobody stepped up during a call for<br> assistance that was made recently (I believe Campbell noted<br> this in one of the emails, but I'm afraid I lost track of<br> the conversations). It made me wonder how many folks<br> are on the mailing list vs how many folks participate? <br> This is a curiosity question, not a shaming one. I've<br> only made a single contribution to the wiki and it was just<br> a minor correction to another person's much more involved<br> effort, so I myself can't say I have been active either.<br><br><br> The point of this email: it was mentioned that we<br> needed a Project Manager to lead this effort. I am not<br> volunteering myself as I will not be able to devote the<br> attention the Bf-docboard team deserves, but I am very<br> earnest when I say that I am more than happy to help mentor<br> the process. (My credentials: I have been a Flight<br> Chief for the US Air Force leading teams of 100+ individuals<br> from all services and a wide range of ranks. I have<br> been a Superintendent of a Wing-level directorate<br> responsible for planning and programming for 4,000 Airmen<br> and directly managing a $19,000 annual budget and $20K in IT<br> assets (not large, but sizable enough). My job is<br> Project Management, but not software project management or<br> software development. However, I am familiar with<br> Agile methodology, Six Sigma, AFSO 21 as well as the more<br> common "waterfall" way of doing things.)<br><br> I have built a template "Review" process. The .pdf<br> link is below as well as the .pptx--you are free to use this<br> document if the team choses (use the slide master to remove<br> my name and add the name of the person building the<br> deck). We have successfully used this process for<br> several years to guide multi-million dollar projects<br> impacting thousands of people across the globe.<br><br> PDF: <a href="https://www.dropbox.com/s/lwu6dhdn9hmcw63/Blender%20Documentation%20Project%20Review%20%28proposal%29.pdf?dl=0" target="_blank">https://www.dropbox.com/s/lwu6dhdn9hmcw63/Blender%20Documentation%20Project%20Review%20%28proposal%29.pdf?dl=0</a><br> PPTX: <a href="https://www.dropbox.com/s/pcorrecirwi9dos/Blender%20Documentation%20Project%20Review%20%28proposal%29.pptx?dl=0" target="_blank">https://www.dropbox.com/s/pcorrecirwi9dos/Blender%20Documentation%20Project%20Review%20%28proposal%29.pptx?dl=0</a><br><br> It is useful for:<br> (1) Spurring discussion and ideas,<br> (2) Solidifying those ideas and discussion points into<br> actionable tasks,<br> (3) Providing clear direction for those that are responsible<br> for performing (or delegating) those tasks,<br> (4) Providing a method for updates and recommendations on<br> existing tasks,<br> (5) Focusing a discussion onto a single vision and effort,<br> (6) and documenting progress, identifying trends, and<br> adjusting effort quickly.<br><br> The "Review" does take time to update and build, but by<br> consolidating tasks and inputs into a single document, it<br> does help create a helpful overview and guiding document to<br> manage the project--not just for the project leaders, but<br> for all participants. When we do these reviews, we<br> consolidate inputs from as many as 30 offices and hold<br> meetings to discuss the inputs and adjust focus or<br> re-allocate assets (manpower, money, etc). This is<br> much more efficient than holding 30 different discussions,<br> each with a meeting and side tasks--resulting in duplication<br> of effort, starving some offices while overfeeding others,<br> etc. I think this is the best way to guide and lead a<br> project of this undertaking.<br><br> Once the Project's goal is met (or solidly on track), the<br> review process can end. This is not meant to be a<br> permanent fixture, but a simpler "metric" or "stoplight"<br> document can take its place if desired.<br><br> Please let me know if you have questions on how this might<br> help the project. I am not knowledgeable on software<br> (although I do play with HTML/PHP/SQL/etc), and I don't use<br> Blender as much any more, but I am passionate about the<br> community and what Blender represents, and I hope this is<br> somewhat useful.<br><br> Thank you for reading, and sorry for the long-windedness.<br><br> v/r,<br> Michael Fink<br> BnBGobo99<br><br><br>_______________________________________________<br>Bf-docboard mailing list<br><a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br><a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>