Code of Conduct Updates - Please Read

[sylvia-leaf]

Code of Conduct Updates

Introduction

Please read these updates carefully.

You can find the latest version of the Code of Conduct here.

20 December 2025

Introducing Guidelines

The guidelines previously included in the SFE/SFe license have been moved to the Code of Conduct.

10 November 2025

Introducing Code of Conduct Update Announcements

Starting from this update, we will announce changes to the Code of Conduct here.

Examples of Allowed and Disallowed Behaviour

We've added examples of allowed and disallowed behaviour for some of the clauses.

Deprecation Now Permitted

It is now permitted to deprecate features that are both redundant and seldom used, at the discretion of the SFE Team. Complete removal of SFE features without a valid reason remains forbidden.

Sample Management Clarification

The Code of Conduct has been updated to clarify that the SFE Team manages the minimal number of samples required to provide reference implementations for the format.

[LoveBodhi]

Sample Management Clarification

I'm just want to collab with Sample Lib makers such as SP in Musical Artifacts, stgiga, and FreePats, instead of SFE...

[stgiga]

I should mention a few things:
My libre stuff is often inadvertent but welcome. For obvious reasons the other stuff won't be uploaded.

As for the AI stuff: Copilot horribly misses the mark so I wouldn't worry too much. To the anti-AI people out there, it's not so bad because AI vibecoding is currently as shoddy as all the dropshipped AI scam stuff you see on Meta-owned places.

Oh and some of my repos definitely aren't ace, but those bits won't go here either for obvious reasons.

Oh and Ruffle the Adobe Flash emulator plugged Flash's security holes, and Ruffle can run in browser, so security removals at least somewhat may not mean the end of a feature. Now as for what could be a causer of these: likely buffer overflows. Or stuff that shouldn't be executed as code being ran as code, but at least on non-Windows you can just set the NX bit via not doing the equivalent of chmod 777 in your code. It would take advanced scripting of the type of doing HarfBuzz WebAssembly table in the least-secure way possible to lead to anything truly fatal for security. It may as well be vandals who try to set us up the bait bomb, and that ain't pretty at all. We don't need another XZ exploit (even though it did make B3K more viable for some time, as part of your daily dose of beyond-BZip# tarballs) in something that shouldn't even be executable. Also if you spot some sort of hack going on, do everyone a favor and make sure to tell EXACTLY what you found so that we can take proper precautions, figure out how to get rid of it, and make everything safe again, and foil the scammers.

Oh and for whatever difference it makes, siliconpr0n has decaps of several SF2-capable Sound Blaster cards, not that anyone here likely can achieve anything with those. I mean, MAYBE China in a situation where they adjust voice count calculation and load from NAND, and use cards that are over 20yo (United States patent terms) which even includes SF2.04 cards like the X-Fis that can do it. I won't have the funds to do any of THAT ASIC commission stuff for a few more years, and it ain't exactly within scope, so you don't need to worry. Oh also sometimes the wording I use when writing stuff is either referential or something for the niche nerds out there. (Just to give you an idea, UnifontEX's giant README.md is a nerd paradise, but that's besides the point. /ref) But at least I'm pragmatic about it, so there is that. AKA: I have standards.

One other thing: IF I legally could, I'd go full public domain on all my work as a conscientious objector to IP. But that currently isn't possible. If I tried, well... Let's just say I'd have MUCH bigger issues to grapple with. /ref
Don't expect me to pollute this repo with anything I shouldn't, or anyone's CC0 stuff. The whole idea just reeks of a bad idea.

I think I've covered my response to this to address a few things of a

📟 Viewers provided extra information they think you should know.
nature, which I felt needed to be said. Hopefully I've covered everything, and decently so at that. Best Wishes from AFK!