Open Stack

My experience.work here.

I think all become under one doc.project will be the best, and extend
training guide to workshop guide.

Make all in one rather all independent.

And focus.in.reuse and collaborate between subproject

That my opinion
On Jun 10, 2014 6:54 PM, "Anne Gentle" <anne at openstack.org> wrote:

>
>
>
> On Tue, Jun 10, 2014 at 4:31 AM, Christian Berendt <berendt at b1-systems.de>
> wrote:
>
>> On 06/10/2014 04:35 AM, Jeremy Stanley wrote:
>> > Conversely, there is nothing in our current policies which would
>> > prevent a project under incubation within an official program from
>> > having its Git repository called openstack/something (and in fact we
>> > seem to generally encourage it).
>>
>> Why not using openstack/training-guides when that's possible?
>>
>>
> That's what I'm thinking as well, let's treat this move like the security
> guide and move it to openstack/training-guides.
>
> I'll amend Tom's patch.
>
> Anne
>
>
>> Christian.
>>
>> --
>> Christian Berendt
>> Cloud Computing Solution Architect
>> Mail: berendt at b1-systems.de
>>
>> B1 Systems GmbH
>> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
>> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140610/7a6cff38/attachment.html>