+1
I was wondering what reaction this would get.
Well done and interesting commentary on one of those critical decisions in
open source development.
--
SCAP Security Guide mailing list
scap-security-guide@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
62.html
[11] http://www.vincentpassaro.com/2012/04/01/red-hat-summit-2012-2/
[12]
https://lists.fedorahosted.org/mailman/private/aqueduct/2011-July/23.html
[13]
https://fedorahosted.org/aqueduct/attachment/wiki/Call/intro-SCAP-tech-talk.pdf?format=raw
[14]
https://sas.elluminate.com/p.jnlp?psid=
On Wed, Sep 3, 2014 at 10:03 PM, Shawn Wells wrote:
> On 9/3/14, 9:59 AM, Gabe Alford wrote:
>
>
> Having pull requests merged against the existing baseline would be huge
>> as well, especially for release note documentation. Any idea how to set
>> that up?
>>
>
> Do you mean that all pull req
On Wed, Sep 3, 2014 at 10:03 PM, Shawn Wells wrote:
> On 9/3/14, 10:02 AM, Gabe Alford wrote:
>
>
> Speaking about blockers (issues that definitely need to go into next
>> release)
>> would it be possible to set up an agreement that such fixes would receive
>> the
>> [BLOCKER] prefix together wi
> For case of committing - corresponding git hook (checking if the git log
> message
> contains at least one of [blocker], [bugfix], [enhancement], .. any
> others?)
> would be handy to prevent log messages not specifying type of change.
>
Correct me if I am wrong, but this would most likely need
Thanks, Shawn.
Fix the NFS insecure OVAL and made some suggestions on the A/V OVAL check.
On Wed, Sep 3, 2014 at 9:17 PM, Shawn Wells wrote:
> On 9/3/14, 10:04 PM, Gabe Alford wrote:
>
> Hello,
>
> I have the following git pull requests below that need final review. I
> can merge if ack'ed
>
Thanks for all the input!
Philip
smime.p7s
Description: S/MIME Cryptographic Signature
--
SCAP Security Guide mailing list
scap-security-guide@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
https://github.com/OpenSCAP/scap-security-guide/
That looks really nice actually.
I *think* that you can get the Agile board from Jira free with an Open
Source offering, but I'm not quite sure.
I would also like to propose the use of Gerrithub for code reviews:
http://gerrithub.io/
I like it better than the native Github reviews since it can f
- Original Message -
> From: "Shawn Wells"
> To: scap-security-guide@lists.fedorahosted.org
> Sent: Thursday, September 4, 2014 6:12:20 AM
> Subject: Re: Best ways to say this system is not compliant
>
> On 9/3/14, 7:38 AM, Martin Preisler wrote:
> > - Original Message -
> >> > Fr
- Original Message -
> From: "Shawn Wells"
> To: scap-security-guide@lists.fedorahosted.org
> Sent: Thursday, September 4, 2014 5:34:01 AM
> Subject: Re: SCAP Security Guide - make validate fails after make templates
> run
>
> On 9/3/14, 4:06 PM, Gabe Alford wrote:
>
>
>
> Hello,
>
>
- Original Message -
> From: "Shawn Wells"
> To: scap-security-guide@lists.fedorahosted.org
> Sent: Thursday, September 4, 2014 5:51:12 AM
> Subject: Re: Test run of Jenkins (CI tool)
>
> On 9/3/14, 11:19 AM, Trevor Vaughan wrote:
> > Seems like this might be a good case for a public Open
- Original Message -
> From: "Gabe Alford"
> To: "SCAP Security Guide"
> Sent: Wednesday, September 3, 2014 4:04:33 PM
> Subject: Re: Implementing GitHub Milestones
>
> Went ahead and added some milestones. Check them out here:
> https://github.com/OpenSCAP/scap-security-guide/mileston
- Original Message -
> From: "Gabe Alford"
> To: "SCAP Security Guide"
> Sent: Wednesday, September 3, 2014 4:02:04 PM
> Subject: Re: Implementing GitHub Milestones
>
>
>
>
> Speaking about blockers (issues that definitely need to go into next release)
> would it be possible to set up
13 matches
Mail list logo
