<HTML><BODY>GitLab?<br>= wiki + md + git + OpenID<br><br><br><br><blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">
Понедельник, 11 декабря 2017, 12:41 +03:00 от Fabian Arrotin <arrfab@centos.org>:<br>
<br>
<div id="">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div>
<base target="_self" href="https://e.mail.ru/">
<div id="style_15129853160000000744_BODY">On 11/12/17 10:22, Thibaut Perrin wrote:<br>
> Hello Fabien,<br>
> <br>
> First, thank you for even trying for what seems to be an impossible task :(<br>
> <br>
> Quick points : <br>
> - if it was decided not to continue, what would happen to the current<br>
> wiki ? Dismantled or would it remain as read-only for documentation<br>
> purpose ?<br>
> - What about Sphinx <<a href="http://www.sphinx-doc.org/en/stable/" target="_blank">http://www.sphinx-doc.org/en/stable/</a>> ? seems to be<br>
> frequentely used nowadays<br>
> - As you mentioned, a solution of the type of github with pull requests<br>
> for documentation updates might be a solution here. <br>
> <br>
> There is a wiki feature <<a href="https://guides.github.com/features/wikis/" target="_blank">https://guides.github.com/features/wikis/</a>> on<br>
> Github. I don't know to which extend it would fit the needs of the project.<br>
> <br>
> Hope this helps,<br>
> <br>
> Thibaut<br>
<br>
So far there is no decision, reason why I started this thread :)<br>
I guess our target would be to convert (and sanitize ?) existing content<br>
anyway as we don't want to lose such content. Then either replacing<br>
wiki.centos.org with new solution (but trying to keep the same structure<br>
so that all the things in cache for search engines and/or articles<br>
pointing to wiki can still work) or move to something different and<br>
indeed keeping existing wiki.centos.org in Read-Only mode<br>
<br>
I'd like to avoid Github specifically but having something else that<br>
would permit to use ACO (https://acccounts.centos.org) as auth source. I<br>
already played with gitea and it works with openid so self-hosted git<br>
instance using ACO works fine. (but that's a different thread)<br>
<br>
We should divide all parts into specific areas. Benefits of using .md<br>
means being able to switch to something else even later and not be tied<br>
to $yet_another_tool to generate the web part. (just my idea)<br>
<br>
-- <br>
Fabian Arrotin<br>
The CentOS Project | <a href="https://www.centos.org" target="_blank">https://www.centos.org</a><br>
gpg key: 56BEC54E | twitter: @arrfab<br>
<br>
</div>
<div>_______________________________________________<br>
CentOS-docs mailing list<br>
<a href="mailto:CentOS-docs@centos.org">CentOS-docs@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-docs" target="_blank">https://lists.centos.org/mailman/listinfo/centos-docs</a><br>
</div>
<base target="_self" href="https://e.mail.ru/">
</div>
</div>
</div>
</blockquote>
<br>
<br>С уважением, Дорохов И.А.<br></BODY></HTML>