Elektrine lite

← Feed

@luis_in_brief@social.coop

Post #2093489

2023-09-20 15:24 UTC

So who has a list of the *types* of human-governance systems in FOSS? Among others (and to help show the breadth of what I mean): - the obvious one: each project with >1 contributor is a governance system even if the governance is “don’t be a dick” - product management at GitHub, via the product features that constrain (govern) collaboration there - the license community (including drafting, interpretation, and enforcement/scanning) I assume someone has a list?

Replies (10)

  • @luis_in_brief@social.coop 2023-09-20 15:42

    This thought brought to you by some musings on Ostrom, polycentricity, and the underappreciated role of the IRL social network of open lawyers as a governance layer. cc @greggish@mastodon.cloud

    Open ##2445514

  • @ldodds@mastodon.me.uk 2023-09-20 15:47

    @luis_in_brief@social.coop I don't have a list, but it's an interesting question! If you split yr list into governance of the project vs governance of the infrastructure (creation, deployment, release, use), then you'd maybe add in: - package management and distribution - cloud/hosting services - security auditing ...to the latter. Also maybe interactions between major projects. E.g. Rails removing from TypeScript has implications for it as project in terms of its broader use?

    Open ##2445515

  • @luis_in_brief@social.coop I would ask @shauna@social.coop if such a list exists.

    Open ##2445516

  • @aeva@mastodon.gamedev.place 2023-09-20 16:03

    @luis_in_brief@social.coop "lonely singular contributor who can't find any interested users or other people to help" is pretty popular

    Open ##2445519

  • @FinchHaven@sfba.social 2023-09-20 16:20

    @luis_in_brief@social.coop [probably should know better, but...] "I assume someone has a list?" Thinking you've got three lists here 1) governance of conduct (read: moderation) on an instance where "don't be a dick" comes into play 2) the mechanics of code review via Issues, Pull requests, (and Discussions) that result in changes to source code 3) licensing: broadly, Public domain; Permissive; Copyleft; Noncommercial; Proprietary 3) alone would make a long list if you want distro/app names 2) would be a man page of instructions at the very least 1) would be the entire universe of "everybody has an opinion on *that* topic" which I have stepped away from entirely in recent weeks Too much noise there; too many people talking past one another Good luck in your quest(s)

    Open ##2445520

  • @B@urbanists.social 2023-09-20 16:37

    @luis_in_brief@social.coop perhaps @axz@hci.social ?

    Open ##2445521

  • @iw@troll.social 2023-09-20 18:50

    @luis_in_brief@social.coop I have never read "don't be a ****" in any governance documents except as in your case, when posted by a **** trying to call others a **** when they are the real ****. P.S. The Linux Foundation is hosting the EU OSS 2023 this week and has TONS of material on this and have already shared tons this week LIVE. May I suggest less time on Mastodon and more time in the real world paying attention?

    Open ##2445523

  • @mhoye@mastodon.social 2023-09-20 19:26

    @luis_in_brief@social.coop https://blog.mozilla.org/wp-content/uploads/2018/05/MZOTS_OS_Archetypes_report_ext_scr.pdf

    Open ##2445524

  • @pg@hci.social 2023-09-21 00:18

    @luis_in_brief@social.coop this book may be relevant? not sure if it has an exact list tho https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862

    Open ##2445528

  • @gaditb@icosahedron.website 2023-09-22 02:36

    @luis_in_brief@social.coop Another dimension of project governance is moderating (or just, being the loudest person in) the support mailing list/IRC channel/forum/Discord/Matrix channel/etc.

    Open ##2445530