[Openstack-security] Developer Guidance

Clark, Robert Graham robert.clark at hp.com
Fri Feb 27 14:40:16 UTC 2015



On 26/02/2015 23:58, "Andreas Jaeger" <aj at suse.com> wrote:

>On 02/26/2015 08:23 PM, Clark, Robert Graham wrote:
>> On 26/02/2015 10:47, "Andreas Jaeger" <aj at suse.com> wrote:
>> 
>>> On 02/26/2015 07:20 PM, Clark, Robert Graham wrote:
>>>> Hi All,
>>>>
>>>> The developer guidance stuff now lives in a Github organisation
>>>> ŒOpenStack-Security¹
>>>>
>>>> https://github.com/openstack-security/Developer-Guidance
>>>>
>>>> If you want access and don¹t have it (most contributors already should
>>>> have) please ping me and I¹ll add you.
>>>
>>> I suggest to move this to a folder in the security-doc repository so
>>> that you can use the same workflow here as for other documents,
>>>
>>> Andreas
>>> -- 
>>> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>>>  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>>>   GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
>>>       Graham Norton, HRB 21284 (AG Nürnberg)
>>>    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>>>
>> 
>> 
>> Yeah we all like using gerrit, however we don¹t have a nice way to parse
>> and publish the Markdown at the moment. We will do that eventually but
>> currently it¹s sat in GH because it does nice things with Markdown and
>>the
>> docs aren¹t finished yet.
>
>You could convert to RST instead of using markdown, shouldn't be that
>much work - and docs is going to RST as well right now, so I can help
>with publishing workflow (and we don't need to publish *directly* if you
>don't want),
>
>Andreas
>-- 

We’ll get there Andreas, this was the quickest and nicest way to get to a
form of output that we wanted during the documentation sprint that was
part of the mid-cycle. We figured we could convert MD to anything else
when we wanted to :)

-Rob



More information about the Openstack-security mailing list