<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 30, 2013 at 1:36 PM, Sean Roberts <span dir="ltr"><<a href="mailto:seanrob@yahoo-inc.com" target="_blank">seanrob@yahoo-inc.com</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:10pt;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif"><div>

<span>I tend to agree. Comments are more social, but quickly out of date. Bugs are actionable. If we should the link for an active bug against a page for the comments to be posted on launchpad, then that would be helpful. </span></div>

</div></div></blockquote><div><br></div><div>That's what happens now, so I think we're good with the overall process:</div><div><br></div><div>1. For books that have a release URL, turn disqus comments and bug reporting on.</div>

<div>2. For books without a release URL, ensure the bug reporting link is on.</div><div>3. If a comment is logged without a corresponding bug, manually log a doc bug if needed.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div><div style="font-size:10pt;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif"><span class="HOEnZb"><font color="#888888"><div></div><div> </div><div><div><b><br></b></div><div style="font-family:arial,helvetica,clean,sans-serif;font-weight:bold">

<b>Sean Roberts</b></div><div>Infrastructure Strategy, Yahoo</div><div><span><a rel="nofollow" href="mailto:seanrob@yahoo-inc.com" target="_blank">seanrob@yahoo-inc.com</a></span></div><div><a href="tel:%28925%29%20980-4729" value="+19259804729" target="_blank">(925) 980-4729</a></div>

</div></font></span><div><div class="h5"><div style="display:block"> <br> <br> <div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:10pt"> <div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:12pt">

 <div dir="ltr"> <font face="Arial"> On Monday, December 30, 2013 6:18 AM, Diane Fleming <<a href="mailto:diane.fleming@RACKSPACE.COM" target="_blank">diane.fleming@RACKSPACE.COM</a>> wrote:<br> </font> </div>  <div>

Now that David Cramer has implemented the "log a bug against this page"<br clear="none">feature, I don't think we need disqus for these books.<br clear="none"><br clear="none">Disqus is not particularly useful (as far as I'm concerned!)<br clear="none">

<br clear="none"><br clear="none">Diane<br clear="none">----------------------------------------------<br clear="none">Diane Fleming<br clear="none">Software Developer II - US<br clear="none"><br clear="none"><a shape="rect" href="mailto:diane.fleming@rackspace.com" target="_blank">diane.fleming@rackspace.com</a><br clear="none">

Cell  <a href="tel:512.323.6799" value="+15123236799" target="_blank">512.323.6799</a><br clear="none">Office <a href="tel:512.874.1260" value="+15128741260" target="_blank">512.874.1260</a><br clear="none">Skype drfleming0227<br clear="none">

Google-plus <a shape="rect" href="mailto:diane.fleming@gmail.com" target="_blank">diane.fleming@gmail.com</a><br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none">

On 12/30/13 4:19 AM, "Andreas Jaeger" <<a shape="rect" href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>> wrote:<br clear="none"><br clear="none">>I noticed that some of the manuals that we build from trunk do not have<br clear="none">

>disqus enabled:<br clear="none">>* End User Guide<br clear="none">>* Admin User Guide<br clear="none">>* Cloud Administrator Guide<br clear="none">>* Operations Guide<br clear="none">>* Security Guide<br clear="none">

>* Virtual Machine Image Guide<br clear="none">>* Training Guides<br clear="none">><br clear="none">>Which of these should get disqus enabled?<br clear="none">><br clear="none">>I can do the changes but like to know whether this is desired,<br clear="none">

>Andreas<br clear="none">>-- <br clear="none">> Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br clear="none">

>  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br clear="none">>   GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br clear="none">>    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126<br clear="none">

><br clear="none">>_______________________________________________<br clear="none">>Openstack-docs mailing list<br clear="none">><a shape="rect" href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a><br clear="none">

><a shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><div><br clear="none"><br clear="none"><br clear="none">

_______________________________________________<br clear="none">Openstack-docs mailing list<br clear="none"><a shape="rect" href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a><br clear="none">

<a shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a></div><br><br></div>  </div> </div>  </div> </div>

</div></div></div><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></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>