[pkgdb2] call for testers, bug reports and RFE

Kevin Kofler kevin.kofler at chello.at
Tue Nov 26 02:48:44 UTC 2013

Till Maas wrote:
> It is possible, but I have to agree that github is more
> convenient/efficient than the workflow you describe.

Huh? The "export patches, attach to issue tracker" workflow allows me to 
work with a normal local clone. The GitHub pull request workflow forces me 
to create a fork on GitHub and push my clone there (and for some projects, 
users who don't know how GitHub works will most likely attempt to use those 
forks, even though they aren't actually meant to be used other than as a 
source for pull requests; for pkgdb2, this is probably not an issue though 
;-) ), then juggling with the 2 different "upstreams" (the true upstream and 
the clone it forced me to create).

And GitHub tries to enforce that broken workflow in all silly ways possible. 
For example, their issue tracker arbitrarily only accepts image (picture) 
files as file uploads, no patches (nor even any other non-image content, 
e.g. log files). It is also not possible to file a pull request from 
anything other than a repo located on GitHub, you cannot even use a clone 
hosted elsewhere, let alone submit an exported patch (the way ReviewBoard, 
used e.g. on reviewboard.kde.org, works, a much better patch review 
interface, which I guess would be easy to set up on Fedora Hosted if 
maintainers think the issue tracker is not good enough).

So from the patch submitter's point of view, GitHub is much worse!

And from the maintainer's point of view, I don't see what's wrong with git 
am and git push either. Those are normal git commands you can issue on the 
command line, or if (like me) you prefer point-and-click UIs, you can apply 
the patch with qgit and push it with git-cola. (By the way, don't ask me why 
git-cola doesn't have a menu entry for "git am", or why qgit doesn't support 
even basic repository manipulation such as "git push". At least I can fire 
up qgit from git-cola, having it set up as the history viewer.) So you can 
just use the same tools you use for your own development, you don't have to 
go through some crappy proprietary web interface.

        Kevin Kofler

More information about the devel mailing list