<div dir="ltr">This is happening NOW :)<div><br></div><div><a href="https://github.com/openssl/openssl/pulls?q=is%3Apr%20label%3Acode-health">https://github.com/openssl/openssl/pulls?q=is%3Apr%20label%3Acode-health</a><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Feb 27, 2017 at 4:24 PM Richard Levitte <<a href="mailto:levitte@openssl.org">levitte@openssl.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'd suggest prefixing the PR subject with "code-health:" or<br class="gmail_msg">
"[code-health]", just like work in progress is prefixed "WIP:" or<br class="gmail_msg">
"[WIP]"<br class="gmail_msg">
<br class="gmail_msg">
Cheers,<br class="gmail_msg">
Richard<br class="gmail_msg">
<br class="gmail_msg">
In message <<a href="mailto:9ECBF19A-3239-440C-B874-B959B6BB912B@akamai.com" class="gmail_msg" target="_blank">9ECBF19A-3239-440C-B874-B959B6BB912B@akamai.com</a>> on Mon, 27 Feb 2017 14:54:09 +0000, "Short, Todd" <<a href="mailto:tshort@akamai.com" class="gmail_msg" target="_blank">tshort@akamai.com</a>> said:<br class="gmail_msg">
<br class="gmail_msg">
tshort> I’m not sure us mere mortals can add a label to a PR...<br class="gmail_msg">
tshort> --<br class="gmail_msg">
tshort> -Todd Short<br class="gmail_msg">
tshort> // <a href="mailto:tshort@akamai.com" class="gmail_msg" target="_blank">tshort@akamai.com</a><br class="gmail_msg">
tshort> // "One if by land, two if by sea, three if by the Internet."<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> On Feb 27, 2017, at 5:04 AM, Emilia Käsper <<a href="mailto:emilia@openssl.org" class="gmail_msg" target="_blank">emilia@openssl.org</a>><br class="gmail_msg">
tshort> wrote:<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort><br class="gmail_msg">
tshort><br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> Hi OpenSSL developers!<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> We’re always looking for ways to improve code quality and pay our<br class="gmail_msg">
tshort> technical debt. This week we thought we’d run a little experiment.<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> We declare this Tuesday (Feb 28th) Code Health Tuesday. We’ll be<br class="gmail_msg">
tshort> setting some time aside to do cleanups in the codebase. The theme<br class="gmail_msg">
tshort> is “Delete”: we’ll be cleaning up unused files, dead code, and<br class="gmail_msg">
tshort> obsolete hacks. We invite you all to participate on Github!<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> Cheers,<br class="gmail_msg">
tshort> Emilia<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> FAQ:<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> Q: How do I participate?<br class="gmail_msg">
tshort> A: Find something to delete. Create a Github pull request and add<br class="gmail_msg">
tshort> the “code-health” label. We’ll be monitoring Github for quick<br class="gmail_msg">
tshort> turnaround.<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> Q: Which branches should I target?<br class="gmail_msg">
tshort> A: You should target master. In stable branches, code churn comes<br class="gmail_msg">
tshort> with a cost, so let’s focus on the next release.<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> Q: What can I delete?<br class="gmail_msg">
tshort> A: Normal compatibility rules apply. You cannot delete anything<br class="gmail_msg">
tshort> from public headers, remove command-line tool options or prune<br class="gmail_msg">
tshort> supported platform configurations. You can delete dead code,<br class="gmail_msg">
tshort> obsolete workarounds (16-bit platforms!) and outdated<br class="gmail_msg">
tshort> documentation. If you’re not sure about a particular<br class="gmail_msg">
tshort> functionality, open a Github issue and add the “code health”<br class="gmail_msg">
tshort> label.<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> Q: Do you have any tools to find what to delete?<br class="gmail_msg">
tshort> A: We have a coverage report:<br class="gmail_msg">
tshort> <a href="https://coveralls.io/github/openssl/openssl" rel="noreferrer" class="gmail_msg" target="_blank">https://coveralls.io/github/openssl/openssl</a><br class="gmail_msg">
tshort> We’ll also be setting up a tools repo where you can share any<br class="gmail_msg">
tshort> tools that you build.<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> Q: Will you do it again?<br class="gmail_msg">
tshort> A: We hope so! This is an experiment but we’ll be looking into<br class="gmail_msg">
tshort> making it a habit. We have a list of ideas for themed Tuesdays<br class="gmail_msg">
tshort> lined up: Document, Test, Refactor, ...<br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> Q: How did you come up with this idea?<br class="gmail_msg">
tshort> A: We were looking at this file…<br class="gmail_msg">
tshort> <a href="https://github.com/openssl/openssl/blob/master/crypto/pkcs7/pk7_dgst.c" rel="noreferrer" class="gmail_msg" target="_blank">https://github.com/openssl/openssl/blob/master/crypto/pkcs7/pk7_dgst.c</a><br class="gmail_msg">
tshort><br class="gmail_msg">
tshort> --<br class="gmail_msg">
tshort> openssl-dev mailing list<br class="gmail_msg">
tshort> To unsubscribe:<br class="gmail_msg">
tshort> <a href="https://mta.openssl.org/mailman/listinfo/openssl-dev" rel="noreferrer" class="gmail_msg" target="_blank">https://mta.openssl.org/mailman/listinfo/openssl-dev</a><br class="gmail_msg">
tshort><br class="gmail_msg">
tshort><br class="gmail_msg">
--<br class="gmail_msg">
openssl-dev mailing list<br class="gmail_msg">
To unsubscribe: <a href="https://mta.openssl.org/mailman/listinfo/openssl-dev" rel="noreferrer" class="gmail_msg" target="_blank">https://mta.openssl.org/mailman/listinfo/openssl-dev</a><br class="gmail_msg">
</blockquote></div></div></div>