For the wiki, I believe we have to file a request to the OpenStack infra team to enable it. @Dean, is that right? Once we have it, I assume the content on the Etherpad would move to the wiki.
Believe it’s similar for the docs, which would be published from source docs we write and keep in the source code – assuming in stx-docs which may also need to be created. Dean will likely also have to help
us get that set up or tell someone how to do it.
On our side we plan to assign engineers and tech writers to work on documentation and follow all the OpenStack conventions.
brucej
What are the plans for
·
https://wiki.openstack.org/wiki/starlingx
·
and
·
https://docs.openstack.org/starlingx/latest/
Greg.
From: "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com>
Date: Thursday, June 14, 2018 at 6:31 PM
To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io>
Subject: [Starlingx-discuss] Software Development Methodologies and Tools
Our actual StarlingX Etherpad Main Page give us a great overview of the resources to get involved in our community [0]
As a next step, in your experience, how would you suggest to approach the creation of a
“software dev methodology and tools (repo, bug tracking, feature tracking, etc”
How it should look like? Should be it a webpage? a document? Is our OpenStack Developer’s Guide [1] a good example of how this could be implemented and tracked [2]?
Any recommendation is highly valuable to allow us to propose a strong set resources for our community. Thanks in advance.
[0] https://etherpad.openstack.org/p/starlingx
[1]
https://docs.openstack.org/infra/manual/developers.html
[2]
https://storyboard.openstack.org/#!/project/721