<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Agree, count on me. I've some time
again after some really busy months and I'd like to be back on
this topic asap<br>
<br>
Michelangelo aka magicland<br>
<br>
El 25/01/2013 15:37, Nkansah Rexford escribió:<br>
</div>
<blockquote
cite="mid:CAKt11bV0pm_1Comj+6S=E7+Co3Qqh1=j1siFVYBbaz74baV02Q@mail.gmail.com"
type="cite">
<p>I think I'm cool with Ton's point 1. The idea of admins are a
good thing</p>
<p>And as regards the old docs about 2.5x, taking them away is a
nice thing too. </p>
<p>Some weeks ago I signed up to help o that but got crashed up
with work.</p>
<p>Will get back to it as soon as possible</p>
<div class="gmail_quote">On Jan 25, 2013 2:29 PM, "Ton Roosendaal"
<<a moz-do-not-send="true" href="mailto:ton@blender.org">ton@blender.org</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
Lots of activity on this list! I can't be involved daily
unfortunately, but it's a good practice for open/free projects
to facilitate and empower the people who do the actual work.
:)<br>
<br>
I would like to come back to a proposal I sent out some months
ago. Text copied below. Keep reading, there's also more stuff!<br>
<br>
1) Admins<br>
<br>
We could re-establish here a similar structure as we tried in
past - and what we do for the developers; appoint and empower
an admin board of 3 to 5 people.<br>
<br>
The admins will typically not have to do a lot, but will help
defining decisions (when the team has no consensis) and be an
inspiring & positive force to make sure Blender's wiki
keeps being cool to work on! The admins can also be
representing wiki to other teams (to BF, at <a
moz-do-not-send="true" href="http://blender.org"
target="_blank">blender.org</a>, conferences, etc).<br>
<br>
In no way this is meant as a special status, nor is it showing
more appreciation as for the other volunteers; the roles are
there to make sure everyone in the wiki team can function
optimal.<br>
<br>
Based on current activity and what I've been advised, I
propose:<br>
<br>
Admins:<br>
Kesten Broughton<br>
Brendon 'meta-androcto' Murphy<br>
Ivan 'greylica' Paulos Tomé<br>
<br>
Other tasks:<br>
Dan McGrath can assist as system admin<br>
Francesco Siddi as graphics designer (skins, layout)<br>
<br>
All open for discussion or feedback.<br>
<br>
2) Wiki focus<br>
<br>
- Cleanup of old docs<br>
<br>
Since 2.50 we've keept most of the UI and features compatible
though, and that's not going to change for 2.6x versions
either. Also plans for 2.7x and later might not going to
change Blender as much as we had for 2.5.<br>
<br>
For that reason, a first simplification of wiki would be kick
out (hide) old docs. The introduction of separate 2.5 and 2.6
tagged docs is confusing too. A doc is either 'current' or
'outdated'.<br>
<br>
- Limit structure to minimum<br>
<br>
Formatting guidelines and templates and fancy wiki features
should help editors, to make work on wiki more pleasant,
accessible, and efficient (in that order :).<br>
We can only get a good wiki with a large and enthusiast team.
Add structure and conventions only as a means to manage cases
when too much user activity is requiring it.<br>
<br>
- Wiki is just a wiki<br>
<br>
A good doc is a bare-bones, giving a simple and understandable
description of what a function in Blender does, and how to use
it. Just like how you end up on wikipedia looking up a fact,
Blender wiki is just our collective memory where you find
stuff.<br>
Ideally you could just land on a page via a button tip in
Blender.<br>
<br>
Secondary - maybe kept separate - tutorials can get space too.
But I would suggest to limit that.<br>
<br>
3) Blender Foundation support<br>
<br>
We do get donations and some sponsoring in, very regular even.
I'm still struggling with all expenses though, and my
preference is to (also) keep our development support at a high
level.<br>
<br>
I'm always open for ideas how to (financially) support work
for our docboard team though. This could also be via book
contracts (either BF publishing or a 3rd party publisher).<br>
<br>
<br>
Thanks,<br>
<br>
-Ton-<br>
<br>
------------------------------------------------------------------------<br>
Ton Roosendaal Blender Foundation <a
moz-do-not-send="true" href="mailto:ton@blender.org">ton@blender.org</a>
<a moz-do-not-send="true" href="http://www.blender.org"
target="_blank">www.blender.org</a><br>
Blender Institute Entrepotdok 57A 1018AD Amsterdam The
Netherlands<br>
<br>
_______________________________________________<br>
Bf-docboard mailing list<br>
<a moz-do-not-send="true"
href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
<a moz-do-not-send="true"
href="http://lists.blender.org/mailman/listinfo/bf-docboard"
target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Bf-docboard mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a>
<a class="moz-txt-link-freetext" href="http://lists.blender.org/mailman/listinfo/bf-docboard">http://lists.blender.org/mailman/listinfo/bf-docboard</a>
</pre>
</blockquote>
<br>
</body>
</html>