[horde] Fwd: [Tickets #12069] Re: Kronolith meetings don't show Organizer

[Michael M Slusarz]

Quoting Michael J Rubinsky <mrubinsk at horde.org>:

> Quoting Simon Wilson <simon at simonandkate.net>:
>
>>> Zitat von Simon Wilson <simon at simonandkate.net>:
>>>
>>>> ----- Forwarded message from noreply at bugs.horde.org -----
>>>> Subject: [Tickets #12069] Re: Kronolith meetings don't show Organizer
>>>>      To: simon at simonandkate.net
>>>>
>>>> Summary            | Kronolith meetings don't show Organizer
>>>> Queue              | Kronolith
>>>> Version            | 4.0.4
>>>> Type               | Bug
>>>> State              | Duplicate
>>>> Priority           | 1. Low
>>>> ------------------------------------------------------------------------------
>>>>
>>>> simon at simonandkate.net (2013-02-26 11:39) wrote:
>>>>
>>>>>> In Imp, Nowhere can I see who sent me the meeting.
>>>>>
>>>>> Wrong, the organizer is mentioned in the header of the rendered iTip
>>>> attachment.
>>>>>
>>>>
>>>> Sorry - I meant in KRONOLITH I can nowhere see who sent me the meeting, I
>>>> was incorrect. Given that is my calendar app, that is a fundamental flaw.
>>>>
>>>>>> It's lost the Organizer tag.
>>>>>>
>>>>>> I've never noticed this before until working through some issues,
>>>>>> surely this is not working as designed?
>>>>>
>>>>> It is. Duplicate of request #3965
>>>>
>>>> LOL - that's a 7 year old request. I somehow doubt that will see  
>>>> any action
>>>> in a hurry.
>>>>
>>>> Probably more critical this passes through to ActiveSync meetings.
>>>> Accepting a meeting request enters it in Kronolith with no Organizer.
>>>> Kronolith syncs that meeting request to AS devices with no organizer, ie.
>>>> an appointment not a meeting.
>>>>
>>>> How hard would it be for Kronolith to retain that Organizer field into the
>>>> database, and then provide it to AS for syncing?
>>>>
>>>> ----- End forwarded message -----
>>>>
>>>> For list discussion -
>>>>
>>>> Kronolith does not retain Organizer information in an accepted  
>>>> meeting request.
>>>>
>>>> This results in the following:
>>>>
>>>> 1. Once you have accepted a meeting invite in Imp, and it's been  
>>>> put into Kronolith, there is no way to tell in Kronolith who the  
>>>> invite came from
>>>> 2. You can't change your response back to the Organizer without  
>>>> finding the original invitation email
>>>> 3. This is the big one for me - ALL meetings that either you  
>>>> accept in Kronolith, or that you accept on an ActiveSync device  
>>>> that then syncs back to Kronolith, lose Organizer information. On  
>>>> an iOS device this means they show as an appointment, not a  
>>>> meeting (i.e. no "From" or "Invitees").
>>>>
>>>> With H6 I am kicking up our use of Calendars and AS as it is so  
>>>> much more robust, but I see this as a major shortcoming to  
>>>> serious use.
>>>>
>>>> So, open to discussion, does anyone else see this as an issue,  
>>>> and anyone smart enough to help fix it?
>>>>
>>>> Simon
>>>>
>>>> --
>>>> Simon Wilson
>>>> M: 0400 12 11 16
>>>
>>> If it wasn't an issue, there wouldn't be an open RFE for it. It  
>>> just needs someone to implement this or pay for the implementation.
>>> -- 
>>> Jan Schneider
>>
>> IMO Jan calling a 7 year old ticket an open RFE is a little  
>> optimistic. Perhaps some discussion around it instead of leaving it  
>> to rot in a 7 year old ticket may actually generate some progress  
>> to someone maybe implementing it or paying for the  
>> implementation.... :-/
>>
>> 7 years ago Horde ActiveSync did not even exist I don't think. The  
>> ticket you refer to also refers to ticket  
>> http://bugs.horde.org/ticket/6269 which notes impact on ActiveSync,  
>> but that has also had no action for over 2 years.
>>
>> Having this done (the addition of ORGANIZER to Kronolith events)  
>> will significantly enhance functionality in Kronolith and any  
>> connected activeSync device. The only way this will rise in any  
>> priorities to get done is if it is pushed yes?
>
> Just because a ticket is old or not acted on does NOT mean that we  
> have forgotten about it, don't care about it, or are not interested  
> in fixing/implementing it. It means it is not as easy of a fix as a  
> non-developer might believe and no developer currently has the time  
> to volunteer to get it fixed. Bombarding the mailing lists with  
> calls to get it fixed or "bumping" the ticket will not change this  
> fact. The fact of the matter is, non critical related  
> tickets/features/bugs that are not being sponsored are not at the  
> top of the list. Things that are not sponsored are done as  
> developers have the free time and interest. It's not an ideal  
> situation for you, but it's a side effect of Horde being FOSS.

What Mike said.  I'll add that some enhancements require a rewrite of  
the application/framework architecture, so they may be darn near  
impossible when first floated but become feasible 5 years later.

I would love to implement collapsible threading in IMP, which is  
enhancement ticket #3000 something.  A combination of architectural  
issues and priorities have prevented me from doing so to this point.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]