<div dir="ltr"><div>Greets all,</div><div><br></div><div><br></div>First I'd like to appreciate the team for all their efforts and continued work on this massive unfolding project and ginormous undertaking. It's been interesting for me to feel the dynamic of looking from within a project outwards and feel some of the projected high expectation and pressure from users who don't understand what is involved with a project like this. Very cool perceptual exercise to participate in. Thank you for the trust in the responsibilities that you've bestowed to me. <div>
<br></div><div>Second this email got a little long so I am breaking it up in to 3 chunks and sending it staggered so that they get read :) Thanks for bearing with me. I hope to present a proposal that makes sense and appeals toward practicality and not over-sophistication and tech-blingy-ness.</div>
<div><br></div><div>As we approach the 1.5 release (BTW, very exciting) it would be really useful (at least for me) to open for discussion some possible infrastructure improvements. Currently we coordinate things via the Mediawiki which as a medium has it's strengths and weaknesses, in this case less than ideal for the many emerging real-time coordination scenarios. Do not get me wrong, no major complaints I'm just the noticing limitations of the technology (another glaring one is document obsolesence - there are overwhelmingly many many pages that are obsolete and in many different languages...yikes). </div>
<div><br></div><div>Nevertheless, it's use is _undeniably_ important. The reason I bring the Wiki up is because of it's utility. Specifically in order to facilitate better efficiency with bug fixing and organizing Mantis BT, it would therefore be worthwhile to consider implementing a specific Mediaiwki plugin for mantis: </div>
<div><br></div><div>## <a href="https://www.mediawiki.org/wiki/Extension:Mantis">https://www.mediawiki.org/wiki/Extension:Mantis</a> ## </div><div><br></div><div>An example page that shows how this extension would save a lot of time formatting and more time bug testing is: <a href="http://wiki.scribus.net/canvas/Bugs_to_be_Buried">http://wiki.scribus.net/canvas/Bugs_to_be_Buried</a> </div>
<div>The workflow to use this page as an aid to organizing MantisBT is pretty tedious. You can simply view the page history to judge the amount of work involved so far without me going in to details. </div><div><br></div>
<div>On the Extension page it shows a screenshot of what the plugin does. Please take a moment to consider this. How it would improve creating wiki Roadmaps for new releases (Scribus still does this), for tracking certain issues (wiki pages like Bugs to be Buried, Most Annoying Bugs, Most Wanted Features) etc..etc..</div>
<div><br></div><div>To be continued in a follow up email...</div><div><br></div><div>Thanks for your time, attention and considerations.</div><div><br></div><div>Cheers,</div><div>/Kunda</div><div><br></div><div><div>PS I want to appreciate MrB for taking a stab at implementing the Extension/plugin proposal already and yet not succeeding (<a href="http://bugs.scribus.net/view.php?id=12350">http://bugs.scribus.net/view.php?id=12350</a>). </div>
</div></div>