Currently, Panopticon itself, its connectors, the landing site, and the additional software we use to generate data used by Panopticon are just a bunch of repositories scattered across the akeeba organisation on GitHub.
This was great at the beginning when it was just two repositories, but it's now getting too convoluted to manage – and confusing to people who are trying to find the repositories connected to Panopticon.
It would make a lot more sense to have a dedicated organisation. I created one: https://github.com/getpanopticon All repositories should be moved there.
Moving a repository into a different organisation should still redirect the old URL to the new one. Confirm that before committing to moving everything.
It would also make sense to move update information etc into the CDN site instead of pulling it from GitHub. Gives us more flexibility for things like this.
Currently, Panopticon itself, its connectors, the landing site, and the additional software we use to generate data used by Panopticon are just a bunch of repositories scattered across the
akeebaorganisation on GitHub.This was great at the beginning when it was just two repositories, but it's now getting too convoluted to manage – and confusing to people who are trying to find the repositories connected to Panopticon.
It would make a lot more sense to have a dedicated organisation. I created one: https://github.com/getpanopticon All repositories should be moved there.
Moving a repository into a different organisation should still redirect the old URL to the new one. Confirm that before committing to moving everything.
It would also make sense to move update information etc into the CDN site instead of pulling it from GitHub. Gives us more flexibility for things like this.