On Thu, Jun 16, 2016 at 11:02 AM, 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 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.

> We could say that we ask on the list for an agreement

That's what Alex did :) Just need to tell authors to answer to his
mail, but not sure what it would mean for "Groupe Glon" here.

>
> 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



-- 
Thomas Mortagne
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to