Skip to content
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

MAINTAINERS: Remove some people due to political correct #1040

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chenAN6
Copy link

@chenAN6 chenAN6 commented Oct 29, 2024

The final solution to end this conversation of this problem is to remove all contributors except linus, as he would be the most correct one, here is a decision matrix

                                                       Speed                Correct?             Positive Feedback             No future problem
Only remove Russia                                        8                     8                        0                            1
Only remove China                                         7                     8                        0                            1
Only remove US                                            7                     0                        0                            0
Remove everyone except linus                             10                    10                       10                           10

WINNER: Remove everyone except linus

image
image
image
图都是搬运的

@KernelPRBot
Copy link

Hi @chenAN6!

Thanks for your contribution to the Linux kernel!

Linux kernel development happens on mailing lists, rather than on GitHub - this GitHub repository is a read-only mirror that isn't used for accepting contributions. So that your change can become part of Linux, please email it to us as a patch.

Sending patches isn't quite as simple as sending a pull request, but fortunately it is a well documented process.

Here's what to do:

  • Format your contribution according to kernel requirements
  • Decide who to send your contribution to
  • Set up your system to send your contribution as an email
  • Send your contribution and wait for feedback

How do I format my contribution?

The Linux kernel community is notoriously picky about how contributions are formatted and sent. Fortunately, they have documented their expectations.

Firstly, all contributions need to be formatted as patches. A patch is a plain text document showing the change you want to make to the code, and documenting why it is a good idea.

You can create patches with git format-patch.

Secondly, patches need 'commit messages', which is the human-friendly documentation explaining what the change is and why it's necessary.

Thirdly, changes have some technical requirements. There is a Linux kernel coding style, and there are licensing requirements you need to comply with.

Both of these are documented in the Submitting Patches documentation that is part of the kernel.

Note that you will almost certainly have to modify your existing git commits to satisfy these requirements. Don't worry: there are many guides on the internet for doing this.

Where do I send my contribution?

The Linux kernel is composed of a number of subsystems. These subsystems are maintained by different people, and have different mailing lists where they discuss proposed changes.

If you don't already know what subsystem your change belongs to, the get_maintainer.pl script in the kernel source can help you.

get_maintainer.pl will take the patch or patches you created in the previous step, and tell you who is responsible for them, and what mailing lists are used. You can also take a look at the MAINTAINERS file by hand.

Make sure that your list of recipients includes a mailing list. If you can't find a more specific mailing list, then LKML - the Linux Kernel Mailing List - is the place to send your patches.

