+1 to github and hopefully abandoning the sending of patchsets to the
mailing list for review.
Jeff
On 02/16/2014 04:03 PM, Shawn Wells wrote:
As the SSG development community grows, so does the need for matured
tools and workflow. There's been some discussion of moving to GitHub.
On the pro side:
* Easier to signup and request commit access
* Most committers likely to have GitHub account for other projects
anyway
* Easier for community to fork SSG code (e.g. gitmachines project)
* Dramatically better ticketing system
- labels
- user-friendly GUI
- git commit hooks (put ticket # in patch title, auto
resolves ticket)
- multi-developer collaboration on tickets easier through
@name calls
* "Pull Request" concept: Patches centrally managed and merged,
ensures no missed patches on mailing list
* Simplified branching (e.g. allows a -stable and -dev branch).
Possible on FedoraHosted, not as intuitive
* Increased reliability of infrastructure (especially latency of
git pulls)
On the cons:
* Slight developer hassle to migrate SSH keys
* "Not hosted by RedHat" -- concern from some that migrating from
a redhat/fedora hosted URL will diminish project brand.
What does everyone think?
_______________________________________________
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
