Re: Defining the future of the packager workflow in Fedora

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Robbie Harwood wrote:
>I have experienced this as a maintainer as well.  The issue for drive-by
>contributors is not so much pull requests as the account system itself.
>For example, I had a contributor from OpenSUSE email me patches to my
>pagure-hosted project (gssproxy) rather than opening a pull request
>because they didn't have a Fedora account.

It's not just the account. Fork → clone → patch → commit → push →
request is a rather long series of hoops to jump through. Clone → edit
→ commit → submit should be sufficient. Or what if I could just upload
a patch and have it turned into a pull request automatically?

Björn Persson

Attachment: pgpKcQiontdcx.pgp
Description: OpenPGP digital signatur

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux