> > > 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. >
+1 Good idea. So, here is proposal: 1) Mark all unmaintained extensions on our site 2) Send mail to authors of extensions with request to make propriate changes (in some short period) 3) If author does not answer on our mail, or does not update his extension, we will make this changes As I wrote, mr. Jorg was made this changes on one Serbian unmaintained extension, and now it working on AOO 4.0. Question: how can we put this extension on our site (there is still only old version)? Old version of this extension you can find here: http://extensions.openoffice.org/en/project/oootranslit Regards, Wlada
