Open Stack

On Sat, May 7, 2016 at 1:51 PM, Andreas Jaeger <aj at suse.com> wrote:

> On 05/07/2016 06:09 PM, Ildikó Váncsa wrote:
> > Hi Matt,
> >
> > I'm open to discuss what would be the best way forward in this topic.
> First of all I would like to understand the intention with document
> structures long term to see how we can have a scalable and maintainable
> process.
> >
> > My experience is that keeping the documentation up to date separately
> from the code can be difficult that results in outdated materials, which
> also leads to bad user experience and impression.
> >
> > Would this topic be sufficient for one of the team meetings?
>
> Right now we have the Install Guide as first guide where we move content
> to the teams and still want to provide this from one place.
>
> I suggest that we do the Install Guide first and then consider whether
> that is a model that we should use for other documents as well,
>

Another example model to keep an eye on is the current move of content from
api-site to project repos. Let's see how that goes as well --
quality/accuracy, usefulness, and ongoing maintenance as first goals.

Anne


>
> 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, Graham Norton,
>        HRB 21284 (AG Nürnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
>
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Anne Gentle
www.justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20160507/7ae85806/attachment.html>