2013/10/28 Vladislav Stevanovic <[email protected]>: >>If you wish I might do the same for >>oootranslit, or if you're already in touch with the original author >>please make sure he/she does the update or ask him/her to send me a note. > > I sent a mail to the author of OooTranslit, also on forum, but he > never answered. > If you can, please try.
I'll give it a try, sure. >> Our plan A will be like 2), but if we do not get any answer this is >> what I suggest as plan B. >> Enhance the Extensions website and if an end-user try to download an >> extension that has not been updated a pop-up might ask him/her if >> they're looking for an extension compatible with AOO 4.x or older >> version. If they ask for AOO 4.x they'll be redirected to the new >> extension page, otherwise they'll get the 3.x compatible extension. > > If I understood you correctly, we can not making any changes on some > web page of site "Extension" where is stored some extension, because > we are not authors for this page. > > Ok. > So, here is new proposal: > 1) Mark all unmaintained extensions on our site Why should we mark them? > 2) Send mail to authors of extensions with request to make appropriate > changes (in some short period) Ok > 3) If author does not answer on our mail, or does not update his > extension, we will make this changes inside extension (if licence of > extension permit) and make new web page on site "Extensions" for this > new version. Who's going to do those changes? > 4) If an end-user try to download an extension that has not been > updated a pop-up might ask him/her if they're looking for an extension > compatible with AOO 4.x or older version. If they ask for AOO 4.x > they'll be redirected to the new extension page, otherwise they'll get > the 3.x compatible extension. > 5) Maybe is cleaver next: therms and conditions for web site > "Extension" we must look carefully, and, if it is possible, make > changes in that manner that this problems we can manage in future much > more easily. ToS can't tell a legitimate author he/she is not owning his/her content page. We might invite them to consider to have a co-maintainer - a new feature we're working on - but I wouldn't go any further, though. Roberto > > Regards, > Wlada > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
