Hi Jan, thanks for your feedback on this whole discussion.
>From my experience on github, here are the positive aspects: - users can file issues in a convenient and nice UI: most devs often have a github account and enjoy contributing to other projects (social network coding) - repositories are provided with stats (on commits, traffic and views, contributors, ...) - users can fork the code and see how there code evolves compared to the actual master (nice to have derivated policies and let them evolve on a side track) - forks can also be identified easily and contributed to with a possible merge in the upsteam repo (side track goes back to the main road) - users can issue patch (pull requests) which are easy to diff (nice UI) and integrate in the repo - considerable communities of devs and lots of features to consolidate a community (follow, repository starring, repo watch,...) - and most important: all those aspects are all integrated into a single interface (single account). Beside all this, I fairly understand that such a move should not be decided in a snap :) Ronald On Wed, Apr 9, 2014 at 12:11 PM, Jan Lieskovsky <[email protected]> wrote: > > ----- Original Message ----- > > From: "Frank Caviggia" > > Sent: Wednesday, April 9, 2014 5:33:36 AM > > > > +1 on moving the source repository to GitHub - the projects I've put up > there > > are easy to manage and I've had great interaction with contributors. > > Frank, same question - can you elaborate what makes the project(s) easy to > be manageable & have great interaction with contributors? (ideally via > listing > the underlying features allowing this) > > Thank you && Regards, Jan. > -- > Jan iankko Lieskovsky / Red Hat Security Technologies Team > > > > > ----- Original Message ----- > > From: "Shawn Wells" <[email protected]> > > To: [email protected] > > Sent: Tuesday, April 8, 2014 3:01:37 PM > > Subject: Re: [RFC] time to move to github? > > > > On 4/8/14, 2:57 PM, Ronald wrote: > > > Hi there, > > > > > > from a personal perspective, as a github users (read biased opinion), > > > I've been refrained from contributing and publishing diffs because: > > > - the process of patch approval was not clear, > > > - communication around a patch is made difficult by mail (which are > > > already follinwg throughout the days) > > > - current open issues are not listed and cannot be discussed by the > > > community (to propose patch for instance) > > > > > > I have the feeling that a move to github would make lots of things > > > clear for global collaboration. Although, the fact that the project is > > > hosted at fedora is a good quality stamp/branding :) > > > > The https://fedorahosted.org/scap-security-guide/ could remain the same > > (for branding, as pointed out), however the underling source repo could > > be moved to github. > > > > > > > > my two cents. > > Thank you! > > _______________________________________________ > > scap-security-guide mailing list > > [email protected] > > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide > > > > -- > > Frank Caviggia > > Consultant, Red Hat > > [email protected] > > (M) (571) 295-4560 > > _______________________________________________ > > scap-security-guide mailing list > > [email protected] > > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide > > > _______________________________________________ > scap-security-guide mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide >
_______________________________________________ scap-security-guide mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
