> On June 10, 2016, 4:25 p.m., Jie Yu wrote:
> > In fact, for working groups, I would prefer adding that to the docs so that 
> > people can find/read it on github. It is also constantly changing, updating 
> > it in docs sounds easier than updating the website. What do you think?
> 
> Tomasz Janiszewski wrote:
>     So this will end the same as [powered by 
> Mesos](http://mesos.apache.org/documentation/latest/powered-by-mesos/) which 
> has noting to do with latest documentation but only with community. I think 
> real problem is site updating. Using docs for anything that change often is 
> not a solution.

In my opinion, if the target of document are users, I prefer to host it in 
project website. If the target of document are devlopers(framework developers, 
contributors, committer and etc), I perfer to host it in docs.


- haosdent


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/48530/#review137027
-----------------------------------------------------------


On June 10, 2016, 1:53 a.m., Tomasz Janiszewski wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48530/
> -----------------------------------------------------------
> 
> (Updated June 10, 2016, 1:53 a.m.)
> 
> 
> Review request for mesos, haosdent huang, Jie Yu, and Vinod Kone.
> 
> 
> Bugs: MESOS-5591
>     https://issues.apache.org/jira/browse/MESOS-5591
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> Change was discussed at
> http://www.mail-archive.com/dev@mesos.apache.org/msg35506.html
> 
> 
> Diffs
> -----
> 
>   site/data/working_groups.yaml PRE-CREATION 
>   site/source/working-groups.html.erb PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/48530/diff/
> 
> 
> Testing
> -------
> 
> Page could be viewed at 
> http://janisz.github.io/mesos/site/publish/working-groups/
> 
> 
> Thanks,
> 
> Tomasz Janiszewski
> 
>

Reply via email to