<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 31, 2013 at 1:32 PM, Diane Fleming <span dir="ltr"><<a href="mailto:diane.fleming@rackspace.com" target="_blank">diane.fleming@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Steve,<br>
<br>
<br>
Good points.<br>
<br>
I have no objections to you moving shared content into the "common"<br>
directory.<br>
<br>
I will move my "common" files into common this afternoon. (The CLI guide<br>
is going away - I just wanted it to build successfully until I got the end<br>
and admin user guides sorted out - so I sources files for the CLI guide<br>
from the user guide.)<br>
<br>
Once I move my files, you can continue moving anything else that should go<br>
there as you see fit!<br>
<br>
Thanks,<br>
<br>
<br>
Diane<br>
----------------------------------------------<br>
Diane Fleming<br>
Software Developer II - US<br>
<br>
<a href="mailto:diane.fleming@rackspace.com">diane.fleming@rackspace.com</a><br>
Cell <a href="tel:512.323.6799" value="+15123236799">512.323.6799</a><br>
Office <a href="tel:512.874.1260" value="+15128741260">512.874.1260</a><br>
Skype drfleming0227<br>
Google-plus <a href="mailto:diane.fleming@gmail.com">diane.fleming@gmail.com</a><br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
On 7/31/13 1:20 PM, "Steve Gordon" <<a href="mailto:sgordon@redhat.com">sgordon@redhat.com</a>> wrote:<br>
<br>
>Hi all,<br>
><br>
>In the lead up to the Grizzly release I made a handful of commits to move<br>
>shared content into the common directory, where it was not already there.<br>
>This had the effect of:<br>
><br>
>- Making it more obvious which content was actually shared (in one case I<br>
>even found a file inside the openstack-compute-admin folder that was no<br>
>longer used in that guide at all, but was used by others).<br></div></div></blockquote><div><br></div><div>Great find. Would you mind another search round for files not being used anywhere at all and patching to remove those? </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
>- Making it easier for me to transform/build with Publican (an admittedly<br>
>selfish reason but listing for completeness :)).<br>
><br></div></div></blockquote><div><br></div><div>Sure, good reason!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
>Looking at the state of the repository as it stands today I have noticed<br>
>that a few instances of the following have been creeping back in as a<br>
>result of the restructuring efforts:<br>
><br>
>- Content that has become common (linked in to multiple guides) but not<br>
>been moved to a location beneath the "common" folder (I'm ignoring here<br>
>the case where the cli-guide now largely includes content from the<br>
>user-guide folder as I believe the cli-guide is effectively now part of<br>
>the user-guide effort?).<br></div></div></blockquote><div><br></div><div>Yep, Diane's on it. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">
>- Content in the "common" folder that itself links in content from other<br>
>guides - effectively resulting in (1).<br>
><br>
>I was wondering whether there are any objections to me continuing to<br>
>submit patches to move common content falling into these categories into<br>
>common (and of course update the relevant xi:includes)? There are by no<br>
>means a lot of these but I feel like it's probably easier to keep on top<br>
>of them as they come to light rather than waiting - that is if others<br>
>agree it's not problematic for me to be doing this. I was also wondering<br>
>if there might be a need to define a deeper taxonomy for content under<br>
>the "common" folder?<br></div></div></blockquote><div><br></div><div>No objections at all, I love this cleanup effort. </div><div><br></div><div>For a deeper taxonomy, do you mean you'll put more folders in to help show where it's reused? Or some file renaming? Let me know your thoughts there so when I review I know what the taxonomy will be. </div>
<div><br></div><div>Thanks,</div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
>Thanks,<br>
><br>
>Steve<br>
><br>
>_______________________________________________<br>
>Openstack-docs mailing list<br>
><a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</div></div>