Create a tool to sync GroupWise calendars with a local radicale server
a project by cbosdonnat
Updated over 5 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 11 years ago: aspiers liked this project.
  • about 11 years ago: rhafer liked this project.
  • about 11 years ago: abonilla liked this project.
  • about 11 years ago: wpreston2 liked this project.
  • about 11 years ago: Nijel liked this project.
  • about 11 years ago: cbosdonnat liked this project.
  • about 11 years ago: cbosdonnat started this project.
  • about 11 years ago: cbosdonnat left this project.
  • about 11 years ago: cbosdonnat started this project.
  • about 11 years ago: cbosdonnat joined this project.
  • about 11 years ago: cbosdonnat added keyword "python" to this project.
  • about 11 years ago: cbosdonnat added keyword "calendar" to this project.
  • about 11 years ago: cbosdonnat added keyword "groupwise" to this project.
  • about 11 years ago: cbosdonnat added keyword "ical" to this project.
  • about 11 years ago: cbosdonnat originated this project.


    • Comments

    • Thnielsen
      about 11 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 11 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

    Ansible for add-on management by lmanfredi

    Description

    Machines can contains various combinations of add-ons and are often modified during the time.

    The list of repos can change so I would like to create an automation able to reset the status to a given state, based on metadata available for these machines

    Goals

    Create an Ansible automation able to take care of add-on (repo list) configuration using metadata as reference

    Resources

    Results

    Created WIP project Ansible-add-on-openSUSE

    Symbol Relations by hli

    Description

    There are tools to build function call graphs based on parsing source code, for example, cscope.

    This project aims to achieve a similar goal by directly parsing the disasembly (i.e. objdump) of a compiled binary. The assembly code is what the CPU sees, therefore more "direct". This may be useful in certain scenarios, such as gdb/crash debugging.

    Detailed description and Demos can be found in the README file:

    Supports x86 for now (because my customers only use x86 machines), but support for other architectures can be added easily.

    Tested with python3.6

    Goals

    Any comments are welcome.

    Resources

    https://github.com/lhb-cafe/SymbolRelations

    symrellib.py: mplements the symbol relation graph and the disassembly parser

    symrel_tracer*.py: implements tracing (-t option)

    symrel.py: "cli parser"

    Make more sense of openQA test results using AI by livdywan

    Description

    AI has the potential to help with something many of us spend a lot of time doing which is making sense of openQA logs when a job fails.

    User Story

    Allison Average has a puzzled look on their face while staring at log files that seem to make little sense. Is this a known issue, something completely new or maybe related to infrastructure changes?

    Goals

    • Leverage a chat interface to help Allison
    • Create a model from scratch based on data from openQA
    • Proof of concept for automated analysis of openQA test results

    Bonus

    • Use AI to suggest solutions to merge conflicts
      • This would need a merge conflict editor that can suggest solving the conflict
    • Use image recognition for needles

    Resources

    Timeline

    Day 1

    • Conversing with open-webui to teach me how to create a model based on openQA test results

    Day 2

    Highlights

    • I briefly tested compared models to see if they would make me more productive. Between llama, gemma and mistral there was no amazing difference in the results for my case.
    • Convincing the chat interface to produce code specific to my use case required very explicit instructions.
    • Asking for advice on how to use open-webui itself better was frustratingly unfruitful both in trivial and more advanced regards.
    • Documentation on source materials used by LLM's and tools for this purpose seems virtually non-existent - specifically if a logo can be generated based on particular licenses

    Outcomes

    • Chat interface-supported development is providing good starting points and open-webui being open source is more flexible than Gemini. Although currently some fancy features such as grounding and generated podcasts are missing.
    • Allison still has to be very experienced with openQA to use a chat interface for test review. Publicly available system prompts would make that easier, though.

    Saline (state deployment control and monitoring tool for SUSE Manager/Uyuni) by vizhestkov

    Project Description

    Saline is an addition for salt used in SUSE Manager/Uyuni aimed to provide better control and visibility for states deploymend in the large scale environments.

    In current state the published version can be used only as a Prometheus exporter and missing some of the key features implemented in PoC (not published). Now it can provide metrics related to salt events and state apply process on the minions. But there is no control on this process implemented yet.

    Continue with implementation of the missing features and improve the existing implementation:

    • authentication (need to decide how it should be/or not related to salt auth)

    • web service providing the control of states deployment

    Goal for this Hackweek

    • Implement missing key features

    • Implement the tool for state deployment control with CLI

    Resources

    https://github.com/openSUSE/saline

    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 and Salt-ssh clients, but NOT traditional clients, which are deprecated.

    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 :-)

    Pending

    FUSS

    FUSS is a complete GNU/Linux solution (server, client and desktop/standalone) based on Debian for managing an educational network.

    https://fuss.bz.it/

    Seems to be a Debian 12 derivative, so adding it could be quite easy.

    • [W] Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
    • [W] Onboarding (salt minion from UI, salt minion from bootstrap script, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator) --> Working for all 3 options (salt minion UI, salt minion bootstrap script and salt-ssh minion from the UI).
    • [W] Package management (install, remove, update...) --> Installing a new package works, needs to test the rest.
    • [I] Patching (if patch information is available, could require writing some code to parse it, but IIRC we have support for Ubuntu already). No patches detected. Do we support patches for Debian at all?
    • [W] Applying any basic salt state (including a formula)
    • [W] Salt remote commands
    • [ ] Bonus point: Java part for product identification, and monitoring enablement