Nice.

On Thu, Jul 2, 2020 at 12:21 PM Julien Pivotto <[email protected]>
wrote:

> MySQL had decided
>
> https://mysqlhighavailability.com/mysql-terminology-updates/
>
>
> Le mer. 1 juil. 2020 à 09:54, Matthias Rampke <[email protected]> a
> écrit :
>
>> +1 for changing the default branch, +1 to seeing what GitHub does to help
>> us, but if there is no movement on that we can also work out a plan
>> ourselves.
>>
>> For the MySQL case, *if* we are willing to break compatibility and
>> consistency, we could change the metric names even without waiting for the
>> underlying commands to change. A risk is that we choose one terminology,
>> and upstream ends up choosing another in a year. A chance is that we set a
>> precedent and upstream eventually follows :)
>>
>> /MR
>>
>> On Wed, Jun 24, 2020 at 4:38 PM Frederic Branczyk <[email protected]>
>> wrote:
>>
>>> Tobias’ idea sounds great, and I’m +1 with this!
>>>
>>> On Wed 24. Jun 2020 at 17:17, Tobias Schmidt <[email protected]> wrote:
>>>
>>>> +1
>>>>
>>>> As Github seems to be working on it already, I'd wait to see what they
>>>> can provide to simplify the transition. Would it make sense to tweet from
>>>> our Twitter account to let them know we're interested in such 
>>>> functionality?
>>>>
>>>> I looked at other problematic terminologies across our code bases, and
>>>> it'll be hard to do much about it until third-parties have changed it on
>>>> their side, e.g.
>>>> https://github.com/search?q=org%3Aprometheus+slave&type=Code
>>>>
>>>> On Wed, Jun 24, 2020 at 4:15 PM Bartłomiej Płotka <[email protected]>
>>>> wrote:
>>>>
>>>>> +1 on this from Prometheus side, but also cc Thanos Team, I think we
>>>>> should do that everywhere.
>>>>>
>>>>> Kind Regards
>>>>> Bartek
>>>>>
>>>>> On Wed, 24 Jun 2020 at 16:06, Richard Hartmann <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Dear all,
>>>>>>
>>>>>> I talked about this with a few of you already and the general feeling
>>>>>> of the room was "this is worthwhile, but it carries an opportunity
>>>>>> cost". So: What do you think? Should this be a goal?
>>>>>>
>>>>>> CNCF is on board and assigned tech writer resources to switching over,
>>>>>> and I suggested making CI/CD migrations etc part of Community Bridge
>>>>>> outreach as it's a great intern project.
>>>>>>
>>>>>> It definitely makes sense to wait for GitHub to decide on a name and
>>>>>> to provide tooling to minimize toil.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>>
>>>>>> Richard
>>>>>>
>>>>>> --
>>>>>> 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/CAD77%2BgTerwefdtSU5PB0vPmYA%2BW-20VoDy2GG7AH6F%2BG2RoL3Q%40mail.gmail.com
>>>>>> .
>>>>>>
>>>>> --
>>>>> 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/CAMssQwZPF36eS-Sz0c%3DTArmdy7scuZ7FGv2KQjaF2CzwnkLF1g%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/prometheus-developers/CAMssQwZPF36eS-Sz0c%3DTArmdy7scuZ7FGv2KQjaF2CzwnkLF1g%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Thanos Team" 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/thanos-io/CAChBsdC01oRuGXRmTk-gJVwB1MmbwF5nGfj4OD732Oswfbp1dA%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/thanos-io/CAChBsdC01oRuGXRmTk-gJVwB1MmbwF5nGfj4OD732Oswfbp1dA%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/CAOs1Umwj%3DtUA8RzN2z2bUGd7uoopf9yidh01K1qLMUyngvB%3DKw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/prometheus-developers/CAOs1Umwj%3DtUA8RzN2z2bUGd7uoopf9yidh01K1qLMUyngvB%3DKw%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/CAMV%3D_gZ8UM0S-fV%3D%3D%3D6ZbQ4hiMkRqX0vqfg3zPj83xSTC0%2BNTw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/prometheus-developers/CAMV%3D_gZ8UM0S-fV%3D%3D%3D6ZbQ4hiMkRqX0vqfg3zPj83xSTC0%2BNTw%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/CAFJ6V0pbo1F1n0dMuDf2wtVL%2BZZg_4HyAyMw-EhemcwJEVDoVw%40mail.gmail.com
> <https://groups.google.com/d/msgid/prometheus-developers/CAFJ6V0pbo1F1n0dMuDf2wtVL%2BZZg_4HyAyMw-EhemcwJEVDoVw%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/CABbyFmprXao3rX0%2Bv5wE5JOfwSOMx7mmrAD5cUKKQC1koBQjbA%40mail.gmail.com.

Reply via email to