<p dir="ltr"><br>
On Jun 4, 2015 12:17 PM, "Karsten Wade" <<a href="mailto:kwade@redhat.com">kwade@redhat.com</a>> wrote:<br>
><br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> On 06/01/2015 10:30 PM, Lei Yang wrote:<br>
> > Hi,<br>
> ><br>
> > As discussed earlier about the workflow, I and Kunaal will need a<br>
> > server space to host Bugzilla, a test repository at Github + a git<br>
> > repository at <a href="http://git.centos.org">git.centos.org</a> <<a href="http://git.centos.org/">http://git.centos.org/</a>>. This is<br>
> > temporary, required for development and testing.<br>
> ><br>
> > Please let us know how do we obtain the same? We need it to get<br>
> > started on our project.<br>
><br>
> Thanks for asking on centos-devel, I'll reply there with some<br>
> specifics on requesting resources.<br>
><br>
> I think you will get push back about Bugzilla. For example, someone<br>
> has to continue to administer the system after the summer is done. The<br>
> rest of the toolchain looks like it's something that the sysadmin team<br>
> can handle with the proper documentation. An entire Bugzilla instance<br>
> is another thing, however -- web server, PHP code, database, and so fort<br>
> h.<br>
><br>
> Are you sure that <a href="http://bugs.centos.org">bugs.centos.org</a> cannot work well enough?<br>
><br>
> Regards,<br>
><br>
> - - Karsten<br>
> - --<br>
> </p>
<p dir="ltr">I'm tentatively planning on working pagure[0] into the Fedora Docs toolchain. It handles issue tracking, process documentation/contribution guidelines, and of course repo management and pull requests. It might fit for CentOS docs as well.</p>
<p dir="ltr">[0] <a href="https://pagure.io/pagure">https://pagure.io/pagure</a></p>
<p dir="ltr">--Pete</p>