Cypht in Tiki vs Cypht standalone

Cypht is a webmail aggregator. It was picked to become Tiki's webmail component.

Cypht is a standalone webmail and an independent project. However, in the last few years, Tiki developers have had a preponderant influence because they contributed a lot of code.

So what features go to Cypht vs Tiki?

As much as reasonably possible, we add features to Cypht to make them available to a broader community (All Tiki users have Cypht built-in). But for some features, it's quite debatable if it should be in Cypht. A good example is advanced calendar support. From the moment a tool is used as someone's main calendar, there can be a need for CalDAV, CardDAV, invitations by email, appointment slots, permissions and delegation, recurring events, etc.. This can become quite complex. Tiki already has an advanced Calendar system, so the very basic calendar in Cypht standalone is not getting attention from Tiki developers.

If you use Cypht, and are ́lacking some features, you will likely find them in Tiki. Similary, Roundcube doesn't support a built-in calendar and relies on plugins like Kolab's calendar

How Cypht and Tiki are converging

• License
• Dependencies
  • Bootstrap
  • Markdown handling
• Cypht added an LTS: https://github.com/cypht-org/cypht/wiki/Lifecycle. This is a small step in the direction of Tiki's Lifecycle

Code designed to work together

• Tags

What Tiki does extra

• Parts of Email filters
• Calendar Invitations by email
• More advanced Contacts
• Email folders Tracker Field

How Tiki is helping Cypht be easier to integrate with

• https://github.com/cypht-org/cypht/wiki/Integration-Options#examples