On Tue, May 24, 2016 at 11:56 AM, Bruno Wolff III <bruno@xxxxxxxx> wrote:
On Tue, May 24, 2016 at 11:34:53 -0400,
Chris Lumens <clumens@xxxxxxxxxx> wrote:
>Certainly! Only possible issue from the community/contributor perspective could be
>that there are some people who don't use or don't want to use GitHub, for various reasons.
Hopefully the project will someday move to Pagure.
I can't see that happening.
If the reasons are limitations of Pagure, filing issues for needed features would help in making Pagure better for everyone.
I wouldn't expect the network effects of github to be that important to outweigh running on a service run by non-free software. Nor would I expect a migration to be too much effort to do eventually. (Though there are costs and it would be prudent not to rush a change until Pagure's future is more well known.) There certainly could be technical blockers, but hopefully those could be eventually addressed.
Changing the development workflow is not something we've ever taken lightly. There have been two major shifts in the last 10+ years. First was the move from cvs to git. The second was to move off Fedora infrastructure to github, and that decision wasn't just rushed through.
github has made it significantly easier for us to accept contributions from other individuals and companies. Like it or not, github has succeeded in making contributing to projects easy. If Pagure is just duplicating this functionality, fine, but that's not a good enough reason for us to change the development workflow. A large part of us wanting to move off Fedora infrastructure was the barrier to entry for gaining outside contributors. It was simply too high.
I'm not saying yes or no regarding moving things off github, but just that there are significant benefits to github that are very beneficial to the project right now.
--
David Cantrell <dcantrell@xxxxxxxxxx>
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
