Improve the UX of the Sieve filter editor

[cptsanifair]

🚀 Feature

Actually the Sieve Filter is hard to handle.

Max be its possible to implement things from the following project to upgrade sieve filter technics

Design, Layout, Architecture

https://github.com/thsmi/sieve

[marclaporte]

Thank you @cptsanifair for the suggestion.

https://github.com/thsmi/sieve is AGPL so we can't reuse any code, but we certainly get inspiration for features to implement.

Can you give one example of something better done in thsmi/sieve?

[cptsanifair]

The UI with drag and drop, and switch to source without any metadata-header.
it parse existing source and show it in the UI

[marclaporte]

Here is a demo: https://thsmi.github.io/sieve-demo/

If we'd really prefer to intergrate, we can reach out to author about a potential license change.

[marclaporte]

Current situation:

[marclaporte]

More info:

General info about Sieve: http://sieve.info/
Find implementations: https://implementations.modernemail.org/

The Sieve filters need to work nicely within Cypht of course.

But do keep in mind that Cypht is also embeddable. Nowadays in https://doc.tiki.org/Cypht and we are making it easier and easier to integrate within other applications.

When we added Sieve support to Cypht, we created a new PHP library:
https://github.com/cypht-org/php-sieve-manager
#569
#1308

As for filters: We need to to keep in mind that they can be extended. For example: In Tiki, there are filters for filters not available in Cypht: https://doc.tiki.org/Email-filters

[marclaporte]

The UI with drag and drop, and switch to source without any metadata-header.
it parse existing source and show it in the UI

@cptsanifair We will soon start working on this, so any more feedback you have, the better.

[marclaporte]

SnappyMail (fork of RainLoop) is another one to look at:
https://github.com/the-djmaze/snappymail

[marclaporte]

@jeremiah The monthly Cypht community meetings are a great opportunity to discuss this: https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings

[jeremiah]

@marclaporte Okay, I'll see if I can join. It's on my calendar.

Regarding AGPL licensed code - there is no reason Cypht can't use AGPL licensed code, one simply provides a "complete and corresponding" copy of the original code.

[jeremiah]

With regard to UI and UX, this is pretty impressive: https://mpa.nuejs.org/app/?rust

[marclaporte]

there is no reason Cypht can't use AGPL licensed code

My understanding is that LGPL code can be included in AGPL but not the other way around, as per:

• https://dwheeler.com/essays/floss-license-slide.html
• https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility

[jeremiah]

Here's the approach I took when doing license compliance for one of the largest software companies in the US; the AGPLv3 is just like the GPLv3, but for SaaS projects. The FSF itself says; "The GNU Affero General Public License is a modified version of the ordinary GNU GPL version 3. It has one added requirement: if you run a modified program on a server and let other users communicate with it there, your server must also allow them to download the source code corresponding to the modified version running there.”

As long as you release the AGPLv3 code, you're fine. If you're modifying the AGPLv3 code into a combined work, the combined work has to be AGPLv3.

In any case, if we're referring to the "Sieve editor" web app, there are different portions of this app since it includes third-party code. The third party code is licensed MIT, GPLv3, and likely other licenses. So if Cypht is interested in using the MIT licensed parts of the Sieve editor, it is free to do so. (FWIW I've filed a bug upstream in the Sieve repo so they mention the GPLv3 perl code in the LICENSING_INFO.md file.)

I apologize for being so pedantic. All I really want to say is Cypht should try to remain open source and that there is a lot of flexibility with other FOSS licenses if you are already open source.

[marclaporte]

So if Cypht is interested in using the MIT licensed parts of the Sieve editor, it is free to do so

I agree with this. So we seem to be in agreement that Cypht can't continue to claim being LGPL if it includes AGPL code.

We could ask https://github.com/thsmi/sieve to dual license or relicense the code. This happened to Cypht itself: #333

But before we get to that, we need to determine

1. if it's better to just improve what we have or replace all/part it with an external dependency
2. if we decide for an external dependency, is https://github.com/thsmi/sieve our best option?

@Baraka24 Please add to the agenda for our next https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings