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

should pephubclient become part of peppy to simplify things? #462

Open
Tracked by #457
donaldcampbelljr opened this issue Dec 5, 2023 · 2 comments
Open
Tracked by #457

Comments

@donaldcampbelljr
Copy link
Contributor

No description provided.

@khoroshevskyi
Copy link
Member

In my opinion, pephubclient shouldn't be part of peppy.

  1. It will be harder to maintain these two things.
  2. I want to avoid recursive dependency.

@nsheff
Copy link
Contributor

nsheff commented Dec 5, 2023

after some discussion in infrastructure, we think it might make sense to:

  • bring pephubclient into peppy as a submodule
  • bring eido back into peppy as a submodule
  • leave pepdbagent outside of peppy

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

No branches or pull requests

3 participants