Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I would love to Help! #244

Closed
shavrasho opened this issue Nov 30, 2018 · 9 comments
Closed

I would love to Help! #244

shavrasho opened this issue Nov 30, 2018 · 9 comments

Comments

@shavrasho
Copy link

Hallo Pro,

I'm would like to help maintain dkim-exchange for new 2013/2016 CUs and then help add additional features and support for 2019 with future updates.
My Visual Studio skills are good, also I'm a programmer & Systems engineerso i will be able to test newer releases further also quicker support.

@dniakamal
Copy link

Check out CONTRIBUTING.md https://github.com/Pro/dkim-exchange/blob/master/CONTRIBUTING.md for more info.

@luxzg
Copy link

luxzg commented Dec 6, 2018

Is there a professional coder that can issue a valid invoice that we can "reward" for contributing new updates for Exchange 2016 CUs? This offer is also open to the project maintainer. If we can expect new CUs of 2016 supported, and get a valid invoice, we would rather support this project then go with other DKIM signing solutions for Exchange. At very least general public would have the same benefits. We did a "hack" of CU10 to CU11 on test server and seems to work without issues, but simply reusing dlls from old CU doesn't sound like a solution for production or any long term deployment. Please post a reply if interested.

@shavrasho
Copy link
Author

Sure! Please contact me!

@luxzg
Copy link

luxzg commented Dec 6, 2018

Mail or link to website? Thanks!

@shavrasho
Copy link
Author

omar@omarino.de

@luxzg
Copy link

luxzg commented Dec 6, 2018

Sent to email to both @Pro and @shavrasho

@Pro
Copy link
Owner

Pro commented Dec 6, 2018

I am happy if someone is willing to maintain the project further (I also don't mind if someone is getting paid for that!). I'm really sorry that I don't have more time to support this further.

The general process is:

  1. Create a few PRs which I can review. also mention there that you would like to maintain the project in the future.
  2. After I see that the PRs are apropriate quality, I will add that person as maintainer to the project, so he/she can directly push/release

@luxzg
Copy link

luxzg commented Dec 6, 2018

Sounds reasonable to me. Let me know how it goes. Also, there's that PR for 2016 CU11 that @dniakamal was kind to provide. Thank you all!

@DJBenson
Copy link
Collaborator

DJBenson commented Jan 7, 2020

Closing as I am have been made collaborator on the project and will be taking the project forward. Will still need support from the community but regular releases should now be available to everybody again.

@DJBenson DJBenson closed this as completed Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants