Re: [Openstack] Call for help on Grizzly documentation
Hi, Even I'm interested. Ill be working on this for sure. Regards, Pranav On Fri, Mar 15, 2013 at 7:42 PM, Michael Basnight mbasn...@rackspace.comwrote: Of course... I spaced. I'd love to review the doc for this. Sent from my digital shackles On Mar 15, 2013, at 5:47 AM, Anne Gentle a...@openstack.org wrote: Yes, go ahead. Use the guidelines we have for Doc bug triage. [1] Hey Bas, a DocImpact would have been ideal on that commit message so we could already have a doc bug logged. [2] Thanks, Anne 1. https://wiki.openstack.org/wiki/Documentation/HowTo#Doc_Bug_Triaging_Guidelines 2. https://wiki.openstack.org/wiki/Documentation/HowTo#Using_the_DocImpact_Flag_in_a_Commit_Message On Fri, Mar 15, 2013 at 6:11 AM, Jérôme Gallard jeronimo...@gmail.comwrote: Hi Anne, I'm a newbie in the documentation area but, I would like to give an help. I haven't found any documentations (or open bug) regarding the cinder multi-backend feature ( https://wiki.openstack.org/wiki/Cinder-multi-backend -- https://review.openstack.org/#/c/21815/ ). Do you know if this documentation is planed to be written? Can I open a bug for this? Thanks a lot, Jérôme On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle a...@openstack.org wrote: Hi all, You all did great with DocImpact, but now that we're less than a month from release, the tiny doc team is facing a long list of doc bugs that won't be done by April 4th, many generated by DocImpact flags. We typically do a release of the docs about a month after the actual release date, to ensure packages are available and to try to get our doc bug backlog to a manageable level. As you can see from our backlog for operator docs in openstack-manuals [1] and API docs in api-site [2], there are over 50 confirmed doc bugs for Grizzly operator and admin docs and less than 20 for API docs. With those numbers we need all the help we can get. Please dive in, the patch process is just like code and fully documented. [3] We're on IRC in #openstack-doc and can answer any questions you have as you go. Thanks! Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps 1. https://launchpad.net/openstack-manuals/+milestone/grizzly 2. https://launchpad.net/openstack-api-site/+milestone/grizzly 3. http://wiki.openstack.org/Documentation/HowTo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Call for help on Grizzly documentation
Hi Anne, I'm a newbie in the documentation area but, I would like to give an help. I haven't found any documentations (or open bug) regarding the cinder multi-backend feature ( https://wiki.openstack.org/wiki/Cinder-multi-backend -- https://review.openstack.org/#/c/21815/ ). Do you know if this documentation is planed to be written? Can I open a bug for this? Thanks a lot, Jérôme On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle a...@openstack.org wrote: Hi all, You all did great with DocImpact, but now that we're less than a month from release, the tiny doc team is facing a long list of doc bugs that won't be done by April 4th, many generated by DocImpact flags. We typically do a release of the docs about a month after the actual release date, to ensure packages are available and to try to get our doc bug backlog to a manageable level. As you can see from our backlog for operator docs in openstack-manuals [1] and API docs in api-site [2], there are over 50 confirmed doc bugs for Grizzly operator and admin docs and less than 20 for API docs. With those numbers we need all the help we can get. Please dive in, the patch process is just like code and fully documented. [3] We're on IRC in #openstack-doc and can answer any questions you have as you go. Thanks! Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps 1. https://launchpad.net/openstack-manuals/+milestone/grizzly 2. https://launchpad.net/openstack-api-site/+milestone/grizzly 3. http://wiki.openstack.org/Documentation/HowTo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Call for help on Grizzly documentation
Yes, go ahead. Use the guidelines we have for Doc bug triage. [1] Hey Bas, a DocImpact would have been ideal on that commit message so we could already have a doc bug logged. [2] Thanks, Anne 1. https://wiki.openstack.org/wiki/Documentation/HowTo#Doc_Bug_Triaging_Guidelines 2. https://wiki.openstack.org/wiki/Documentation/HowTo#Using_the_DocImpact_Flag_in_a_Commit_Message On Fri, Mar 15, 2013 at 6:11 AM, Jérôme Gallard jeronimo...@gmail.comwrote: Hi Anne, I'm a newbie in the documentation area but, I would like to give an help. I haven't found any documentations (or open bug) regarding the cinder multi-backend feature ( https://wiki.openstack.org/wiki/Cinder-multi-backend -- https://review.openstack.org/#/c/21815/ ). Do you know if this documentation is planed to be written? Can I open a bug for this? Thanks a lot, Jérôme On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle a...@openstack.org wrote: Hi all, You all did great with DocImpact, but now that we're less than a month from release, the tiny doc team is facing a long list of doc bugs that won't be done by April 4th, many generated by DocImpact flags. We typically do a release of the docs about a month after the actual release date, to ensure packages are available and to try to get our doc bug backlog to a manageable level. As you can see from our backlog for operator docs in openstack-manuals [1] and API docs in api-site [2], there are over 50 confirmed doc bugs for Grizzly operator and admin docs and less than 20 for API docs. With those numbers we need all the help we can get. Please dive in, the patch process is just like code and fully documented. [3] We're on IRC in #openstack-doc and can answer any questions you have as you go. Thanks! Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps 1. https://launchpad.net/openstack-manuals/+milestone/grizzly 2. https://launchpad.net/openstack-api-site/+milestone/grizzly 3. http://wiki.openstack.org/Documentation/HowTo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Call for help on Grizzly documentation
Of course... I spaced. I'd love to review the doc for this. Sent from my digital shackles On Mar 15, 2013, at 5:47 AM, Anne Gentle a...@openstack.orgmailto:a...@openstack.org wrote: Yes, go ahead. Use the guidelines we have for Doc bug triage. [1] Hey Bas, a DocImpact would have been ideal on that commit message so we could already have a doc bug logged. [2] Thanks, Anne 1. https://wiki.openstack.org/wiki/Documentation/HowTo#Doc_Bug_Triaging_Guidelines 2. https://wiki.openstack.org/wiki/Documentation/HowTo#Using_the_DocImpact_Flag_in_a_Commit_Message On Fri, Mar 15, 2013 at 6:11 AM, Jérôme Gallard jeronimo...@gmail.commailto:jeronimo...@gmail.com wrote: Hi Anne, I'm a newbie in the documentation area but, I would like to give an help. I haven't found any documentations (or open bug) regarding the cinder multi-backend feature ( https://wiki.openstack.org/wiki/Cinder-multi-backend -- https://review.openstack.org/#/c/21815/ ). Do you know if this documentation is planed to be written? Can I open a bug for this? Thanks a lot, Jérôme On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle a...@openstack.orgmailto:a...@openstack.org wrote: Hi all, You all did great with DocImpact, but now that we're less than a month from release, the tiny doc team is facing a long list of doc bugs that won't be done by April 4th, many generated by DocImpact flags. We typically do a release of the docs about a month after the actual release date, to ensure packages are available and to try to get our doc bug backlog to a manageable level. As you can see from our backlog for operator docs in openstack-manuals [1] and API docs in api-site [2], there are over 50 confirmed doc bugs for Grizzly operator and admin docs and less than 20 for API docs. With those numbers we need all the help we can get. Please dive in, the patch process is just like code and fully documented. [3] We're on IRC in #openstack-doc and can answer any questions you have as you go. Thanks! Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps 1. https://launchpad.net/openstack-manuals/+milestone/grizzly 2. https://launchpad.net/openstack-api-site/+milestone/grizzly 3. http://wiki.openstack.org/Documentation/HowTo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
