@dido-b I say “hopefully” because there are a lot of major bugfixes and stability upgrades that have to be done this year, and that may potentially push back the Calendar. That’s been the case for some time; as you can imagine, the stability and usability of existing features is more important than adding new features. (There’s even another feature slated for this year that has been more in-demand than the Calendar, so that has to come first!)
Historically, Mailspring has just one developer (@bengotow), who works on this project in addition to a full-time job. Over the last couple of years especially, the sheer mass of the issue list on GitHub — much of which consists of questions, minor edge-case bugs, duplicate issues, and wishlist feature requests — has made it difficult to find and focus efforts on the most urgent bugs and features, especially given limited development time. Software development is time-intensive at best, and Mailspring is a particularly complicated project.
That’s why I was brought on as the Volunteer Community Manager. I can determine the most urgent bugs and highest demand features, with an eye towards the actual development effort involved.
All that to say, patience — yes, even years of it — is more than warranted. There is nothing about Mailspring that is simple and easy. If you’d like to help things along, consider helping us fix some of the bugs, especially urgent ones. That will free up Ben to implement these larger features, such as the Calendar.