Delete stale branches

[stv0g]

The DPsim repo on GitHub has currently quite a number of stale branches. We should aim at removing the number of open branches and delete or merge them wherever possible.

Here is list of open branches:

• 255-pypi-build-and-deploy-fails
• ACDC_HVDCTests
• ControlBlocks
• DP-vsi-voltage-control
• DP-vsi-voltage-control-rebase
• IterativeMNASolverDirect
• Sundials
• ba-can
• benchmark-networks
• benchmark-networks-cosim
• centos-dockerfile
• ci-minimal-build
• compiler-warning-fixes-256
• cosim-examples
• cosim-examples-rebase
• cwirtz-fgh-EMT_Ph1_Switch
• dependabot/npm_and_yarn/docs/hugo/yaml-2.2.2
• deploy-docker was used for docker ci action but not anymore - deleted @m-mirz
• deploy-docs-test
• dp-9-bus-dyn-switch-nb @m-mirz will check
• droop-control
• eigenvalues
• emt-syngen-trstab
• fix-cmake
• fix-devcontainer @m-mirz need to finalize
• fix-docs-leo some commits were merged with cherry-pick, deleted by @leonardocarreras
• fix-doxygen-input-paths
• fix-sonar-jdk
• fix_initialization_rxload
• fix_power_flow_initialisation
• gh-pages docs website @m-mirz
• grid-forming-inverter
• grid-forming-inverter-rebase
• hotfix-missing-simulation-stop
• ieee14-v2
• improve-logging
• inergy-demo
• iterative_syngens_optim_lsc
• jl-mna-plugin
• jl-mna-plugin-32bit
• klu-default
• klu-solver-error
• klu-testing
• klu-testing-cr
• klu-testing-pr
• kundur-two-area
• libxil-dep
• mat2dpsimpy
• mnasolver-nicslu-adapter
• mybinder
• no-actions-on-pr
• opal-rtlab
• pju-devcontainer
• pmu-signal
• powerflow-revision
• pyproject
• python-logsteptimes
• remove-rwth-gitlab-deps
• revise-pf-solver
• rl-element
• rl-element-rebase
• rm-gitlab-docker-build
• sg-controllers
• slew-scenarios-all
• solver-parameters
• ssn
• ssn-linear
• syngen-vbr-nicslu
• unify-mna-subcomponents-old
• update-contacts
• update-repo-refs
• update-villas-version
• villas-worker
• voltage-source-delay
• vsi-voltage-control
• vsi-voltage-control-RMS-fix

[georgii-tishenin]

Hi, @stv0g, thanks for creating this issue.
To move this forward and eventually close the issue we can:
1. Identify Stale Branches

• We can use this list of stale branches. These are the branches with >3 months without a commit. Or we could may be use our own more relaxed definition of stale, e.g., 1 year without a commit.

2. Assign Ownership

• Assign each stale branch to its creator.

3. Set a Response Deadline

• Give creators 1 month to confirm if their branch is needed or can be deleted.

4. Delete Unclaimed Branches

• Delete branches with no response after the deadline.

what do you think?