So, in this case, you already know the requirements, right? Does that ease the blow of being told what to do? I mean, also I assure you that I'm not trying to tell you what to do. I presume that more or less the same items would appear on the TODO list if you told me what to do.
I can and will give up on this whole idea if it's truly a bad idea.
But, lets look at some alternative timelines here. Suppose that I'd immediately hunkered down and started writing an uninstaller in isolation. Note: this is not something I'd finish today. Thus: by the time I had a working or semi-working uninstaller, the world would have moved on.
By starting the work in public, I hoped to avoid that eventuality not just for myself but also for anyone else who might otherwise have walked that path. (Experts who could finish the software quickly don't need the suggestion, of course.)
And, by starting the work in public, I hoped to reduce the cost-of-entry for others. I mean, I don't know about you, but I'd rather start with a couple of kb of skeleton than an empty repo.
I likely can make one in a few hours, if I made it I'd put it on my blog. What is your contribution to the project? Why do you even need to be involved?
