Developers minimum requiremet before listing plugin

[swguy]

Under your "rules" here's the explanation for the author of the ceon mods.. "ummm my apologies for not responding to posts on the support thread, I've been a little busy being deceased.."

He had a good sense of humor and would have laughed at this.

[DivaVocals]

To clarify: these are not proposed rules. They're the opinion of one person posting on the forum.

Oh I get that Scott.. but you're right, it's good to clarify this for folks stumbling in here.. :)

He had a good sense of humor and would have laughed at this.

Oh I know this, I think others who didn't know him might have been a little taken aback though..

[hairydog]

I deliberately do *not* remove old unsupported mods because someone may need to download a copy for comparison during upgrade. When it is requested, I update the mod description saying that this mod is no longer appropriate for specific versions, or has been superseded by another mod, or whatever.

I'd like to thank you for that. A few times I've found old plugins a useful help in understanding how to do things, or as a basis of how to make an old plugin suitable for current sites, where there is nothing current available.

What I'm not sure about is the situation where, for example, a free plugin is no longer supported here, but the author is selling (or worse, renting) a newer version on a commercial basis. Would it be OK to update the old free version and post it as a new version, when it is then head-to-head with the paid-for one? I think it probably wold, but so far I've not done it because of the extra effort in properly documenting what is done.

[hairydog]

Make it a requirement that every mod / plugin has it's own support thread where any issues can be discussed, good, bad or indifferent. This can be enforced by the appointed moderator who approves a submission.

Anyone can start a support thread. So the first person to want one can start the thread.

What would be a good idea would be to make a clear unique ID for each plugin, so that there would be an easy way to link support threads to specific plugins. I expect there already are plugin IDs, but they're not very obvious.

[swguy]

What I'm not sure about is the situation where, for example, a free plugin is no longer supported here, but the author is selling (or worse, renting) a newer version on a commercial basis. Would it be OK to update the old free version and post it as a new version, when it is then head-to-head with the paid-for one?

This is my position, subject to approval by the Zen Cart core team: Yes. The free one was licensed under the GPL and is in the public domain.