+1 to mark archived. Manually graveyarding things isn't really needed anymore unless we really want to break use of a thing.
On Tue, Aug 17, 2021 at 10:54 AM Matthias Rampke <[email protected]> wrote: > I think the no-magic route is better. You can also archive the repo[0] to > make it clear that it's read only (with this GitHub feature, do we still > need to graveyard anything ourselves? > > /MR > > > > [0] > https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/archiving-repositories > > On Fri, Aug 13, 2021, 17:57 Bjoern Rabenstein <[email protected]> wrote: > >> Hi, >> >> More than a year ago, I added a pointer from >> https://github.com/prometheus/nagios_plugins (the "old repo") to its >> fork https://github.com/magenta-aps/check_prometheus_metric (the "new >> repo"), see https://github.com/prometheus/nagios_plugins/pull/26 . >> >> I've never heard any complaints about the new plugin, so I think it's >> about time to properly deprecate the old repo. >> >> First of all: Does anyone have any objections? >> >> Assuming we can go forward with it: What do you think is the best >> procedure? Ideally, we would redirect from the old to the new >> repo. However, that's not as easy as it looks. So far, I think this >> would require the following gymnastics: >> >> - Delete the new repo. >> - Transfer the ownership of the old repo to magenta-aps with >> the same name as the (deleted) new repo. >> - Replay all the commits that happened in the new repo to the >> transfered repo to make it appear like the new repo before, >> just not as a fork. >> >> Does anyone have a better idea? >> >> And if not, should we really do that or would it be better to apply less >> magic, just put a big and fat deprecation warning onto the old repo, >> and graveyard it after another half year or so? >> >> Any feedback welcome. >> -- >> Björn Rabenstein >> [PGP-ID] 0x851C3DA17D748D03 >> [email] [email protected] >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Prometheus Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/prometheus-developers/20210813155716.GE3669%40jahnn >> . >> > -- > You received this message because you are subscribed to the Google Groups > "Prometheus Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/prometheus-developers/CAMV%3D_gYjKWMns7DgkhBXr3g%3DKVonp4fyGG%2B6GhnhCiO5tEkAjA%40mail.gmail.com > <https://groups.google.com/d/msgid/prometheus-developers/CAMV%3D_gYjKWMns7DgkhBXr3g%3DKVonp4fyGG%2B6GhnhCiO5tEkAjA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/CABbyFmpsBcOwf3Y710xGirVsuTywdRiGK07H5n4VGvmgK4b3Xw%40mail.gmail.com.
