<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Oct 2, 2008 at 11:19 PM, Sean Dague <span dir="ltr"><<a href="mailto:sdague@gmail.com">sdague@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Rob Smart wrote:<br>
> Random suggestion here ... anyone think it would be a good/bad idea to track<br>
> documentation on Mantis ?<br>
><br>
> By this I mean create a Mantis category for documentation, then people can<br>
> submit a bug report on there if they can't find enough info about something<br>
> they need.<br>
><br>
> Then we can use Mantis to track the state of the docs too, plus people can<br>
> raise defects against out of date/incorrect docs in a more visible way.<br>
<br>
</div>You over estimate how visible stuff in mantis is. :)</blockquote><div><br>Hehe point taken...<br>however, it is more visible and manageable than the wiki simply for the fact that new bug entries and fixed bug entries get posted in multiple locations. IRC and Twitter for a start.<br>
<br>There's also the recognition bonus for none code contributors i.e. "So and So added some useful documentation about X" seeing documentation updates like that might make other IRC/Twitter<br>listeners more inclined t goa nd look at the new entries or contrbute their own..<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
><br>
> Thoughts ?<br>
<br>
Do you mean for documentation in code, or in the wiki? If it's for the<br>
code, I think mantis is appropriate. If it's in the wiki I think there<br>
are better ways to do that.<br>
</blockquote><div><br>I meant documentation in the wiki. I'm open to suggestions of how to better track and request entries/changes on the wiki. However at the moment i feel documentation is lacking currently<br>and bringing the request/recognition mechanisms inline with those for code contribution may help.<br>
<br>The problem with normal wiki usage is that yes you can add comments on the comment pages but someone has to actively go and look for them. rather than doing a quick priority sort on documentation<br>in Mantis, plus the IRC updates help give peripheral vision of updates occuring.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
We just started using macros in the wiki like {{obsolete}} and<br>
{{content}} that help to tag parts of the wiki that need work. I owe a<br>
structural guideline for the wiki as well.<br>
<br>
It also turns out that because the template is so changed from the media<br>
wiki default a lot of people didn't realize <a href="http://opensimulator.org" target="_blank">opensimulator.org</a> was<br>
actually a wiki, and that they could edit it. I'm going to craft a new<br>
opensim theme that keeps the color scheme, and some of the graphics, but<br>
makes the layout look more like monobook in the hope that this helps get<br>
more people to participate.<br>
<div><div></div><div class="Wj3C7c"><br>
-Sean<br>
<br>
--<br>
Sean Dague / Neas Bade<br>
<a href="mailto:sdague@gmail.com">sdague@gmail.com</a><br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
<br>
</div></div><br>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br></blockquote></div><br></div>