Dear MantisBT-Community,
I'm wondering, how do you manage/share your knowledge for each project? What's the best practice?
I read about the DokuWiki integration, but I'm more looking for a lightweight knowledge base.
Does MantisBT 2.x provide a feature like this out of the box or can anyone recommend a good plugin for version 2.x?
Thanks in advance
Ben
P.S.: Special thanks to the MantisBT-Team!
Best practice: knowledge management for each project?
Moderators: Developer, Contributor
Re: Best practice: knowledge management for each project?
There is no such a feature out of the box.
Not sure what you expect when saying "knowledge management", maybe some kind of FAQ is enough for what you want.
There is a community plugin (never tried myself) https://github.com/mantisbt-plugins/faq
I had a very short look at it. It's quite outdated, will hardly run with latest MantisBT and seems not to be maintained.
You could try to contact the author and to ask if he plans to adapt it for MantisBT 2.x.
https://github.com/mantisbt-plugins/faq ... FAQ.php#L9
Not sure what you expect when saying "knowledge management", maybe some kind of FAQ is enough for what you want.
There is a community plugin (never tried myself) https://github.com/mantisbt-plugins/faq
I had a very short look at it. It's quite outdated, will hardly run with latest MantisBT and seems not to be maintained.
You could try to contact the author and to ask if he plans to adapt it for MantisBT 2.x.
https://github.com/mantisbt-plugins/faq ... FAQ.php#L9
Re: Best practice: knowledge management for each project?
Thanks for your fast response and suggestion, atrol.
@MantisBT team
Am I allowed to use the public repository name "mantisbt_knowledgebase" or don't you want me to mention "mantisbt"? I'll share the plugin for free.
I'd like to add some documentation to my projects, e.g. an introduction for new team members, workarounds to well known (external) problems or just a simple list which contains information about the branding (font, logo, etc.). Probably 5-15 pages, nested into max. 3 levels.atrol wrote:Not sure what you expect when saying "knowledge management"
I'll have a look at the MantisBT plugin docs and try to develop something myself.atrol wrote: There is no such a feature out of the box.
...
There is a community plugin (never tried myself) https://github.com/mantisbt-plugins/faq
I had a very short look at it. It's quite outdated, will hardly run with latest MantisBT and seems not to be maintained.
@MantisBT team
Am I allowed to use the public repository name "mantisbt_knowledgebase" or don't you want me to mention "mantisbt"? I'll share the plugin for free.
Re: Best practice: knowledge management for each project?
There are some other plugins having Mantis(BT) in their name https://github.com/mantisbt-pluginsBen wrote: @MantisBT team
Am I allowed to use the public repository name "mantisbt_knowledgebase" or don't you want me to mention "mantisbt"? I'll share the plugin for free.
You might also want your plugin hosted at the same place, see https://www.mantisbt.org/wiki/doku.php/ ... ganization
"Knowledgebase" would be enough as repository name.