-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HEADs UP: This repo has moved from "master" to "main" #258
Comments
Dear @stronk7, I can sort of get the possible 'why' of this, but mainly I'm interested in what instigated it in the first place? Has there been lots of complaints? Have things gone too PC or is this proportionate? If this is being implemented, then what about '/lib/womenslib.php'? Does that have an issue in a new equalitarian World if it is perceived to give bias in one direction or is it that it seeks to bring balance? I had noticed that the default branches for new repo's on GitHub are now 'main' and given enough reason, I'm prepared to migrate my own. Cheers, Gareth |
Hola @gjb2048, this was decided for core (with public announce, plan et all) @ MDLSITE-7418. And, for consistency (and ease of integration between them), as part of the detailed plan, we agreed to also move all these "subproducts" (tools) in the same direction (we had a good mix). If you have any question, opinion or rant to share I'd suggest you to do that in the issue. Personally, I don't have any interest or intention to discuss about that here, I'm afraid. I'm just the Ciao and see you in the issue! |
Thanks @stronk7, Perhaps, pragmatically I'm concerned about annoying MHQ more than I already have and wanted a more friendly ear to listen to my concerns. Thanks again, Gareth |
Heh, you're welcome, 100%, always, Gareth! 🤗 |
Not trying to stir up emotions - I think it's important to highlight that this is a beneficial feature and not just a nod to "consistency". The amount of effort to change a branch name is far less than the benefit of undoing one more example - however small - of systemic racism. And that's part of why MySQL, Git/GitHub and other tools are moving away from these words that were previously cemented into our day-to-day processes and discussions. It's both the right thing to do and the efficient thing long term. We need more diversity in open source development (and it helps a lot if people feel like they are welcomed, such as by not constantly being faced with microaggressions), to increase the flexibility/agility of the application, but also so that casual prejudice is not acceptable. If you ever hear someone say "Well now that so-and-so is part of our team/organization/community, we won't be able to joke about something related to their background.", that's probably indicative that the joke wasn't ever really acceptable in the first place. Also, "Easter eggs" like the file Gareth mentioned are a security/maintenance concern/waste and should be removed for multiple reasons: https://www.securityweek.com/examining-threat-easter-eggs/ https://github.com/moodle/moodle/commits/main/lib/womenslib.php |
Thank you @jrchamp, Spot on. I completely agree. Whilst small changes like this may seem insignificant, or a waste of time, or a "nod to PC" to some of us, we are the privileged ones who aren't impacted and don't feel those micro-agressions. |
I would be enormously grateful if you move those opinions and proclamas out from the issue. You are plenty of places to express your opinions. And they don’t have to match the opinions of the rest of the world. Said with all respects, of course, how not. |
Dear @stronk7, Many apologies for asking about this in the first place, I just wanted to know a bit of the background to it rather than express an opinion or view on any particular side. Totally happy to retract my initial post if you'd like me to. I appreciate the 'heads up' as this will now cause me to make positive adjustments. Kind regards, Gareth |
My apologies for continuing the off-topic discussion. I sincerely tried to respond directly to the question of "Why?" using facts and logic, not to express my personal opinion or make a proclamation (specifically, my words there should be read in a boring, monotone, factual voice; not as a fiery critique). Like Gareth, I am happy to retract my post from here and move it to a more appropriate location. Which is best: MDL-69042 or MDLSITE-7418? |
really, no need to explain, apologise, retract nor anything. Just, let's keep this clean and focused on the technical aspects that may arise. You know that I personally appreciate and love to you both, like to any other moodler around the world! And I'm happy with people actively sharing ideas, opinions, suggestions, criticism... all the time and (near, hahah) everywhere. You both are! 🧡 Mostly technical stuff, I'd say, because I consider that other "affairs" fall out from my role in this project, no matter I've, like an high % of people, an opinion, point of view, background, implication... about some/many of them. Like everybody else, I'd say. In any case, finito! Many thanks for your collaboration and see you around, enjoy the weekend! Ciao :-) |
Hi all,
today (30th Nov 2023), we have proceeded to rename the "master" branch of this repository to "main".
You can find more details about the migration @ https://tracker.moodle.org/browse/MDLSITE-7418
For some guidance about how to proceed with your clones you can follow the information that GitHub provides in the home page of the repo and, also, take a look to this (still draft!) document:
https://gist.github.com/stronk7/d007be57062ebef2dd6549010954a378
(you're welcome to help amending it with your experiences, feel free to comment there)
Once ready, the document will be moved to https://moodledev.io
Sorry for the trouble and ciao :-)
PS: This issue will be closed in a few weeks.
The text was updated successfully, but these errors were encountered: