You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Suresh Anaparti <Su...@shapeblue.com> on 2021/05/11 07:41:43 UTC
[RESULT][VOTE] Renaming default git branch name from
'master' to 'main' and replace offensive words as appropriate
for inclusiveness
Hi all,
The vote [1] for renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness, in the Apache CloudStack project has passed with the following votes:
+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)
+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)
+0
1 person (Andrija)
Thank you all for participating. Next steps, I'll close any review feedback on the PRs and get them accepted. Once the PRs are accepted, we can merge them to 'master' (may be after 4.15.1 release) and will request ASF infra (track through new INFRA ticket) to disable pushes to 'master', rename 'master' to 'main and set 'main' as the default branch, for all the CloudStack repos.
[1] https://markmail.org/message/n6sbl3vgm7hy77zj
Regards,
Suresh
Re: [RESULT][VOTE] Renaming default git branch name
from 'master' to 'main' and replace offensive words as appropriate
for inclusiveness
Posted by Suresh Anaparti <Su...@shapeblue.com>.
Thanks Dahn.
So far, no issues with Travis CI, Jenkins. Packaging also seems fine. Smoke tests in progress, not observed any issues with renaming until now. I think, we still have to wait few more weeks (until most of us adapts to default branch 'main') and watch for any issues reported with renaming.
Please let us know if you have noticed any issues.
Regards,
Suresh
On 18/06/21, 1:40 PM, "Daan Hoogland" <da...@gmail.com> wrote:
thanks Suresh for the hard work,
Are there any remaining actions or arisen issues on this?
On Fri, Jun 11, 2021 at 12:23 PM Suresh Anaparti <
Suresh.Anaparti@shapeblue.com> wrote:
> Hi All,
>
> The default branch has been renamed to 'main' (from 'master'), for the
> following CloudStack project repos.
>
> - cloudstack
> - cloudstack-documentation
> - cloudstack-www
> - cloudstack-cloudmonkey
> - cloudstack-kubernetes-provider
> - cloudstack-ec2stack
> - cloudstack-gcestack
>
> Next steps, I'll run health checks and see if there are any issues with
> the integrated jobs/systems (Travis CI, Jenkins, etc).
>
> Please run the below cmds to update your existing cloned repos.
>
> git branch -m master main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> Regards,
> Suresh
>
> On 08/06/21, 6:55 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi All,
>
> Here is the update, All the PRs that addressed the inclusive changes
> (changing the default branch name from 'master' to 'main' and replacing
> some offensive words) in the CloudStack repos are accepted/merged. I've
> created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978,
> to rename the default branch to 'main' (which should automatically
> re-target all the open/draft PRs against 'master' to 'main'). I'll let you
> know once renaming is done, and the next steps.
>
> Regards,
> Suresh
>
> On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi all,
>
> The vote [1] for renaming default git branch name from 'master' to
> 'main' and replace offensive words as appropriate for inclusiveness, in the
> Apache CloudStack project has passed with the following votes:
>
> +1 (PMC / binding)
> 4 persons (Daan, Gabriel, Rohit, Wei)
>
> +1 (non-binding)
> 5 persons (David, Rene, Nathan, Hari, Suresh)
>
> +0
> 1 person (Andrija)
>
> Thank you all for participating. Next steps, I'll close any review
> feedback on the PRs and get them accepted. Once the PRs are accepted, we
> can merge them to 'master' (may be after 4.15.1 release) and will request
> ASF infra (track through new INFRA ticket) to disable pushes to 'master',
> rename 'master' to 'main and set 'main' as the default branch, for all the
> CloudStack repos.
>
> [1] https://markmail.org/message/n6sbl3vgm7hy77zj
>
>
> Regards,
> Suresh
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Daan
Re: [RESULT][VOTE] Renaming default git branch name
from 'master' to 'main' and replace offensive words as appropriate
for inclusiveness
Posted by Suresh Anaparti <Su...@shapeblue.com>.
Thanks Dahn.
So far, no issues with Travis CI, Jenkins. Packaging also seems fine. Smoke tests in progress, not observed any issues with renaming until now. I think, we still have to wait few more weeks (until most of us adapts to default branch 'main') and watch for any issues reported with renaming.
Please let us know if you have noticed any issues.
Regards,
Suresh
On 18/06/21, 1:40 PM, "Daan Hoogland" <da...@gmail.com> wrote:
thanks Suresh for the hard work,
Are there any remaining actions or arisen issues on this?
On Fri, Jun 11, 2021 at 12:23 PM Suresh Anaparti <
Suresh.Anaparti@shapeblue.com> wrote:
> Hi All,
>
> The default branch has been renamed to 'main' (from 'master'), for the
> following CloudStack project repos.
>
> - cloudstack
> - cloudstack-documentation
> - cloudstack-www
> - cloudstack-cloudmonkey
> - cloudstack-kubernetes-provider
> - cloudstack-ec2stack
> - cloudstack-gcestack
>
> Next steps, I'll run health checks and see if there are any issues with
> the integrated jobs/systems (Travis CI, Jenkins, etc).
>
> Please run the below cmds to update your existing cloned repos.
>
> git branch -m master main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> Regards,
> Suresh
>
> On 08/06/21, 6:55 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi All,
>
> Here is the update, All the PRs that addressed the inclusive changes
> (changing the default branch name from 'master' to 'main' and replacing
> some offensive words) in the CloudStack repos are accepted/merged. I've
> created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978,
> to rename the default branch to 'main' (which should automatically
> re-target all the open/draft PRs against 'master' to 'main'). I'll let you
> know once renaming is done, and the next steps.
>
> Regards,
> Suresh
>
> On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi all,
>
> The vote [1] for renaming default git branch name from 'master' to
> 'main' and replace offensive words as appropriate for inclusiveness, in the
> Apache CloudStack project has passed with the following votes:
>
> +1 (PMC / binding)
> 4 persons (Daan, Gabriel, Rohit, Wei)
>
> +1 (non-binding)
> 5 persons (David, Rene, Nathan, Hari, Suresh)
>
> +0
> 1 person (Andrija)
>
> Thank you all for participating. Next steps, I'll close any review
> feedback on the PRs and get them accepted. Once the PRs are accepted, we
> can merge them to 'master' (may be after 4.15.1 release) and will request
> ASF infra (track through new INFRA ticket) to disable pushes to 'master',
> rename 'master' to 'main and set 'main' as the default branch, for all the
> CloudStack repos.
>
> [1] https://markmail.org/message/n6sbl3vgm7hy77zj
>
>
> Regards,
> Suresh
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Daan
Re: [RESULT][VOTE] Renaming default git branch name from 'master' to
'main' and replace offensive words as appropriate for inclusiveness
Posted by Daan Hoogland <da...@gmail.com>.
thanks Suresh for the hard work,
Are there any remaining actions or arisen issues on this?
On Fri, Jun 11, 2021 at 12:23 PM Suresh Anaparti <
Suresh.Anaparti@shapeblue.com> wrote:
> Hi All,
>
> The default branch has been renamed to 'main' (from 'master'), for the
> following CloudStack project repos.
>
> - cloudstack
> - cloudstack-documentation
> - cloudstack-www
> - cloudstack-cloudmonkey
> - cloudstack-kubernetes-provider
> - cloudstack-ec2stack
> - cloudstack-gcestack
>
> Next steps, I'll run health checks and see if there are any issues with
> the integrated jobs/systems (Travis CI, Jenkins, etc).
>
> Please run the below cmds to update your existing cloned repos.
>
> git branch -m master main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> Regards,
> Suresh
>
> On 08/06/21, 6:55 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi All,
>
> Here is the update, All the PRs that addressed the inclusive changes
> (changing the default branch name from 'master' to 'main' and replacing
> some offensive words) in the CloudStack repos are accepted/merged. I've
> created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978,
> to rename the default branch to 'main' (which should automatically
> re-target all the open/draft PRs against 'master' to 'main'). I'll let you
> know once renaming is done, and the next steps.
>
> Regards,
> Suresh
>
> On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi all,
>
> The vote [1] for renaming default git branch name from 'master' to
> 'main' and replace offensive words as appropriate for inclusiveness, in the
> Apache CloudStack project has passed with the following votes:
>
> +1 (PMC / binding)
> 4 persons (Daan, Gabriel, Rohit, Wei)
>
> +1 (non-binding)
> 5 persons (David, Rene, Nathan, Hari, Suresh)
>
> +0
> 1 person (Andrija)
>
> Thank you all for participating. Next steps, I'll close any review
> feedback on the PRs and get them accepted. Once the PRs are accepted, we
> can merge them to 'master' (may be after 4.15.1 release) and will request
> ASF infra (track through new INFRA ticket) to disable pushes to 'master',
> rename 'master' to 'main and set 'main' as the default branch, for all the
> CloudStack repos.
>
> [1] https://markmail.org/message/n6sbl3vgm7hy77zj
>
>
> Regards,
> Suresh
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Daan
Re: [RESULT][VOTE] Renaming default git branch name from 'master' to
'main' and replace offensive words as appropriate for inclusiveness
Posted by Daan Hoogland <da...@gmail.com>.
thanks Suresh for the hard work,
Are there any remaining actions or arisen issues on this?
On Fri, Jun 11, 2021 at 12:23 PM Suresh Anaparti <
Suresh.Anaparti@shapeblue.com> wrote:
> Hi All,
>
> The default branch has been renamed to 'main' (from 'master'), for the
> following CloudStack project repos.
>
> - cloudstack
> - cloudstack-documentation
> - cloudstack-www
> - cloudstack-cloudmonkey
> - cloudstack-kubernetes-provider
> - cloudstack-ec2stack
> - cloudstack-gcestack
>
> Next steps, I'll run health checks and see if there are any issues with
> the integrated jobs/systems (Travis CI, Jenkins, etc).
>
> Please run the below cmds to update your existing cloned repos.
>
> git branch -m master main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> Regards,
> Suresh
>
> On 08/06/21, 6:55 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi All,
>
> Here is the update, All the PRs that addressed the inclusive changes
> (changing the default branch name from 'master' to 'main' and replacing
> some offensive words) in the CloudStack repos are accepted/merged. I've
> created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978,
> to rename the default branch to 'main' (which should automatically
> re-target all the open/draft PRs against 'master' to 'main'). I'll let you
> know once renaming is done, and the next steps.
>
> Regards,
> Suresh
>
> On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi all,
>
> The vote [1] for renaming default git branch name from 'master' to
> 'main' and replace offensive words as appropriate for inclusiveness, in the
> Apache CloudStack project has passed with the following votes:
>
> +1 (PMC / binding)
> 4 persons (Daan, Gabriel, Rohit, Wei)
>
> +1 (non-binding)
> 5 persons (David, Rene, Nathan, Hari, Suresh)
>
> +0
> 1 person (Andrija)
>
> Thank you all for participating. Next steps, I'll close any review
> feedback on the PRs and get them accepted. Once the PRs are accepted, we
> can merge them to 'master' (may be after 4.15.1 release) and will request
> ASF infra (track through new INFRA ticket) to disable pushes to 'master',
> rename 'master' to 'main and set 'main' as the default branch, for all the
> CloudStack repos.
>
> [1] https://markmail.org/message/n6sbl3vgm7hy77zj
>
>
> Regards,
> Suresh
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Daan
Re: [RESULT][VOTE] Renaming default git branch name
from 'master' to 'main' and replace offensive words as appropriate
for inclusiveness
Posted by Suresh Anaparti <Su...@shapeblue.com>.
Hi All,
The default branch has been renamed to 'main' (from 'master'), for the following CloudStack project repos.
- cloudstack
- cloudstack-documentation
- cloudstack-www
- cloudstack-cloudmonkey
- cloudstack-kubernetes-provider
- cloudstack-ec2stack
- cloudstack-gcestack
Next steps, I'll run health checks and see if there are any issues with the integrated jobs/systems (Travis CI, Jenkins, etc).
Please run the below cmds to update your existing cloned repos.
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
Regards,
Suresh
On 08/06/21, 6:55 PM, "Suresh Anaparti" <Su...@shapeblue.com> wrote:
Hi All,
Here is the update, All the PRs that addressed the inclusive changes (changing the default branch name from 'master' to 'main' and replacing some offensive words) in the CloudStack repos are accepted/merged. I've created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978, to rename the default branch to 'main' (which should automatically re-target all the open/draft PRs against 'master' to 'main'). I'll let you know once renaming is done, and the next steps.
Regards,
Suresh
On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com> wrote:
Hi all,
The vote [1] for renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness, in the Apache CloudStack project has passed with the following votes:
+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)
+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)
+0
1 person (Andrija)
Thank you all for participating. Next steps, I'll close any review feedback on the PRs and get them accepted. Once the PRs are accepted, we can merge them to 'master' (may be after 4.15.1 release) and will request ASF infra (track through new INFRA ticket) to disable pushes to 'master', rename 'master' to 'main and set 'main' as the default branch, for all the CloudStack repos.
[1] https://markmail.org/message/n6sbl3vgm7hy77zj
Regards,
Suresh
Re: [RESULT][VOTE] Renaming default git branch name
from 'master' to 'main' and replace offensive words as appropriate
for inclusiveness
Posted by Suresh Anaparti <Su...@shapeblue.com>.
Hi All,
The default branch has been renamed to 'main' (from 'master'), for the following CloudStack project repos.
- cloudstack
- cloudstack-documentation
- cloudstack-www
- cloudstack-cloudmonkey
- cloudstack-kubernetes-provider
- cloudstack-ec2stack
- cloudstack-gcestack
Next steps, I'll run health checks and see if there are any issues with the integrated jobs/systems (Travis CI, Jenkins, etc).
Please run the below cmds to update your existing cloned repos.
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
Regards,
Suresh
On 08/06/21, 6:55 PM, "Suresh Anaparti" <Su...@shapeblue.com> wrote:
Hi All,
Here is the update, All the PRs that addressed the inclusive changes (changing the default branch name from 'master' to 'main' and replacing some offensive words) in the CloudStack repos are accepted/merged. I've created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978, to rename the default branch to 'main' (which should automatically re-target all the open/draft PRs against 'master' to 'main'). I'll let you know once renaming is done, and the next steps.
Regards,
Suresh
On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com> wrote:
Hi all,
The vote [1] for renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness, in the Apache CloudStack project has passed with the following votes:
+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)
+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)
+0
1 person (Andrija)
Thank you all for participating. Next steps, I'll close any review feedback on the PRs and get them accepted. Once the PRs are accepted, we can merge them to 'master' (may be after 4.15.1 release) and will request ASF infra (track through new INFRA ticket) to disable pushes to 'master', rename 'master' to 'main and set 'main' as the default branch, for all the CloudStack repos.
[1] https://markmail.org/message/n6sbl3vgm7hy77zj
Regards,
Suresh
Re: [RESULT][VOTE] Renaming default git branch name
from 'master' to 'main' and replace offensive words as appropriate
for inclusiveness
Posted by Suresh Anaparti <Su...@shapeblue.com>.
Hi All,
Here is the update, All the PRs that addressed the inclusive changes (changing the default branch name from 'master' to 'main' and replacing some offensive words) in the CloudStack repos are accepted/merged. I've created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978, to rename the default branch to 'main' (which should automatically re-target all the open/draft PRs against 'master' to 'main'). I'll let you know once renaming is done, and the next steps.
Regards,
Suresh
On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com> wrote:
Hi all,
The vote [1] for renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness, in the Apache CloudStack project has passed with the following votes:
+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)
+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)
+0
1 person (Andrija)
Thank you all for participating. Next steps, I'll close any review feedback on the PRs and get them accepted. Once the PRs are accepted, we can merge them to 'master' (may be after 4.15.1 release) and will request ASF infra (track through new INFRA ticket) to disable pushes to 'master', rename 'master' to 'main and set 'main' as the default branch, for all the CloudStack repos.
[1] https://markmail.org/message/n6sbl3vgm7hy77zj
Regards,
Suresh
Re: [RESULT][VOTE] Renaming default git branch name from 'master' to
'main' and replace offensive words as appropriate for inclusiveness
Posted by Andrija Panic <an...@gmail.com>.
Hi Rich,
not going to argue about what you said, as most of that I agree with - but
for the sake of discussion (which this thread is not a right place, but
perhaps some time again on Apache con, with a beer or tea) - I would like
to understand the part of your response:
***This entire effort, across the entire software industry, is about
creating a place where people feel part of the team, rather than
outsiders***
I'm not sure how my colour, race or sex could let me feel like an outsider
to any project I want to contribute to (due to my personal
preference/color/sex is not emphasized/mentioned in the project)?
If I want to contribute, I will contribute, this is my decision/good will.
Or I can behave childishly like a 3-year kid who feels parents are not
paying enough attention, so he/she/it (I'm being inclusive here, am I not?)
is screaming and seeking attention.
Again, to me (and it seems only to me...I am a weird one, indeed) this is
pure politics - but, of course, I have nothing against choosing the words
more carefully and using more generic/softer/correct terms (as you said
"... is more about choosing the right words/phrases") - but where is the
limit/boundaries when a person can be offended by some words, or feel
excluded? i.e. I can be "offended" or feel "excluded" because our project
uses blue colour... (e.g. I like red). You get my point, I'm sure.
I'm ending my involvement in this email thread, as I have no intention to
"offend" or feel anyone "unwelcome" by my opinions... it's about time to
let the inclusivity bloom since everything has been so "exclusive" for the
last 20 years...
On Mon, 24 May 2021 at 14:47, Rich Bowen <rb...@apache.org> wrote:
>
>
> On 2021/05/24 09:13:45, Andrija Panic <an...@gmail.com> wrote:
> > (it's interesting to see that " sanity check " (a very common,
> > non-offensive wording used in coding) is considered inappropriate (by
> > whatever authority...???)
>
> I don't think that "inappropriate" is really the point here. Rather, the
> goal is to avoid terms that have other, unrelated meanings, which may have
> implications for members of your project community. "Sanity" has no actual
> meaning in software, but it does have a meaning to actual humans in your
> community who suffer from mental health issues. And in avoiding terms like
> that, it gives an opportunity to use terms that actually mean something
> useful. You are not checking the "sanity" of your software, as it has none?
> What are you checking? Community clearly by choosing words that say what
> you actually mean. This, in turn, makes it easier for those for whom
> English is not a first language to understand what is being communicated.
>
> In general, avoiding jargon, colloquialisms, and slang helps expand the
> number of people who can read your words with clarity and understanding.
>
> > ( also "he/she" is considered "gender" and that also seems
> > inappropriate????? - I can't believe this nonsense (otherwise, it may be
> > grammatical errors, and yes, those should be corrected)
>
> While you are, of course, welcome to think that this is nonsense, it's
> meaningful to those individuals in your community who identify as neither
> "he" nor "she", and feel that they are being excluded by these word
> choices. Do you want them to feel unwelcome? No, of course you don't. So
> choosing words that include everyone is good for you, too, because it
> extends a welcome to a larger contributor community, which, in turn,
> increases the opportunity for innovation.
>
> Focusing on "offense" and "inappropriate" and so on is only a small part
> of the story. Rather, a conscious language effort (or "inclusive language,"
> if you prefer) is more about choosing the right words/phrases than about
> avoiding "bad" ones. This entire effort, across the entire software
> industry, is about creating a place where people feel part of the team,
> rather than outsiders. Words matter, and this is just one way to use words
> to craft such a place.
>
>
--
Andrija Panić
Re: [RESULT][VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness
Posted by Rich Bowen <rb...@apache.org>.
On 2021/05/24 09:13:45, Andrija Panic <an...@gmail.com> wrote:
> (it's interesting to see that " sanity check " (a very common,
> non-offensive wording used in coding) is considered inappropriate (by
> whatever authority...???)
I don't think that "inappropriate" is really the point here. Rather, the goal is to avoid terms that have other, unrelated meanings, which may have implications for members of your project community. "Sanity" has no actual meaning in software, but it does have a meaning to actual humans in your community who suffer from mental health issues. And in avoiding terms like that, it gives an opportunity to use terms that actually mean something useful. You are not checking the "sanity" of your software, as it has none? What are you checking? Community clearly by choosing words that say what you actually mean. This, in turn, makes it easier for those for whom English is not a first language to understand what is being communicated.
In general, avoiding jargon, colloquialisms, and slang helps expand the number of people who can read your words with clarity and understanding.
> ( also "he/she" is considered "gender" and that also seems
> inappropriate????? - I can't believe this nonsense (otherwise, it may be
> grammatical errors, and yes, those should be corrected)
While you are, of course, welcome to think that this is nonsense, it's meaningful to those individuals in your community who identify as neither "he" nor "she", and feel that they are being excluded by these word choices. Do you want them to feel unwelcome? No, of course you don't. So choosing words that include everyone is good for you, too, because it extends a welcome to a larger contributor community, which, in turn, increases the opportunity for innovation.
Focusing on "offense" and "inappropriate" and so on is only a small part of the story. Rather, a conscious language effort (or "inclusive language," if you prefer) is more about choosing the right words/phrases than about avoiding "bad" ones. This entire effort, across the entire software industry, is about creating a place where people feel part of the team, rather than outsiders. Words matter, and this is just one way to use words to craft such a place.
Re: [RESULT][VOTE] Renaming default git branch name from 'master' to
'main' and replace offensive words as appropriate for inclusiveness
Posted by Andrija Panic <an...@gmail.com>.
All good Rohit, I get that, inside the code in particular, it should
usually always be "it", simply due to grammar.
I'm waiting for the moment where using "monkey" words and other animals
would be found inappropriate to be used with software (like i.e.
cloudmonkey and many others) due to someone finding that inappropriate ;)
Cheers,
On Mon, 24 May 2021 at 11:23, Rohit Yadav <ro...@shapeblue.com> wrote:
> Andrija,
>
> I think the point in particular with "he/she" is for projects to consider
> updating their code/docs with gender-neutral terms.
>
>
> Regards.
>
> ________________________________
> From: Andrija Panic <an...@gmail.com>
> Sent: Monday, May 24, 2021 14:43
> To: dev <de...@cloudstack.apache.org>
> Cc: private@cloudstack.apache.org <pr...@cloudstack.apache.org>
> Subject: Re: [RESULT][VOTE] Renaming default git branch name from 'master'
> to 'main' and replace offensive words as appropriate for inclusiveness
>
> (it's interesting to see that " sanity check " (a very common,
> non-offensive wording used in coding) is considered inappropriate (by
> whatever authority...???)
> ( also "he/she" is considered "gender" and that also seems
> inappropriate????? - I can't believe this nonsense (otherwise, it may be
> grammatical errors, and yes, those should be corrected)
>
>
>
>
> On Fri, 21 May 2021 at 12:11, Sven Vogel <S....@ewerk.com> wrote:
>
> > Thanks Suresh. I will take a look.
> >
> >
> > __
> >
> > Sven Vogel
> > Senior Manager Research and Development - Cloud and Infrastructure
> >
> > EWERK DIGITAL GmbH
> > Brühl 24, D-04109 Leipzig
> > P +49 341 42649 - 99
> > F +49 341 42649 - 98
> > S.Vogel@ewerk.com
> > www.ewerk.com<http://www.ewerk.com>
> >
> > Geschäftsführer:
> > Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
> > Registergericht: Leipzig HRB 9065
> >
> > Support:
> > +49 341 42649 555
> >
> > Zertifiziert nach:
> > ISO/IEC 27001:2013
> > DIN EN ISO 9001:2015
> > DIN ISO/IEC 20000-1:2018
> >
> > ISAE 3402 Typ II Assessed
> >
> > EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
> > https://www.linkedin.com/company/ewerk-group> | Xing<
> > https://www.xing.com/company/ewerk> | Twitter<
> > https://twitter.com/EWERK_Group> | Facebook<
> > https://de-de.facebook.com/EWERK.Group/>
> >
> >
> > Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
> >
> > Disclaimer Privacy:
> > Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien)
> ist
> > vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> > bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> > Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> > informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> > die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem
> System.
> > Vielen Dank.
> >
> > The contents of this e-mail (including any attachments) are confidential
> > and may be legally privileged. If you are not the intended recipient of
> > this e-mail, any disclosure, copying, distribution or use of its contents
> > is strictly prohibited, and you should please notify the sender
> immediately
> > and then delete it (including any attachments) from your system. Thank
> you.
> >
> > ________________________________
> > Von: Suresh Anaparti <Su...@shapeblue.com>
> > Gesendet: Friday, May 21, 2021 11:19:38 AM
> > An: dev@cloudstack.apache.org <de...@cloudstack.apache.org>;
> > private@cloudstack.apache.org <pr...@cloudstack.apache.org>
> > Betreff: Re: [RESULT][VOTE] Renaming default git branch name from
> 'master'
> > to 'main' and replace offensive words as appropriate for inclusiveness
> >
> > FYI. A language scanner for inclusive terminology is being proposed in
> > Apache Diversity. A demo scanner service for CloudStack repo here:
> > https://clcdemo.net/analysis.html?project=cloudstack.git
> >
> > I hope CloudStack counters will go down, after merging the
> > renaming/inclusive PRs.
> >
> > Regards,
> > Suresh
> >
> > On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> > wrote:
> >
> > Hi all,
> >
> > The vote [1] for renaming default git branch name from 'master' to
> > 'main' and replace offensive words as appropriate for inclusiveness, in
> the
> > Apache CloudStack project has passed with the following votes:
> >
> > +1 (PMC / binding)
> > 4 persons (Daan, Gabriel, Rohit, Wei)
> >
> > +1 (non-binding)
> > 5 persons (David, Rene, Nathan, Hari, Suresh)
> >
> > +0
> > 1 person (Andrija)
> >
> > Thank you all for participating. Next steps, I'll close any review
> > feedback on the PRs and get them accepted. Once the PRs are accepted, we
> > can merge them to 'master' (may be after 4.15.1 release) and will request
> > ASF infra (track through new INFRA ticket) to disable pushes to 'master',
> > rename 'master' to 'main and set 'main' as the default branch, for all
> the
> > CloudStack repos.
> >
> > [1] https://markmail.org/message/n6sbl3vgm7hy77zj
> >
> >
> > Regards,
> > Suresh
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
>
> Andrija Panić
>
--
Andrija Panić
Re: [RESULT][VOTE] Renaming default git branch name
from 'master' to 'main' and replace offensive words as appropriate
for inclusiveness
Posted by Rohit Yadav <ro...@shapeblue.com>.
Andrija,
I think the point in particular with "he/she" is for projects to consider updating their code/docs with gender-neutral terms.
Regards.
________________________________
From: Andrija Panic <an...@gmail.com>
Sent: Monday, May 24, 2021 14:43
To: dev <de...@cloudstack.apache.org>
Cc: private@cloudstack.apache.org <pr...@cloudstack.apache.org>
Subject: Re: [RESULT][VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness
(it's interesting to see that " sanity check " (a very common,
non-offensive wording used in coding) is considered inappropriate (by
whatever authority...???)
( also "he/she" is considered "gender" and that also seems
inappropriate????? - I can't believe this nonsense (otherwise, it may be
grammatical errors, and yes, those should be corrected)
On Fri, 21 May 2021 at 12:11, Sven Vogel <S....@ewerk.com> wrote:
> Thanks Suresh. I will take a look.
>
>
> __
>
> Sven Vogel
> Senior Manager Research and Development - Cloud and Infrastructure
>
> EWERK DIGITAL GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> S.Vogel@ewerk.com
> www.ewerk.com<http://www.ewerk.com>
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
> Registergericht: Leipzig HRB 9065
>
> Support:
> +49 341 42649 555
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 20000-1:2018
>
> ISAE 3402 Typ II Assessed
>
> EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
> https://www.linkedin.com/company/ewerk-group> | Xing<
> https://www.xing.com/company/ewerk> | Twitter<
> https://twitter.com/EWERK_Group> | Facebook<
> https://de-de.facebook.com/EWERK.Group/>
>
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
>
> ________________________________
> Von: Suresh Anaparti <Su...@shapeblue.com>
> Gesendet: Friday, May 21, 2021 11:19:38 AM
> An: dev@cloudstack.apache.org <de...@cloudstack.apache.org>;
> private@cloudstack.apache.org <pr...@cloudstack.apache.org>
> Betreff: Re: [RESULT][VOTE] Renaming default git branch name from 'master'
> to 'main' and replace offensive words as appropriate for inclusiveness
>
> FYI. A language scanner for inclusive terminology is being proposed in
> Apache Diversity. A demo scanner service for CloudStack repo here:
> https://clcdemo.net/analysis.html?project=cloudstack.git
>
> I hope CloudStack counters will go down, after merging the
> renaming/inclusive PRs.
>
> Regards,
> Suresh
>
> On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi all,
>
> The vote [1] for renaming default git branch name from 'master' to
> 'main' and replace offensive words as appropriate for inclusiveness, in the
> Apache CloudStack project has passed with the following votes:
>
> +1 (PMC / binding)
> 4 persons (Daan, Gabriel, Rohit, Wei)
>
> +1 (non-binding)
> 5 persons (David, Rene, Nathan, Hari, Suresh)
>
> +0
> 1 person (Andrija)
>
> Thank you all for participating. Next steps, I'll close any review
> feedback on the PRs and get them accepted. Once the PRs are accepted, we
> can merge them to 'master' (may be after 4.15.1 release) and will request
> ASF infra (track through new INFRA ticket) to disable pushes to 'master',
> rename 'master' to 'main and set 'main' as the default branch, for all the
> CloudStack repos.
>
> [1] https://markmail.org/message/n6sbl3vgm7hy77zj
>
>
> Regards,
> Suresh
>
>
>
>
>
>
>
>
>
--
Andrija Panić
Re: [RESULT][VOTE] Renaming default git branch name from 'master' to
'main' and replace offensive words as appropriate for inclusiveness
Posted by Andrija Panic <an...@gmail.com>.
(it's interesting to see that " sanity check " (a very common,
non-offensive wording used in coding) is considered inappropriate (by
whatever authority...???)
( also "he/she" is considered "gender" and that also seems
inappropriate????? - I can't believe this nonsense (otherwise, it may be
grammatical errors, and yes, those should be corrected)
On Fri, 21 May 2021 at 12:11, Sven Vogel <S....@ewerk.com> wrote:
> Thanks Suresh. I will take a look.
>
>
> __
>
> Sven Vogel
> Senior Manager Research and Development - Cloud and Infrastructure
>
> EWERK DIGITAL GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> S.Vogel@ewerk.com
> www.ewerk.com
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
> Registergericht: Leipzig HRB 9065
>
> Support:
> +49 341 42649 555
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 20000-1:2018
>
> ISAE 3402 Typ II Assessed
>
> EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
> https://www.linkedin.com/company/ewerk-group> | Xing<
> https://www.xing.com/company/ewerk> | Twitter<
> https://twitter.com/EWERK_Group> | Facebook<
> https://de-de.facebook.com/EWERK.Group/>
>
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
>
> ________________________________
> Von: Suresh Anaparti <Su...@shapeblue.com>
> Gesendet: Friday, May 21, 2021 11:19:38 AM
> An: dev@cloudstack.apache.org <de...@cloudstack.apache.org>;
> private@cloudstack.apache.org <pr...@cloudstack.apache.org>
> Betreff: Re: [RESULT][VOTE] Renaming default git branch name from 'master'
> to 'main' and replace offensive words as appropriate for inclusiveness
>
> FYI. A language scanner for inclusive terminology is being proposed in
> Apache Diversity. A demo scanner service for CloudStack repo here:
> https://clcdemo.net/analysis.html?project=cloudstack.git
>
> I hope CloudStack counters will go down, after merging the
> renaming/inclusive PRs.
>
> Regards,
> Suresh
>
> On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com>
> wrote:
>
> Hi all,
>
> The vote [1] for renaming default git branch name from 'master' to
> 'main' and replace offensive words as appropriate for inclusiveness, in the
> Apache CloudStack project has passed with the following votes:
>
> +1 (PMC / binding)
> 4 persons (Daan, Gabriel, Rohit, Wei)
>
> +1 (non-binding)
> 5 persons (David, Rene, Nathan, Hari, Suresh)
>
> +0
> 1 person (Andrija)
>
> Thank you all for participating. Next steps, I'll close any review
> feedback on the PRs and get them accepted. Once the PRs are accepted, we
> can merge them to 'master' (may be after 4.15.1 release) and will request
> ASF infra (track through new INFRA ticket) to disable pushes to 'master',
> rename 'master' to 'main and set 'main' as the default branch, for all the
> CloudStack repos.
>
> [1] https://markmail.org/message/n6sbl3vgm7hy77zj
>
>
> Regards,
> Suresh
>
>
>
>
>
>
>
>
>
--
Andrija Panić
Re: [RESULT][VOTE] Renaming default git branch name from 'master' to
'main' and replace offensive words as appropriate for inclusiveness
Posted by Sven Vogel <S....@ewerk.com>.
Thanks Suresh. I will take a look.
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com
www.ewerk.com
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<https://www.linkedin.com/company/ewerk-group> | Xing<https://www.xing.com/company/ewerk> | Twitter<https://twitter.com/EWERK_Group> | Facebook<https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank.
The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you.
________________________________
Von: Suresh Anaparti <Su...@shapeblue.com>
Gesendet: Friday, May 21, 2021 11:19:38 AM
An: dev@cloudstack.apache.org <de...@cloudstack.apache.org>; private@cloudstack.apache.org <pr...@cloudstack.apache.org>
Betreff: Re: [RESULT][VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness
FYI. A language scanner for inclusive terminology is being proposed in Apache Diversity. A demo scanner service for CloudStack repo here: https://clcdemo.net/analysis.html?project=cloudstack.git
I hope CloudStack counters will go down, after merging the renaming/inclusive PRs.
Regards,
Suresh
On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com> wrote:
Hi all,
The vote [1] for renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness, in the Apache CloudStack project has passed with the following votes:
+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)
+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)
+0
1 person (Andrija)
Thank you all for participating. Next steps, I'll close any review feedback on the PRs and get them accepted. Once the PRs are accepted, we can merge them to 'master' (may be after 4.15.1 release) and will request ASF infra (track through new INFRA ticket) to disable pushes to 'master', rename 'master' to 'main and set 'main' as the default branch, for all the CloudStack repos.
[1] https://markmail.org/message/n6sbl3vgm7hy77zj
Regards,
Suresh
Re: [RESULT][VOTE] Renaming default git branch name
from 'master' to 'main' and replace offensive words as appropriate
for inclusiveness
Posted by Suresh Anaparti <Su...@shapeblue.com>.
FYI. A language scanner for inclusive terminology is being proposed in Apache Diversity. A demo scanner service for CloudStack repo here: https://clcdemo.net/analysis.html?project=cloudstack.git
I hope CloudStack counters will go down, after merging the renaming/inclusive PRs.
Regards,
Suresh
On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com> wrote:
Hi all,
The vote [1] for renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness, in the Apache CloudStack project has passed with the following votes:
+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)
+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)
+0
1 person (Andrija)
Thank you all for participating. Next steps, I'll close any review feedback on the PRs and get them accepted. Once the PRs are accepted, we can merge them to 'master' (may be after 4.15.1 release) and will request ASF infra (track through new INFRA ticket) to disable pushes to 'master', rename 'master' to 'main and set 'main' as the default branch, for all the CloudStack repos.
[1] https://markmail.org/message/n6sbl3vgm7hy77zj
Regards,
Suresh
Re: [RESULT][VOTE] Renaming default git branch name
from 'master' to 'main' and replace offensive words as appropriate
for inclusiveness
Posted by Suresh Anaparti <Su...@shapeblue.com>.
Hi All,
Here is the update, All the PRs that addressed the inclusive changes (changing the default branch name from 'master' to 'main' and replacing some offensive words) in the CloudStack repos are accepted/merged. I've created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978, to rename the default branch to 'main' (which should automatically re-target all the open/draft PRs against 'master' to 'main'). I'll let you know once renaming is done, and the next steps.
Regards,
Suresh
On 11/05/21, 1:12 PM, "Suresh Anaparti" <Su...@shapeblue.com> wrote:
Hi all,
The vote [1] for renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness, in the Apache CloudStack project has passed with the following votes:
+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)
+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)
+0
1 person (Andrija)
Thank you all for participating. Next steps, I'll close any review feedback on the PRs and get them accepted. Once the PRs are accepted, we can merge them to 'master' (may be after 4.15.1 release) and will request ASF infra (track through new INFRA ticket) to disable pushes to 'master', rename 'master' to 'main and set 'main' as the default branch, for all the CloudStack repos.
[1] https://markmail.org/message/n6sbl3vgm7hy77zj
Regards,
Suresh