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

[Karsten Wade]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/05/2015 05:50 AM, Sankarshan Mukhopadhyay wrote:
> On Fri, Jun 5, 2015 at 6:15 PM, kunaal jain <kunaalus at gmail.com>
> wrote:
>> This is the a good post to get started on what we are planning to
>> do 
>> http://lists.centos.org/pipermail/centos-docs/2015-May/005665.html
>> Please let us know what you think.
> 
> Is the concern limited to mitigating changes due to Github API
> change or, git itself? In other words, if you set up a Gerrit
> instance on CentOS infra, does similar, would it work? I am very
> much against using Bugzilla as anything but a defect tracking tool.
> Trying to make it into a patch review system for text seems fraught
> with design decisions.

Just to help explain a bit, the concern (which I raised initially) was
in tying our patch review process entirely to GitHub.

Patch review happens on the editor/Docs SIG side rather than on the
content contributor side. A content contributor can use GitHub purely,
or (with commit rights in the future) git.centos.org directly.

We also discussed using git comments for review, and that might for
some part of the need. It doesn't really replace the status you get in
a review system -- proposed, draft, ready to publish, etc.

Now that I've looked at bit at pagure.io, that might be a good way to
go. The Kunaal and Lei will need to have a discussion with pingou
about this -- what might work, etc.

- - Karsten
- -- 
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)

iEYEARECAAYFAlVyGycACgkQ2ZIOBq0ODEES9ACfRCOMEffln3d7MrNYEtWwegCr
L4gAoK0g0g99Jm1U7IJAmsvwnnE1mA5L
=SC/X
-----END PGP SIGNATURE-----