<div dir="ltr"><span style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif">> I have not used it yet. Do you mind sharing briefly what you like about </span><span style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif">it?</span><div><font color="#212121" face="helvetica neue, helvetica, arial, sans-serif"><br></font></div><div><font color="#212121" face="helvetica neue, helvetica, arial, sans-serif">It works ;-)</font></div><div><font color="#212121" face="helvetica neue, helvetica, arial, sans-serif">The hosted version does not require any of your short time for maintaining the system.</font></div><div>It is easy to use - IMHO.</div><div>It is feature-rich.</div><div><br></div><div><span style="line-height:1.5;color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif">> Does it allow for offline editing like we can do using the github wiki?</span><span style="line-height:1.5"> </span><br></div><div><span style="line-height:1.5"><br></span></div><div><span style="line-height:1.5">It supports editing with local editors - i do not know if this requires an active connection.</span></div><div><span style="line-height:1.5">But is provides an API.</span></div><div><span style="line-height:1.5"><br></span></div><div><span style="line-height:1.5"><br></span></div><div><span style="line-height:1.5">As auth provider it accepts only itself (My Atlassian) or google business :-(</span><br></div><div><br></div><div><br></div><div><span style="line-height:1.5"><br></span></div></div><br><div class="gmail_quote"><div dir="ltr">Isaac Bennetch <<a href="mailto:bennetch@gmail.com">bennetch@gmail.com</a>> schrieb am Mi., 15. Juni 2016 um 03:16 Uhr:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sebastian, I'm glad to hear from you.<br>
<br>
On 6/13/16 11:54 AM, Sebastian Mendel wrote:<br>
> I am not sure what type of git integration you are looking for, but I<br>
> like Atlassian Confluence:<br>
> <a href="https://de.atlassian.com/software/views/open-source-license-request" rel="noreferrer" target="_blank">https://de.atlassian.com/software/views/open-source-license-request</a><br>
<br>
I have not used it yet. Do you mind sharing briefly what you like about<br>
it? Does it allow for offline editing like we can do using the github wiki?<br>
<br>
> Isaac Bennetch <<a href="mailto:bennetch@gmail.com" target="_blank">bennetch@gmail.com</a> <mailto:<a href="mailto:bennetch@gmail.com" target="_blank">bennetch@gmail.com</a>>> schrieb<br>
> am Mo., 13. Juni 2016, 15:08:<br>
><br>
><br>
><br>
> On 6/13/16 8:02 AM, Michal Čihař wrote:<br>
> > Hi<br>
> ><br>
> > this topic was discussed quite a lot on the mailing list, but<br>
> still I'd<br>
> > like to hear feedback which solution do you prefer.<br>
> ><br>
> > Dne 8.6.2016 v 13:33 Michal Čihař napsal(a):<br>
> >> Possible solutions:<br>
> >><br>
> >> * bring Mediawiki on <a href="http://wiki.phpmyadmin.net" rel="noreferrer" target="_blank">wiki.phpmyadmin.net</a><br>
> <<a href="http://wiki.phpmyadmin.net" rel="noreferrer" target="_blank">http://wiki.phpmyadmin.net</a>> back to usable state<br>
> >><br>
> >> - we will have to handle security fixes and so on<br>
> >> - need some way to prevent vandalism<br>
> ><br>
> > Alec Teal offered help with this. The best approach here is<br>
> probably to<br>
> > start with updating latest Mediawiki and avoid using Debian packages<br>
> > completely.<br>
><br>
> I am not against staying with Mediawiki, however the obvious shortcoming<br>
> is lack of git integration. This is not a deal-killer for me, but it is<br>
> a negative.<br>
><br>
> >> * use wiki on GitHub<br>
> >><br>
> >> - it's for free with the repository<br>
> >> - the wiki is quite limited (no categories, no search, ...)<br>
> >> - having wiki content as Git repository is great<br>
> ><br>
> > The wiki features are rather limited here, on the other side we really<br>
> > did not use much of them anyway...<br>
><br>
> We can work around the lack of features, since there aren't many we use,<br>
> but the limitations with how data is displayed (for instance, only about<br>
> 70% of the page is used for actual wiki data) make this difficult. I'm<br>
> not fond of Github wiki and only consider it because it's easy and has<br>
> great git integration.<br>
><br>
> >> * use other solution for <a href="http://wiki.phpmyadmin.net" rel="noreferrer" target="_blank">wiki.phpmyadmin.net</a><br>
> <<a href="http://wiki.phpmyadmin.net" rel="noreferrer" target="_blank">http://wiki.phpmyadmin.net</a>><br>
> >><br>
> >> - we could use cleaned up wiki content which is currently used<br>
> on GitHub<br>
> >> - I'd really prefer something with Git integration<br>
> >> - preferably use GitHub authentication, so that we do not have to<br>
> >> maintain another list of users<br>
> >> - one of possible tools to do that is ikiwiki<br>
> ><br>
> > Anybody has experience with ikiwiki or other wiki engines?<br>
><br>
> I've been looking in to ikiwiki, actually. It has git integration, which<br>
> I think is the feature we're most looking for. The underlying language<br>
> is Markdown, which we're rather familiar with. However, the rendered<br>
> pages are a bit ugly.<br>
><br>
> You can quickly clone the repository with<br>
> > git clone git://<a href="http://ikiwiki.branchable.com/" rel="noreferrer" target="_blank">ikiwiki.branchable.com/</a><br>
> <<a href="http://ikiwiki.branchable.com/" rel="noreferrer" target="_blank">http://ikiwiki.branchable.com/</a>><br>
> to view the demo wiki. Look in the ./doc/ folder for the actual wiki<br>
> content. The rendered pages are visible at <a href="https://ikiwiki.info/" rel="noreferrer" target="_blank">https://ikiwiki.info/</a><br>
><br>
> They appear to allow authentication using accounts from OpenID, Yahoo,<br>
> WordPress, and more; in fact there's a page with discussion about their<br>
> plans/roadmap for authentication[1]. However, it seems the path to<br>
> OpenID is a bumpy one[2].<br>
><br>
> I'm more excited about Gitit[3][4]. Gitit has a git backend (or darcs or<br>
> mercurial), pages are able to be written in about ten different flavors<br>
> including Markdown and reStructuredText (anything understood by Pandoc),<br>
> and it looks like Mediawiki (which isn't a big goal for me, but it's a<br>
> common and easy-to-use structure). The default/suggested authentication<br>
> seems to be GitHub OAuth. Downsides about it: their own wiki is a mess<br>
> (broken links to the Install guide and README, not a whole lot of<br>
> information in general), development seems slow (there are plenty of<br>
> Issues and Pull Requests without a comment, last commit was 12 days<br>
> ago), and it's written in Haskell (with which I'm not very familiar) --<br>
> but this is my favorite right now. This random guy[5] has similar goals<br>
> to ours and settled on Gitit.<br>
><br>
> Finally, there is Realms[6][7] and Gollum[8]. Realms is built on Gollum,<br>
> uses GitHub OAuth, and it looks really modern. However, the<br>
> documentation seems really weak and it looks like they haven't published<br>
> an actual release yet (though running their git 'master' branch seems to<br>
> work okay). Realms is very interesting to me, but with my cursory<br>
> examination it doesn't feel like production-ready software. I could be<br>
> wrong. Gollum is apparently what GitHub is using for their wiki engine.<br>
> I don't have a good sense of what Gollum is like, because as near as I<br>
> can tell they don't have a demo and I haven't gotten around to<br>
> installing it on my test machine. There's a fork to add OAuth<br>
> support[9].<br>
><br>
> For looks, I think Realms acts best; it's modern and slick and easy to<br>
> use. However, Gitit seems much more established and reliable.<br>
><br>
><br>
> 1 - <a href="https://ikiwiki.info/todo/emailauth/" rel="noreferrer" target="_blank">https://ikiwiki.info/todo/emailauth/</a><br>
> 2 - <a href="https://ikiwiki.info/plugins/openid/troubleshooting/" rel="noreferrer" target="_blank">https://ikiwiki.info/plugins/openid/troubleshooting/</a><br>
> 3 - <a href="http://gitit.net/" rel="noreferrer" target="_blank">http://gitit.net/</a><br>
> 4 - <a href="https://github.com/jgm/gitit" rel="noreferrer" target="_blank">https://github.com/jgm/gitit</a><br>
> 5 - <a href="http://nathantypanski.com/blog/2014-07-09-personal-wiki.html" rel="noreferrer" target="_blank">http://nathantypanski.com/blog/2014-07-09-personal-wiki.html</a><br>
> 6 - <a href="http://realms.io/" rel="noreferrer" target="_blank">http://realms.io/</a><br>
> 7 - <a href="https://github.com/scragg0x/realms-wiki" rel="noreferrer" target="_blank">https://github.com/scragg0x/realms-wiki</a><br>
> 8 - <a href="https://github.com/gollum/gollum" rel="noreferrer" target="_blank">https://github.com/gollum/gollum</a><br>
> 9 - <a href="https://github.com/aleiphoenix/gollum-with-auth" rel="noreferrer" target="_blank">https://github.com/aleiphoenix/gollum-with-auth</a><br>
><br>
> _______________________________________________<br>
> Developers mailing list<br>
> <a href="mailto:Developers@phpmyadmin.net" target="_blank">Developers@phpmyadmin.net</a> <mailto:<a href="mailto:Developers@phpmyadmin.net" target="_blank">Developers@phpmyadmin.net</a>><br>
> <a href="https://lists.phpmyadmin.net/mailman/listinfo/developers" rel="noreferrer" target="_blank">https://lists.phpmyadmin.net/mailman/listinfo/developers</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Developers mailing list<br>
> <a href="mailto:Developers@phpmyadmin.net" target="_blank">Developers@phpmyadmin.net</a><br>
> <a href="https://lists.phpmyadmin.net/mailman/listinfo/developers" rel="noreferrer" target="_blank">https://lists.phpmyadmin.net/mailman/listinfo/developers</a><br>
><br>
<br>
_______________________________________________<br>
Developers mailing list<br>
<a href="mailto:Developers@phpmyadmin.net" target="_blank">Developers@phpmyadmin.net</a><br>
<a href="https://lists.phpmyadmin.net/mailman/listinfo/developers" rel="noreferrer" target="_blank">https://lists.phpmyadmin.net/mailman/listinfo/developers</a><br>
</blockquote></div>