[jira] [Commented] (THRIFT-4710) Move all ASF CMS website content to GitHub

["Duru Can Celasun (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/THRIFT-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954129#comment-16954129 ] 

Duru Can Celasun commented on THRIFT-4710:
------------------------------------------

With the release of 0.13 behind us, I'd like to bump this issue and discuss feasible next steps. I'm willing to dedicate some time to working on this if we reach consensus on they way forward. Keeping in mind the discussion so far, I propose:
 - We use readthedocs with the [mkdocs documentation type|https://docs.readthedocs.io/en/stable/builds.html#how-we-build-documentation]. It alternatively supports sphinx, but mkdocs is far more popular and easier for potential contributors as it uses plain markdown files.

 - We incorporate as much of "[Thrift: The Missing Guide|http://diwakergupta.github.io/thrift-missing-guide/]" as possible. The author contributed it to the project [almost 7 years ago|https://issues.apache.org/jira/browse/THRIFT-1550]. I see James has already asked for renewed permission, but we should reach out via email as well.

 - Similarly, try to include "[Thrift RPC specification|https://erikvanoosten.github.io/thrift-missing-specification/]" if the author permits us to do so. This would be very valuable for attracting new contributors to the project.

Thoughts, everyone?

> Move all ASF CMS website content to GitHub
> ------------------------------------------
>
>                 Key: THRIFT-4710
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4710
>             Project: Thrift
>          Issue Type: Documentation
>          Components: Documentation, Website
>    Affects Versions: 0.12.0
>            Reporter: James E. King III
>            Priority: Major
>
> Recent changes in Apache infrastructure has made it impossible to use the existing ASF CMS system to manage the Apache Thrift web site.  We need to extract and move the content somewhere else.  For reference, see:
> https://issues.apache.org/jira/browse/INFRA-17519
> This is a bunch of work nobody was expecting to have to do.
> My recommendation is to put the documentation into the "docs/" (or leave it in "doc/", perhaps, it if works) and use https://readthedocs.org/ to create the documentation web site.  Documentation updates can be pushed into the repository with {{`[ci skip]`}} or maybe we teach GitHub and/or our Appveyor and Travis to do nothing on pull requests that only contain updates to markdown and/or rst files.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)