Create a tool to sync GroupWise calendars with a local radicale server
a project by cbosdonnat
Updated over 6 years ago. 6 hacker ♥️.

I already have a python script processing mails received in the Calendar folder to get the ical event and push it to radicale. It has several drawbacks:

  • It doesn't detect appointment changes (pretty easy to fix as each event has a unique ID)
  • It doesn't detect deleted appointments. This would need to change the script to loop over the mails and already existing events in radicale to sync them.
  • It's a one way script only: from GroupWise to Radicale, the other way still needs to be done.

For this project there are two ways to go and I am still unsure which one would be the best:

  • Use the GroupWise SOAP API: that's what evolution connector used to do and it's only activated on some post offices.
  • Continue the IMAP way: that would require to loop over the whole content of the Calendar folder regularly... is that slower than looping over the events via the SOAP API?

The code of the hackweek project is on github. The project has progressed a lot, but is still not finished. I ended up with:

  • Reading the ical events from IMAP: less parsing work than SOAP and easy to get working
  • Diffing iCalendar files
  • Listing on the changes on a iCalendar file using pyinotify
  • Writing a simple SOAP client in python to access the events to update / remove them (adding could work easily through SMTP)
  • Attachments files are downloaded and properly linked from the events

What is missing:

  • Getting the event ID in a not too time-consuming way using SOAP
  • Convert from iCAL representation to the XML description used by the SOAP API
  • Actually delete / update events
  • Actually add events (may not got the SOAP way)

Join this project

Looking for hackers with the skills:

python calendar groupwise ical

This project is part of:

Hack Week 10

