I am open to a rename if the name is potentially offensive. I share the same concerns as Julius, and I believe that we should consider the impact on searchability, and confusion among end users.
Cheers, Suraj On Fri, Sep 10, 2021 at 1:40 AM Matthias Rampke <[email protected]> wrote: > *resurrecting thread* > > I agree that we should rename it. I wince every time I need to call it by > name. I often just call it prober anyway and even unaffiliated people > immediately know what I'm talking about. > > More broadly, I think "blackbox" / "whitebox" monitoring is not very > descriptive, and would propose using "probing" and "instrumentation" > respectively. > > It would take a bit of transition planning, maybe with one "double > release" under both names. > > What do the maintainers think? > > /MR > > On Thu, Jun 11, 2020, 18:49 Ben Kochie <[email protected]> wrote: > >> +1 for "prober". We could call it simply "prober". It more directly >> describes what it's doing. >> >> >> >> On Thu, Jun 11, 2020 at 12:35 PM Julius Volz <[email protected]> >> wrote: >> >>> Btw. in case we do end up going for a rename, I think Probe Exporter or >>> Prober Exporter would be a nice and descriptive name for what it's doing >>> (active probing of things). >>> >>> On Thu, Jun 11, 2020, 12:03 Julius Volz <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> Good motivation, personally I think that kind of replacement is a good >>>> thing to do with blacklist/whitelist (as is happening with flag names in >>>> the Node Exporter). But I don't know how people feel about blackbox / >>>> whitebox yet, as it doesn't carry the same negative/positive association >>>> with colors. It would mean more invasive changes, like renaming the entire >>>> repository and related documentation web pages, and potential Google >>>> findability confusion (old blog posts etc. mentioning the old name). >>>> >>>> I haven't heard blackbox/whitebox crop up in the same way as e.g. >>>> blacklist/whitelist yet, but would be interested to affected Black people's >>>> opinion on whether this seems troublesome as well. If this turns out to be >>>> offensive to affected people, that'd be a good argument for renaming it >>>> IMO. >>>> >>>> Julius >>>> >>>> On Thu, Jun 11, 2020 at 11:29 AM Frederic Branczyk <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I would like to propose to change all occurrences and namings within >>>>> the Prometheus project of whitebox and blackbox monitoring. In itself the >>>>> term Black box <https://en.wikipedia.org/wiki/Black_box> doesn't seem >>>>> to come from a racist background, but I think it's problematic when the >>>>> opposite is "white", in particular as this has a connotation in relation >>>>> to >>>>> whitelist/blacklist namings which are undoubtedly problematic. I would >>>>> like >>>>> to propose to replace them with open/closed box monitoring, which not only >>>>> removes any potential of being offensive, it actually conveys much more >>>>> clearly what is meant without having to explain. >>>>> >>>>> The biggest impact this would have would be renaming of the >>>>> blackbox_exporter <https://github.com/prometheus/blackbox_exporter> >>>>> to closedbox_exporter, all other occurrences of this language seem to be >>>>> limited to documentation. >>>>> >>>>> Best regards, >>>>> Frederic >>>>> >>>>> -- >>>>> 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/98b3d620-d0d6-4436-bf15-3d90915f7909o%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/prometheus-developers/98b3d620-d0d6-4436-bf15-3d90915f7909o%40googlegroups.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/CA%2BT6Yoyawu8gP7XU95jFyO24Dk_bZ8VnKy-7wUwHE%2BVDnRTcNQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/prometheus-developers/CA%2BT6Yoyawu8gP7XU95jFyO24Dk_bZ8VnKy-7wUwHE%2BVDnRTcNQ%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/CABbyFmrju%2BxYo6pvjEOhNh-gFXa9%2BB5rKyHwXsSjgSy-KCSFSA%40mail.gmail.com >> <https://groups.google.com/d/msgid/prometheus-developers/CABbyFmrju%2BxYo6pvjEOhNh-gFXa9%2BB5rKyHwXsSjgSy-KCSFSA%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/CAGv31%3Di6RTDaNzm%3DvDO7YFYOqyaOv3MJB-2Tegcjjwcptw%3D31g%40mail.gmail.com.
