Open Stack

On 09/10/2014 11:49 AM, Rochelle.RochelleGrober wrote:
> [Rocky Grober] Some parts of the developer documents will be useful
> for enduser developers, such as the API docs (which really are for
> all developers in/on OpenStack), but many of the documents are
> specifically focused on OpenStack *code* developers.  I think
> Endusers, Operators and Docs teams need to work to determine which
> docs belong where, and with links to the main pages where the other
> OpenStack documents live (with a short description of the focus of
> those other document libraries).  For instance, I don't really see
> the Gerrit Workflow document being particularly useful for the
> enduser community.

I haven't conveyed my thoughts clearly. I'll try again.

1) I noticed that the word "developer" appears on
http://developer.OpenStack.org and on http://docs.OpenStack.org/developer
2) developer.Mozilla.org referenced as an example clearly caters for all
sorts of different 'developers' (from Firefox to Firefox OS to html5
apps to tools and more...)

Since:
- we all seem to agree that the word 'developer' means different things
in different contexts and
- well designed information flow can help the readers select their own
paths based on their own needs, and
- Docs.openstack.org is being redesigned and
- currently developer.openstack.org is pretty much a static page with
curated links to outside resources

I don't think it's inappropriate to give a serious thought to widening
the scope of the portal developers.openstack.org.

It's with that in mind, and with the wider picture of a re-design of
Docs.openstack.org that I suggest thinking holistically.

We may want to continue this conversation on another list though as I
think it may be off-topic here.

/stef

-- 
Ask and answer questions on https://ask.openstack.org