[
https://issues.apache.org/jira/browse/THRIFT-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045968#comment-17045968
]
Christopher Tubbs commented on THRIFT-4710:
-------------------------------------------
For what it's worth, Apache Accumulo recently switched to using the new
.asf.yaml automated build infrastructure provided by INFRA. It works wonders:
all we have to do is merge a pull request and the staging site is automatically
built (using Jekyll / Kramdown (a flavor of markdown), but Pelican also is
supported by INFRA). A simple git one-liner publishes the configuration to the
site from the staging site. This is the lowest-barrier workflow I've seen
utilized on any project to maintain their website so far.
I think Thrift should do something similarly automated... but I do not know
about "readthedocs". COMDEV was recently discussing using a similar workflow,
but with Hugo as the site generator. I still they will have to use Jenkins to
build their site, since INFRA doesn't support Hugo right now. Although
"readthedocs" might be neat... I think it'd probably still be better to just
use Jekyll (or Pelican) to lower the bar to contributing as far as possible. It
may be possible to use "readthedocs" with automated Jenkins builds, though... I
just don't know enough about that workflow.
> 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.13.0
> Reporter: James E. King III
> Assignee: Duru Can Celasun
> 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)
