You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of these incident categories have also happened with foundation-led projects too - not just individual/small maintainer led projects.
Is there any desire in the project to consider more project issues at foundation-hosted projects as well? I see some foundation project issues here, but the docs/tone really focuses on individual maintainers.
Separately: the context of some incidents actually start with corporations somehow abusing a FOSS project or maintainer. Even if the FOSS project's reaction might be remembered, the core issue really came from outside the project, not inside. Is that something you're interested in covering more? I see some issues like that are here, but again the docs seem to focus primarily on the maintainers causing an issue, not an outside party (that might get a reaction from a maintainer).
The text was updated successfully, but these errors were encountered:
If you have more examples where individuals, teams, or organizations / foundations had problems and stopped or changed the way they develop OSS feel free to add a merge request.
And I thought it was clear that the maintainer's reaction is often only a reaction on an external action (mostly from companies) - can you give a specific example where this can be misinterpreted?
Some of these incident categories have also happened with foundation-led projects too - not just individual/small maintainer led projects.
Is there any desire in the project to consider more project issues at foundation-hosted projects as well? I see some foundation project issues here, but the docs/tone really focuses on individual maintainers.
Separately: the context of some incidents actually start with corporations somehow abusing a FOSS project or maintainer. Even if the FOSS project's reaction might be remembered, the core issue really came from outside the project, not inside. Is that something you're interested in covering more? I see some issues like that are here, but again the docs seem to focus primarily on the maintainers causing an issue, not an outside party (that might get a reaction from a maintainer).
The text was updated successfully, but these errors were encountered: