This is update of proposal: 1) Mark all unmaintained extensions on our site (With appropriate mark, and with button with link to the page where exist new, compatilble version of extension. Note: button will be added if exist new version. Marks and buttons will be on "preview" page, as result of search engeen) 2) Send mail to authors of extensions with request to make appropriate 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 inside extension (if licence of extension permit) and make new web page on site "Extensions" for this new version. 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.
It is now this proposal good? Regards, Wlada 2013/10/29 Roberto Galoppini <roberto.galopp...@gmail.com> > 2013/10/28 Vladislav Stevanovic <stevanovicvladis...@gmail.com>: > >>Why should we mark them? > > > > If there is some warning mark, visually you will in easier way to > > know that this extension is not compatible with AOO4.0. We can even > > more. We can (near that mark) add button for link to the version > > which can run on AOO4.0. Where we can add this marks, buttons?Before > > you actual go inside some of extension's page, you have page where is > > some kind list of extensions, what serve as preview. I think that this > > page with list of extensions, given by search engine, is not page of > > authors of extensions, so I think that we can freely add this helpful > > marks, buttons etc. Purpose of this is to save time for end-user when > > he/she want to find appropriate extension. But, if somebody miss to > > see marks or he/she using direct link to the author's page of > > extension, your idea to having pop-ups will solve the potential > > problem. With this pop-up dialog we will get good warnings and solver > > system for end-users. > > You got the gist, right. > > > >>Who's going to do those changes? > > > > That is next step of this discussion. If we have consensus about this > > basic steps (how we want to manage this problem) than next step is to > > see who want to take responsibility for that area. Who have skills, > > time and good will to make changes on site "Extensions", and who want > > to made corrections inside extensions (if licence of extensions permit > > that). > > In other words we can provide a platform doing the magic, but we need > people to take care of updating those Extensions. We might want to run > in parallel those two processes, though. > > Roberto > > > > > > Regards, > > Wlada > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
