Will you post links to your blender channel<br><br><div class="gmail_quote">On Sat, Nov 13, 2010 at 6:06 PM, Roger Wickes <span dir="ltr"><<a href="mailto:me@rogerwickes.com">me@rogerwickes.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Sorry to have caused some ill will between people. But sticking to the<br>
facts,,,Regarding video, having authored hundreds of tutorial videos available<br>
for subscription and for free, and having watched tons, they can be good, but<br>
they can be bad and annoying, depending on how they are done, and what they<br>
are billed as versus what they actually deliver.<br>
<br>
Video is knowledge encapsulated in a moving visual form. That knowledge could<br>
be flawed and that is the disadvantage, since the user community cannot<br>
annotate or correct. However, it is powerful and plays a big part in the<br>
future. The knowledge management plan must speak to this and set up a<br>
framework whereby we:<br>
1. Identify the video that it even exists. There are thousands. It's too<br>
much for even two people to maintain a list. it needs to be crowdsourced.<br>
2. attribute the content of the video by audience and subject matter and<br>
blender version and whether it has audio and if so in which language, and<br>
whether it is free or if it costs or if it is packaged on a DVD somewhere and<br>
where it can be found or ordered.<br>
2a. Allow the community to either assign attributes (distribute the work)<br>
and grade it<br>
3. Provide a search engine so people can find knowledge, video<br>
specifically, by attribute, within this knowledge domain. "beginner spanish<br>
animation video". The search engine could be something hosted locally, or be a<br>
BoF kind of google/aggregator. for example, right now we have YouTube. doing<br>
the above query prefixed by "Blender tutorial" on youtube returned about 10<br>
results and referrals to 100 more. Video Aulas este es muy `util.<br>
<br>
><br>
> 1. Videos would dominate life in future, and overtake the written<br>
<div class="im">> instructions (wiki/pdf).<br>
> So we better plan for this medium.<br>
><br>
> It can easily be hosted on Youtube etc., by having a *Blender channel*,<br>
> (bidirectional links between Blender wiki and Youtube).<br>
><br>
</div>Blender Foundation has a YouTube channel, <a href="http://www.youtube.com/BenderFoundation" target="_blank">www.youtube.com/BenderFoundation</a>. It<br>
is awesome and growing by the day. So does David Ward, so do I.<br>
<br>
The wiki fully supports hosted video. Mindrones or maybe it was martin wrote<br>
us a nice little plugin. See my mocap tutorial as example of how the wiki can<br>
embed video quite nicely. Almost any other content engine can as well.<br>
<br>
> 2. About translations, my point was, we cannot plan for translations<br>
<div class="im">> with just 3 people.<br>
> However, in wiki, we would not be blocking anyone from translating an<br>
> existing page.<br>
<br>
</div>We can and do and must plan for foreign language translations, and facilitate<br>
them in a non-blocking manner.<br>
<br>
> 5. I do not see how the "wiki" and "sandbox" concepts mix.<br>
<br>
Wiki authors should use Sandbox as a temporary pre-release place for them to<br>
complete a logical unit of work, before moving it into production. We should<br>
not put half-baked garbage/outlines into the wiki, but as an author, I need a<br>
place to put my notes and outlines so that I can work on it from time to time.<br>
<br>
Our tools must support this concept that writing or documenting some knowledge<br>
may not be able to be accomplished all in one sitting by one person. The tools<br>
must support a person working over time, building and refining knowledge until<br>
it is ready for prime time. There must be at least a "development" and a<br>
"production" space for knowledge authors. It would be nice if it the tool<br>
supported a "testing" status, where the author wrote what they thought, but<br>
would like someone else to check their work. When you write a book, you have a<br>
technical editor that checks your work. They catch stuff before the book goes<br>
final. It's a good process, and our tool should support this kind of "test"<br>
space or connotation. An end user can use this knowledge at their peril, but<br>
should have comfort in knowing that "production" knowledge is good and<br>
accurate for the version it documents.<br>
<br>
regarding ideas and coordinating multiple people; I put in place the wiki user<br>
manual To Do list. I even documented the process and used the status<br>
templates. See the wiki for how it is supposed to work; basically a manual<br>
ticket system. Anyone can add items to be documented, anyone can grab an item<br>
and fix it directly, or make an edit and ask someone to check their work. It<br>
never caught on as a work management system; perhaps because it was manual or<br>
required you to be a wiki author or whatever. But, imho, Basically,<br>
identifying bugs and defects and missing knowledge should be crowdsourced into<br>
a bug-tracking system. We should allow the community to identify what<br>
knowledge it needs through some tool or system.<br>
<br>
Then the community of authors should be able to grab items they want to work<br>
on, and then close the bug when they commit the change...just like software.<br>
Right now, the blender code base is not managed that way for very good reason,<br>
but we do not need the same types of controls over knowledge content.....or do<br>
we? The plan needs to address the type and level of control over knowledge,<br>
and the knowledge acquistion process, and the maintenance process and workflow<br>
and specific tool use to support the process.<br>
<div><div></div><div class="h5">_______________________________________________<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><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Current theme song<br>I hope you die<br>Bloodhound gang<br><br>Willie Pierce<br><br>