Closed ryan-jacobs closed 2 years ago
I suppose there is the question of fork status. We originally forked the main VuFind repo, but then detached from the fork so that we could work in private while considering next steps around open-source/dev for this and other CRL projects. It is possible to re-attach as a fork of the main VuFind project to:
But this comes with drawbacks:
For any PRs we may work on against the main VuFind project I suspect we'll need to spin up new branches largely independent of our production codebase, which could be done as new forks just as effectively as new branches on our own project. So in this regard I'm leaning toward leaving things detached.
Note that the following line in httpd-vufind.conf adds the changelog redirect
# The changelog location has moved to Github Oct 2022
RewriteRule ^/changelog(\.txt)* https://github.com/Center-for-Research-Libraries/vufind/releases [R=301,NC,L]
This is a local config not traced in VC.
This is a bit past-due. The build team already discussed and approved making the repo public, and I have also advocated for this to other org leadership with supportive feedback. So it's time to finalize the move to open-development on this project.
GPL licensing terms will be automatically inherited from core VuFind codebase, so no licensing steps are needed