[Starlingx-discuss] Documentation being part of the StarlingX development process
Hi Bruce, Following up on my action items from the Community call I wanted to see where to add notes about highlighting that writing documentation should be part of the development process from now on and then do further communications. I came across to this wiki, which is documented to be outdated: https://wiki.openstack.org/wiki/StarlingX/Feature_Development_Process And this documentation page that links to a Storyboard item: https://docs.starlingx.io/contributor/development_process.html As the StoryBoard item doesn’t seem to hold enough information I got a little stuck. Do you have a plan/preference on how to progress? It would be great to have the information on docs.starlingx.io as it is probably easier to find it there and we can link that page to the wiki as well. I can help writing it up, but it would be great to have an outline of the process as I’ve never gone through it myself so I only have partial knowledge. Thanks, Ildikó
This has been on my to do list for a long time and I don't know if/when I will get to it. :( If someone else in the community can drive this, I would be happy to help out. brucej -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa@gmail.com] Sent: Thursday, September 12, 2019 11:43 AM To: Jones, Bruce E <bruce.e.jones@intel.com> Cc: starlingx <starlingx-discuss@lists.starlingx.io> Subject: Documentation being part of the StarlingX development process Hi Bruce, Following up on my action items from the Community call I wanted to see where to add notes about highlighting that writing documentation should be part of the development process from now on and then do further communications. I came across to this wiki, which is documented to be outdated: https://wiki.openstack.org/wiki/StarlingX/Feature_Development_Process And this documentation page that links to a Storyboard item: https://docs.starlingx.io/contributor/development_process.html As the StoryBoard item doesn’t seem to hold enough information I got a little stuck. Do you have a plan/preference on how to progress? It would be great to have the information on docs.starlingx.io as it is probably easier to find it there and we can link that page to the wiki as well. I can help writing it up, but it would be great to have an outline of the process as I’ve never gone through it myself so I only have partial knowledge. Thanks, Ildikó
Hi Bruce, We could talk through the process on one of the community calls and I can write up a first version based on the notes. What do you think? Thanks, Ildikó
On 2019. Sep 12., at 22:43, Jones, Bruce E <bruce.e.jones@intel.com> wrote:
This has been on my to do list for a long time and I don't know if/when I will get to it. :( If someone else in the community can drive this, I would be happy to help out.
brucej
-----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa@gmail.com] Sent: Thursday, September 12, 2019 11:43 AM To: Jones, Bruce E <bruce.e.jones@intel.com> Cc: starlingx <starlingx-discuss@lists.starlingx.io> Subject: Documentation being part of the StarlingX development process
Hi Bruce,
Following up on my action items from the Community call I wanted to see where to add notes about highlighting that writing documentation should be part of the development process from now on and then do further communications.
I came across to this wiki, which is documented to be outdated: https://wiki.openstack.org/wiki/StarlingX/Feature_Development_Process And this documentation page that links to a Storyboard item: https://docs.starlingx.io/contributor/development_process.html
As the StoryBoard item doesn’t seem to hold enough information I got a little stuck. Do you have a plan/preference on how to progress?
It would be great to have the information on docs.starlingx.io as it is probably easier to find it there and we can link that page to the wiki as well. I can help writing it up, but it would be great to have an outline of the process as I’ve never gone through it myself so I only have partial knowledge.
Thanks, Ildikó
Hi Ildiko, thanks - I think that would work and we'd (hopefully) get lots of help :) brucej -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa@gmail.com] Sent: Friday, September 13, 2019 1:58 AM To: Jones, Bruce E <bruce.e.jones@intel.com> Cc: starlingx <starlingx-discuss@lists.starlingx.io> Subject: Re: Documentation being part of the StarlingX development process Hi Bruce, We could talk through the process on one of the community calls and I can write up a first version based on the notes. What do you think? Thanks, Ildikó
On 2019. Sep 12., at 22:43, Jones, Bruce E <bruce.e.jones@intel.com> wrote:
This has been on my to do list for a long time and I don't know if/when I will get to it. :( If someone else in the community can drive this, I would be happy to help out.
brucej
-----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa@gmail.com] Sent: Thursday, September 12, 2019 11:43 AM To: Jones, Bruce E <bruce.e.jones@intel.com> Cc: starlingx <starlingx-discuss@lists.starlingx.io> Subject: Documentation being part of the StarlingX development process
Hi Bruce,
Following up on my action items from the Community call I wanted to see where to add notes about highlighting that writing documentation should be part of the development process from now on and then do further communications.
I came across to this wiki, which is documented to be outdated: https://wiki.openstack.org/wiki/StarlingX/Feature_Development_Process And this documentation page that links to a Storyboard item: https://docs.starlingx.io/contributor/development_process.html
As the StoryBoard item doesn’t seem to hold enough information I got a little stuck. Do you have a plan/preference on how to progress?
It would be great to have the information on docs.starlingx.io as it is probably easier to find it there and we can link that page to the wiki as well. I can help writing it up, but it would be great to have an outline of the process as I’ve never gone through it myself so I only have partial knowledge.
Thanks, Ildikó
participants (2)
-
Ildiko Vancsa
-
Jones, Bruce E