RFC: Archiving unmaintained git repositories

RFC: Archiving unmaintained git repositories

Decision Due Date: November 16, 2026

Context and Problem Statement

The Foreman and related ecosystem repositories have grown organically over time which means there can be git repositories that exist but are no longer actively maintained. These unmaintained repositories should be archived to give a clear indicator to users that they should not rely on them. Additionally, for contributors, unmaintained repositories may fall into dis-repair and when time comes to fix them nothing works.

There may be some repositories that have not needed any maintenance as the problem they solve continues to simply just work.

Proposal

Close git repositories that are unmaintained and remove them from packaging (and installer if present). Here is a list of potential candidates based on activity. Not all of these should be closed, but serve as a candidate list.

Help is needed to identify repositories that are still actively used and should not be archived.

No push in 2+ years (29)

Project Last push
theforeman/foreman_graphite 2015-03-11
theforeman/foreman_transfer_repo 2015-11-06
theforeman/puppet-letsencrypt 2016-06-01
theforeman/smart_proxy_dns_plugin_template 2018-02-09
Dynflow/dynflow.github.io 2018-03-26
theforeman/smart_proxy_dhcp_device42 2018-04-23
Dynflow/dynflow-benchmark 2019-02-28
theforeman/smart_proxy_vault 2020-04-30
theforeman/foreman_datacenter 2020-11-17
theforeman/puppetlabs-postgresql 2021-02-16
theforeman/smart_proxy_dhcp_bluecat 2021-09-29
theforeman/smart_proxy_discovery_image 2022-01-17
theforeman/puppetlabs-apache 2022-09-26
theforeman/hammer-cli-foreman-statistics 2023-06-30
theforeman/hammer-cli-foreman-ssh 2023-10-02
theforeman/foreman_setup 2024-01-23
theforeman/foreman_host_extra_validator 2024-02-22
theforeman/foreman_hooks 2024-03-07
theforeman/foreman_scap_client 2024-07-24
theforeman/foreman_supervisory_authority 2024-08-21

No push in 1–2 years (13)

Project Last push
theforeman/smart_proxy_omaha 2024-11-29
theforeman/smart_proxy_realm_ad_plugin 2025-02-18
theforeman/hammer-cli-foreman-admin 2025-02-20
theforeman/smart_proxy_monitoring 2025-03-06
theforeman/foreman_default_hostgroup 2025-04-03
theforeman/foreman_monitoring 2025-08-19
theforeman/smart_proxy_dhcp_dnsmasq 2025-10-04

Repositories that should be kept active

Project Last push
theforeman/puppet-restic 2023-04-18
Apipie/apipie-bindings 2025-05-14
theforeman/ldap_fluff 2025-05-06
theforeman/smart_proxy_openscap 2025-04-09
theforeman/smart_proxy_dns_route53 2021-11-16
theforeman/smart_proxy_dhcp_infoblox 2025-03-06
theforeman/smart_proxy_dns_infoblox 2025-03-06
theforeman/smart_proxy_dns_powerdns 2021-11-16
theforeman/puppet-foreman_simple_user 2024-04-26
theforeman/katello-pull-transport-migrate 2024-11-01
Apipie/apipie-demo 2023-03-03
Apipie/apipie-diff 2018-01-02

Decision Outcome

What was the decision that was ultimately made and relevant outcomes with links.

I think archiving old/unused repos is a good thing, but I am afraid your search has a few flaws :slight_smile:

  1. it found several forks (mostly puppet modules). theforeman/puppet-restic is actively used in foreman-infra, the others can probably be just deleted as those were old forks of modules we needed to ship a patched version of.
  2. it found several repos that are shipped and used in our downstream products (infoblox, openscap, discovery image)
  3. it found things that are slow but absolutely required (apipie-bindings, ldap_fluff)
  4. it found templates (*_plugin_template)

I am sure other maintainers will speak up for their individual plugins, but I think especially for smart proxy ones having a few years without any changes is not actually bad or an indicator for decay.

:+1: to archiving no longer used/maintained git repositories. As a follow-up step, did you think about removing those plugins from foreman-packaging? E.g. foreman_graphite is still packaged for nightly but IMO we should not package unmaintained plugins.

Good call – I updated the proposal with that.

We are still interested in some of these projects:

  • infoblox
  • route53

I guess, the smart proxy plugins in general are used by some of us - and, if they work and the API is stable there is no need to adapt them.

Regarding *_monitoring, I think @Dirk has a pretty big interest to have them working?

Generally yes, when it comes time to update something about the smart-proxy (e.g. Ruby support, Sinatra) if that means having to touch plugins, that is when the active nature can have an affect.

Besides what @evgeni already brought up:

@ananace do you still intend to keep this?

I still feel responsible for this and would like to keep it alive. Though these days it doesn’t have external dependencies so it could be moved into smart-proxy.git.

I still feel responsible for this. IMHO it’s feature complete so it doesn’t really need a lot of changes.

Also, if you’re removing it from packaging, don’t forget docs, installer, etc :slight_smile:

I don’t really have a way to dogfood smart_proxy_dhcp_dnsmasq or smart_proxy_dns_dnsmasq any longer, so it’s probably reasonable to sunset them - unless someone wants to take over maintenance.

katello-pull-transport-migrate is still used in documentation: Managing hosts

If we want to sunset it, we would need to provide another way (once REX pull mode returns) to set up pull mode on an already-registered host that does not have SSH set up.

I would not say pretty big, but I have it already on my list of things to discuss as I would say we need to put more work into it (meaning I need someone at NETWAYS to help me) or we really should archive. As I am on vacation I will not have an update for you in the next day, but I will come back to it after we discussed it.

Already was mentioned, but:

  • Anything related to Apipie: no, even though we have access, it’s not “our” org. If there is something that we no longer use, e.g. apipie-params, just remove it on our side.
  • theforeman/foreman_hooks - yes, please.
  • theforeman/foreman_scap_client - yes, please.
  • theforeman/hammer-cli-foreman-admin - maybe, it seems we ship it, so probably worth sunset/deprecation warning first…
  • theforeman/hammer-cli-foreman-ssh - probably, I don’t think we even ship it, also, the real last update was in 2015 (disregard my latest commit), I’m afraid it’s heavily unmaintained

We already agreed on this in summer: Archiving hammer-cli-foreman-ssh - #4 by ekohl

I included it in part because I think folks from our community are the primary maintainers of it these days.

Back at work and discussed this today. As I have not enough time and knowledge to maintain the UI part and there is no additional man-power for it, I will open a thread here if someone wants to take over and if noone is found I will sunset the monitoring integration.

Thread is open now: Monitoring integration looking for a new maintainer
I know the decision due date here is 16.11.2026 and Foreman 5.1 is branching already before this, but as there are some users I have the feeling two weeks is not long enough, so I have set a deadline of December for finding a new maintainer. If noone steps up, I will sunset it after this deadline.