Collaboration with jwilder/dockerize

[powerman]

I had to detach this fork from original jwilder/dockerize because @jwilder refuse to collaborate and (so far) don't actually maintain his project himself.

Timeline for jwilder/dockerize project:

• 8 May 2018 (10 months ago) - latest commit from @jwilder
• 6 Sep 2018 (6 months ago) - @luisdavim opened issue Is this still being maintained?
• 18 Nov 2018 (4 months ago) - at there was no replies or other activity from @jwilder in last 6 months I've created this fork because I need this tool but I can't use unmaintained project.
• 30 Nov 2018 - I've finished with planned code changes, merged all reasonable PRs and changes from other forks, replied to all PRs and issues in original repo - i.e. completed pending @jwilder's maintenance tasks. It also worth to say I've tried hard to contact @jwilder both by email and in LinkedIn all this time, but he didn't reply.
• 1 Dec 2018 - @jwilder block my access to his repo and replied "Yes. This project is still maintained." on issue Is this still being maintained? (but I didn't receive notification about this because block prevents me from watching his repo).
• 4 Mar 2019 - I've noticed I can't comment on Is this still being maintained? (at this moment I had no idea why this happens because I wasn't aware about blocking my account), so I've opened new issue About powerman/dockerize fork using different GitHub account.
• 4 Mar 2019 - @jwilder delete issue About powerman/dockerize fork without replying.
• 4 Mar 2019 - It's now 3 months since @jwilder reply "Yes. This project is still maintained." without any @jwilder activity except deleting my issue.
• 5 Mar 2019 - I've asked GitHub support to detach my fork from original repo. 😞

Below is body of my deleted issue About powerman/dockerize fork (sent to me by GitHub support):

---

(This is @powerman - I had to use different account because it looks like I can't create issues in this repo anymore.)

This is a jwilder/dockerize#120 followup. Not sure why, but I can't reply in old issue, GitHub says "You can't perform this action at this time.", and also sorry for delay with the response - I didn't received email from GitHub with jwilder/dockerize#120 (comment) and next comment, maybe this somehow related to mentioned above permission error. I can't even "watch" this repo now - any chance you've banned me?

In short, I'm not trying to hijack this tool and will be more than happy to provide and discuss several PRs with improvements already implemented in my fork (and finally close the fork - I've a lot of own open source projects to maintain and don't like to maintain one more if I can avoid this). Yeah, at some point I did large refactoring to make it easier to maintain the project, and merging it very likely will became an issue and may be rejected, but we can at least start with something less controversial. E.g. I've already opened about 4 months ago trivial PRs jwilder/dockerize#122 and jwilder/dockerize#123 - why don't you take a look and at least reply, if not merge? You have said project is still maintained, but I didn't see any your activity in last 10 month except mentioned above single comment.

The fork that has been created is quite different than this project.

How is this? Main and only real difference is massive refactoring. I neither plan nor done any critical changes to project behaviour, because I don't need this - only reason to fork was needs in having maintained project. Even if this happens somehow - it wasn't intentional and I'll be happy to discuss and fix such a changes.

It also has questionable contributor practices in that anyone can become a contributor if they ask.

Actually, this isn't a real problem. If you'll take a look at https://github.com/powerman/dockerize/blob/master/.github/CODEOWNERS you'll notice no one can merge to master without having me to review and accept changes first. My plan was to slowly add trusted contributors there if/when waiting for my review will became an issue. So, even with a lot of contributors there is no way to make malicious changes in code.