[horde] Fwd: [Tickets #12069] Re: Kronolith meetings don't show Organizer
Michael J Rubinsky
mrubinsk at horde.org
Wed Feb 27 15:16:34 UTC 2013
Quoting simon at simonandkate.net:
>> 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
>
> Whilst I take your points, and thank you for the reassurance that
> the old tickets are not forgotten.... "Bombarding the mailing
> lists"? I sent one email quoting a ticket that likely a lot of
> mailing list users would not see, to genuinely question it in the
> community (which by its silence has spoken about how much of an
> issue they see it as). Is this community not for open discussion?
I was not strictly speaking about your response(s). Mine was a general
comment, since there seems to have been a tendency to this type of
behavior/attitude lately on the various mailing lists and support
channels. That being something along the lines of, "it sounds like a
simple fix, why hasn't it been done (for free) in the last x
years/months/whatever". If things were really so simple, they would
have been fixed. My apologies if you took this personally, and I
admit it read a bit on that side.
> Seems a little harsh to call that bombarding. Nor have I bumped any
> ticket related to this question, so I'm not sure where that came
> from either.
>
> Anyway, moving on... is there a way to "+1" feature requests or bugs
> or similar, as some places have, to provide opportunity for your
> user community to give input on what they think important? How do
> you prioritise what is in the queue and is getting attention? Do you
> publish this information?
We prioritize things pretty much the way I already described them.
While I can't speak for other developers, I'm sure we all do similar
prioritizing for the code we are responsible for. For me, it's like
this:
1) Security and other high-impact bugs take first priority.
2) This is followed by features/bug fixes that Horde LLC is being paid
for. I also try to fix/implement low hanging fruit during this step.
3) After that (for me I very rarely get to this point) I work on stuff
that I have been promising or promoting for the longest, or things
that have had large discussion in the lists. For example, Ansel has
been dry rotting since Horde 5 development started and needs to be
refactored just so it can be released (with no real new functionality
that I was hoping for) in the upcoming releases planned from
April-ish. For me, getting a full application ready for a late release
trumps individual minor enhancement requests.
4) Repeat (3) based on priority in bug tracker, personal interest,
widest impact etc...
I also set aside dedicated time to review my various custom bug
tracker queries and related saved emails at least twice a week to be
sure I haven't forgotten anything important...and, yes, the ORGANIZER
issue is on that list, along with about a dozen others.
> I know it's FOSS, and it is truly awesome FOSS. Having now used for
> about 6 years, nothing comes close. Thank you for providing it, I
> realise that at times it must be a thankless task. Special thanks to
> Michael R for taking the time to explain the calendaring sequences
> and changes in the ticket that this email came from. Your patience
> is appreciated, and I am really looking forward to the changes.
>
> I take the time to feedback issues and bugs (and yes I know I have a
> lot in the last few weeks), and to troubleshoot my Horde installs,
> not just for my own install, but because it gives me a feeling that
> I too contribute to the end result.
..and we absolutely thank you (and others) who spend a considerable
amount of time to help track down these issues instead of just giving
up on the software or hoping someone else will discover it. It truly
is appreciated and is part of what makes our software so great.
Personally, I know that the ActiveSync implementation has benefited
greatly from your input. We understand not everybody is a developer
(but sometimes forget this) and appreciate the patience people like
you show in tracking down issues we have a hard time
understanding/reproducing.
> Oh, and +1 to Kronolith getting ORGANIZER support... ;-p
Understood :)
--
mike
The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6062 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/horde/attachments/20130227/2aed1e1c/attachment.bin>
More information about the horde
mailing list