On Fri, Apr 25, 2014 at 10:03 AM, Jeff Trawick <traw...@gmail.com> wrote:
> On Thu, Apr 24, 2014 at 7:08 PM, Matt Caswell <fr...@baggins.org> wrote: > >> On 24 April 2014 18:31, Ben Laurie <b...@links.org> 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/). >> > > ... > > Meta-suggestion: > > a. Get this and any other information needed by patch submitters and more > involved contributers on the wiki ASAP (I guess the wiki allows the widest > possible group to maintain it). > Silly me, now I see http://wiki.openssl.org/index.php/Defect_and_Feature_Review_Process Something I wonder about for the sake of onetime/sometime contributors... Is it practical for the triage team to give the onetime/sometime contributor a heads up that it looks promising before they backport to supported branches? b. Get someone with web site commit access and code commit access to axe > inconsistent and/or out of date instructions about contributions and point > to the wiki. > > This is probably also out of date, but, for example, it has the one true > info on using svn (in httpd's case) for > > http://httpd.apache.org/dev/ > > --/-- > > I doubt that I can help much in general, but I can put the recap of this > thread in an appropriate place there and create some sort of structure to > contain information needed by contributors, and I guess submit patches to > axe out of date information from other places. > > Concerns? > > -- > Born in Roswell... married an alien... > http://emptyhammock.com/ > http://edjective.org/ > > -- Born in Roswell... married an alien... http://emptyhammock.com/ http://edjective.org/
