Hi,
On 05/06/15 13:36, kunaal jain wrote:
I am sorry modifying is wrong word. We will be using API, Hooks of bugzilla, which have excellent API, hooks.
well, we dont use bugzilla in CentOS, so doing the work for bugzilla would mostly be a waste of time. Our trackers run Mantis, which also have good api's
But since we will be doing experiments, it won't be a good idea using bugs.centos.org http://bugs.centos.org initially.
There are test instances and devel instances for implementations around bugs.centos.org - you are welcome to use those. But lets first establish exactly what you need and why.
- KB
-- Regards, Kunaal Jain
On Fri, Jun 5, 2015 at 5:41 PM, Sankarshan Mukhopadhyay <sankarshan.mukhopadhyay@gmail.com mailto:sankarshan.mukhopadhyay@gmail.com> wrote:
On Fri, Jun 5, 2015 at 5:36 PM, kunaal jain <kunaalus@gmail.com <mailto:kunaalus@gmail.com>> wrote: > We will be developing a issue tracking system by modifying possibly > bugzilla, or similar tool, which will be two way synced with Github. What we > aim to do is use the very Github tools as an alternate source of Content > contribution, but at the same time not depending on Github by syncing all > these content to our issue tracking system. This is one major part of the > tool chain we discussed. Hmm... let's back up a little bit. Anything that requires "modifying" bugzilla would really have to end up being part of upstream bugzilla project itself or, maintained by the specific Infra/SysOp team for the downstream project (eg. CentOS). Instead of a wholesale modification of bugzilla, would using a specific product/component combination allow you to test the sync? --