<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 24, 2012, at 9:28 AM, Ghe Rivero wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 24, 2012 at 2:40 PM, Mark McLoughlin <span dir="ltr"><<a href="mailto:markmc@redhat.com" target="_blank">markmc@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
Hi Ghe,<br>
<div><br>
On Tue, 2012-04-24 at 12:15 +0200, Ghe Rivero wrote:<br>
> Hi Everyone,<br>
> i've been looking through wsgi code, and i have found a lot of<br>
> duplicated code between all the projects.<br>
<br>
</div>Thanks for looking into this. It sounds quite daunting.<br>
<br>
I wonder could we do this iteratively by extract the code which is most<br>
common into openstack-common, move the projects over to that and then<br>
start again on the next layer?<br>
<br>
Cheers,<br>
Mark.<br></blockquote><div><br></div><div>I have plans to try to move as much as possible into openstack-common. I will start with nova as a test bed and see what we get from there. My future plans include db code and tests (in the case of quantum, plugins test also have a lot of duplicated code).</div>
<div>I register a bp for the wsgi issue: <a href="https://blueprints.launchpad.net/openstack-common/+spec/wsgi-common">https://blueprints.launchpad.net/openstack-common/+spec/wsgi-common</a></div><div><br></div><div>Ghe Rivero</div>
</div></div></blockquote></div><br><div>Is there a code metrics site that continually reports on metrics like duplication? Adding Ghe's report to a metric site would be the first step. That has always been a starting point as it gives code reviewers quick evaluation criteria to stop duplication before it ends up in trunk. Going at it directly fixes it looking backward but the duplication ends up back int the code eventually. The reports help fix the issue going forward.</div></body></html>