Hi Greg, ----- Original Message ----- > From: "Greg Elin" > Sent: Wednesday, April 9, 2014 3:07:28 PM > > Jan, thanks for responding to me. > > Let's say I want to make a small patch to fix a typo. Do you have a link that > explains how I would get started using current process?
It was provided in my original reply: https://fedorahosted.org/scap-security-guide/wiki/becomeadeveloper Thank you && Regards, Jan. -- Jan iankko Lieskovsky / Red Hat Security Technologies Team > > Greg > > Greg Elin > P: 917-304-3488 > E: [email protected] > > Sent from my iPhone > > > On Apr 9, 2014, at 5:59 AM, Jan Lieskovsky <[email protected]> wrote: > > > > Hello Greg, > > > > thank you for the reply. > > > > ----- Original Message ----- > >> From: "Greg Elin" > >> Sent: Tuesday, April 8, 2014 9:16:29 PM > >> > >> I also find the patch by email process confusing. > > > > It's confusing because it differs from the GitHub's one? [*] Or you are > > missing the Gerrit instance to be able to focus just at the most preferred > > issue and have easy way to comment on that one? Or the ticketing system? > > Anything else? > > > >> > >> 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. > > > > So the issue is git-email setup? [*] > > > >> > >> 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. > > > > Thank you && Regards, Jan. > > -- > > Jan iankko Lieskovsky / Red Hat Security Technologies Team > > > > [*] As already mentioned, it's documented at: > > https://fedorahosted.org/scap-security-guide/wiki/becomeadeveloper > > > > but maybe it should be improved to be more elaborated / sophisticated like > > e.g. oVirt's one: > > http://www.ovirt.org/Working_with_oVirt_Gerrit > > > > is (so interested contributor could "in five minutes" finish the setup > > easily, > > and start looking into the issues) > > > >> > >> Greg Elin > >> personal cell: 917-304-3488 > >> personal email: [email protected] > >> email: [email protected] > >> > >> > >> > >> On Tue, Apr 8, 2014 at 3:01 PM, Shawn Wells < [email protected] > 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 > >> > >> > >> _______________________________________________ > >> 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
