dennis future

[willkg]

I created Dennis 8 years ago to solve a class of problems plaguing Mozilla sites. Over the intervening years, I've gotten a little help, but no one has stepped up to share the maintenance burden. Further, I haven't worked on a site that required translations in 5 years, so I don't use Dennis anymore.

Dennis is still used by some Mozilla sites, so I'd like to keep it mostly as it is. I think there are some Mozilla-centric quirks in Dennis.

I have no idea if anyone else uses Dennis. I know attempts to find out who's using it and getting help have failed. There are probably other tools out there that do similar things.

Given all that, I think I want to do as follows:

1. I will continue to maintain Dennis, but limited to fixing big issues Mozilla sites are having, updating support as Python versions come and go, and maybe doing things I find fun
2. If there's a need for Dennis elsewhere, I suggest you all band together and fork Dennis and then you're free to make the changes you need.

Let me know what you're thinking and use this discussion for coordination.

[willkg]

Current status with this: I never heard back from anyone (not wildly surprising) and so I was going to end the project. However, there are a couple of Mozilla projects that still use it, so I spruced everything up to do a 1.0.0 release, transferred it to the Mozilla org, and added @diox and @akatsoulas as admin. After all that, I'm going to step down as maintainer.