<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type></HEAD>
<BODY>
<DIV>
<DIV style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">I can setup the repo. <BR><BR>Thanks,<BR>Sriram</DIV></DIV>
<DIV dir=ltr>
<HR>
<SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">From: </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif"><A href="mailto:aj@suse.com">Andreas Jaeger</A></SPAN><BR><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">Sent: </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">8/26/2014 1:22 PM</SPAN><BR><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">To: </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif"><A href="mailto:anne@openstack.org">Anne Gentle</A>; <A href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</A></SPAN><BR><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">Cc: </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif"><A href="mailto:matt.griffin@percona.com">Matt Griffin</A>; <A href="mailto:david.medberry@canonical.com">David Medberry</A>; <A href="mailto:sriram@sriramhere.com">Sriram Subramanian</A></SPAN><BR><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">Subject: </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">Re: [Openstack-docs] High Availability Guide team</SPAN><BR><BR></DIV>On 08/26/2014 08:09 PM, Anne Gentle wrote:<BR>> Hi all, <BR>> Cross-posting to -docs and -operators. <BR>> <BR>> At the Ops mid-cycle meetup this week, Matt Griffin, David Medberry, and<BR>> Sriram Subramanian offered to start a review team for the High<BR>> Availability Guide. It needs some updates and it's best if the review<BR><BR>If this is as successfull as the Security and Training Guides, let's go<BR>for it ;)<BR><BR>> team works similar to the Security Guide -- subject matter experts<BR>> working with core docs team members for reviews. So I'm proposing we<BR>> pull it into its own repo just like the Security Guide. Any reasons not<BR>> to? I think the next steps are:<BR>> <BR>> 1. Propose a patch to openstack/governance to show the repo is governed<BR>> by the Docs program.<BR>> 2. Propose a patch that sets up a separate review team starting with<BR>> Matt, David, and Sriram. We think Emilien would be interested too, sound<BR>> good? Any others? We can have members of openstack-docs-core as well,<BR>> similar to the Security Guide.<BR><BR>I'm happy to help reviewing if need but don't count me in as subject<BR>matter expert.<BR><BR>> 3. Propose a patch that gets that guide building separately in a<BR>> different repo.<BR>> 4. Start working on the four bugs already logged [1] and logged more as<BR>> needed.<BR><BR>If somebody wants to do the initial setup of the repository, feel free<BR>to ask me for help. Anne, if nobody volunteers, I can do it as well,<BR><BR>Andreas<BR><BR>> Any other subtasks? Any interested parties? <BR>> <BR>> Thanks,<BR>> Anne<BR>> <BR>> 1. https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide<BR>> <BR>> <BR>> _______________________________________________<BR>> Openstack-docs mailing list<BR>> Openstack-docs@lists.openstack.org<BR>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs<BR>> <BR><BR><BR>-- <BR>Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi<BR> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<BR> GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<BR> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<BR></BODY></HTML>