2008.09.01 21:33 "Re: [Tiff] Some security fixes from RHEL", by Frank Warmerdam

I am willing to volunteer to:

• Commit applicable downstream patches (i.e. security patches in RedHat's build).
• Commit applicable patches that appear on this mailing list, on bugzilla, or come to me in a more private manner.
• Monitor bug reports (esp. bugzilla) in an effort to encourage the reporter to provide enough information such that the problematic code can be pinpointed or such that a patch is provided.
• Perform test builds and run the test suite (I assume that libtiff has one now?) after every commit to make sure that the commit did not break anything - and if it did then to either fix the problem myself, return to the patch developer for a fix, or to back out the patch.

Lee,

Welcome aboard! (cvs commit info provided privately).

What I would require in return is:

* Regular and frequent releases. (And what I mean by that is approximately once per month whenever there has been any non-trivial amount of code changes committed.) If this cannot be done due to other maintainer time constraints, then I am willing to assist in the releases to whatever degree is necessary.

I'm keen on putting out some additional 3.9.0 and 4.0.0 betas on a fairly regular basis.

Would you like to review and apply the CVE-2008-2327 patches in 3.9 branch and cvs head (aka 4.0.0) as a first task? I'm not convinced this has been filed in Bugzilla yet, so you may have to do that yourself.

Best regards,
--
---------------------------------------+--------------------------------------

I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam

and watch the world go round - Rush    | Geospatial Programmer for Rent