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

switch from OpenGlobus fork to OpenGlobus as npm package #45

Open
3 tasks
jdohm opened this issue Mar 21, 2021 · 0 comments
Open
3 tasks

switch from OpenGlobus fork to OpenGlobus as npm package #45

jdohm opened this issue Mar 21, 2021 · 0 comments
Labels
backlog Improvements and small bugs, that won't be worked on now, but will be relevant in the future.

Comments

@jdohm
Copy link
Owner

jdohm commented Mar 21, 2021

In the long run it seems cleaner and easier to use OpenGlobus as a package rather than forking it.

  • To change this, all references must be changed.

  • Our code needs to be separated from OpenGlobus code.

  • Changes to the OpenGlobus code need to be eliminated. Either by changing the specific behavior inside our code or by contributing to OpenGlobus where applicable.

@jdohm jdohm added the backlog Improvements and small bugs, that won't be worked on now, but will be relevant in the future. label Mar 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Improvements and small bugs, that won't be worked on now, but will be relevant in the future.
Projects
None yet
Development

No branches or pull requests

1 participant