<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I like it and +1 for “identity-api” since it will have both authZ and authN capabilities.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> openstack-bounces+joe.savak=rackspace.com@lists.launchpad.net [mailto:openstack-bounces+joe.savak=rackspace.com@lists.launchpad.net]
<b>On Behalf Of </b>Anne Gentle<br>
<b>Sent:</b> Wednesday, September 07, 2011 6:57 AM<br>
<b>To:</b> openstack@lists.launchpad.net<br>
<b>Subject:</b> Re: [Openstack] API documentation move<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello again - <br>
In yesterday's team meeting, Brian Lamar brought up a good point - why name the API projects after the project name, why not the product name? This makes a lot of sense to me. So the names for the API repos will be:<br>
<br>
compute-api<br>
identity-api (should this be auth-api?)<br>
image-api<br>
storage-api (should this be object-api?)<br>
<br>
Let me know your feedback on this naming standard.<br>
<br>
Thanks Jay for catching the keystone-api typo. :) <br>
<br>
Anne<o:p></o:p></p>
<div style="margin-top:24.0pt;margin-bottom:24.0pt" name="sig_d41d8cd98f">
<div>
<p class="MsoNormal"><strong><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#666666">Anne Gentle</span></strong><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#666666">
<br>
<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#666666"><a href="http://justwriteclick.com/" target="_blank">my blog</a> |
<a href="http://xmlpress.net/publications/conversation-community/" target="_blank">
my book</a> | <a href="http://www.linkedin.com/in/annegentle" target="_blank">LinkedIn</a> |
<a href="http://del.icio.us/annegentle" target="_blank">Delicious</a> | <a href="http://twitter.com/annegentle" target="_blank">
Twitter</a> <o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal">On Tue, Sep 6, 2011 at 1:02 PM, Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi all -<br>
<br>
I wanted to discuss some changes to the API documentation for each project prior to implementation to make sure I'm not missing any crucial detail and to ensure you all feel you have ownership of the solution and input into it. My goal is to move all the OpenStack
 documentation into github repos. In doing so, I will also move all the API documentation into separate repos with a goal of completing the move by October 1st.<br>
<br>
Here is my current proposal, please feel free to suggest corrections as you see fit.
<br>
<br>
1. Create new github repos named <project>-api that contain:<br>
API documentation including existing API Dev Guides and in the case of Nova, an API Spec. Four new projects for now: openstack/glance-api, openstack/keystone, openstack/nova-api, openstack/swift-api.
<br>
<br>
2. Create connection to Gerrit for review by core devs for each project, plus the creation of a new group, openstack-core-doc, for reviews of all four projects.<br>
<br>
3. Create a new github repo named openstack/openstack-manuals to contain sys admin documentation such as the Admin manuals (installation, configuration, administration docs).<br>
<br>
4. Automated build/publish on Jenkins to the correct location on <a href="http://docs.openstack.org/" target="_blank">
docs.openstack.org</a> (or <a href="http://project.openstack.org/" target="_blank">
project.openstack.org</a> as appropriate), either /diablo or /api or /incubation depending on project's state. Also includes Jenkins jobs to validate the docs pre-merge, for XML validation and testing for missing figures.<br>
<br>
Please give me your feedback by the end of this week so we can make the next moves. Ha! Move! I've also added this item for discussion at today's team meeting.
<br>
<br>
Thanks,<br>
Anne<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<font face="monospace">This email may include confidential information. If you received it in error, please delete it.</font></body>
</html>