You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As i understand, the plan for the ipyoptimade fork was to just simplify maintenance for the aiidalab team and there is no plan to merge back to this repo?
This causes the problem of two diverged versions and it's not clear to me what to modify/make PRs to if I need to update the Materials Cloud tool.
It would be great to have a single version of this app to maintain. And this single version should be available in PYPI.
I see two options:
We could keep this repo as the primary version and give direct access to the maintainers. Potentially could also be transferred to a different organization.
We adopt aiidalab/ipyoptimade as the primary version and use that in both Materials Cloud and AiiDAlab.
Hi, we currently have two versions of this optimade client:
As i understand, the plan for the ipyoptimade fork was to just simplify maintenance for the aiidalab team and there is no plan to merge back to this repo?
This causes the problem of two diverged versions and it's not clear to me what to modify/make PRs to if I need to update the Materials Cloud tool.
It would be great to have a single version of this app to maintain. And this single version should be available in PYPI.
I see two options:
We could keep this repo as the primary version and give direct access to the maintainers. Potentially could also be transferred to a different organization.
We adopt aiidalab/ipyoptimade as the primary version and use that in both Materials Cloud and AiiDAlab.
Thoughs? @CasperWA @unkcpz
The text was updated successfully, but these errors were encountered: