I also find the patch by email process confusing. 

I consider that my issue, of course, and that I need to just sit down and learn it. Alas, learning patch by email becomes one of those tasks that is very easy to put off in the face of other urgencies. 

I'll ask a silly question. What if we put a branch on GitHub to test while continuing to use Fedora hosted? It would be a little extra work for a bit for someone to keep them in sync. But if they are both Git under the hood, shouldn't it be relatively easy to maintain both for a 45 day trial.

Greg Elin
personal cell: 917-304-3488
personal email: greg@fotonotes.net
email: gregelin@gitmachines.com



On Tue, Apr 8, 2014 at 3:01 PM, Shawn Wells <shawn@redhat.com> wrote:
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
scap-security-guide@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide