I agree with Pete. Using bugzilla for discussion takes all the fun part of Documentation. We need something more engaging as well as easy for discussion. I too mentioned my concern about relying on Github during discussion with Karsten . I suggested Mailing list for discussion. I think using existing open source platforms for discussions and modifying them for our toolchain will be the best option. One important thing which I focused on my proposed tool chain is minimal effort by the contributor once he pushes his new content. I don't wish to make the documentation procedure like bug tracking procedure, we review and suggest changes, he makes them and proposes it and then the cycle starts again. Ideally he pushes content, docs people review it for the correctness, make / suggests minor changes through mailing list, a part of our tool chain runs some basic tests on the docs, and the content is approved and pulled to our repository. It should be push and forget, but that can't happen. :) Github is best for this. We can discuss changes on PR, the content resides on the respective forks of the users visible to public, everyone is free to fork the users changes, improve it and push it again. So in the end using Github or our own site or the Mailing list is a call to be made by the people who'll actually use it i.e. docs people. Regards, Kunal Jain On Tue, Apr 7, 2015 at 10:30 PM, Pete Travis <me at petetravis.com> wrote: > > On Apr 7, 2015 9:28 AM, "杨 垒" <yltt1234512 at gmail.com> wrote: >> >> Hi Kunal! >> >> Thanks for your reply! I think the official mirroring is a great method >> because of higher efficiency. >> >> Another thing I am trying to solve is how to retrieve and store all the >> discussion / issue / PR on GitHub? These functions are great for a doc >> toolchain. However we shouldn’t rely on GitHub as a part of our project. My >> plan now is to use bugs.cents.org as a place to discuss about docs >> contributions. Or we can create a new site to track / discuss about the docs >> but it is a too huge job. Any ideas? >> >> Regards, >> Lei Yang >> _______________________________________________ > > I've found bugzilla to be great for tracking actual flaws in the product, > but not great for internal discussion and process tracking. Lists or Trac > can be better, respectively. I'm also keeping a close eye on pagure, > http://blog.pingoured.fr/index.php?post/2015/03/25/Progit-is-dead%2C-long-live-pagure > > --Pete > > > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs >