Rules of engagement for cyrus-sasl contributions

[Simo Sorce]

Thanks Ken,
I posted another PR and noticed that travis is not able to show results
on new PRs.

I know that I had to change one of my projects to allow GitHub Oauuth
integration. This comment from another user with the same issue
explains how to fix it: 
https://github.com/travis-ci/travis-ci/issues/9440#issuecomment-378707440

That said, I see there are no tests run in travis, only a build of
sources. Is there any interest in adding at least some minimal testing
via something like sample-server/sample-client ?

Simo.

On Fri, 2019-03-29 at 10:31 -0400, Ken Murchison wrote:
> PRs are the best way to contribute.  I will try to find some time to 
> work through the existing PRs.
> 
> 
> On 3/29/19 10:11 AM, Simo Sorce wrote:
> > Hello list,
> > as of recently I am working as the Red Hat maintainer for the cyrus-
> > sasl package taking over from Jakub Jelen.
> > 
> > I am writing to ask what is the correct way to engage with regard to
> > patch review and getting work done in general. I have submitted a few
> > PRs to the github tree over the last few months but I've seen no
> > reaction so I am wondering if I need to ping any individual
> > specifically or need to drop a message here, or anything else.
> > 
> > I am planning to write some more patches, for example we would like to
> > move away from any custom cryptography implementation in our packages
> > and I found DES, RC4 and MD5 algorithms implemented in the package.
> > I would like to replace them with simple calls to the OpenSSL EVP
> > interface but it is not clear to me that is is ok, and how to deal with
> > other platforms I do not have access to (like Mac OS X).
> > 
> > Any guidance ?
> > 
> > Thanks,
> > Simo.
> > 

-- 
Simo Sorce
Sr. Principal Software Engineer
Red Hat, Inc