[Openstack-security] OpenStack Security Notes - Contributors Wanted

Nathan Kinder nkinder at redhat.com
Tue Nov 19 16:35:17 UTC 2013


On 11/19/2013 05:46 AM, Clark, Robert Graham wrote:
>
> Hi All,
>
> I've had a little downtime recently due to being horribly ill  - I'm 
> glad to say I've been feeling much better recently but I have a rather 
> impressive pile of emails that I'm currently wading through. I have 
> 3-4 people wanting to help out with the OSSNs, I've been really 
> impressed with the response and I'm looking forward to seeing how this 
> works moving forward. I'll send an email around those of you who 
> wanted to help.
>
> My general thought is that I'll stay on to help out with OSSNs and 
> generally co-ordinate the project. I'm looking for authors and editors 
> to collaborate on individual OSSNs. My role would be to identify and 
> accept new OSSNs, to occasionally author my own OSSNs and regularly 
> edit/+1 the OSSNs of others.
>
> So, to those of you who are interested in helping out, are you 
> anticipating authoring (which normally includes some amount of 
> research) or editing?
>
I am fine with authoring.
>
> We currently have 3 OSSNs waiting to be written, 
> https://bugs.launchpad.net/ossn/+bugs perhaps between you it would be 
> possible to make a start on 1-2 of them. Each OSSN follows the same 
> template
>
I would be happy to work on this one:

     https://bugs.launchpad.net/ossn/+bug/1237989

Thanks,
-NGK
>
> Short title describing the issue
>
> ---
>
> ### Summary ###
> [One or two sentences discussing the issue, where it comes from and 
> who it may affect.]
>
> ### Affected Services / Software ###
> [Freeform keywords, metadata, comma separated] Keystone, DevStack, 
> Deployment
>
> ### Discussion ###
>
> [As much text as is required to describe the problem to a reasonably 
> technical audience. This section should be written carefully and 
> reviewed for content, grammar, spelling etc. When writing these 
> sections consider that the OSSN will later be included in the 
> OpenStack Security Guide, writing well here makes the process of 
> mixing the OSSN into the Security Guide much easier later on. Code 
> Snippets are welcome if they help illustrate the problem.
>
> ### Recommended Actions ###
> [Actions that should be taken to remediate or work around the problem, 
> note that this will often include configuration snippets]
>
> ### Contacts / References ###
> This OSSN :[The URL of the OSSN]
> Original LaunchPad Bug : [The URL of the original Launchpad Bug, if 
> there was one]
> OpenStack Security ML : openstack-security at lists.openstack.org
> OpenStack Security Group :https://launchpad.net/~openstack-ossg 
> <https://launchpad.net/%7Eopenstack-ossg>
> CVE: [Any CVE]
>
> [Any other References]
>
> *From:*Sriram Subramanian [mailto:sriram at sriramhere.com]
> *Sent:* 14 November 2013 07:01
> *To:* noloader at gmail.com
> *Cc:* Clark, Robert Graham; openstack-security at lists.openstack.org
> *Subject:* Re: [Openstack-security] OpenStack Security Notes - 
> Contributors Wanted
>
> Rob - any emails yet? Are we meeting tomorrow?
>
> On Fri, Nov 8, 2013 at 2:59 AM, Sriram Subramanian 
> <sriram at sriramhere.com <mailto:sriram at sriramhere.com>> wrote:
>
> Perfect.
>
> Rob - please send those emails out. Jeff and I will try to get this 
> rolling, Safe travels!
>
> On Fri, Nov 8, 2013 at 3:02 PM, Jeffrey Walton <noloader at gmail.com 
> <mailto:noloader at gmail.com>> wrote:
>
> Hi Robert,
>
> I'd be happy to help out with spare cycles.
>
> Jeff
>
>
> On Wed, Nov 6, 2013 at 11:08 AM, Clark, Robert Graham
> <robert.clark at hp.com <mailto:robert.clark at hp.com>> wrote:
> > Hi All,
> >
> > I'm looking for help with the OpenStack Security Notes. I currently 
> am struggling to keep up with them and do all the other things I'm 
> involved in.  Individually they don't take that much time so with one 
> or two people helping out they wouldn't be a significant burden.
> >
> > If anyone wants to run the management of this project and publishing 
> the OSSNs I'd be happy to support them in an editorial capacity.
> >
> > Cheers
> > -Rob
> >
> > _______________________________________________
> > Openstack-security mailing list
> > Openstack-security at lists.openstack.org 
> <mailto:Openstack-security at lists.openstack.org>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-security
>
> _______________________________________________
> Openstack-security mailing list
> Openstack-security at lists.openstack.org 
> <mailto:Openstack-security at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-security
>
>
>
> -- 
>
> Thanks,
>
> -Sriram
>
>
>
> -- 
>
> Thanks,
>
> -Sriram
>
>
>
> _______________________________________________
> Openstack-security mailing list
> Openstack-security at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-security

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-security/attachments/20131119/49dd088c/attachment.html>


More information about the Openstack-security mailing list