On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote: > Note that this is just how to help me, not a consensus view from the > whole team, though I have no doubt much of it will be helpful to the > team, too. > > 1. Triage RT (https://rt.openssl.org/). > > RT has been neglected for a long time. People could usefully go > through it and identify: > > a) Tickets that can be closed > > b) Tickets that should have action taken, and how urgent that action is. > > If a ticket describes a potential security issue, then please don't > just announce it to the list. Instead send it to > [email protected]. > > In order to avoid duplication of effort, perhaps someone should set up > a github repo (or something else) assigning ranges to volunteers? It > might also be useful to use the same repo to hold the triage results > (so things can be ticked off as they are actioned).
I already created a github branch for this, but I stopped adding patches at it since I didn't know if this was going to be useful or not. See: https://github.com/kroeckx/openssl/commits/master-proposed > 2. Triage Github pull requests > > There are less of these, and I do try to look at them from time to > time, nevertheless I think we are behind. I've looked over them several time already, and I've merged a few of those. But it's hard for me to know what you would find an acceptable change and what not, so I've tried to be conservative. > 3. Write fixes > 4. Convert fixes to pull requests I'll try to work on that. > 5. Port pull requests across all branches I wasn't really sure what to do here, and was planning to have branches you can pull for the various branches. Kurt ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