Activity

  • about 12 years ago: aspiers liked this project.
  • about 12 years ago: rhafer liked this project.
  • about 12 years ago: abonilla liked this project.
  • about 12 years ago: wpreston2 liked this project.
  • about 12 years ago: Nijel liked this project.
  • about 12 years ago: cbosdonnat liked this project.
  • about 12 years ago: cbosdonnat started this project.
  • about 12 years ago: cbosdonnat left this project.
  • about 12 years ago: cbosdonnat started this project.
  • about 12 years ago: cbosdonnat joined this project.
  • about 12 years ago: cbosdonnat added keyword "python" to this project.
  • about 12 years ago: cbosdonnat added keyword "calendar" to this project.
  • about 12 years ago: cbosdonnat added keyword "groupwise" to this project.
  • about 12 years ago: cbosdonnat added keyword "ical" to this project.
  • about 12 years ago: cbosdonnat originated this project.


    • Comments

    • Thnielsen
      about 12 years ago by Thnielsen | Reply

      ehh pragmatic comment on the choice of imap or soap - not knowing the complexity of neither the one nor the other, but Groupwise components rather use soap between them (webaccess to postOffice)(datasynchroniser to postOffice) The knowledge in the GroupWise team - should you need help, may be more ready available on SOAP. Bear in mind that Datasynchroniser conains a number of connectors if there are other ways to pass in and out of groupwise: http://www.novell.com/documentation/datasync_connectors1/ (hmm i think they stripped a few connectors in the latest doc - not a good sign . . .

    • vuntz
      about 12 years ago by vuntz | Reply

      As mentioned a few weeks ago on research@, I wrote http://w3.suse.de/~vuntz/tmp/maildir-to-ics which is similar to your existing python script, but writes to a .ics file instead of caldav. It's also lacking true synchronization, though.

    Similar Projects

    Improvements to osc (especially with regards to the Git workflow) by mcepl

    Description

    There is plenty of hacking on osc, where we could spent some fun time. I would like to see a solution for https://github.com/openSUSE/osc/issues/2006 (which is sufficiently non-serious, that it could be part of HackWeek project).

    Update M2Crypto by mcepl

    There are couple of projects I work on, which need my attention and putting them to shape:

    Goal for this Hackweek

    • Put M2Crypto into better shape (most issues closed, all pull requests processed)
    • More fun to learn jujutsu
    • Play more with Gemini, how much it help (or not).
    • Perhaps, also (just slightly related), help to fix vis to work with LuaJIT, particularly to make vis-lspc working.

    Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil

    Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

    Uyuni is a configuration and infrastructure management tool that saves you time and headaches when you have to manage and update tens, hundreds or even thousands of machines. It also manages configuration, can run audits, build image containers, monitor and much more!

    Currently there are a few distributions that are completely untested on Uyuni or SUSE Manager (AFAIK) or just not tested since a long time, and could be interesting knowing how hard would be working with them and, if possible, fix whatever is broken.

    For newcomers, the easiest distributions are those based on DEB or RPM packages. Distributions with other package formats are doable, but will require adapting the Python and Java code to be able to sync and analyze such packages (and if salt does not support those packages, it will need changes as well). So if you want a distribution with other packages, make sure you are comfortable handling such changes.

    No developer experience? No worries! We had non-developers contributors in the past, and we are ready to help as long as you are willing to learn. If you don't want to code at all, you can also help us preparing the documentation after someone else has the initial code ready, or you could also help with testing :-)

    The idea is testing Salt (including bootstrapping with bootstrap script) and Salt-ssh clients

    To consider that a distribution has basic support, we should cover at least (points 3-6 are to be tested for both salt minions and salt ssh minions):

    1. Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
    2. Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator)
    3. Package management (install, remove, update...)
    4. Patching
    5. Applying any basic salt state (including a formula)
    6. Salt remote commands
    7. Bonus point: Java part for product identification, and monitoring enablement
    8. Bonus point: sumaform enablement (https://github.com/uyuni-project/sumaform)
    9. Bonus point: Documentation (https://github.com/uyuni-project/uyuni-docs)
    10. Bonus point: testsuite enablement (https://github.com/uyuni-project/uyuni/tree/master/testsuite)

    If something is breaking: we can try to fix it, but the main idea is research how supported it is right now. Beyond that it's up to each project member how much to hack :-)

    • If you don't have knowledge about some of the steps: ask the team
    • If you still don't know what to do: switch to another distribution and keep testing.

    This card is for EVERYONE, not just developers. Seriously! We had people from other teams helping that were not developers, and added support for Debian and new SUSE Linux Enterprise and openSUSE Leap versions :-)

    In progress/done for Hack Week 25

    Guide

    We started writin a Guide: Adding a new client GNU Linux distribution to Uyuni at https://github.com/uyuni-project/uyuni/wiki/Guide:-Adding-a-new-client-GNU-Linux-distribution-to-Uyuni, to make things easier for everyone, specially those not too familiar wht Uyuni or not technical.

    openSUSE Leap 16.0

    The distribution will all love!

    https://en.opensuse.org/openSUSE:Roadmap#DRAFTScheduleforLeap16.0

    Curent Status We started last year, it's complete now for Hack Week 25! :-D

    • [W] Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file) NOTE: Done, client tools for SLMicro6 are using as those for SLE16.0/openSUSE Leap 16.0 are not available yet
    • [W] Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator)
    • [W] Package management (install, remove, update...). Works, even reboot requirement detection

    Bring to Cockpit + System Roles capabilities from YAST by miguelpc

    Bring to Cockpit + System Roles features from YAST

    Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.

    Goals

    The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.

    Resources

    A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit

    Linux System Roles:

    First meeting Hackweek catchup

    Liz - Prompt autocomplete by ftorchia

    Description

    Liz is the Rancher AI assistant for cluster operations.

    Goals

    We want to help users when sending new messages to Liz, by adding an autocomplete feature to complete their requests based on the context.

    Example:

    • User prompt: "Can you show me the list of p"
    • Autocomplete suggestion: "Can you show me the list of p...od in local cluster?"

    Example:

    • User prompt: "Show me the logs of #rancher-"
    • Chat console: It shows a drop-down widget, next to the # character, with the list of available pod names starting with "rancher-".

    Technical Overview

    1. The AI agent should expose a new ws/autocomplete endpoint to proxy autocomplete messages to the LLM.
    2. The UI extension should be able to display prompt suggestions and allow users to apply the autocomplete to the Prompt via keyboard shortcuts.

    Resources

    GitHub repository