Ah... Well, just add "Code Health" to your PR title, and we'll do the labeling.
On Mon, Feb 27, 2017 at 3:54 PM Short, Todd <tsh...@akamai.com> wrote: > I’m not sure us mere mortals can add a label to a PR... > -- > -Todd Short > // tsh...@akamai.com > // "One if by land, two if by sea, three if by the Internet." > > On Feb 27, 2017, at 5:04 AM, Emilia Käsper <emi...@openssl.org> wrote: > > Hi OpenSSL developers! > > We’re always looking for ways to improve code quality and pay our > technical debt. This week we thought we’d run a little experiment. > > We declare this Tuesday (Feb 28th) Code Health Tuesday. We’ll be setting > some time aside to do cleanups in the codebase. The theme is “Delete”: > we’ll be cleaning up unused files, dead code, and obsolete hacks. We invite > you all to participate on Github! > > Cheers, > Emilia > > FAQ: > > Q: How do I participate? > A: Find something to delete. Create a Github pull request and add the > “code-health” label. We’ll be monitoring Github for quick turnaround. > > Q: Which branches should I target? > A: You should target master. In stable branches, code churn comes with a > cost, so let’s focus on the next release. > > Q: What can I delete? > A: Normal compatibility rules apply. You cannot delete anything from > public headers, remove command-line tool options or prune supported > platform configurations. You can delete dead code, obsolete workarounds > (16-bit platforms!) and outdated documentation. If you’re not sure about a > particular functionality, open a Github issue and add the “code health” > label. > > Q: Do you have any tools to find what to delete? > A: We have a coverage report: https://coveralls.io/github/openssl/openssl > <https://urldefense.proofpoint.com/v2/url?u=https-3A__coveralls.io_github_openssl_openssl&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=QBEcQsqoUDdk1Q26CzlzNPPUkKYWIh1LYsiHAwmtRik&m=13nqmVuCNoNG9k4QVgE5mgd1cfBW9qihs8MSZ8JrXIM&s=MyxZLYoIPNgIVwojq5YuUwF4zW5oHhuq79iGx-CpFNE&e=> > We’ll also be setting up a tools repo where you can share any tools that > you build. > > Q: Will you do it again? > A: We hope so! This is an experiment but we’ll be looking into making it a > habit. We have a list of ideas for themed Tuesdays lined up: Document, > Test, Refactor, ... > > Q: How did you come up with this idea? > A: We were looking at this file… > *https://github.com/openssl/openssl/blob/master/crypto/pkcs7/pk7_dgst.c > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openssl_openssl_blob_master_crypto_pkcs7_pk7-5Fdgst.c&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=QBEcQsqoUDdk1Q26CzlzNPPUkKYWIh1LYsiHAwmtRik&m=13nqmVuCNoNG9k4QVgE5mgd1cfBW9qihs8MSZ8JrXIM&s=X7rAKijz4Sb6PLyqD87MXKi1Xrs3vJN7bFdk2ZJT2RY&e=>* > > -- > openssl-dev mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev > > > -- > openssl-dev mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev >
-- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev