# code of conduct

Published articles for code of conduct.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Microsoft drafts feel-good AI model guidelines and wants your input

DevFeed: [Microsoft drafts feel-good AI model guidelines and wants your input](<https://devfeed.tech/articles/microsoft-drafts-feel-good-ai-model-guidelines-and-wants-your-input-21625.md>)

Original publisher: [Read original article](<https://www.theregister.com/ai-and-ml/2026/09/15/microsoft-drafts-feel-good-ai-model-guidelines-and-wants-your-input/5296431>)

Author: Thomas Claburn

Published: 2026-09-15T00:15:29Z

Content type: news

Language: en

Sources: [www.theregister.com - Articles](<https://devfeed.tech/sources/www-theregister-com-articles.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [ai and ml](<https://devfeed.tech/topics/ai-and-ml.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-and-ml](<https://devfeed.tech/tags/ai-and-ml.md>), [ai-safety](<https://devfeed.tech/tags/ai-safety.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [code-of-conduct](<https://devfeed.tech/tags/code-of-conduct.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [model](<https://devfeed.tech/tags/model.md>)

### AI overview

Microsoft has drafted aspirational guidelines for AI model behavior and is seeking public input, while acknowledging that models may still get things wrong.

### Source excerpt

Redmond outlines 'aspirational' goals for model behavior, but gives itself a pass if it gets things wrong

## Safer Internet Day and Open Source Codes of Conduct

DevFeed: [Safer Internet Day and Open Source Codes of Conduct](<https://devfeed.tech/articles/safer-internet-day-and-open-source-codes-of-conduct-29049.md>)

Original publisher: [Read original article](<https://code.flickr.net/2022/02/14/safer-internet-day-and-open-source-codes-of-conduct/>)

Author: Sarah Graywood

Published: 2022-02-14T17:23:51Z

Content type: article

Language: en

Sources: [Flickr](<https://devfeed.tech/sources/flickr.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [code-of-conduct](<https://devfeed.tech/tags/code-of-conduct.md>), [community](<https://devfeed.tech/tags/community.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [developers](<https://devfeed.tech/tags/developers.md>), [github](<https://devfeed.tech/tags/github.md>), [internet](<https://devfeed.tech/tags/internet.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [repositories](<https://devfeed.tech/tags/repositories.md>)

### AI overview

Flickr describes adding a code of conduct to its most trafficked open-source repositories on GitHub as part of its Safer Internet Day efforts. The article explains how codes of conduct establish expectations for developer interactions and support safer, more inclusive communities.

### Source excerpt

To continue the work of making our spaces safer and more accessible to all, we have added a code of conduct to our most trafficked open source repositories on GitHub in celebration of Safer Internet Day! Continue reading ->

## Conference Conduct

DevFeed: [Conference Conduct](<https://devfeed.tech/articles/conference-conduct-21789.md>)

Original publisher: [Read original article](<http://blog.cleancoder.com/uncle-bob/2020/09/23/ConferenceConduct.html>)

Published: 2020-09-23T00:00:00Z

Content type: opinion

Language: en

Sources: [Robert C. Martin](<https://devfeed.tech/sources/robert-c-martin.md>), [The Clean Code Blog](<https://devfeed.tech/sources/the-clean-code-blog.md>)

Topics: [Software](<https://devfeed.tech/topics/software.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [code-of-conduct](<https://devfeed.tech/tags/code-of-conduct.md>), [conference](<https://devfeed.tech/tags/conference.md>), [conferences](<https://devfeed.tech/tags/conferences.md>), [identity](<https://devfeed.tech/tags/identity.md>), [speakers](<https://devfeed.tech/tags/speakers.md>)

### AI overview

The article argues that software conference codes of conduct should not be weaponized to exclude people. It calls for transparent adjudication processes that give accused attendees and speakers notice, an opportunity to defend themselves, and knowledge of their accusers' identities.

### Source excerpt

It was just a few years ago, at the height of the Me Too revelations, that codes of conduct began to prominently appear in Software Conferences. At the time I felt this was appropriate given the horror stories that had been circulating about sexual harassment and misbehavior at some of those conferences. I wrote a blog about it at the time. Since then I have seen the other side of the coin. Codes of conduct have been used as weapons to exclude people on the basis of their political opinions, or on the basis of their associations, or just because someone didn't like them. I have written blogs about this as well. (1), (2) As much as I think that codes of conduct are a good idea, we must not allow them to be weaponized. If we are going to set up rules with consequences, then we also need to set up the the due processes by which those rules and consequences are adjudicated. Otherwise the people who police the codes of conduct will be free of the due checks and balances that protect conference attendees and speakers from unfair and malicious actions. As we have seen, such malicious and unfair actions have become all too common. It seems to me that if a conference is going to publish a code of conduct, like the one below, they must also publish the process by which alleged violations will be adjudicated. That process must include provisions for the accused to be able to defend themselves against the allegation, and must also allow the accused to know the identity of the accuser(s). Otherwise all conference attendees and speakers will be exposed to malicious and falsified complaints with no recourse to defend themselves. The conference I was disinvited from is over. I was ejected because code of conduct complaints were registered against me by three relatively minor speakers in quick succession. I do not know if those speakers acted in concert. Nor am I certain of the identities of those speakers (though I have a good idea). What I do know is that three or four weeks befor

## The Disinvitation

DevFeed: [The Disinvitation](<https://devfeed.tech/articles/the-disinvitation-21788.md>)

Original publisher: [Read original article](<http://blog.cleancoder.com/uncle-bob/2020/09/12/TheDisinvitation.html>)

Published: 2020-09-12T00:00:00Z

Content type: opinion

Language: en

Sources: [Robert C. Martin](<https://devfeed.tech/sources/robert-c-martin.md>), [The Clean Code Blog](<https://devfeed.tech/sources/the-clean-code-blog.md>)

Topics: [Software](<https://devfeed.tech/topics/software.md>), [Website](<https://devfeed.tech/topics/website.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [code-of-conduct](<https://devfeed.tech/tags/code-of-conduct.md>), [community](<https://devfeed.tech/tags/community.md>), [conference](<https://devfeed.tech/tags/conference.md>), [covid](<https://devfeed.tech/tags/covid.md>), [presentation](<https://devfeed.tech/tags/presentation.md>), [speaking](<https://devfeed.tech/tags/speaking.md>)

### AI overview

The author describes being disinvited from a Chicago software conference shortly before it became virtual. Organizers cited concerns from Code of Conduct representatives about the author's political opinions, while some speakers reportedly refused to participate if the author spoke. The author argues that the organizers may have breached an agreement and that the other speakers may have committed tortious interference.

### Source excerpt

I have a friend, in the Chicago area, who calls me up two or three times a year to ask me to give a talk at a User Group, or a conference he's involved with, or something like that. If my schedule is free I always say yes. I don't charge anything because I enjoy supporting the Chicago software community, and it's never a bad thing to get my face out in front of new people. I am a consultant, after all, and giving pro-bono talks is one of the ways I promote myself. Anyway, he wrote to me last October (That's right, a full year ago!) and asked me to give a presentation at a Chicago conference this September 21st. I agreed, and he thanked me, and that was that. Then, in June, he wrote to tell me that the conference was going to be virtual due to Covid. I acknowledged and, once again, that was that. Last Wednesday, September 9th, twelve days before the conference, he called me on the phone and said: "This is going to be the most uncomfortable phone call I have ever made." He went on to say that the "Code of Conduct" people at the conference were concerened about some of my political opinions, and that some of the speakers of the conference refused to speak if I was going to speak. Like I said, this guy is a friend of mine, and I don't want to get him into any trouble, so I decided not to raise a fuss about it, and I promised him I would not mention his name or the name of the conference on line. He responded by telling me: I'm scared to death of these people. Over the last few days I've been mulling this situation over in my mind, and I've come to a few interesting conclusions. The conference organizers are in breach of contract. OK, we didn't have a formal written contract, but we had emails. And we also had the fact that, for the better part of a year, the conference website had my picture on it, and advertised me as a speaker. I conclude that the conference organizers derived substantial benefit from those pictures and from promising my virtual presence to their audi

## Announcing: Our Open Source Code of Conduct

DevFeed: [Announcing: Our Open Source Code of Conduct](<https://devfeed.tech/articles/announcing-our-open-source-code-of-conduct-15799.md>)

Original publisher: [Read original article](<https://developer.squareup.com/blog/our-open-source-code-of-conduct>)

Author: Square Engineering

Published: 2015-01-27T17:08:00Z

Content type: release

Language: en

Sources: [Square Corner Blog RSS Feed](<https://devfeed.tech/sources/square-corner-blog-rss-feed.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [code-of-conduct](<https://devfeed.tech/tags/code-of-conduct.md>), [community](<https://devfeed.tech/tags/community.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-software](<https://devfeed.tech/tags/open-source-software.md>)

### AI overview

Square announces the publication of its open source code of conduct, which sets expectations for participants and explains how to report unacceptable behavior. The company says the policy is intended to support a welcoming and inclusive open source community.

### Source excerpt

Our commitment to providing a welcoming and inspiring open source community