Hi all -
Dipping my toes into this thread.
Large projects need tools to help manage what's coming in. Matt brings
this point home well below.
Some history, for about 7 or 8 years, I was the ON CRT Chair for Solaris.
The CRT, or Change Review Team, reviewed all changes for the ON (Operating
On 11 April 2014 00:00, Steve Marquess marqu...@opensslfoundation.com wrote:
With the very, very important caveat that I'm not one of the people who
directly carry this burden:
There is certainly room for improvement in the process by which patches
are reviewed and merged into OpenSSL. For
On Fri, Apr 11, 2014 at 10:26:08AM +0100, Matt Caswell wrote:
On 11 April 2014 00:00, Steve Marquess marqu...@opensslfoundation.com wrote:
With the very, very important caveat that I'm not one of the people who
directly carry this burden:
There is certainly room for improvement in the
Hi,
I've seen many examples of patches being submitted but never
getting applied. For some problems there are actually multiple
people submitting a patch for the same issue, and none of them
getting applied.
What is the problem getting them applied? Not enough people to do
the reviewing?
On 04/10/2014 03:22 PM, Kurt Roeckx wrote:
Hi,
I've seen many examples of patches being submitted but never
getting applied. For some problems there are actually multiple
people submitting a patch for the same issue, and none of them
getting applied.
What is the problem getting them
On Thu, Apr 10, 2014 at 04:40:13PM -0400, Steve Marquess wrote:
On 04/10/2014 03:22 PM, Kurt Roeckx wrote:
Hi,
I've seen many examples of patches being submitted but never
getting applied. For some problems there are actually multiple
people submitting a patch for the same issue, and
On 04/10/2014 05:36 PM, Kurt Roeckx wrote:
...
While I'm not one of the OpenSSL committers, I've had the honor and
privilege of being close enough to some of the action to have an
appreciation for the heavy burden of responsibility they carry.
IMHO user community contributions, and the care
