Open Stack

We have had teams publish to readthedocs.org in the past. Linking to the docs there from a home page in the wiki should make them discoverable. 

Doug

> On Dec 2, 2015, at 4:01 AM, Dina Belova <dbelova at mirantis.com> wrote:
> 
> Thierry,
> 
> the main issue is to publish docs somewhere people will be easily able to read them and leave feedback on them. So just repository with the docs is not enough (wherever to place it, openstack/* is cool), we need a place to publish them. And as I understand, we need some excuse to publish the docs to the docs.openstack.org - like being now part of 'Rally' program.
> 
> Cheers,
> Dina
> 
>> On Wed, Dec 2, 2015 at 11:53 AM, Thierry Carrez <thierry at openstack.org> wrote:
>> Dina Belova wrote:
>> > of course that's possible in future if there will be significant results
>> > and TC will recognise them ;)
>> >
>> > Ok, so I believe we may use Rally as a parent here, I may add new docs
>> > project as a child to Rally in programs.yam :)
>> > If everybody is ok with that, let's do it.
>> 
>> I'm fine with that option, but would like to suggest an alternative
>> solution. You could set up a git repository under openstack/* while not
>> being an official team (what used to be "stackforge").
>> 
>> Your work group currently needs a git repository under Gerrit to start
>> working, and it's too early (in terms of team results) to apply to be an
>> official team. Just setting up the git repo under the OpenStack
>> infrastructure sounds like a reasonable solution ?
>> 
>> --
>> Thierry Carrez (ttx)
> 
> 
> 
> -- 
> Best regards,
> Dina Belova
> Software Engineer
> Mirantis Inc.
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151202/842b8a6d/attachment.html>