-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/29/2015 12:33 PM, kunaal jain wrote: > Hi, > > Over the last week, Lei and I have been researching about the > review platform where the content submitted can be reviewed, > commented, tagged and pushed. This will be an alternative to github > pull requests interface, which will thus reduce our dependency on > Github in case Github changes its API anytime in future. Definitely I agree with that thinking. One thing to consider is that some people may us the pull request model and then not want to go further outside of the tool. One way to think of this is to see if you can work with someone entirely in GitHub, if that happens, maybe by having the content reviewer do the shuffles with bug tracking. > Even firefox is considering using Github as an alternative medium > to receive contribution. > http://gregoryszorc.com/blog/2015/01/12/utilizing-github-for-firefox-d evelopment/ > > Lei made a great chart comparing the platforms. > > https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp= sharing Were > you able to compare with Mantis, which is what runs http://bugs.centos.org? What are the time implications with connecting to a bug/task tracking tool? I'm glad you are thinking about this at the start, in case you also use GitHub in parallel with git comments and pull requests, as a way to get a minimal feature set running. I'll comment in other parts of this thread, to keep context. Regards, - - Karsten > So overall Bugzilla looks a great option. But there is one major > flaw, we need to view the article submitted at each point(code > review) which bugzilla lacks. > > The solution to this is creating a plugin for markdown previewing. > > The typical workflow might look like this: > > 1. Author writes content in markdown language. 2. Makes a pull > request on github. 3. Corresponding to the pull request a issue is > created on bugzilla. 4. CentOS staff can either review the article > on github pull request, or on bugzilla. 5. Comments are two way > synced. 6. 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. 8. Staff > tags it, and pushes to git.centos.org. 9. Using git.centos.org, new > website is generated and pushed. > > There are many challenging tasks in this, especially the bugzilla > issue creation on pull request and two way comment sync. This has > never been done before, but we looked at the API and think we can > make it work. Another challenging task is markdown preview on > bugzilla. > > Please let us know, what you think about this? > > Regards, Kunaal > > > -- Regards, Kunaal Jain > > > > _______________________________________________ CentOS-docs mailing > list CentOS-docs@xxxxxxxxxx > http://lists.centos.org/mailman/listinfo/centos-docs > - -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVslN4ACgkQ2ZIOBq0ODEGrBQCggSwF5XlvvVoxquhk2HHp8F7k z8oAoJxoO7etPolWuN+eeut9NWMX7ptS =pwGB -----END PGP SIGNATURE----- _______________________________________________ CentOS-docs mailing list CentOS-docs@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-docs
