Is this product dead?
palefire19 opened this issue · 50 comments
Update from the Maintainers
Nylas Mail was officially sunset in August and re-licensed under MIT. Nylas is no longer maintaining Nylas Mail. Instead, check out it's successors:
-
Mailspring: One of the original developers is continuing Nylas Mail as Mailspring. Mailspring includes the same Pro features and a new C++ sync engine built on Mailcore2, which is faster, uses less RAM, and fixes many provider-related bugs.
-
Nylas Mail Lives: A group of community members forked Nylas Mail to keep it alive, accept contributions from the community and publish new releases that fix bugs and add features.
Original Post
It increasingly appears as if Nylas is basically giving up on Nylas Mail...after converting from N1 barely 2 months ago?
Anyone from Nylas, are you out there? Can you at least respond to one ticket on Github and give us a sense of whether you plan to continue developing and providing support for this product?
from the next issue in the list:
Unfortunately, we are no longer providing help support for Nylas Mail or N1. As a company, Nylas is focused on our API products to help other developers build email, calendar, and sync capabilities into their own applications.
That's a real shocker but it explains the absence of reactions to the pile of issues.
It's a shame that nobody is communicating with the community. They clearly have a lot of interest.
There are developers (myself included) who are willing to help support this, but I'm not an Electron developer, so can't take lead.
I think the only hope is that somebody (or group) forks the project and runs it independently from nylas, who clearly have no interest in working on this as an OSS project.
1000 people have forked it, I am sure someone must be updating it. We just need to find that someone who is trying to fix things
Oh man I literally just installed this last night. Was looking for a good replacement for Thunderbird. What a shame. I really like this UI too, but it is ungodly slow retrieving my mail, and it's not like I have thousands of messages either.
@anechol the same shit ) replaced Thunderbird a week ago. I think I have to come to their office and check what's going on - there are pretty close to our :)
@DmitryLoki do it. Or at least make them transfer the contributor rights to someone who might wanna continue the project and commit other people's changes
Damn. Have been watching few of the issues without progress in half a year. Just downgraded just for this reason, would have liked to continue using Nylas Mail... bummer.
Is this still maintained by Nylas or not? Do they only stop to support?
@sotayamashita in theory, but they have shown no sign nor intention to do anything with the OSS project. They have still been making releases.
@lxalln I see. Thank you.
The CEO of Nylas replied to tweet with this
I'd be happy and try to help maintain this tool, as it has helped a lot in organizing my stuff.
Should we create a new organization and for the project there? May be the issues (and the precious pull requests) can be transfered to there as well?
@danielmelogpi yeah that would be good. I want to get involved with maintaining this as well but when I saw that no one is maintaining I figured what can I do on my own
@danielmelogpi I can help you for code and translation 💻 🗺️
great @danielmelogpi and @sotayamashita are in, I wanna do this as well so we have three people keen on picking this up
@danielmelogpi I don't think that the PRs can be cloned, but the issues can. See this thread: holman/ama#413. There are two tools there; the python tool can 'clone' the PRs but in the destination repo they are turned into issues.
I gave this a shot and forked the project to https://github.com/nylas-mail-lives/nylas-mail.
I still need to study it in my spare time and I imagine you guys are in the same boat.
@mayurdw, @sotayamashita and @dweremeichik I sent you invites for membership.
May be we can try to set this in motion!
Yay!! @danielmelogpi thanks. I have just joined it. We should have some kind of way to talk to one another at least? @sotayamashita @dweremeichik
Let's try slack then
https://join.slack.com/nylasisalive/shared_invite/MTkyNTkyNzMwODA1LTE0OTY2MjIyMDQtMWNhNzI0NWM4Mg (updated in june 4th)
@danielmelogp I appreciate you creating org and slack. I have joined both of them. 😄
Anyone else willing to help us organize this endevour, please, use the link above and join us. We still need to understand the next steps and also, to understand this codebase to start working :)
@jstejada , would you be able to help us understand a good strategy to contribute? You sure have a lot of commits there and may be you can help us out
Hi guys - I would love to help out here, but I'm not a developer. I do think I could serve as a reasonably useful product manager / ticket prioritizer, if that would be a helpful contribution...
@palefire19 , join us at slack :)
Hello everyone! I work at Nylas and am extremely sorry for the lack of communication leading to this issue! Our engineering team has been heavily tasked on our enterprise API product for the past couple of weeks but we have not forgotten about Nylas Mail!
We'd like to bring the community in closer and do everything we can to establish and support community maintainers. We’re internally working through the proper governance issues right now, but to begin, I’d love to start chatting with at least @mayurdw, @dweremeichik and @danielmelogpi plus whoever else is interested. I’ll be posting more updates about this over the next several days.
Hey guys I would like to help out too here. I'm experienced in react.js, node, electron and am also quite handy in responsive design, scss, compass/bourbon and all the faff. I think this is a great product with great potential and we should take this chance and make email great again. Pun intended.
@palefire19 I'm interested to join the Slack too, even if I'm not experienced with Node/Electron.
Looks like the Slack is invite-only for now so I can't join :/
@MickaelBergem and others, I just found out that the invitation link expires after 30 days. Will try to reach out slack team to get it reenabled.
You can always send me an e-mail with your e-mail address and I will set up an invitation as soon as I reach my computer.
Just received a new link from Slack:
https://join.slack.com/nylasisalive/shared_invite/MTkyNTkyNzMwODA1LTE0OTY2MjIyMDQtMWNhNzI0NWM4Mg
Also, updating my first message to avoid mistakes
Hey everyone, is there still discussion going on in that Slack group? I tried the link but it's expired
Indeed there is. I will ping @danielmelogpi to see if we can get that link sorted out.
@iansinnott I sent a slack invite to the email listed on your profile.
Thanks @dweremeichik :)
Can I have a invitation to Slack?
@rgaiacs done.
Would also love a Slack invite :)
@adriantombu incorrect, Nylas is still working on the product internally and releasing "updates". They are currently not including feedback and pull requests from this community however. Also, the fork that was made from this project still relies on the Nylas API (Nylas pays for those servers to run).
Fairly annoying situation! I was an early adopter, from before we had to sign up for another account and everything went all ‘cloud’.
@danielmelogpi @mayurdw @sotayamashita @dweremeichik So is nylas-mail-lives now the main fork as far as this community is concerned?
I would like to see the project not die, and willing to contribute when I can… I work on/in Atom all the time so I know my way around Electron and any remnants of the CoffeeScript (which I love!) codebase, as this app was a fork of Atom early on. Incidentally, CoffeeScript 2 (which compiles to ES6) is pretty much ready now in it’s 3rd beta.
Anyway, some things I would like to see happen:
- Decouple the app from requiring Nylas altogether (especially removing the need to sign into a separate account before signing in again to your actual email account!)
- Refactor ‘send later’/‘snooze’ etc to work independently/locally (these could use a launch agent on macOS for example)
- Reinstate and expand mail rules for automatic sorting of mail
- Fix the Markdown composer! (PR here thanks to @morsby nylas/N1-Markdown-Composer#27)
- Rename the new forked project to something else, maybe ‘Open Mail’ or something
- It’s own GitHub project/org page
- Proper package management with a cli, probably based on npm
Is it worth joining the new #Slack group? Wouldn’t using the existing Nylas one have been a better option? Or Gitter even…
We have seen a good bit of interest from the community on a number of your bullet points. Unfortunately for a majority of them, no one has stepped up to tackle them as of yet.
It is definitely worth it to join the new slack channel. The new one was created due to the circumstances surrounding this repository (not knowing what was/is going to happen).
I would recommend creating issues in the fork for feature requests that you would like to see worked on. Note that the fork relies heavily on the community, so if you see something you would like to work on, mention it in the issue.
Contributors of any caliber are welcome!
@danielbayley at least the first point should be easier since they already moved the main e-mail part away from the cloud.
@dweremeichik @emorikawa @GM-Polyakov @jackiehluo @jstejada @khamidou @necrobuffalo @pfista @spang
I've been trying to contact Nylas for a week now. As an early adopter and a paying customer, I'm very upset with how you're communicating this change. My Nylas email account has been broken for a week and I guess your response is
You can imagine that as a developer I'm now less likely to consider your new venture into developer tools if this is how you communicate.
Same here @amccloud , i'm an early adopter and i'm really really very upset. This is very stupid from Nylas team, not a mail, not a twit. Shame on you .
@amccloud I don't work for Nylas, I do contribute to the new fork though.
https://github.com/nylas-mail-lives/nylas-mail/
What issue are you seeing with your client? The fork may have fixed it already, if it isn't, you are more than welcome to try and tackle the issue in the fork. Or at least create the issue there.
Mind linking the issue in?
@amccloud , I recommend you keep trying contact with Nylas Support team, as none of us in this thread, as far as I read it, works for Nylas. . This thread is the root the for fork and we are looking forward to have an application maintained by the community, without the reliance on Nylas to accept PRs.
If it comes to it, I suggest you cancel your subscription with them. It is, indeed, very upsetting to pay and not receive your goods anymore. Use social media. People fear it.
Hey folks - I'm one of the original authors of Nylas Mail and worked at Nylas until last winter. As you've all mentioned, Nylas has pulled engineers off of the mail client and shifted focus to the API products that are the primary revenue drivers for the company. As frustrating as this move has been (for me as well), it was definitely necessary. Nylas is a venture-backed startup and startups need to make money.
I've always loved Nylas Mail, and I'm working on a fork that will fix longstanding bugs and put it on a better foundation for continued development. I'm actually re-writing the entire mail sync engine in C++ for better performance and battery life, and deploying backend infrastructure to run snooze, send later, etc.
You can download the new version (called Mailspring) here: https://getmailspring.com/, or find it on GitHub at https://github.com/Foundry376/Mailspring/.
It would be wonderful if the two forks had each other in mind to come to some consensus later.
Somehow I'd missed all this discussion until this morning. I've found Nylas to be frustrating since the switch from N1 earlier this year. The product simply isn't working to the level needed to be considered a viable email client. I'd be fine with this, and just move on, except they're also now trying to get me to pay for features that used to be free (really, I've reached my maximum number of email snoozes for the week?)
Not meaning to rant, and I respect that a company has to make money, but this was all very poorly handled. The complete lack of transparency is really, really frustrating.