I think Tom's points are correct. Another option would be plain text or markdown files inside the git repo. Those would be harder to update, but then would have review for developer docs changes, which might be nice.
FWIW, right now getting a wiki login requires asking for one on this mailing list because of spambots. On Wed, Jul 20, 2016 at 1:37 AM, Tom White <t...@cloudera.com> wrote: > On Wed, Jul 20, 2016 at 4:56 AM, Dimitris Tsirogiannis > <dtsirogian...@cloudera.com> wrote: >> Hi community, >> >> We need to move our developer documentation to a proper location. >> Currently, it's in Cloudera's internal wiki and in the wiki pages of the >> Cloudera Impala git repo ( >> https://github.com/cloudera/Impala/wiki/Contributing-to-Impala). >> >> The options are: >> * Impala's webpage (http://impala.io/) > > This is moving to http://impala.incubator.apache.org/, so it's the > equivalent of the third option (below), isn't it? > >> * Apache hosted Impala wiki ( >> https://cwiki.apache.org/confluence/display/IMPALA/Impala+Home) > > This is probably the best since a wiki is the most frictionless way of > updating dev docs. > >> * Apache hosted Impala webpage (http://impala.incubator.apache.org/) >> * The wiki pages of the Apache Impala git repo ( >> https://github.com/apache/incubator-impala) > > This isn't hosted on ASF infrastructure (unlike source code which is > mirrored), so I think we can rule this one out. > > Thanks, > Tom > >> >> Please state your preference. >> >> Dimitris
