Come contribute to the drafting of a feature request.
Here is the draft feature request: https://badsender.notion.site/Feature-Request-Manage-Email-Expiration-Dates-in-OpenSource-Email-Clients-139dd12c64084147bf21c105fa7af9b7?pvs=4
As I explain each time I present the email expiration dates project, our biggest challenge is that we want to integrate into an existing ecosystem. The entire chain must move forward together for expiration dates to become a reality: senders, sending solutions, and email providers.
Therefore, some players need to move ahead of others. To prove the interest. To get initial adoption. To pave the way for other stakeholders.
In this context, why not draft specifications that can be adopted in open source email clients? Whether natively or via extensions/plugins, these specifications could then serve as examples when commercial email providers want to implement the feature.
I have therefore drafted a base feature request that will then be distributed to all open source email clients (Thunderbird, Roundcube, Zimbra, Balsa, Kmail, Gnome Evolution, Rainloop…).
But I need your contributions to improve this work.
How to contribute?
- Post your comments
- Suggest text modifications
- Propose other ideas (for example, in the implementation proposals)
- Tag open-source email client developers in this conversation
- Create wireframes for certain features
Here is the draft feature request: https://badsender.notion.site/Feature-Request-Manage-Email-Expiration-Dates-in-OpenSource-Email-Clients-139dd12c64084147bf21c105fa7af9b7?pvs=4
Recent Comments