<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Question,<div><br></div><div>Do you have any Maven ninja skills?<br><div>
<div><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="MsoNormal">Regards,</p><p class="MsoNormal">Colin</p><p class="MsoNormal">If you would like to schedule a time to speak with me, please <i><a href="https://my.timedriver.com/L89ZG">click here</a></i> to see my calendar and pick a time that works for your schedule. The system will automatically send us both an outlook meeting invite.</p><div>Colin McNamara<br>(858)208-8105<br>CCIE #18233,VCP<br><a href="http://www.colinmcnamara.com/">http://www.colinmcnamara.com</a><br><a href="http://www.linkedin.com/in/colinmcnamara">http://www.linkedin.com/in/colinmcnamara</a><br><br>"The difficult we do immediately, the impossible just takes a little<br>longer"</div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline">
</div>
<br><div><div>On Jul 15, 2013, at 1:15 PM, Denis Bradford <<a href="mailto:denisbatgm@gmail.com">denisbatgm@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Thanks all for the helpful suggestions.<br><br><blockquote type="cite">see if there are more conventions we could add to better use DocBook's semantic markup...<br>You can always pick up doc bugs after working through a few convention/markup types of patches.<br></blockquote><br>I like that the current set of conventions is minimal -- the less<br>process the better, imo. But I'll read them again with an eye to what<br>makes sense for these docs. Maybe I can run any ideas by you (Anne) at<br>that point.<br><br><blockquote type="cite">What gets you interested in OpenStack?<br></blockquote><br>No specific project yet. Where ever newbies usually start (gui<br>procedures, reference, markup patches as mentioned above?) is fine<br>with me. Maybe after I get my feet wet, a focus will come to mind. I<br>might also mention that I like working with graphics, and am<br>reasonably handy with Gimp and Inkscape.<br><br><blockquote type="cite">In case you're ever in the mood to do any xslt or tools work as well, let us know.<br></blockquote><br>Thanks David, I will. I'm not in your league when it comes to tools,<br>but might spot an occasional style sheet bug.<br><br>P.S. I'll be attending the OpenStack meetup near MIT tomorrow night:<br> <a href="http://www.meetup.com/Openstack-Boston/events/126684312/t/wm1_5/?rv=wm1">http://www.meetup.com/Openstack-Boston/events/126684312/t/wm1_5/?rv=wm1</a><br>The presentation will be over my head, but I thought documentation<br>should be represented ;-)<br><br>_______________________________________________<br>Openstack-docs mailing list<br><a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs<br></blockquote></div><br></div></body></html>