maildev@lists.thunderbird.net

Thunderbird email developers

View all threads

Re: [Maildev] Addons no longer maintained.

MM
Magnus Melin
Wed, Feb 13, 2019 6:45 AM

On 13-02-2019 01:26, Ben Bucksch wrote:

if the add-on is no longer working with a new thunderbird version, he
may not do the update. that's really bad for everybody.

Since the update system has been changed to avoid having people to stay
on an old version, this is really less of an issue going forwards. Now
you can only choose if you want to A) install updates automatically or
B) get nagged into it. There's no end-user UI to opt out.

 -Magnus

On 13-02-2019 01:26, Ben Bucksch wrote: > if the add-on is no longer working with a new thunderbird version, he > may not do the update. that's really bad for everybody. Since the update system has been changed to avoid having people to stay on an old version, this is really less of an issue going forwards. Now you can only choose if you want to A) install updates automatically or B) get nagged into it. There's no end-user UI to opt out.  -Magnus
PK
Philipp Kewisch
Wed, Feb 13, 2019 7:44 AM

My suggestion does include a replacement add-on UI which I believe already exists, but the action the user takes from that is to go to the ATN page where they can make an informed decision to install.

Philipp

On 13. Feb 2019, at 12:26 AM, Ben Bucksch ben.bucksch@beonex.com wrote:

I'm looking at it from an end user perspective. he just wants the functionality. if the add-on is no longer working with a new thunderbird version, he may not do the update. that's really bad for everybody.

to avoid that, the user should be explicitly informed that there is a replacement. a note on the add-on page on ATN is not sufficient. it needs to be displayed in whatever places thunderbird it is shown that the add-on is incompatible. next to that message, we should show the replacement add-on, in order to achieve the goal of a) being user friendly and b) encouraging users to update.

this can be shown in the add-ons page in thunderbird, and other places.

Ben

Am 12. Februar 2019 11:34:25 MEZ schrieb Philipp Kewisch kewisch@thunderbird.net:

Hey Folks,

trademarks on ATN are handled via the DMCA safe harbor agreement, so trademarks MUST NOT be checked, but can be filed by the trademark owner as a complaint and must then be removed. Regardless, I think it is best we keep the legal discussions out of this thread completely. It is best we come to a set of options and then seek legal advice. IANAL and even if some of you are, you probably know legal opinions are not well discussed on public lists.

What I can tell you from my perspective is that anything that involves adding an author to an existing listing or replacing an add-on is a recipe for trouble. The new add-on would maybe not be feature complete, making the user unhappy. Or they might not like the UI. This could also make the original developer unhappy and it would end in a lot of hand holding and resolving disputes on our end. The new developer may also have different data collection policies, which would not be apparent from a mere update.

What I think would be acceptable is to:

  1. Soft-block add-ons that are breaking Thunderbird functionality
  2. Offer hand-picked replacement add-ons for blocked add-ons. If the user wants these, they are redirected to the ATN page and can make an informed decision if they want to install the add-on.

For (2) there may already be a system in place. As for offering replacements for add-ons not breaking Thunderbird I think this should require explicit consent from the original author.

We could consider getting in touch with authors if they would be willing to have someone else continue maintenance using the reviewer reply functionality, but we need to make sure this is compliant since we can only send transactional messages pertaining to the add-on review this way.

I don't think anything more automatic than this would be a good move for us, for developers, or users.

Philipp

On 12. Feb 2019, at 9:41 AM, Magnus Melin mkmelin+mozilla@iki.fi wrote:

On 12-02-2019 01:37, Ben Bucksch wrote:
Just because you chose a name for your app and registered it somewhere on some website, does not make it a trademark.

Perhaps not, but something with say 50-100k users can probably be argued in some court, that it is widely known enough to be a trademark.

I'd like to point out that as often with law, you really need prevent being exposed to legal arguments in the first place, no matter if you would likely win or lose. Too much of a mess and resource drain.

It's true that there can be a trademark without being registered. But there is a fairly high bar for that. The name needs to be commonly known to count as trademark without registration. For example, news coverage with wide audience. For a trademark violation, the original owner would first need to prove that there is in fact a trademark, even though there was no trademark registration.

