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)
This project is part of:
Hack Week 10
Activity
Comments
-
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 . . .
-
Similar Projects
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.
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: https://linux-system-roles.github.io/
Enhance git-sha-verify: A tool to checkout validated git hashes by gpathak
Description
git-sha-verify is a simple shell utility to verify and checkout trusted git commits signed using GPG key. This tool helps ensure that only authorized or validated commit hashes are checked out from a git repository, supporting better code integrity and security within the workflow.
Supports:
- Verifying commit authenticity signed using gpg key
- Checking out trusted commits
Ideal for teams and projects where the integrity of git history is crucial.
Goals
A minimal python code of the shell script exists as a pull request.
The goal of this hackweek is to:
- Add more unit tests
- Make the python code modular
- Add code coverage if possible
Resources
- Link to GitHub Repository: https://github.com/openSUSE/git-sha-verify
Improve chore and screen time doc generator script `wochenplaner` by gniebler
Description
I wrote a little Python script to generate PDF docs, which can be used to track daily chore completion and screen time usage for several people, with one page per person/week.
I named this script wochenplaner and have been using it for a few months now.
It needs some improvements and adjustments in how the screen time should be tracked and how chores are displayed.
Goals
- Fix chore field separation lines
- Change screen time tracking logic from "global" (week-long) to daily subtraction and weekly addition of remainders (more intuitive than current "weekly time budget method)
- Add logic to fill in chore fields/lines, ideally with pictures, falling back to text.
Resources
tbd (Gitlab repo)
Improve/rework household chore tracker `chorazon` by gniebler
Description
I wrote a household chore tracker named chorazon, which is meant to be deployed as a web application in the household's local network.
It features the ability to set up different (so far only weekly) schedules per task and per person, where tasks may span several days.
There are "tokens", which can be collected by users. Tasks can (and usually will) have rewards configured where they yield a certain amount of tokens. The idea is that they can later be redeemed for (surprise) gifts, but this is not implemented yet. (So right now one needs to edit the DB manually to subtract tokens when they're redeemed.)
Days are not rolled over automatically, to allow for task completion control.
We used it in my household for several months, with mixed success. There are many limitations in the system that would warrant a revisit.
It's written using the Pyramid Python framework with URL traversal, ZODB as the data store and Web Components for the frontend.
Goals
- Add admin screens for users, tasks and schedules
- Add models, pages etc. to allow redeeming tokens for gifts/surprises
- …?
Resources
tbd (Gitlab repo)