Upstream repo naturalis/ansible-opnsense

[rudibroekhuizen]

Hi, we created the original version of the ansible-opnsense repository. We would like to remove this repository, because it is outdated and not maintained by us anymore.

Can you update your readme file, to let users know that the original upstream repository is removed and that your branch is now leading.

Another option may be to transfer ownership of the naturalis/ansible-opnsense repo to you. Please let us know what your suggestions are.

Regards, Rudi

[zerwes]

Hello @rudibroekhuizen
Thank you for your message and your great work on that repo.

I just created a PR for the migration
https://github.com/Rosa-Luxemburgstiftung-Berlin/ansible-opnsense/tree/update-readme-for-35
Just let me know if this is OK for you.

Would you mind to set the RLS fork as the new upstream repo? (https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#deleting-a-public-repository)

Greetings, THX and good luck with your further projects ....

[davidheijkamp]

Hi, we've just archived the repo with a reference in the README to this one. Based on the Github documentation, and a small test we can not select your fork as the new upstream repo when deleting the repo. In my test the first fork of a test repo was selected as the new upstream one, but maybe Github chooses the most active one.

That's why we've now added a text to the README, giving people the chance to change their git remotes.

Keep up the good work, and if you're ever interested in visiting Leiden / our museum, let us know. We could set up a meeting, because we're also still actively using OPNsense.

[zerwes]

Hello @davidheijkamp
Thank you for your note and your kind invitation. Well, one never knows ...
Well, then let us proceed this way.
Good luck with your further projects and maybe there will be the chance for another collaboration.
CU