Bug 336386

Summary: Support for freebusy FBTYPE
Product: [Applications] kdepimlibs Reporter: Sandro Knauß <sknauss>
Component: kcalcoreAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: GIT (master)   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sandro Knauß 2014-06-18 09:41:42 UTC
Free Busy support different types in a freebusy file. With the additional fbtype you can deside, if a attendee is tentative or busy.

Reproducible: Always




[copied form RFC 5545]

   Parameter Name:  FBTYPE

   Purpose:  To specify the free or busy time type.

   Format Definition:  This property parameter is defined by the
      following notation:

       fbtypeparam        = "FBTYPE" "=" ("FREE" / "BUSY"
                          / "BUSY-UNAVAILABLE" / "BUSY-TENTATIVE"
                          / x-name
                ; Some experimental iCalendar free/busy type.
                          / iana-token)
                ; Some other IANA-registered iCalendar free/busy type.

   Description:  This parameter specifies the free or busy time type.
      The value FREE indicates that the time interval is free for
      scheduling.  The value BUSY indicates that the time interval is
      busy because one or more events have been scheduled for that
      interval.  The value BUSY-UNAVAILABLE indicates that the time
      interval is busy and that the interval can not be scheduled.  The
      value BUSY-TENTATIVE indicates that the time interval is busy
      because one or more events have been tentatively scheduled for
      that interval.  If not specified on a property that allows this
      parameter, the default is BUSY.  Applications MUST treat x-name
      and iana-token values they don't recognize the same way as they
      would the BUSY value.

   Example:  The following is an example of this parameter on a
      "FREEBUSY" property.

       FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z
Comment 1 Denis Kurz 2016-09-24 20:56:05 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:27:14 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.