Open Stack

One of our larger problems is that people just use Google, and Google loves
to rank our old (often unlinked on d.o.o) content higher than new content
because we can't effectively delete files. Without knowledge of release
naming/cycle and the latest version, people often stumble upon older
documentation that is either irrelevant or of questionable quality. For
example, compare the installation guide for Juno with the installation
guide for Mitaka.

On Thu, Jun 16, 2016 at 6:01 PM, Lana Brindley <openstack at lanabrindley.com>
wrote:

> Hi Pranav,
>
> Thanks for sending this, I really appreciate all the kind words you have
> for the project!
>
> As far as 'extra' efforts, I do try to get involved as much as possible,
> but there's always more that can be done (and by people who are not me!).
> I'm considering putting in a documentation talk for Barcelona, which I
> haven't done since becoming PTL, and I'm also spending a lot of time
> talking to our CPLs to ensure we have project visibility. The What's Up,
> Doc newsletter is also my way of getting our message out to other groups.
>
> I'm always up for new ideas, though :)
>
> L
>
> On 15/06/16 23:44, Pranav Salunke wrote:
> > Hello,
> >
> > I was made to think about the visibility of docs in the internet as I
> heard from the users of OpenStack about their reference documentation
> coming from *other sources*. I am not against other people/companies
> posting OpenStack related documentation. But most of the problems/learning
> that this team wanted to have was OpenStack specific and not vendor or
> platform or plugin specific. I asked them if they found some shortcomings
> from the upstream documentation and they barely had any idea about all
> different things that the Documentation Project covers.
> >
> > IMHO OpenStack Documentation project provides really high quality
> documentation covering a vast variety of topics addressing many levels of
> positions (Devs, Ops, Beginners, Architects, Sales, and more!) and we have
> a lively community which basically provides us with an advantage to keep
> these Docs, books, guides etc. updated with the speed and agility which is
> unmatched and rather difficult to compete with.
> >
> > I wanted to ask if we are taking any extra efforts apart from normal
> Analytics and SEO bits for promoting the official OpenStack documentation!
> It would also work in getting more contributors as the side effect but the
> main motivation point is to provide more visibility to the community,
> users, especially beginners. I would personally love to see some efforts in
> this direction, any efforts like more visibility during the summit and
> other community events around the world, and more ... hope to hear some
> interesting things here.
> >
> > Regards,
> > Pranav
> >
> >
> > _______________________________________________
> > OpenStack-docs mailing list
> > OpenStack-docs at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> >
>
> --
> Lana Brindley
> Technical Writer
> Rackspace Cloud Builders Australia
> http://lanabrindley.com
>
>
> _______________________________________________
> 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/20160616/711da05c/attachment.html>