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

Seperate Loklak common components used by SUSI into it's own library #1534

Open
yukiisbored opened this issue Sep 15, 2017 · 1 comment
Open

Comments

@yukiisbored
Copy link
Member

This is a common problem between the Loklak and SUSI project. Every changes made to the core components has to be backported to SUSI. The problem of this is backporting is a tricky job and can lead to misconfiguration, regression, "whoops I forgot something". Which adds to the development hell.

I'm proposing separating the common components that SUSI and Loklak uses and make that into a common web framework used by both projects.

Pros:

  • Reduces mistakes
  • Reduces development time
  • Enables other developers to use the same library to leverage their own applications

Cons:

  • Hard to do
  • Sometimes it's annoying to add the feature into the common library while working on something
@yukiisbored yukiisbored changed the title Seperate Loklak into a common Web application API Seperate Loklak common components used by SUSI into it's own library Sep 15, 2017
@yukiisbored
Copy link
Member Author

The coala project does something similar like this. coala separates useful common decorators, functions, etc into it's own project called coala-utils.

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

No branches or pull requests

2 participants