On Sat, May 30, 2015 at 1:04 AM, kunaal jain kunaalus@gmail.com wrote:
The typical workflow might look like this:
- Author writes content in markdown language.
- Makes a pull request on github.
Is this github.com or, a git instance off CentOS infrastructure?
- Corresponding to the pull request a issue is created on bugzilla.
- CentOS staff can either review the article on github pull request, or on
bugzilla.
I would recommend using one tool for handle inbound and review. Having 2 tools that need to be kept synchronized would add overhead that you don't want to deal with. Also, it has the effect of puzzling contributors.
- Comments are two way synced.
- At each point the article can be viewed on bugzilla, using an extension
we propose to make. 7. After many iterations of commenting, and improving, article is finally accepted.
Have you considered review workflow tools like Gerrit?
- Staff tags it, and pushes to git.centos.org.
- Using git.centos.org, new website is generated and pushed.
'Website' or, is the content rendered from the version control (g.c.o) and pushed live?