On Fri, Jun 17, 2016 at 10:21 AM, Alexandru Cotiuga < [email protected]> wrote:
> Since some suggestions have been added in this topic, I would like to use > it to make a proposal for the retiring mechanism: > A small note: on e.x.o we already have a 'deprecated' and an 'obsolete' tag, see http://extensions.xwiki.org/xwiki/bin/view/Main/Tags?do=viewTag&tag=obsolete and http://extensions.xwiki.org/xwiki/bin/view/Main/Tags?do=viewTag&tag=deprecated . So we should standardize the process and mark everything the same. > * add a new list xproperty to the "ExtensionCode.ExtensionClass" called > "status" which will have a "Retired" value, a default one and later a > "Recommended" one (this depends on the need of using this field in the > livetable; we don't want a filter to show "Retired" extensions). > Not sure we will want to present on the same level / make related the Recommended and Retired status. Recommended should be always presented to the user, Retired never. > * using "status" property, hide the retired extensions from e.x.o livetable > and EM > * create a new document "Extension.RetiredExtensions" with a livetable > listing the retired extensions > * add a small note(link) above the livetable of Extensions: "See retired > extensions". > We should not have a link above the livetable, since this is not something we want to promote to the users. Also I'm not sure about keeping everything on e.x.o. In the future we might want to remove snippets, so we could agree that some content might be moved someday. Now it's true that we use e.x.o for multiple functions: documentation, shop, snippets and each function has different purposes, so for the shop function I would like to see just the relevant information, while for the documentation function I would like to have archives. IMO the EM should contain a link to the documentation. The retired extensions should not be listed at all on e.x.o, but the users might access the documentation by following the EM links. Thanks, Caty > > WDYT? > > Thanks, > Alex > > On Thu, Jun 16, 2016 at 6:04 PM, Eduard Moraru <[email protected]> > wrote: > > > On Thu, Jun 16, 2016 at 4:28 PM, Marius Dumitru Florea < > > [email protected]> wrote: > > > > > On Thu, Jun 16, 2016 at 12:02 PM, Vincent Massol <[email protected]> > > > wrote: > > > > > > > +1 in general. > > > > > > > > > On 16 Jun 2016, at 10:57, Thomas Mortagne < > [email protected] > > > > > > > wrote: > > > > > > > > > > On Thu, Jun 16, 2016 at 10:43 AM, Eduard Moraru < > > [email protected]> > > > > wrote: > > > > >> +1 > > > > >> > > > > >> Also, if we retire the jira project, it means that we stop the > > support > > > > for > > > > >> this application (since no new issues can be created), effectively > > > > retiring > > > > >> the whole application itself, not only its jira project. > > > > >> > > > > >> I`m not sure if we currently have a documented process for > retiring > > > > contrib > > > > >> extensions, but we should at least update the descriptions (and > > maybe > > > > title > > > > >> as well - marking it [Retired]) on the e.x.o. page and on the > > contrib > > > > repo > > > > >> to clearly mention that the app is no longer actively supported by > > > > anyone. > > > > > > > > > > We don't have any process. We actually never done it before. What > we > > > > > could easily do is add a property in ExtensionClass to indicate an > > > > > extension is retired in which case: > > > > > * the extension does not appear in EM anymore (i.e. make the > > extension > > > > > "invalid") since that's something we want for this kind of > extension > > I > > > > > think > > > > > * the extension sheet make clear it's retired with some visible > > marker > > > > > in the title and some warning at the beginning of the content > > > > > > > > Or simply remove the extension from e.x.o. I don’t think they should > > even > > > > be visible on e.x.o since they’ll be visible when someone filters or > > > > searches for extensions and will potentially confuse the user (even > > with > > > > the banner/warnings). > > > > > > > > > > > > > > > If we want to keep it visible I’d not mix them with other extensions > in > > > > the LT but instead I'd introduce another page for retired extensions > > and > > > > we’d add a link to retired extensions on e.x.o home page somewher. > > > > > > > > > > I would keep it on e.x.o for documentation. There may be users that are > > > forced to use this application. Note that this application is in a > > similar > > > situation to the Radeox macros that Thomas wanted to remove from e.x.o > . > > > Check the "Remove old Radeox macros from e.x.o?" thread. > > > > > > I agree that it shouldn't appear on EM and on the e.x.o live table. > > > > > > > +1 to keep and not show by default. > > > > Thanks, > > Eduard > > > > > > > > Thanks, > > > Marius > > > > > > > > > > > > > > I think we need an agreement from authors in order to mark an > extension > > > as > > > > retired. We could say that we ask on the list for an agreement > putting > > in > > > > cc the authors (when we have their email addresses) and if we don’t > get > > > any > > > > answer in 2 weeks, we go ahead and retire it. If they say they still > > want > > > > to maintain it, we keep it. > > > > > > > > WDYT? > > > > > > > > Thanks > > > > -Vincent > > > > > > > > > > > > > P.S.: The link to the new old jira project would still need to be > > added > > > > to > > > > >> the e.x.o page since it`s currently missing. > > > > >> > > > > >> Thanks, > > > > >> Eduard > > > > >> > > > > >> On Thu, Jun 16, 2016 at 10:20 AM, Alexandru Cotiuga < > > > > >> [email protected]> wrote: > > > > >> > > > > >>> Hi devs, > > > > >>> > > > > >>> Currently, the Meeting Manager Application [ > > > > >>> > > > > >>> > > > > > > > > > > http://extensions.xwiki.org/xwiki/bin/view/Extension/Meeting+Manager+Application > > > > >>> ] > > > > >>> is marked, with a warning, as "This application is superseded by > > the > > > > >>> Meeting > > > > >>> Application". The application is written in xwiki/1.0 syntax and > is > > > > full of > > > > >>> deprecated usages which makes it unusable at least since XWiki > 6.2. > > > > >>> > > > > >>> Considering the above reasons I propose to retire the MEETING > Jira > > > > project. > > > > >>> > > > > >>> Thanks, > > > > >>> Alex > > > > _______________________________________________ > > > > devs mailing list > > > > [email protected] > > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > > _______________________________________________ > > > devs mailing list > > > [email protected] > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > _______________________________________________ > > devs mailing list > > [email protected] > > http://lists.xwiki.org/mailman/listinfo/devs > > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
