Zum Hauptinhalt springen
tsecurity.de LIVE
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
•••
Sicherheitslücken (CVE)MCP Python SDK Flaw Exposes OAuth Credentials(30.09.2026 um 17:31 Uhr)
••••
IT Security Nachrichten40M McDonald's Records Exposed Through Customer Data Platform(30.09.2026 um 17:40 Uhr)
•
IT Security NachrichtenSemantics 21’s CCTV Review Tool Is Built For Footage That Cannot Wait(30.09.2026 um 17:17 Uhr)
•
IT Security NachrichtenIntegrating probabilistic programming in enterprise risk management(30.09.2026 um 17:44 Uhr)
••••
Sicherheitslücken (CVE)MCP Python SDK Flaw Exposes OAuth Credentials(30.09.2026 um 17:31 Uhr)
••••
IT Security Nachrichten40M McDonald's Records Exposed Through Customer Data Platform(30.09.2026 um 17:40 Uhr)
•
IT Security NachrichtenSemantics 21’s CCTV Review Tool Is Built For Footage That Cannot Wait(30.09.2026 um 17:17 Uhr)
•
IT Security NachrichtenIntegrating probabilistic programming in enterprise risk management(30.09.2026 um 17:44 Uhr)
•
Intelligence View
⚡ tsecurity.de Intelligence

Code of Conduct

The Linux kernel community operates a Code of Conduct based on the Contributor Covenant Code of Conduct with a Linux Kernel Contributor Covenant Code of Conduct Interpretation. Code of Conduct Committee The Linux kernel Code of Conduct…

0
↗ Quelle (kernel.org)
Reagiere als Erste:r — dein Feedback zählt!

The Linux kernel community operates a Code of Conduct based on the
Contributor Covenant Code of Conduct with a Linux Kernel Contributor Covenant Code of Conduct Interpretation.



Code of Conduct Committee


The Linux kernel Code of Conduct Committee is currently made up of the
following people:





Committee members can be reached all at once by writing to
<[email protected]>.




Committee Reports


We would like to thank the Linux kernel community members who have supported
the adoption of the Code of Conduct and who continue to uphold the professional
standards of our community. If you have any questions about these reports,
please write to <[email protected]>.



September 2023


Archival copy: https://lore.kernel.org/r/[email protected]


In the period of April 1, 2023 through September 30, 2023, the Code of
Conduct Committee received the following reports:




  • Unacceptable behavior or comments in email: 4




The result of the investigation:


  • Education and coaching clarifying the Code of Conduct conduct related to normal review and patch acceptance process: 3

  • Clarification on the Code of Conduct conduct related to maintainer rights and responsibility to reject code: 1




The reports were about the discussion during the patch review and decisions made in rejecting code and these actions are not viewed as violations of the Code of Conduct.


Please see the excerpt from the Responsibilities section in the Linux Kernel Contributor Covenant Code of Conduct Interpretation document:



setting expertise expectations, making decisions and rejecting unsuitable
contributions are not viewed as a violation of the Code of Conduct.



March 2023


Archival copy: https://lore.kernel.org/r/[email protected]


In the period of October 1, 2022 through March 31, 2023, the Code of
Conduct Committee received the following reports:




  • Unacceptable behavior or comments in email: 6




The result of the investigation:


  • Education and coaching clarifying the Code of Conduct conduct related to normal review and patch acceptance process: 1

  • Clarification on the Code of Conduct conduct related to maintainer rights and responsibility to reject code: 5




The reports were about the decisions made in rejecting code and these actions are not viewed as violations of the Code of Conduct.


Please see the excerpt from the Responsibilities section in the Linux Kernel Contributor Covenant Code of Conduct Interpretation document:



setting expertise expectations, making decisions and rejecting unsuitable
contributions are not viewed as a violation of the Code of Conduct.



September 2022


Archival copy: https://lore.kernel.org/r/[email protected]


In the period of April 1, 2022 through September 30, 2022, the Code of
Conduct Committee received the following reports:




  • Unacceptable behavior or comments in email: 1




The result of the investigation:


  • Resolved with a public apology from the violator with a commitment from them to abide by the Code of Conduct in the future.







March 2022


Archival copy: https://lore.kernel.org/r/[email protected]


In the period of October 1, 2021 through March 31, 2022, the Code of
Conduct Committee received the following reports:




  • Unacceptable behavior or comments in email: 2




The result of the investigation:


  • Education and coaching clarifying the Code of Conduct conduct related to normal review process: 2





September 2021


Archival copy: https://lore.kernel.org/r/[email protected]


In the period of May 1, 2021 through September 30, 2021, the Code of
Conduct Committee received the following reports:




  • Unacceptable behavior or comments in email: 1




The result of the investigation:


  • Education and coaching clarifying the Code of Conduct conduct related to normal review process: 1






April 2021


Archival copy: https://lore.kernel.org/r/[email protected]


In the period of November 1, 2020 through April 30, 2021 the Code of
Conduct Committee received the following reports:




  • Unacceptable behavior or comments in email (3rd party): 4




The result of the investigation:


  • Education and coaching: 1

  • Public response to call attention to the behavior and request correction with consequence of ban if behavior persists: 1

  • Public response to attention to the behavior and request correction: 1

  • Clarification on the Code of Conduct conduct related to maintainer rights and responsibility to reject code: 1






October 2020


Archival copy: https://lore.kernel.org/lkml/[email protected]/


In the period of January 1, 2020 through October 31, 2020 the Committee
received the following reports:




  • Unacceptable behavior or comments in email: 1

  • Unacceptable comments in github repo by non-community members: 1

  • Unacceptable comments toward a company: 1




The result of the investigation:


  • Education and coaching: 1

  • Locking of github repo for any comments: 1

  • Clarification that the Code of Conduct covers conduct related to individual developers only: 1






December 2019


Archival copy: https://lore.kernel.org/lkml/[email protected]/


In the period of December 1, 2019 through December 30, 2019 the Committee
received the following report:




  • Insulting behavior in email: 1



The result of the investigation:




  • Education and coaching: 1





August to November 2019


Archival copy: https://lore.kernel.org/lkml/[email protected]/


In the period of August 1, 2019 through November 31, 2019, the Committee
received no reports.




September 2018 to July 2019


Archival copy: https://lore.kernel.org/lkml/[email protected]/


In the period of September 15, 2018 through July 31, 2019, the Committee
received the following reports:




  • Inappropriate language in the kernel source: 1

  • Insulting behavior in email: 3



The result of the investigations:




  • Education and coaching: 4




Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Code of Conduct

Thematisch verwandte Begriffe: Code, Conduct · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-82307 | Improper neutralization of special elements used in an SQL command ('SQL…
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel • Rechts: nächster Artikel • unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

Zurück: vorheriger • Vor: nächster
↗ Original-Quelle
Social Reaktionen Deine Reaktion zählt
Einstufung & Relevanz-Poll 0 Stimmen
In sozialen Netzwerken teilen 1-Klick