Dgar
and 1 other
boosted
Athavariel - for peace
and 1 other
boosted
@EUCommission OR join our #FOSS alternative called #Loops!
https://vido.social/invite/a_019c0565-43b2-7142-a249-c4193ce9565dFNNtC5E
We've preliminary found that TikTok is in breach of the DSA for its addictive design.
There are important indicators of compulsive use of the app that TikTok has disregarded in its risk assessment.
Key features of the addictive design:
🔹Infinite scroll
🔹Autoplay
🔹Push notifications
🔹Highly personalised recommender system
We consider that TikTok needs to change the basic design of its service.
TikTok can now exercise its right to examine and reply to the finding.
@EUCommission OR join our #FOSS alternative called #Loops!
https://vido.social/invite/a_019c0565-43b2-7142-a249-c4193ce9565dFNNtC5E
The Fulcrum 🏴☠️ 🛠️ ⛓️💥
and 8 others
boosted
Do any moots know someone who we might be able to consult about restructuring a mid-size FOSS project? Essentially to migrate from a BDFL model to a more flat-structured democratic organisation.
We are discussing how to restructure #postmarketOS so that it can continue to scale up and be a truly community-run project.
We have some idea of how co-ops like Igalia do this, but we have a lot of differences (like being largely volunteer run and having very different goals) which leave us with a lot of unknowns.
To give an example of the kind of structure we're thinking of (by no means final, there hasn't been any broad agreement on a new structure yet):
We have the relevant pieces in place to form an assembly (everyone listed on https://postmarketos.org/team/ ) which could then democratically form teams and delegate responsibilities to them (e.g. finance/budget, technical policy-making, maintainers for various OS components).
The assembly would then also be responsible for deciding on focus areas and long term goals for the project (e.g. improving reliability, building a production-ready immutable version of the distro)
We could then form working groups to enable cross-team collaboration to move towards our specific goals.
Currently we lack a lot of understanding of the potential implications of something like this, how we can ensure the project doesn't get hijacked, that we don't drift too far from our mission statement, etc etc...
If you have a background in sociology and/or relevant experience from other projects then I would love to reach out and be able to discuss this in more detail!
Pen
boosted
OK Team Fedi, we've now just got $2,797 left to raise in this year's Software Freedom Conservancy fundraiser!!
If you care about our awesome member projects, about helping newcomers get their start in #FOSS, or standing up for the #GPL and #copyleft, now is the time!
https://sfconservancy.org/sustainer/
Let's go for #softwarefreedom!!!
OK Team Fedi, we've now just got $2,797 left to raise in this year's Software Freedom Conservancy fundraiser!!
If you care about our awesome member projects, about helping newcomers get their start in #FOSS, or standing up for the #GPL and #copyleft, now is the time!
https://sfconservancy.org/sustainer/
Let's go for #softwarefreedom!!!
Do any moots know someone who we might be able to consult about restructuring a mid-size FOSS project? Essentially to migrate from a BDFL model to a more flat-structured democratic organisation.
We are discussing how to restructure #postmarketOS so that it can continue to scale up and be a truly community-run project.
We have some idea of how co-ops like Igalia do this, but we have a lot of differences (like being largely volunteer run and having very different goals) which leave us with a lot of unknowns.
To give an example of the kind of structure we're thinking of (by no means final, there hasn't been any broad agreement on a new structure yet):
We have the relevant pieces in place to form an assembly (everyone listed on https://postmarketos.org/team/ ) which could then democratically form teams and delegate responsibilities to them (e.g. finance/budget, technical policy-making, maintainers for various OS components).
The assembly would then also be responsible for deciding on focus areas and long term goals for the project (e.g. improving reliability, building a production-ready immutable version of the distro)
We could then form working groups to enable cross-team collaboration to move towards our specific goals.
Currently we lack a lot of understanding of the potential implications of something like this, how we can ensure the project doesn't get hijacked, that we don't drift too far from our mission statement, etc etc...
If you have a background in sociology and/or relevant experience from other projects then I would love to reach out and be able to discuss this in more detail!
Bob Monsour
boosted
How Eleventy Survived: Funding, Growth, and Open Source Reality, by @zachleat and @matthewejohnson.bsky.social (@fontawesome):
How Eleventy Survived: Funding, Growth, and Open Source Reality, by @zachleat and @matthewejohnson.bsky.social (@fontawesome):