Seriously - it's not beyond current technical capabilities by a long shot. Cerbot is dying. I'll fix it with financial support. Sorry - I know you'd rather have free stuff - but I don't live in my mother's basement. I've been around too long to think about solving all the tech problems out there for free just to boost my self-esteem. I'm only posting this because - obviously - it's not getting done. Too many stupid problems. And abandoning Windows support really sets the icing on the cake for what I'm saying. Obviously, contributors have insufficient knowledge and experience.
a) By all means, fork away, as long as you'll adhere to the Apache Version 2.0 if you use (parts of) the Certbot code;
b) Why are you posting this here, in that manner, with that tone, and in the incorrect category too? Just do what you (think you) need to do and post your results in the Client dev section once it's done? Nobody is stopping you. Nobody is going to stop you. You do you, good luck.
4 Likes
I think contacting EFF who develops certbot (rather than ISRG / Let's Encrypt who does not) might be more fruitful for your career aspirations. Happy to see the initiative!
6 Likes
I am sure the EFF would be happy to accept donations for their effort. You are better off addressing that team here: Contribute To Certbot
Let's Encrypt (ISRG) are not responsible for Certbot's development.
There are many other ACME Clients if you are unhappy with Certbot. I don't agree with many of your comments but LE has this list of alternatives: ACME Client Implementations - Let's Encrypt
Some servers even have built-in ACME Clients (like Apache, Caddy, and nginx has one in development). With these you don't need a stand-alone client. There are other similar examples.
Another option is using Cloudflare CDN which handles the certificates at the edge and provides you an "Origin CA" cert for your server. If that is suitable your own server does not need to run an ACME Client.
HMM UPDATE: Upon re-reading your post you may be saying you want financial support to fix it rather than you offering financial support. In that case please see @osiris comment 
6 Likes
I wish OP the best of luck trying to get any financial support on this Community with that attitude
5 Likes
As one who originally approached around here with a similar attitude, I concur @Osiris. Could prove to be a valuable growth opportunity. I made a pretty big 
of myself back then, so if there's one thing I've learned about this community it's that it tends to be passionate and forgiving while tempering with some direct feedback.
6 Likes
Hello,
Financial support for contributing to Certbot or other ACME clients is not something ISRG can provide at this time.
Thank you.
8 Likes
You do know how collaborative development works, right?
I expect there's a CONTRIBUTING.md file in the certbot repo that can tell you what the current developers ask of you.
If you want to be paid doing so, your best option is finding an employer willing to sponsor your time for the effort. Or maybe finding a grant for doing so, there's several organisations offering them (please don't ask me who they are).
5 Likes
Coming in here with a vague claim that "certbot is broken," and a promise to fix whatever you perceive its problems to be if someone pays you enough, isn't exactly an effective way to endear you to, well, much of anyone.
Personally, I'm not a fan, though much of that may be flashbacks to trying to make it work under CentOS 5. But OK, say it's broken--so what? As Mike says, there are lots of options. Let's Encrypt still recommend certbot for some reason (perhaps nothing more than simple inertia, and I wish they wouldn't), but acme.sh is a pretty popular alternative, as is lego, or the built-in ACME facilities in Caddy and Traefik. Nobody needs to deal with certbot's deficiencies (real or imagined) if they don't want to.
5 Likes
See also
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.