Custom logger adapter for pykolab

Logger names for rest wallace modules

now with icon

@machniak: not sure how to handle translateable strings.

• Do I need to do more to add a new one than adding it to the en_US version?
• should I remove the obsolete $labels['tabattachments'] = 'Attachments'; from all files in localization ?

now without the spaces

(09:06:30) bohlender: petersen: vanmeeuwen: I am in the process of reworking the event editor for elastic. (see https://git.kolab.org/T4845 for screenshots). there are two fields that don't seem to be used by kolab (privacy & priority). In the privacy case, this is actually a usability bug because users could assume that their "private" event is not displayed to others the calendar is shared with. Can we remove these two fields or am I missing a reason to keep them?
(09:08:21) vanmeeuwen: i don't care much for either, but private does have a use-case in the sending back and forth of invitations and the recipient putting it not in a default calendar but instead a calendar marked as private
(09:09:05) vanmeeuwen: so in this case the "private" checkbox would basically indicate "for any attendees that do have a private calendar to have wallace automatically store events in, put it there"
(09:09:30) petersen: How do you mean that they do not get used by Kolab? Those fields exist in Kolab and can be set..
(09:10:37) alec: you can set them, but that's all you can do + the case described above
(09:11:10) petersen: we have had a number of requests for the usecase mentioned above..
(09:12:06) petersen: priority doesn't make much sense to me in a calendar..
(09:12:25) vanmeeuwen: unless we make wallace obey it ;-)
(09:12:52) vanmeeuwen: "lunch, priority 3", "invitation to meeting, priority 1" -> BOOM
(09:13:00) petersen: right
(09:13:20) petersen: perhaps it doesn't make sense to me because we didn't do so yet
(09:14:19) vanmeeuwen: it's wrong in that it is at the sender's discretion
(09:14:25) petersen: with all the above in mind, I would not remove those for now - Bring it to Bern next week - We'll have time to discuss it on Wednesday
(09:15:26) bohlender: alright. thank you for your feedback
(09:15:41) vanmeeuwen: the simpler approach would be to remove the arbitrarily confusing shit out of the way of one's workflow
(09:15:55) vanmeeuwen: which is not to say i've reviewed the tickets / ideas / proposals
(09:16:09) petersen: we will discuss next Wednesday

@machniak I gave roundcube development a try:

Make Wallace log message queue id. That makes it easier to track log records associated with a processed message. Queue ID is a file name of Wallace message

I confirm regression in php-kolab-net-ldap3-1.1.0. A workaround would be do downgrade this package or to disable memcache use in webadmin.

Improved version committed in 58c993a308e4.

According to the spec. it makes a lot of sense.

Kolab support for KDE PIM is discontinued. Create a ticket on https://bugs.kde.org

Kolab support for KDE PIM is discontinued. Create a ticket on https://bugs.kde.org

Kolab support for KDE PIM is discontinued. Create a ticket on https://bugs.kde.org

Kolab support for KDE PIM is discontinued. Create a ticket on https://bugs.kde.org

Kolab support for KDE PIM is discontinued. Create a ticket on https://bugs.kde.org

Kolab support for KDE PIM is discontinued. Create a ticket on https://bugs.kde.org