Skip to content
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.
/ Timotheus Public archive

The Timotheus project aims to create software that can help manage a small association´s calendar, data storage, consent forms etc. in a GDPR compliant fashion. It is currently written in C# and Avalonia to give Cross-Platform support.

License

Apache-2.0, Unknown licenses found

Licenses found

Apache-2.0
LICENSE
Unknown
LICENSE.rtf
Notifications You must be signed in to change notification settings

mjrj97/Timotheus

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Timotheus screenshot

📝 Description

The purpose of this project is to create free open-source software that can manage a small association's calendar, data storage, consent forms etc. in a GDPR compliant fashion (or atleast to its best ability). The program is perfectly suited for organizations, that needs to securely share files internally without using services like Dropbox, Google Drive, and OneDrive, that has been shown to comprise with GDPR guidelines. The program can also help handle a calendar/schedule, and manage a list of consent forms. The project is primarily aimed towards small associations e.g. the Danish LM and IM, that handle sensitive data (names, ages, addresses etc.).

🔥 Features

✔️ Platform-Independent (Windows, macOS)
✔️ Calendar editor and publishing
✔️ File sharing/synchronization using SFTP
✔️ English and Danish localization
✔️ GDPR consent form management
❌ Group Management
❌ Board/Committee administration
❌ Accounting

🚀 How to use

The program is free to use, but no warranty or liability is provided (See the license for more information). The latest version can be downloaded from Martin's website. The program revolves around the key file. This key file is used to save the last opened calendar, people file, usernames, password etc. When the user opens or save fx. the calendar, the key file saves the path to the calendar, so it loads the correct file. When creating a new key file, it should be placed in an empty folder, and the calendar and consent forms are required to be in the same folder (or subfolders).

If the calendar is connected to a remote calendar, the key can also save the username and password. The key is encrypted with a password, which is chosen when the key is saved. This password is required to open (decrypt) the key on subsequent uses.

There are plans to create YouTube tutorials for different use cases, but these are not in the works at the moment.

🏗️ Contribution

You are welcome to contribute to the project!
Send an e-mail to [email protected] for further information.

Visual Studio with the Avalonia extension is highly recommended, as it adds a UI editor which allows you to see changes as you code.

All commits should be on their own branch before being merged into the pre-release branch. On the pre-release branch the program is thoroughly tested before being pulled to the master branch with a version number (Pull requests to the master are done by Martin). The program is being used by an association to handle sensitive data, so quality and security is a priority! 🔒

Find issues and their status & priority in the project.

This project has taken a lot of effort, so donations of all sizes are greatly appreciated. The money will first and foremost go to pay for the yearly $99 / 99€ / 779 kr. Apple Developer License, so the macOS version can keep getting updates.

Donate

🗃️ Libraries

Avalonia 0.10.18
FluentFTP 39.4.0
iCal.Net 4.2.0
PdfSharpCore 1.3.38
SSH.NET 2020.0.2

About

The Timotheus project aims to create software that can help manage a small association´s calendar, data storage, consent forms etc. in a GDPR compliant fashion. It is currently written in C# and Avalonia to give Cross-Platform support.

Topics

Resources

License

Apache-2.0, Unknown licenses found

Licenses found

Apache-2.0
LICENSE
Unknown
LICENSE.rtf

Stars

Watchers

Forks

Languages