It's not usually necessary to subscribe to the mailing list before you send the patches, but if you're interested in kernel development, subscribing to a subsystem mailing list is a good idea. (At this point, you probably don't need to subscribe to LKML - it is a very high traffic list with about a thousand messages per day, which is often not useful for beginners.)

How do I send my contribution?

Use git send-email, which will ensure that your patches are formatted in the standard manner. In order to use git send-email, you'll need to configure git to use your SMTP email server.

For more information about using git send-email, look at the Git documentation or type git help send-email. There are a number of useful guides and tutorials about git send-email that can be found on the internet.

How do I get help if I'm stuck?

Firstly, don't get discouraged! There are an enormous number of resources on the internet, and many kernel developers who would like to see you succeed.

Many issues - especially about how to use certain tools - can be resolved by using your favourite internet search engine.

If you can't find an answer, there are a few places you can turn:

If you get really, really stuck, you could try the owners of this bot, @daxtens and @ajdlinux. Please be aware that we do have full-time jobs, so we are almost certainly the slowest way to get answers!

I sent my patch - now what?

You wait.

You can check that your email has been received by checking the mailing list archives for the mailing list you sent your patch to. Messages may not be received instantly, so be patient. Kernel developers are generally very busy people, so it may take a few weeks before your patch is looked at.

Then, you keep waiting. Three things may happen:

  • You might get a response to your email. Often these will be comments, which may require you to make changes to your patch, or explain why your way is the best way. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
  • Your patch might be merged into the subsystem tree. Code that becomes part of Linux isn't merged into the main repository straight away - it first goes into the subsystem tree, which is managed by the subsystem maintainer. It is then batched up with a number of other changes sent to Linus for inclusion. (This process is described in some detail in the kernel development process guide).
  • Your patch might be ignored completely. This happens sometimes - don't take it personally. Here's what to do:
    • Wait a bit more - patches often take several weeks to get a response; more if they were sent at a busy time.
    • Kernel developers often silently ignore patches that break the rules. Check for obvious violations of the Submitting Patches guidelines, the style guidelines, and any other documentation you can find about your subsystem. Check that you're sending your patch to the right place.
    • Try again later. When you resend it, don't add angry commentary, as that will get your patch ignored. It might also get you silently blacklisted.

Further information

Happy hacking!

This message was posted by a bot - if you have any questions or suggestions, please talk to my owners, @ajdlinux and @daxtens, or raise an issue at https://github.com/ajdlinux/KernelPRBot.

@chenAN6
Copy link
Author

chenAN6 commented Oct 29, 2024

image

  • Freedom of speech that support your idea = Freedom of speech
  • Freedom of speech that point out your mistake = Spam
  • Freedom of speech that "against" some of your opinion = Paid actor

@chenAN6
Copy link
Author

chenAN6 commented Oct 29, 2024

image

  • 支持你的想法的言论自由 = 言论自由
  • 指出你的错误的言论自由 = 垃圾邮件
  • “反对”你的某些观点的言论自由 = 付费演员
  • Freedom of speech that support your idea = Freedom of speech
  • Freedom of speech that point out your mistake = Spam
  • Freedom of speech that "against" some of your opinion = Paid actor

@izmyname
Copy link

Linus: GOOOOAAAAL!
Остальные: Ты ебнулся? Мы в In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and
expression, level of experience, education, socio-economic status, nationality играем.

@kolokolovg
Copy link

china's bro - who is guy on 1st picture?
srsly i dnt know

@dodoleon
Copy link

china's bro - who is guy on 1st picture? srsly i dnt know

https://cifu.fudan.edu.cn/a3/7b/c520a107387/page.htm

@izmyname
Copy link

I'm wondering now - whether Linus bringing up politics was due to him being an asshole, or just an attempt to change focus from Linux being indirectly controlled by the US gov to 'all Russians bad' hype.

@chunzha1
Copy link

FINAL SOLUTION

@Juoelenis
Copy link

No, dont remove anyone

@Caferino
Copy link

Amen. Those russian devs need to be protected from their government which is currently at war. Now that they cannot contribute temporarily until the conflict settles down, the government cannot force them to do things they don't want to or shouldn't be doing, under serious threats.

@izmyname
Copy link

izmyname commented Nov 1, 2024

Amen. Those russian devs need to be protected from their government which is currently at war. Now that they cannot contribute temporarily until the conflict settles down, the government cannot force them to do things they don't want to or shouldn't be doing, under serious threats.

"For the sake of protection" is a common excuse for enforcing restrictions. We may, as well, remove Linus himself, since he is a US citizen and the US government can force him to do something politically motivated, like removing maintainers from specific countries... oh, wait.

@Caferino
Copy link

Caferino commented Nov 1, 2024

"For the sake of protection" is a common excuse for enforcing restrictions. We may, as well, remove Linus himself, since he is a US citizen and the US government can force him to do something politically motivated, like removing maintainers from specific countries... oh, wait.

And so is "we should be free to do whatever we want" a common excuse for bad actors to abuse and use to cause irreversible harm. You're now trying to remove the creator and owner of the program itself based on assumptions that he himself has proven, over the past decades, to be wrong. Removing maintainers TEMPORARILY while their countries are at war is the most perfect decision that could've ever be taken in regards to cybersecurity. In war, governments play dirtier than ever, they ignore rules, commit massive crimes. Preventing further damage and protecting people will always be better than being sorry. Free Ukraine and Free Palestine already, innocent citizens from both sides, including the perpetrator and the victim, don't deserve what they're going through at all.

And this restriction by itself is not a big deal. Those maintainers can still download the code and do with it whatever they want. It is highly likely temporal as well, while their conflicts settle down and so on. Your comment comes across as malicious and deliberate, as if you wanted Linux to be potentially harmed for no good reason. It feels like you want human errors to happen more frequently, especially during these times of high and obvious turmoil

@izmyname
Copy link

izmyname commented Nov 2, 2024

"For the sake of protection" is a common excuse for enforcing restrictions. We may, as well, remove Linus himself, since he is a US citizen and the US government can force him to do something politically motivated, like removing maintainers from specific countries... oh, wait.

And so is "we should be free to do whatever we want" a common excuse for bad actors to abuse and use to cause irreversible harm. You're now trying to remove the creator and owner of the program itself based on assumptions that he himself has proven, over the past decades, to be wrong. Removing maintainers TEMPORARILY while their countries are at war is the most perfect decision that could've ever be taken in regards to cybersecurity. In war, governments play dirtier than ever, they ignore rules, commit massive crimes. Preventing further damage and protecting people will always be better than being sorry. Free Ukraine and Free Palestine already, innocent citizens from both sides, including the perpetrator and the victim, don't deserve what they're going through at all.

And this restriction by itself is not a big deal. Those maintainers can still download the code and do with it whatever they want. It is highly likely temporal as well, while their conflicts settle down and so on. Your comment comes across as malicious and deliberate, as if you wanted Linux to be potentially harmed for no good reason. It feels like you want human errors to happen more frequently, especially during these times of high and obvious turmoil

And now, you're attacking me assuming, I'm a 'bad actor'. Great.

Well then, why not remove maintainers from Israel, Ukraine, Palestine and other countries at war, as well? Can't they abuse kernel, as well? And what about the US, then? The US gov is well known for their desire to control everything, everywhere. Also, it's very naive to link malicious actions with the code to actual wars on fields. The global 'war' never ends, as intelligence agencies try to use any means to spy on hostile countries (and their own citizens, as well), so the only option is to become extremely paranoid about any code and remove anyone, who - in theory - can push some malicious code to the project, i.e. literally every single person.

Also, nothing is more constant, than 'temporary' events.

P.S And don't forget Torvalds response to removal of the Russian maintainers. He brought it upon himself.

@izmyname
Copy link

izmyname commented Nov 2, 2024

Also

Removing maintainers TEMPORARILY while their countries are at war is the most perfect decision that could've ever be taken in regards to cybersecurity

No. In case of Russia, it plays exactly in favour of official Russian narrative 'all westerners are Russophobes, so even if you don't support the war - you have no other choice', thus diving the community and breeding politically motivated hostility. And the word 'temporarily' doesn't help the situation, as I said above.

@Justjustifyjudge
Copy link

china's bro - who is guy on 1st picture? srsly i dnt know

He's a man known as VV(weiwei in Chinese), an very interesting political commentator on China TV shows. Some of his comment is humorous, and some are that "humorous". And young Chinese, like him or not, love to use his "quotes" and TV slices as emoticon.

I remembered that He used to be the interpreter of 邓小平(Deng Xiaoping), and Deng was the leader of China country.

@Vec9527
Copy link

Vec9527 commented Nov 5, 2024

china's bro - who is guy on 1st picture? srsly i dnt know

A puppet for the government, spouting nonsense to deceive the public.

@chenAN6
Copy link
Author

chenAN6 commented Nov 17, 2024

china's bro - who is guy on 1st picture? srsly i dnt know

A puppet for the government, spouting nonsense to deceive the public.

This is the best joke I've heard today, a meme = puppet for the government🤣🤣🤣

https://youtu.be/XuZSDJFnZs8?t=25

Copy link

@mysterion mysterion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please add more details on the changes

@lap-does-things
Copy link

goida, bratya

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.