gdata moving to github

Philipp Kewisch kewisch at thunderbird.net
Fri Sep 27 09:36:10 UTC 2019


The code is going away from comm-central, I'll be removing this very soon now. The translations is of course unfortunate, but then again gdata strings haven't changed for a while.

Philipp 

> On 21. Sep 2019, at 8:20 PM, Magnus Melin <mkmelin+mozilla at iki.fi> wrote:
> 
> 
> The existing translations can easily be transferred over. I would also assume the need for string changes is very minimal - there seems to have been only around 10 changes in total during the last decade. Either way, it's not Thunderbird's problem.
> 
>  -Magnus
> 
>> On 20-09-2019 12:01, Onno Ekker wrote:
>> You do realize that when you move out of comm-central, you’ll loose translation of strings used in your add-on?
>> 
>> For me as an extension developer it is very hard to get my extension translated in many languages and to keep everything updated when new strings are added in new versions.
>> 
>> Onno
>> 
>> On 20 Sep 2019, at 08:57, Magnus Melin <mkmelin+mozilla at iki.fi> wrote:
>> 
>>> I think whichever is less work for us, leaving it in or taking it out.
>>> 
>>>  -Magnus
>>> 
>>> On 20-09-2019 00:57, Geoff Lankow wrote:
>>>> Will the code also be removed from comm-esr68?
>>>> 
>>>> GL
>>>> 
>>>> On 20/09/19 04:50, Magnus Melin wrote:
>>>>> Provider for Google Calendar (gdata) is going to move out of comm-central into github. For historical reasons the source code for add-on has been in comm-central, but was never shipped with Thunderbird. 
>>>>> 
>>>>> What does this mean for its users? Nothing really, the add-on will continue to work just like before. We're not planning to do anything special with the gdata users. I'd like to make the Lightning built-in CalDAV access more discoverable, though that applies to all Google CalDAV calendars, not only Google Calendar. 
>>>>> 
>>>>>  -Magnus
>>>>> 
>>>>> P.S. To subscribe to your primary Google CalDAV calendar, set it up in lightning by entering https://apidata.googleusercontent.com/caldav/v2/example@gmail.com/events (where example is replaced with your own address)
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> tb-planning mailing list
>>>>> tb-planning at mozilla.org
>>>>> https://mail.mozilla.org/listinfo/tb-planning
>>>> 
>>>> 
>>>> _______________________________________________
>>>> tb-planning mailing list
>>>> tb-planning at mozilla.org
>>>> https://mail.mozilla.org/listinfo/tb-planning
>>> _______________________________________________
>>> tb-planning mailing list
>>> tb-planning at mozilla.org
>>> https://mail.mozilla.org/listinfo/tb-planning
>> 
>> 
>> _______________________________________________
>> tb-planning mailing list
>> tb-planning at mozilla.org
>> https://mail.mozilla.org/listinfo/tb-planning
> _______________________________________________
> tb-planning mailing list
> tb-planning at mozilla.org
> https://mail.mozilla.org/listinfo/tb-planning
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/tb-planning/attachments/20190927/a3c5b862/attachment.html>


More information about the tb-planning mailing list