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

Restructure Known Source and Plugins for Improved Maintenance and Development #3129

Open
lindner opened this issue Oct 8, 2022 · 0 comments
Milestone

Comments

@lindner
Copy link
Collaborator

lindner commented Oct 8, 2022

Today Known has a core repo in idno/known and a number of core plugins that were split off in the past into separate repos.

While this offers great flexibility it also makes developing Known difficult and requires a developer to juggle multiple repos, composer configs etc. The plugin repos have separate issue trackers, are a chore to maintain, and require setting up configs across many places.

To solve this

  • Import plugins into the main Known Repo (a list will be added as a comment). For each plugin:
    • Import the code into an appropriate directory, preserve change history if possible.
    • Issues should also be moved to the main repo.
    • If there are composer.json for dependencies include them in the main composer.json.

Once this is done it will be much easier to make sure that all core plugins are functioning well.

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

No branches or pull requests

1 participant