I missed the point why to use github and dokuwiki together, dokuwiki is the way to go, yes, but it can track versions alone and the backup is simple since there is no database…fetch the folder in a tar.gz each hour/day and it is done.
Thanks for the interesting discussion, good points are explained there.
Maybe using the Github authentication could be simpler: https://www.dokuwiki.org/plugin:oauth
Markdown plugin is needed too, so we can copy/paste howtos born here on community or drafts extracted from posts
This looks better supported: https://www.dokuwiki.org/plugin:markdowku
Please @zamboni, could you explain what do you mean with BRRR ?
I’m going to point out that it could be offensive to who are trying to debate here, please always provide reasoned counter-arguments that improve the conversation
I don’t like discourse
I think a REAL wiki is really needed
I think that copy and paste from here to there is a bad thing
I think that using external services is not a good idea (BTW, what if tomorrow the hoster of this discourse instance will close? it already happened)
HTH
And I add: someone here, a VERY experienced and propositive user, already told all of it since the beginning… and I see he’s getting more frustrated (as I am)
You don’t like many things man, every time, and imho that approach isn’t constructive. That’s the discussion, baby. Don’t you like it? Be the change you want to see in the world
…until we moved the documentation to ReadTheDocs! Since that time I don’t see any big contribution to the wiki on Redmine, whilst ReadTheDocs was expanded a lot with Pull Requests from GitHub. yes, I think it can be enhanced further, however as @alefattorini said and I agree with him, this is the right way to collaborate with the documentation easing the contribution from everyone.
I second this.
We already have everything, we have user accounts in place, we will have only one place for everything, we can begin to write docs NOW.
When we will find the perfect wiki, we will move contents there.
I’d also like to modify the landing page of www.nethserver.org according to Jim’s suggestions.
I just wrote my first page, see Contribution sections here:
Just for the record, currently Discourse worked fine for our HowTos, that’s a fact. We have a bunch of howtos here, don’t you think?
Most people are using it, check also:
@stephdl from your point of view, what Discourse lacks to became a useful wiki? Please, my memory is short
Automatic table of contents? What else?
Automatic wiki-mode setting of new pages/topics?.
Easy page linking?
Maybe you’re right but 55 different howtos from many people are a fact, isn’t it?
The fact is that It has definitely shown to be easy to use, handy and straightforward.
Also, people can comment below trying to continuously improve the doc.
It’s fragmented maybe, it hasn’t a good structure yep, it hasn’t basic (like TOC) and advanced features maybe, but the fact still remains
Hmm… if there is no other option than to put it in Discourse, it is not strange those howto’s end up there…
I do see the split between wanting to have everything centralized and needing options that are not available (yet) in Discourse.
The other option is to stick with mediawiki and maybe enhance that with some (eye)candy like http://bluespice.com/
@zamboni is right, a wiki is a book that you can follow/discover chapters from the table of content, discourse displays the last content and you find them by key word if you know them? ([of course at first you have no idea what to search][1]).
more over discourse cuts the page content, redmine no, github yes…I love to read a howto on my three 27’'.
yes yes yes
I need to have a go on the page linking by category in redmine I hope it is feasible, it must be a basic feature
From my point of view discourse should be a support forum, and all howto, bug report should be done elsewhere. (recall do one thing but do it well).
I’m a wiki player, [this is who I’m][2], Trying to explain why a wiki is better than discourse for howto is like walking for a homo habilis
For all howto there in discourse for me it is not a problem, now the most important and hard thing to do is in front of the community
sometimes people should really listen to the suggestions coming from experienced users…
I repeat myself: the web2.0 approach is wrong in a professional environment… you can buy an ebook, but sysadmins and developers still buy books made of paper.
now it’s up to who decide to choose between the bell & whistles approach and the professional one
last post of mine here
