Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release timeline #391

Closed
Fastidious opened this issue May 26, 2016 · 12 comments
Closed

Release timeline #391

Fastidious opened this issue May 26, 2016 · 12 comments

Comments

@Fastidious
Copy link

If there a timeline on when this project will reach release status (available on the Play Store), or is being abandoned?

@NoodlesNZ
Copy link

I've been following this project for the last few years, hoping it would be released. Every time I check the github repo there's been work done, but no more blog posts or any sign of a release. I'd really like to use this extension.

@NoSubstitute
Copy link

Just use it! It works fine. You just have to compile and install it manually.

@Fastidious
Copy link
Author

@NoSubstitute I have done that in the past; it is not about me using it. I asked for a release status, that would make it easier for mass adoption and usage. I do little by having it, when there is no one else using it. This is a Google [initiated] project, no? When will it be finished? The question is directed to those who might know.

@geekpete
Copy link

geekpete commented Jul 12, 2016

So it's apache licensed, it could be forked and improved independently and released as a separate supported app in the app store?

@Fastidious
Copy link
Author

Fastidious commented Jul 14, 2016

@geekpete I read somewhere that such thing will be frown upon.

The thing is, the End-to-end Team isn't showing much signs of life. :-(

@sirdarckcat
Copy link
Member

sirdarckcat commented Sep 9, 2016

Hi there

the most current update we have, is that we have been working on the key server and a few other things, but they aren't part of the javascript library anymore (which is why this project has no activity right now).

@geekpete
Copy link

geekpete commented Sep 9, 2016

Thanks for the update! 👍

@Fastidious
Copy link
Author

@sirdarckcat what is your involvement with the project? Where is the source of your update?

@sirdarckcat
Copy link
Member

@Fastidious we are the maintainers of this part of the project. But we aren't doing much on the JavaScript library right now. Most of the work is done by our colleagues at the moment :-) like @gdbelvin

@SystemDisc
Copy link

It would be great to get updates from @gdbelvin or maybe some members of that team, then :)

@sirdarckcat
Copy link
Member

Now that the key server is public (keytransparency.org) and the new UI is public (https://github.com/e2email-org/e2email) there is nothing secret done to announce, just a few more iterations of work.

Availability in the Chrome/Play store is still unclear.

@NoSubstitute
Copy link

@sirdarckcat , so what does this mean?
If I want to use E2E today, should I grab code from here, or instead from e2email?

So far, I have only used code from here, and it has worked ok, with both new ECC keys, but also with my old RSA keys. Does e2email also support non-ECC keys? Reading the short intro that isn't clear.

The initial version only supports ordinary text email, and focuses on new users who all use E2EMail to read PGP/MIME mail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants