Open Stack

On 06/28/2016 08:33 PM, Steve Martinelli wrote:
> I'm cool with the existing keystone repo and adding to docs. If we hit 
> a huge amount of content then we can migrate to a new repo. I think 
> Adam's main concern with this approach is that we reduce the 
> contributors down to folks that know the gerrit workflow.

We don't want a static troubleshooting guide.  We want people to be able 
to ask questionss and link them to answers, have community members add 
their own answer...in short, what we hae in "ask.openstack" now, but not 
well done or maintained.

Its often not a Keystone problem, but a Nova, Glance etc problem. We 
can't stick the Answer in a Keystone repo.





>
> On Tue, Jun 28, 2016 at 8:19 PM, Jamie Lennox <jamielennox at gmail.com 
> <mailto:jamielennox at gmail.com>> wrote:
>
>
>
>     On 29 June 2016 at 09:49, Steve Martinelli <s.martinelli at gmail.com
>     <mailto:s.martinelli at gmail.com>> wrote:
>
>         I think we want something a bit more organized.
>
>         Morgan tossed the idea of a keystone-docs repo, which could have:
>
>         - The FAQ Adam is asking about
>         - Install guides (moved over from openstack-manuals)
>         - A spot for all those neat and unofficial blog posts we do
>         - How-to guides
>         - etc...
>
>         I think it's a neat idea and warrants some discussion. Of
>         course, we don't want to be the odd project out.
>
>
>     What would be the advantage of a new repo rather than just using
>     the keystone/docs folder. My concern is that docs/ already gets
>     stagnate but a new repo would end up being largely ignored and at
>     least theoretically you can update docs/ when the relevant code
>     changes.
>
>
>         On Tue, Jun 28, 2016 at 6:00 PM, Ian Cordasco
>         <sigmavirus24 at gmail.com <mailto:sigmavirus24 at gmail.com>> wrote:
>
>             -----Original Message-----
>             From: Adam Young <ayoung at redhat.com
>             <mailto:ayoung at redhat.com>>
>             Reply: OpenStack Development Mailing List (not for usage
>             questions)
>             <openstack-dev at lists.openstack.org
>             <mailto:openstack-dev at lists.openstack.org>>
>             Date: June 28, 2016 at 16:47:26
>             To: OpenStack Development Mailing List
>             <openstack-dev at lists.openstack.org
>             <mailto:openstack-dev at lists.openstack.org>>
>             Subject:  [openstack-dev] Troubleshooting and
>             ask.openstack.org <http://ask.openstack.org>
>
>             > Recently, the Keystone team started brainstormin a
>             troubleshooting
>             > document. While we could, eventually put this into the
>             Keystone repo,
>             > it makes sense to also be gathering troubleshooting
>             ideas from the
>             > community at large. How do we do this?
>             >
>             > I think we've had a long enough run with the
>             ask.openstack.org <http://ask.openstack.org> website
>             > to determine if it is really useful, and if it needs an
>             update.
>             >
>             >
>             > I know we getting nuked on the Wiki. What I would like
>             to be able to
>             > generate is Frequently Asked Questions (FAQ) page, but
>             as a living
>             > document.
>             >
>             > I think that ask.openstack.org
>             <http://ask.openstack.org> is the right forum for this,
>             but we need
>             > some more help:
>             >
>             > It seems to me that keystone Core should be able to
>             moderate Keystone
>             > questions on the site. That means that they should be
>             able to remove
>             > old dead ones, remove things tagged as Keystone that do
>             not apply and so
>             > on. I would assume the same is true for Nova, Glance,
>             Trove, Mistral
>             > and all the rest.
>             >
>             > We need some better top level interface than just the
>             tags, though.
>             > Ideally we would have a page where someone lands when
>             troubleshooting
>             > keystone with a series of questions and links to the
>             discussion pages
>             > for that question. Like:
>             >
>             >
>             > I get an error that says "cannot authenticate" what do I do?
>             >
>             > What is the Engine behind "ask.openstack.org
>             <http://ask.openstack.org>?" does it have other tools
>             > we could use?
>
>             The engine is linked in the footer: https://askbot.com/
>
>             I'm not sure how much of it is reusable but it claims to
>             be able to do
>             some of the things I think you're asking for except it doesn't
>             explicitly mention deleting comments/questions/etc.
>
>             --
>             Ian Cordasco
>
>             __________________________________________________________________________
>             OpenStack Development Mailing List (not for usage questions)
>             Unsubscribe:
>             OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>             <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>             http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>         __________________________________________________________________________
>         OpenStack Development Mailing List (not for usage questions)
>         Unsubscribe:
>         OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>         <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160701/a881c9d8/attachment.html>