Pre-KEP input sought: Priority for events? (in line with tasks?)(similar to VEVENT & VTODO?)

[Bernhard Reiter]

Am Dienstag, 31. Mai 2011 19:24:01 schrieb Georg C. F. Greve:
>  (a) Does anyone else have this requirement, and particular cases they
>         would request to have taken into account?

So far I have not encountered a request here.
I'd be interested in understanding
the requirements of this request better.
What problem are they attempting to solve? 
Is there a special workflow?

>  (b1) Should we add priority to the 'event' object type?
>
>  (b2) Or should we move priority one level up from 'task' into the common
> fields in events and tasks, of which there are already several?

b2) sounds good, if we are about to make the change.

>  (c1) Should we implement the 0-9 priorities of iCalendar?
>
>  (c2) Or should we stay with the 1-5 approach?

All I can say is that I have not seen priorities used a lot,
not even with tasks. The iCalendar task system seems to be missing a lot to 
become a real project or inter-project management product, for cases where a 
specialised tool is required. 

In order to keep users happy, we want to offer them a solution to their 
organisational needs. Adding priorities could be a solution, but it might not 
be a good or preferred solution. This is why I usually aim for understanding 
of the challenge the user faces first, before making that call.

Best,
Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Deputy Coordinator Germany: fsfe.org. Board member: www.kolabsys.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20110601/e2d5c7b7/attachment.sig>