Our Principles #
1. We commit to the principles that underpin software freedom. #
We believe all users of software should have the right to run, copy, distribute, study, change and improve the software they use on a day-to-day basis. We support this not just for practical, but also ideological reasons. It gives people both control and understanding over the technologies they routinely depend on and it also works to hold those who produce the software accountable to their users.
By extent we also oppose other roundabout ways companies try to infringe on user freedom: DRM schemes, JavaScript tracking, and repair-hostile hardware design.
2. We are serious about actually getting stuff done. #
There’s many in the FOSS (free and open-source software) space who prefer to focus on the hobbyist side of things. There’s nothing wrong with this, but as a group, we’re looking to direct our efforts with a goal in mind. We’re not just looking to ‘purify’ our own software stacks, we’re looking to make it as easy as possible for as many people as possible to cut their ties to the proprietary ecosystem.
We believe actions speak louder than words, and put less emphasis on policing terminology versus asking whether or not a proposed course of action will benefit us in the long run. We are willing to associate with and work with groups that may not align with us as there’s a reasonable common goal worth pooling our efforts towards.
3. We believe a culture of open, informed, and vigorous debate is necessary in order to sustain a healthy movement. #
The FOSS community has never been a monolith and neither has its opinions. In order to plan for the future, members need to be able to freely pick apart, challenge, defend, and reformulate various ideas pertaining to software design and how it functions with respect to society. As a result, we tend to take a relatively ‘big-tent’ approach.
It is to be expected we’ll be working with a variety of ideas, strategies, and people, and that we allow an appropriate amount of space for members and chapters to experiment.
4. We are a group that focuses on prioritizing ‘spadework’. #
It’s very tempting when starting up an initiative like this to start fundraising or plan out big advertising blitzes. But what’s even more important are the tasks that go beyond just plain advocacy: seeding communities, ironing out theories, supporting FOSS developers, and providing opportunities to train talent.
This work might be less flashy, but it’s the true lifeblood of any movement that’s serious about working towards long-term results. You can’t artificially force growth the way you can’t force a flower to bloom in any season. But what is in your control is the ‘spadework’: digging the holes, providing the water, and taking all the necessary steps to lay a stable foundation for growth. That way, when spring does come, you’re in good shape to take full advantage of the opportunities presented to you.
An active and focused minority can often accomplish a lot more than a passive majority: sufficiently creative and determined activists can often find ways to carry out these tasks without even having to rely on financial or institutional backing. We don’t need to court everyone into our group (although we’d love to have anyone), we just need to make sure the people we do bring in are sufficiently committed towards pulling the levers of change.
FAQ #
1. What even is ‘free-software’? #
‘Free-software’ (also called ’libre software’) isn’t just software that costs no money: it’s software that respects your freedom. It doesn’t restrict how you use it, it benefits from your tinkering, and it doesn’t try to harvest your data. Or more specifically, ‘free-software’ guarantees you the right to run, copy, distribute, study, and change software.
2. Why should I care about software freedom? #
Whether we’re talking about the destructive effects of social media algorithms, the rise of mass surviellance, or the controversies surrounding AI, we are seeing that as long as tech remains relevant to our world, so too will the issues in tech.
Being able to see the code helps promote transparency and hold software suppliers to account. Being able to study the code helps promote technological literacy among users. Being able to copy and distribute the code encourages competition and innovation. Being able to edit the code gives you more control over the tools you depend on on a day to day basis.
After all, you should control your computer – not the other way around.
3. Are you affiliated with any organization? #
There’s many organizations in the FOSS space (the FSF, the DFF, the OSI, etc.). Many of our members even have a history of working with some of these groups, but we are not officially affiliated with any of them. We are technically not even an organization: instead, we prefer to refer to ourselves as a ‘caucus’.
We don’t seek to replace or compete with any of these organizations, but rather instead work from below to bring new talent, new ideas, and new strategies into the fold. We believe by doing things this way, we can act as an effective pathway to aid members of the community towards helping the larger cause.
4. Can I join if I have only X experience? #
Absolutely! We have people from all backgrounds in our group and you never know when a certain skillset can come handy. Not to mention what we’re doing is social: the act of building community with other people interested in our cause is inherently valuable, whether or not we think we can get a “practical benefit” out of it.