----- 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" <shawn(a)redhat.com>
To: scap-security-guide(a)lists.fedorahosted.org
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
scap-security-guide(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
--
Frank Caviggia
Consultant, Red Hat
fcaviggi(a)redhat.com
(M) (571) 295-4560
_______________________________________________
scap-security-guide mailing list
scap-security-guide(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide