Hello Ronald,
thank you for the input on this.
----- Original Message -----
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,
It's unclear because it differs from the approach as being used on GitHub?
(=> takes additional time contributors accustomed to GitHub patch process style
to make familiar with it & start contributing)
The process is documented at:
https://fedorahosted.org/scap-security-guide/wiki/becomeadeveloper
- communication around a patch is made difficult by mail (which are
already
follinwg throughout the days)
I am not sure it's due the way we communicate (mail). There are more
sources for the difficulties. Will comment on this further in reply to Shawn's post.
- current open issues are not listed and cannot be discussed by the
community
(to propose patch for instance)
In other words we are not used to utilize the underlying ticketing system too
much, therefore it's not clear what are the current blockers / issues being worked
in that moment at?
Fedorahosted SSG instance has support for ticketing system:
https://fedorahosted.org/scap-security-guide/report/1
But you are correct, that last one was filed ~2months ago:
https://fedorahosted.org/scap-security-guide/ticket/434
and that from this PoV it might seem, there hasn't been progress on the project
from that time (though obviously by count of patches provided in between this
clearly isn't true).
If nothing else, this might indicate we already have features / possibilities
how to make the patch proposal / review process more straightforward to future
contributors. But not might be using them (too) effectively.
Thank you && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Technologies Team
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 :)
my two cents.
Ronald
On Tue, Apr 8, 2014 at 7:53 PM, Shawn Wells < shawn(a)redhat.com > wrote:
On 4/8/14, 10:16 AM, Trevor Vaughan wrote:
Just out of curiosity, what happened with this in the end?
I just noticed a few more suggestions that Github-style pull requests would
be really useful.
There were valid opinions expressed for both staying on FedoraHosted and
migrating to GitHub. So, effectively, a stalemate.
The SSG community has grown amazingly -- both in contributors and usage --
and because of this success Red Hat is preparing to ship SSG in future
versions of RHEL [1]. This exacerbates the need for a manageable ticketing
system with easy patch submission as very shortly every RHEL installation
will have a copy of SSG. FedoraHosted simply wasn't designed to include the
same tooling and developer ecosystem as afforded on GitHub (and that's NOT a
ding against it's designers!).
The community is a coalition of the willing. Our shared purpose drives the
community, and I strongly feel the need to build out tools that will allow
us to scale. I'm concerned -- likely overly so -- at how to prepare for a
wave of interest once we begin shipping in RHEL.
With that said, who am I to *mandate* the migration to GitHub? Admittedly
part of me wants to just go ahead and do it, however that could come at
making a non-trivial amount of people (esp. committers, who would be
effected by the change) feel alienated/ignored. Certainly we can't make
everyone happy all the time, though.
Thoughts would be *most* welcome.
[1]
https://bugzilla.redhat.com/ show_bug.cgi?id=1038655
______________________________ _________________
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
scap-security-guide(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide