[kronolith] CalDav and invitation duplicates

[Ralf Lang]

Am 04.09.19 um 18:49 schrieb Michael J Rubinsky:
>
> Quoting Markus Bozem <mbozem at bozem.de>:
>
>>>
>>> Hi Markus,
>>>
>>> I had the same problem.  If you can't wait for the patch, you can 
>>> always manually disable Kronolith generation of notifications by 
>>> updating /horde/kronolith/lib/Kronolith.php  until the fix is 
>>> available mainstream.  I did so by inserting a 'return' just before
>>>  the section that sends the itip notifications.
>>>
>>> Aria
>>> -- kronolith mailing list
>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>> To unsubscribe, mail: kronolith-unsubscribe at lists.horde.org
>>
>> Hi Aria,
>>
>> thank you for this hint.
>>
>> To all interested persons:
>>
>> return was inserted here:
>>
>>     static public function sendITipNotifications(
>>         Kronolith_Event $event, Horde_Notification_Handler
>> $notification,
>>         $action, Horde_Date $instance = null, $range = null, array
>> $cancellations = array())
>>     {
>>         global $injector, $registry;
>>
>>         return;
>>
>>         if (!$event->attendees) {
>>             return;
>>         }
>>
>>
>> This solution works ok:
>> Active Sync can still be used to send invitations. (iPhone tested)
>> When meeting is created in kronolith - webfronted invitations are not
>> send. (not used here)
>> Only problem when using CalDAV -> when accepting invitations the
>> external organizer will be replaced with the accepting person.
>> (tolerable)
>>
>> To the maintainers:
>>
>> But this is only a workaround. And the patch for an user option is in
>> master branch since 2015.
>
> Correct. Along with major changes to how invitations work at the core.
>
>
>> So what is the problem in integrating this (small) patch for a big
>> problem into stable?
>
> If you are referring to just the user preference; that's technically a
> new feature, so must wait until a feature release, not a bug fix/"dot"
> release. This is why it's in the master branch, and not FRAMEWORK_5_*
>
>> Time to do it?
>
> A major factor, yes. There are major architectural changes in place in
> our entire development and release toolchain. We are also retooling to
> use a distribution channel other than PEAR for our next major
> releases. This takes time, and if I'm honest, more man hours than we
> have at our disposal at the moment.
>
>> Should I create a push reguest?
>
> Wouldn't help, it's already in the code base for the release where it
> will be available.
>
>> Can I help in an other way?
>
> Sure! You can join the dev at lists.horde.org mailing list and help with
> tasks we still have open for our major release.
>
>> Are there other concerns integrating this patch?
>> Is this project death?
>
> Sometimes it seems so, but I assure you we are alive and well :)
>
>> Markus.
>
As for the non-pear stuff, i've been blocked a little lately but it's
being tested / used meanwhile and will find it's way into upstream. Sorry :(


>
>
>
-- 
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang at b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pEpkey.asc
Type: application/pgp-keys
Size: 1757 bytes
Desc: not available
URL: <https://lists.horde.org/archives/kronolith/attachments/20190904/b3503509/attachment.bin>