On 25/10/2013 Rory O'Farrell wrote:
I urge the preservation of old "unloved" extensions; users with computer skills could often extract the code and modify it to their requirements, as I have recently done myself. Clear marking of an extension as 4 compatible would be helpful.
Indeed the idea of deleting extensions creates more problems than it solves (actually, it doesn't solve problems) and I would definitely avoid it.
The real problem comes from unresponsive maintainers. Compatibility information is already available for all releases, but when a user downloads an extension, unless the maintainer hasn't marked it as compatible with 4.0, he cannot know: it may or may not work with 4.0.
Solution: rather than deleting/moving the extension, we should work on the maintainer side and have an "unresponsive maintainer" policy like many other projects do. An extension can be reassigned if the maintainer is not responsive. The new maintainer can add new releases or edit the description (for example, to include information about 4.0 compatibility). It may not be very nice, but surely it's better than removing an extension altogether. And it preserves all older releases.
Regards, Andrea. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
