<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello Aaron,</p>
<p>I'm not sure if that worth it:<br>
- The amount of work creating the tasks vs. actually fixing it
right away.<br>
- Plus the work managing the tasks<br>
- Most important issue: When a todo is fixed, one would also have
to check if the task can be closed.<br>
Sometimes that won't happen and that will lead to a lot of
unclosed tasks.<br>
- The board gets less clear: A solution could be to add a special
category/column for them.<br>
- I'm not optimistic that the #easyToFix tasks will help.</p>
<p>IMO the board works best for keeping track on bigger tasks, but
(almost) nothing is worth kept untried to find new contributors.<br>
</p>
<p>What I'm thinking about for a while now is expanding the "<a
moz-do-not-send="true"
href="https://docs.blender.org/manual/en/dev/about/contribute/editing.html">Editing
the Manual</a>" page with an guide based on FAQs:<br>
1. Where to find info about Blender? - Release Notes, Wiki, Blog,
etc.<br>
2. Where to start? - small todo, section most familiar with.<br>
3. What kind of content fits/is wanted? - no classic tutorials.<br>
</p>
<p>More content has the risk that it appears too overwhelming.<br>
A solution could be to be to have it under an Appendix headline or
even a separate file in the style guides folder.</p>
<p>Tobias</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 01.12.2017 um 19:56 schrieb Aaron
Carlisle:<br>
</div>
<blockquote type="cite"
cite="mid:CAEX7TpXJoDmGO10_gqOs8TC72q2ECnZe_kk=DeTb1kDDEe7HOg@mail.gmail.com">
<div dir="ltr">Thanks Tobias for doing this. Now that we know
where all the todos are
<div>and from when we should spit these off into different tasks
on Phabricator.
<div>These tasks should explain what the todo is about, and
where to find it.</div>
<div>Having these task can help new contributors picking up
small tasks</div>
<div>that they can work on.</div>
</div>
<div><br>
</div>
<div>Thanks again,</div>
<div><br>
</div>
<div>Aaron Carlisle</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Nov 23, 2017 at 11:47 AM,
Tobias Heinke <span dir="ltr"><<a
href="mailto:heinke.tobias@t-online.de" target="_blank"
moz-do-not-send="true">heinke.tobias@t-online.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">arg, upps
mis-click :( sry -- the whole mail:<br>
<br>
Hi all again,<span class=""><br>
<br>
I've recently tagged some of the ToDos with the version
when the feature was added.<br>
</span> This can be used for statistics, to easier find them
in the release notes and prioritization.<br>
I did this based on the release notes. Which worked
surprisingly well. I couldn't tag only 1/3 (unknown) -<br>
which not means they could be tagged at all, but it would
take the ~same time as actually fixing them :)<br>
I used qualifiers like <, >, ~ for todos that couldn't
be dated accurately by me (worst case: first mentioned in a
bug fix) making the statistic a bit inaccurate (aren't that
many).<br>
The todos from the Wiki are split from the rest.<span
class=""><br>
<br>
I also sorted them into categories:<br>
</span> add: general introductory text, the others are (I
hope) are self explanatorily, like re/move, rewrite, etc.<br>
<br>
With the 2.8 release we can draw a line by marking all todos
pre 2.8 (<2.79).<br>
<br>
Cheers,<br>
Tobias<br>
<br>
<br>
STATISTICS<br>
<br>
all: 469<br>
<br>
version stamp total: 153<br>
2.4: 8<br>
2.5: 3<br>
2.6: 84<br>
2.70 - 3: 23<br>
2.74 - 6: 17<br>
2.77: 1<br>
2.78: 15<br>
2.79: 1<br>
<br>
unknown total: 101<br>
<br>
add: 70<br>
add images: 3<br>
add example: 44<br>
<br>
remove: 3<br>
move: 11<br>
rewrite: 2<br>
error: 2<br>
<br>
Wiki total: 71<br>
add image: 5<br>
add example: 17<br>
<br>
rewrite: 2<br>
review: 36<br>
<br>
other: 33<br>
<br>
<br>
Per Chapter from total<br>
game: 48<br>
internal: 33
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
______________________________<wbr>_________________<br>
Bf-docboard mailing list<br>
<a href="mailto:Bf-docboard@blender.org" target="_blank"
moz-do-not-send="true">Bf-docboard@blender.org</a><br>
<a
href="https://lists.blender.org/mailman/listinfo/bf-docboard"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.blender.org/mail<wbr>man/listinfo/bf-docboard</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr"><span style="color:rgb(153,153,153)"><span
style="color:rgb(0,0,0)">Aaron Carlisle</span><br>
</span>
<div><span style="color:rgb(153,153,153)"><br>
Picture taker | Bit cruncher | Pixel pusher | Document
writer | Artist<br>
</span></div>
<div><span style="color:rgb(153,153,153)">Project
administrator for the Blender 3D Documentation Project</span></div>
</div>
</div>
</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="https://lists.blender.org/mailman/listinfo/bf-docboard">https://lists.blender.org/mailman/listinfo/bf-docboard</a>
</pre>
</blockquote>
<br>
</body>
</html>