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.

Sign up for GitHub

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

Jump to bottom

Decide how to implement polices and modes #15

Closed
claucece opened this issue Jul 2, 2018 · 3 comments
Closed

Decide how to implement polices and modes #15

claucece opened this issue Jul 2, 2018 · 3 comments
Labels
architecture importance high An issue that is absolutely necessary to have done before final release
Projects
Pidgin plugin with OTRv4

Comments

@claucece
Copy link
Member

claucece commented Jul 2, 2018 •
edited
Loading

See issues otrv4/libotr-ng#66 and otrv4/libotr-ng#14 of libotr-ng.
@claucece claucece added importance high An issue that is absolutely necessary to have done before final release architecture labels Jul 2, 2018
@claucece
Copy link
Member Author

claucece commented Aug 9, 2018

See the comments on issue: otrv4/libotr-ng#66

@olabini
Copy link
Contributor

olabini commented Aug 25, 2018

As mentioned in the above referenced issue, we will not implement different modes in libotr-ng and pidgin-otrng. The basic support for policies will be implemented in libotr-ng, while the configuration of these policies will be done from inside the plugin.

@claucece
Copy link
Member Author

Yes! I'm closing this one :) @olabini

Pidgin plugin with OTRv4 automation moved this from To Do to Done Aug 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
architecture importance high An issue that is absolutely necessary to have done before final release
Projects
Pidgin plugin with OTRv4
  
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@olabini @claucece