Hi Luca,<br><br> Most of your thoughts are not valid for a wiki environment. Let me explain with examples:<br><ol><li>Videos would dominate life in future, and overtake the written instructions (wiki/pdf). <br>So we better plan for this medium.<br>
<br>It can easily be hosted on Youtube etc., by having a <b>Blender channel</b>, <br>(bidirectional links between Blender wiki and Youtube).<br><br>See examples: <a href="http://www.youtube.com/user/Harvard">Harvard University</a> and <a href="http://www.youtube.com/user/nptelhrd?blend=3&ob=4">IITs+IISc</a>, where huge series of lectures (spanning several HOURS on each subject) are hosted on Youtube, and linked from various departments. <br>
<br>It does not add any load to the Blender website. <br><br>Are you opposing this idea? why?<br> <br></li><li>About translations, my point was, we cannot plan for translations with just 3 people.<br>However, in wiki, we would not be blocking anyone from translating an existing page.<br>
Anyone is welcome to do it. He has to ask the Admin to put a new link on the home page.<br><br></li><li>I do not advocate taking screenshots manually, but if that is unavoidable, I can do it. <br>The idea is to make the other content-writers free to focus on the actual writing.<br>
BTW you talk about a "plan" to automate screenshots, but where is it actually?<br>Unless this is actually coming up soon, there is no point in waiting for it eternally-- I can go ahead and do it. Let it not be a bottleneck.<br>
<br></li><li>I have successfully uploaded screenshots first (using a predetermined naming convention), and then written the rest of the wiki. It is simpler, believe me. In fact, all icons would be readily available as individual files, so we can directly upload them to wiki without needing to take screenshots.<br>
<br></li><li>I do not see how the "wiki" and "sandbox" concepts mix. <br>The sandbox idea is from an old era: In a wiki, we simply go ahead and write what we want.<br>According to wiki principles, if someone does not like it, he can edit it further (There are NO reviews).<br>
Use discussion page to debate any point.<br><br>Further, what is the point of making a sandbox when there are 3 authors in total??<br>Surely we cannot have 3 horses and 30 jockeys? :)<br><br></li><li>Mont29 had proposed the TOC changes long ago.<br>
If anyone had to add any value, he should have done it by now. <br>How long should we wait, and why?? <br><br>Even if any objections come up later, we can simply shift the wiki pages later.<br>The idea of censorship and endlessly waiting for "approval" is just stifling.<br>
<br></li><li>For the wiki issues where you had "?", I'll answer with an <a href="http://www.den4b.com/wiki/Main_Page">example</a>.</li><ul><li>This wiki is NOT flat: It starts with a product-line, and then drill down in each product.<br>
Each product has topics and subtopics.<br>Its actual pages are arranged to mirror that structure.<br>In fact, the pages are also organized in virtual categories, which are used to fire PDFs.<br>(A given page can appear in multiple pdf books.)<br>
</li><li>Some Blender website pages are composed by single authors (They are not wiki).<br>My proposal is to treat all pages as part of wiki. <br>Let volunteers compose+edit all pages in a wiki.</li><li>New wiki pages can be created by simply creating a link in an existing page.<br>
This can lead to haphazard growth of the tree.<br>An Admin should check if the pages are placed in the right place.<br>For example, in the Renamer wiki, the author (Denis Kozlov) took care of this aspect.</li><li>Mediawiki itself provides a built-in backup; and a log of all changes. <br>
It also provides a diff tool to compare the pages, and accept/reject the changes.<br>So you can do rollback to any stage with just a click. Who says restoring is difficult?<br></li></ul></ol>-Narayan<br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup">
</div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style>