Somehow I doubt that people would be willing to put a check mark next to something saying "take my pet project at any time I happen not to want to maintain it". And then for the second part, who would be motivated to take something over as their pet project in case the original author can at any point in the future come back and "claim the fame"?

-Magnus
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

--
Sent from my phone. Please excuse the brevity.

My suggestion does include a replacement add-on UI which I believe already exists, but the action the user takes from that is to go to the ATN page where they can make an informed decision to install. Philipp > On 13. Feb 2019, at 12:26 AM, Ben Bucksch <ben.bucksch@beonex.com> wrote: > > I'm looking at it from an end user perspective. he just wants the functionality. if the add-on is no longer working with a new thunderbird version, he may not do the update. that's really bad for everybody. > > to avoid that, the user should be explicitly informed that there is a replacement. a note on the add-on page on ATN is *not* sufficient. it needs to be displayed in whatever places thunderbird it is shown that the add-on is incompatible. next to that message, we should show the replacement add-on, in order to achieve the goal of a) being user friendly and b) encouraging users to update. > > this can be shown in the add-ons page in thunderbird, and other places. > > Ben > > Am 12. Februar 2019 11:34:25 MEZ schrieb Philipp Kewisch <kewisch@thunderbird.net>: >> >> Hey Folks, >> >> trademarks on ATN are handled via the DMCA safe harbor agreement, so trademarks MUST NOT be checked, but can be filed by the trademark owner as a complaint and must then be removed. Regardless, I think it is best we keep the legal discussions out of this thread completely. It is best we come to a set of options and then seek legal advice. IANAL and even if some of you are, you probably know legal opinions are not well discussed on public lists. >> >> What I can tell you from my perspective is that anything that involves adding an author to an existing listing or replacing an add-on is a recipe for trouble. The new add-on would maybe not be feature complete, making the user unhappy. Or they might not like the UI. This could also make the original developer unhappy and it would end in a lot of hand holding and resolving disputes on our end. The new developer may also have different data collection policies, which would not be apparent from a mere update. >> >> What I think would be acceptable is to: >> >> 1) Soft-block add-ons that are breaking Thunderbird functionality >> 2) Offer hand-picked replacement add-ons for blocked add-ons. If the user wants these, they are redirected to the ATN page and can make an informed decision if they want to install the add-on. >> >> For (2) there may already be a system in place. As for offering replacements for add-ons not breaking Thunderbird I think this should require explicit consent from the original author. >> >> We could consider getting in touch with authors if they would be willing to have someone else continue maintenance using the reviewer reply functionality, but we need to make sure this is compliant since we can only send transactional messages pertaining to the add-on review this way. >> >> I don't think anything more automatic than this would be a good move for us, for developers, or users. >> >> Philipp >> >>>> On 12. Feb 2019, at 9:41 AM, Magnus Melin <mkmelin+mozilla@iki.fi> wrote: >>>> >>>> On 12-02-2019 01:37, Ben Bucksch wrote: >>>> Just because you chose a name for your app and registered it somewhere on some website, does not make it a trademark. >>> >>> Perhaps not, but something with say 50-100k users can probably be argued in some court, that it is widely known enough to be a trademark. >>> >>> I'd like to point out that as often with law, you really need prevent being exposed to legal arguments in the first place, no matter if you would likely win or lose. Too much of a mess and resource drain. >>> >>>> >>>> It's true that there can be a trademark without being registered. But there is a fairly high bar for that. The name needs to be commonly known to count as trademark without registration. For example, news coverage with wide audience. For a trademark violation, the original owner would first need to prove that there is in fact a trademark, even though there was no trademark registration. >>> >>> Somehow I doubt that people would be willing to put a check mark next to something saying "take my pet project at any time I happen not to want to maintain it". And then for the second part, who would be motivated to take something over as their pet project in case the original author can at any point in the future come back and "claim the fame"? >>> >>> -Magnus >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > -- > Sent from my phone. Please excuse the brevity.