I see. Thank you.
2014-04-28 0:48 GMT+08:00 Dr. Stephen Henson st...@openssl.org:
On Sun, Apr 27, 2014, Weibin Yao wrote:
Is it accessable for read (rt.openssl.org) ? I can't access it and
don't know where to register.
Read access is possible through the guest account:
Is it accessable for read (rt.openssl.org) ? I can't access it and
don't know where to register.
2014-04-27 5:35 GMT+08:00 Matt Caswell fr...@baggins.org:
On 25 April 2014 18:24, Kurt Roeckx k...@roeckx.be wrote:
On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote:
1. Triage RT
On Sun, Apr 27, 2014, Weibin Yao wrote:
Is it accessable for read (rt.openssl.org) ? I can't access it and
don't know where to register.
Read access is possible through the guest account:
https://www.openssl.org/support/rt.html
Steve.
--
Dr Stephen N. Henson. OpenSSL project core
I should've said: if a fix is for a potential security issue, please
don't create a pull request (they are public), instead send a patch to
openssl-secur...@openssl.org.
You can create an appropriate patch file by doing something like this:
$ git format-patch revision to diff against --stdout
On 24 April 2014 18:44, Mike Bland mbl...@acm.org wrote:
On Thu, Apr 24, 2014 at 1:31 PM, Ben Laurie b...@links.org wrote:
6. Write new tests
Our test suite sucks. More tests is better.
Shall I send a pull request for this:
On 25 April 2014 00:08, Matt Caswell fr...@baggins.org wrote:
Ben - Is it possible for some of us to get RT users created? The above
assumes we can configure RT statuses - is this possible?
I think you now have RT access, right?
On 24 April 2014 19:54, Kurt Roeckx k...@roeckx.be wrote:
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
Oh, absolutely I've verified it. :-)
I'll get that turned around to you shortly.
Mike
On Sat, Apr 26, 2014 at 6:33 AM, Ben Laurie b...@links.org wrote:
On 24 April 2014 18:44, Mike Bland mbl...@acm.org wrote:
On Thu, Apr 24, 2014 at 1:31 PM, Ben Laurie b...@links.org wrote:
6. Write
On Sat, Apr 26, 2014 at 11:39:13AM +0100, Ben Laurie wrote:
On 24 April 2014 19:54, Kurt Roeckx k...@roeckx.be wrote:
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
On 25 April 2014 18:24, Kurt Roeckx k...@roeckx.be wrote:
On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote:
1. Triage RT (https://rt.openssl.org/).
I think part of this means that you'll need to give some people
access to it so they can actually modify the tickets.
I now have
On 25 April 2014 01:14, Viktor Dukhovni openssl-us...@dukhovni.org wrote:
On Thu, Apr 24, 2014 at 04:56:09PM -0700, Quanah Gibson-Mount wrote:
The problem with this approach are significant requests that have languished
for years. One such example would be
On 25 April 2014 01:58, Daniel Reynolds
daniel.reyno...@providenceday.org wrote:
I am not totally sure how many people would be working on this project, but
is seems to me like it would make sense to split up into 3 groups.
I would be concerned about spreading ourselves too thinly. I hope that
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
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
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
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
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.
That seems completely reasonable to me.
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
On Thu, Apr 24, 2014 at 04:56:09PM -0700, Quanah Gibson-Mount wrote:
The problem with this approach are significant requests that have languished
for years. One such example would be
http://rt.openssl.org/Ticket/Display.html?id=1365, which is 8 years old
now. The best place to get the fix
I am not totally sure how many people would be working on this project, but
is seems to me like it would make sense to split up into 3 groups.
One would do what Viktor suggested, and hunt down patches added in major OS
platforms.
Another would do what Matt suggested, and simply go from the
20 matches
Mail list logo
