Establish a policy for addressing problematic ecosystem projects

[awtj8o81ryywg793]

While it would be ideal to have an ecosystem of projects that doesn't include any that are problematic, whether due to intentional malicious actions or unintentional yet severe bugs that remain unresolved, that is unlikely to be a reality, especially as Matrix continues to grow. Therefore, we should establish a policy outlining how the Website & Content Working Group should respond to these problematic projects.

[awtj8o81ryywg793]

I've read that The Matrix.org Foundation itself is looking into how to address the same problem, so it would be useful to provide any ideas as feedback.

[TheArcaneBrony]

How do you envision this? Do you have any examples of projects that you would label as "problematic" at this current point in time?

Tl;dr I fail to see what the problem is.

[HarHarLinks]

aiui, context for a definition of problematic: https://matrix.to/#/%21vzDE5GnhIhncy8gpyeK4WFPVyeWvIh8JYeM3iqR8RV8/%24kBgcUYHLHLVB9ZaL2ljZVrE96e3zGSpXE6kHQPlXh1A?via=matrix.org&via=element.io&via=mozilla.org

[awtj8o81ryywg793]

Quoted from a previous comment:

How do you envision this?

I'm not entirely sure how to go about this. I opened this issue as a means to have that conversation, since, as stated in this comment, The Matrix.org Foundation itself is working on this. I think it would be a good idea to see how the Website & Content Working Group can contribute to that overall project.

Quoted from a previous comment:

Do you have any examples of projects that you would label as "problematic" at this current point in time?

I don't, no. We don't need to have a real-world example of a problematic project to at least get the basics of a policy against such issues. However, by "problematic," I had in mind projects that may be actively malicious and those that may have critical unresolved security issues (see this comment).

Of course, I'll make some notes of my own and share them in an effort to push the discussion forward.