[CentOS-docs] Resources Needed for Doc Toolchain Project [GSoC]

Fri Jun 5 08:03:41 UTC 2015
kunaal jain <kunaalus at gmail.com>

On Fri, Jun 5, 2015 at 1:28 AM, Pete Travis <me at petetravis.com> wrote:

>
> On Jun 4, 2015 12:17 PM, "Karsten Wade" <kwade at redhat.com> wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 06/01/2015 10:30 PM, Lei Yang wrote:
> > > Hi,
> > >
> > > As discussed earlier about the workflow, I and Kunaal will need a
> > > server space to host Bugzilla, a test repository at Github + a git
> > >  repository at git.centos.org <http://git.centos.org/>. This is
> > > temporary, required for development and testing.
> > >
> > > Please let us know how do we obtain the same? We need it to get
> > > started on our project.
> >
> > Thanks for asking on centos-devel, I'll reply there with some
> > specifics on requesting resources.
> >
> > I think you will get push back about Bugzilla. For example, someone
> > has to continue to administer the system after the summer is done. The
> > rest of the toolchain looks like it's something that the sysadmin team
> > can handle with the proper documentation. An entire Bugzilla instance
> > is another thing, however -- web server, PHP code, database, and so fort
> > h.
> >
> > Are you sure that bugs.centos.org cannot work well enough?
> >
> > Regards,
> >
> > - - Karsten
> > - --
> >
>
> 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.
>
Can you tell us about Fedora Docs toolchain? We can surely help each other
if our interests align.


> [0] https://pagure.io/pagure
>
> --Pete
>
> _______________________________________________
> CentOS-docs mailing list
> CentOS-docs at centos.org
> http://lists.centos.org/mailman/listinfo/centos-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20150605/f5f31639/attachment-0006.html>