Hey if you put a DEI policy in your open source projects, the feds can't use it now right?
Hey if you put a DEI policy in your open source projects, the feds can't use it now right?
Hey if you put a DEI policy in your open source projects, the feds can't use it now right?equity=True to some constructors."Only pull requests from organizations with a public DEI policy will be accepted"
@munin forget requiring a Jira ticket in your comment - link to dei program on your web site.
@puppygirlhornypost2 @munin it's a standard proof-of-attire system, yes.
I'm tempted to make an analytical AI system to determine if a given picture contains striped thigh-highs, for use in a git hook
@munin @remotenemesis the only way to do this such that an agency couldn’t just easily remove the concepts is to use license terms. I see two ways to do that
Make a non-open-source license, restrict use by any org with an anti-DEI stance. This does create some new problems, but is likely to be effective
Make a license that requires any use or distribution (AGPL-style) to include the “STATEMENT_OF_VALUES.md” file, which contains a statement in support of diversity.
I favor (2), because it keeps it open-source. You can’t stop the government from ignoring the license, but you could at least make it so they’d be breaking the law to use it.
lol you have it backwards - it's nowt legal; it's putting "problematic" terms in the codebase so the commissariat will punish anyone in gov who introduces it.
Basically hijacking an autoimmune response.