Introduction

Released Oct 13th, 2025

Staff Changes and Organizational Response

On October 8th, 2025, we, All Things Linux Management, made the difficult decision to terminate five members of our staff team (Amilie, Base, Exulan, Miyu, and Ryna) from their positions, giving them the option to resign from the team if they wished to do so. We aim to provide transparency with this statement about the circumstances leading to these decisions and to address the claims made by the previously mentioned individuals.

The following is a joint statement from All Things Linux management: Kaizen (Founder and Administrator), Scott (Director of Systems and Administrator), FarCotton (Administrator), Hunter (Assistant Administrator), and Zoe/Atmois (Assistant Administrator and Associate Director of Systems) with supplementary statements from Ty (Former Administrator and Director of Moderation), owuawoo (Former Assistant Administrator) and “Tess” (Former Administrator).

This situation revealed gaps in our organizational processes and practices. From this, we aim to improve and uphold our community values, as we made mistakes. However, we hope to improve from them. We hope to grow and learn from our mistakes and implement concrete plans to move forward, acknowledging every concern brought up in good faith. In the aim of transparency, there is a full export attached to this document, we hope you will take everything into consideration and continue to support us as you all have over the past two years.

Our Commitments to Improve

Moving forward, we are committed to resolve every concern brought up by the group and implement improvements to grow not only as a team but as a community. Below, we outline our commitments to improve with concrete examples and goals to spread our values with the FOSS and Linux community to build a better environment for all.

We want to improve and grow, but we cannot do it without your support. If you ever have a question or want to suggest a change or raise a concern please reach out to us, we are only here because of our community, it is core to us. Your feedback and voices are valued and we hope to have you here with us for many years to come.

To Our Community:

• Continued focus on providing a range of Linux resources and support through both support channels and our wiki
• Maintaining an inclusive, welcoming environment for users of all backgrounds and ability levels
• Regular community engagement with improved feedback implementation

To Our Team:

• Creating a positive, collaborative volunteer/work environment for both users and volunteers
• Providing clear advancement opportunities and recognition for our volunteers hard work
• Implementing fair and transparent management practices to ensure everyone has a voice that is heard

To Transparency:

• Implementing regular public reporting on organizational activities and finances through roadmaps and ledgers
• Open communication about challenges and improvements we face to get deeper community involvement in projects
• Accountability measures for leadership performance to improve our own actions and respond to concerns faster

Immediate Actions (Next 30 Days)

• Transparency and Communication Improvements: Implementation of public roadmap and centralisation of project tracking to improve transparency
• Director of Moderation: Appointing a DoM to improve onboardings and help lead the moderation team in the right direction

Short-term Actions (Next 90 Days)

• Improvements to Feedback Response: Strengthen existing communication channels to raise concerns and share feedback to allow better growth and development as a community and for our projects

Long-term Commitments (Next 6-12 Months)

• Community Engagement: Improve suggestion and feedback implementation with accountability of changes. Public open office hours with Q&A opportunities with the team to learn more about what’s going on

Background

In early October 2025, we became aware that several staff members had formed a private communication group to discuss organizational concerns within All Things Linux. While we initially viewed this as a legitimate avenue for constructive feedback, the situation escalated beyond professional discourse into activities that posed risks to our organization and community fueling an echo chamber of harmful ideas and discussion.

As the chat export demonstrates, the members of the group spread false accusations regarding several members of the community. This unfairly smeared people's integrity and goodwill, harming not just themselves but everyone around them. The individuals who claimed to try to help the community by raising awareness to problems went and tried to undermine everything All Things Linux stands for. We systematically disprove their claims throughout the rest of this document with all messages from the original group chat being available in the provided chat export.

This document provides the full context for those who received incomplete information. We hope that this shows our commitment to transparency and improvement and allows us to grow as a team and organisation. Whilst we regret the circumstances that led to this, we are focused on rebuilding trust and continuing to grow and build the community.

What Happened?

Initial Constructive Intent

The private group was initially formed on October 4, 2025, with stated intentions to "discuss the possibility of sending a joint statement on our grievances with the team." Whilst we understand not all feedback can be communicated directly, we try to build a team and an environment in which anyone can raise their voice of any concerns they might have, which we aim to strengthen further in light of this event.

With that being said, we must make it clear that they were well within their rights to make such a group chat and that we would never discourage constructive criticism or venting. Unfortunately, a line was crossed forcing us to take action to protect the community and the projects we run.

Escalation to Malicious Activity

Over the course of a week, the group had discussed several valid concerns - and these concerns have been noted, but all good faith was lost when honest concerns grew into clear malicious intent.

From our investigation, it revealed that the group's activities escalated to include the following:

1. Sharing of Confidential Information

Sensitive details about former and current staff members, including personal information, internal organizational matters and internal private communications, were disclosed inappropriately. This information was then further maliciously shared throughout the community defaming several current and former members of the staff and community. We understand the importance of transparency but sharing personal information and certain internal information is unacceptable.

Example messages from the chat but not limited to:

2. Unsubstantiated Claims about Individuals and the Organization

The members of the group made false assumptions about preceding circumstances that they had no involvement or clear knowledge of spreading lies without once asking for clarification or raising any concerns to anyone in the team. This included insulting, spreading lies and rumors as well as skewing the truth in favor of their own beliefs calling the team “a cult” despite their lack of direct involvement with the areas they discussed. This is unacceptable behavior as we build everything on trust and transparency and this undermines it.

All major claims have been disproven individually within the Allegations tab found on the left hand side of this document.

Some claims and criticisms remain unaddressed because they are highly subjective and require deeper reflection and internal review. We have tried to respond to the most pressing claims that could be factually rebutted. If there are any claims and criticisms that you feel need to be addressed and have concern of, you are free to send your comments to the channels listed at the end of this document.

3. Threats and Attacks Against Individuals and the Organization

Several plans and ideas were raised with the goal of “radical” change. The individuals never once talked to anyone about their concerns outside of this channel nor tried to propose any positive changes. Discussions included proposals to file reports with external authorities, coordinate organized departures of staff members, spreading defamatory statements throughout the whole community and discussing how they could potentially overthrow the whole organization and dissolve the non-profit just because they did not agree with the future goals and ongoing active effort from the whole team. These discussions occurred without any attempt to talk to management or the team as a whole, not allowing for any improvements to be made.

Example messages from the chat but not limited to:

4. Self-Aware Wrongdoing

Multiple participants acknowledged their actions were "horrible ideas" and being a “huge risk” if their communications were shared. Despite recognizing harm, group members escalated activities continuously. They intentionally tried to hide and obscure their activities and identities multiple times knowingly and admitting so. Concerns of it being an “echo chamber” were raised multiple times in the group chat but dismissed.

Example messages from the chat but not limited to:

Conclusion

While we regret that staff changes that were necessary, we believe these decisions were essential to maintain organizational integrity and trust. We do not take such actions lightly and remain committed to learning from this experience to improve and grow not only as individuals but as a community.

We acknowledge that some concerns raised were legitimate and are taking concrete steps to address them with accountability for the progress made. However, we cannot tolerate activities that threaten the security of our organization or the privacy of our community members.

All Things Linux will continue to serve the Linux and FOSS community with dedication, transparency, and integrity. We thank our supporters for their patience and understanding as we implement these improvements.

Contact and Feedback

We welcome constructive feedback and questions through our official channels:

Email: admin@allthingslinux.org

Discord: https://discord.gg/linux

• To create a ticket, use /ticket within the server.

• To submit a suggestion, visit the #suggestions channel.

We are committed to addressing legitimate concerns and maintaining open dialogue with our community.

With love and gratitude,

Logan Honeycutt   or as you all know, Kaizen

Founder - All Things Linux, 501(c)(3)

logan@allthingslinux.org

Timeline of Events

Timeline of Events

Chat Export

Chat Export

When an organization like ATL faces tough times, as has happened this week, there are a lot of ways people might respond. Some handle it well, others not so much. Some react selfishly, some selflessly. Whether it’s going silent, blaming others, spinning the story, or only sharing select details, there’s always another choice: to take responsibility, move forward, and be honest.

We’re sharing the group chat export related to the recent accusations below because we believe in transparency and integrity. We aren’t hiding anything, and we’re not afraid to own up to our mistakes. We have also attached a document produced by the group chat with their collective views for further transparency.

One of ATL’s core principles is actually summed up in a single word: Kaizen.

Kaizen isn’t just our founder’s name - it also stands for continuous improvement.

改善

Direct Messages - Fermat's last theorem deniers [1424173086437277837].html

An Open Letter to Administration - Riseup Pad Doc

It is of great importance that any content found within this export, should remain away from any attempt of misuse, retaliation, bias moving forward. Please do not threaten or harm the individuals involved; we have all made mistakes and we want to give them the opportunity to improve and grow. We are taking all their good faith feedback onboard and implementing real actions to ensure we can grow from this.

Allegations

Claim - Ty blaming

Claim - Kaizen blamed Ty for a Tux Games mistake

The truth:

These accusations are 100% false and Ty provided a statement below disproving them with a full explanation of the events that occurred during the Tux Games below.

A formal statement from Ty, himself:

Hello ATL. This is Ty. Your beloved lord and savior. Godfather of the community and ex-admin. Me, Kaizen, and Scott began ATL many years ago with shared goals of building a proper community for Linux enthusiasts. It has come to my attention that some misinformation has been spread. When the Tux Games were running last year, we collected scores and tallied them in a channel we had created for the event. Kaizen mistakenly deleted the channel before we had finished tallying points. This really upset me due to the countless hours I had spent working on it. I was also in a negative headspace at this time and was at the lowest point in my mental health. I was self harming and suicidal. Due to these circumstances in my life I lashed out. Me and Kaizen got into the worst argument we have ever had. During this argument I do not remember exactly what was said. We both said some nasty things, but I was definitely nastier. Tensions had been rising between us for a while. I believe my mental instability was a massive cause of this. By the end of the argument, Kaizen apologized for deleting the channel and took full responsibility for the fuck up. In reality it was such a small argument in the grand scheme of things that was blown way out of proportion. It ended with me declaring that I was no longer mentally fit to admin the community and I made my leave. I hold no grudge against Kaizen and to this day we are great friends who talk on a regular basis. I have nothing but the utmost respect for the way she has built what I believe to be the best Linux community on the internet. I do regret the way things ended, but I do not blame them on Kaizen or any member of the staff. My departure from the team was a decision based on my own mental health and instability. I had reached a point where I was taking things too seriously and lashing out at members of the team in situations where it was not needed. I am proud of the work I have done for ATL, and I am proud of the way it has moved forwards without me. I still see the ways I contributed helping further progress and I am so proud of each and every person who has stood up to the table of maintaining the place that I love so much. I can say in the truest corner of my heart that Kaizen is the best community leader I have ever met. Her tenacity, integrity, and compassion are the reason this community is the size that it is. I am so sorry to hear bad actors are spreading such vile information on such an integral member in the success of ATL. ATL to the moon. I love you all and I hope this blows over without causing more harm. Emotions can run rampant when drama occurs and the continuous game of telephone can lead to piles of misinformation. Some of you may not know me, but those who do remember that my advice was always taken as strong. My advice, let the wind blow over, let the storm calm, give everyone time to grieve and process this complex situation. When shit hits the fan and mods turn against each other it can feel as though the whole world is ending. It is not. All Things Linux is here to stay and is in good hands. Try to extract the meaningful messages and use this as an opportunity to grow. Everyone can learn from the events that occurred. When you have complaints, echo chambering them in side-conversations does not help. Bringing them up to the team in a formal, professional way which is not led by emotion will truly be the best way for everyone to improve their abilities to foster the community that I love so much. ❤ Scott is really cool btw and you can always hit him up for advice. He is good at confidentiality and is there to help.

Claim - Tess scandal

Claim - Kaizen x Tess Dating Scandal

The truth:

At no point was there a relationship between Kaizen and “Tess” or any deeper complicit conspiracy-like concerns.

From the messages in the group chat there is a clear lack of knowledge of the events. The individuals had no understanding of the timeline of events and made false defamatory assumptions of what had happened based on their limited knowledge of the events also including false claims that Aristocat from the Debian community had been involved in any of the following events.

A statement from “Tess” has been provided below to provide further transparency on the timeline and course of events.

A formal statement from the real “Tess”, themself:

Statement from “Tess,” or at least the person behind who I created and pretended to be.

I have been absent from the ATL community for many months, and I recently learned that the situation surrounding my past actions has resurfaced today, accompanied by new and uninformed accusations from members (former moderators) who had little to no involvement in the “drama” at the time. These individuals lack the context and information necessary to understand everything that happened.

For nearly a year, I engaged in deceitful actions. Misrepresenting myself to those around me, including Kaizen. I fully acknowledge that my actions were wrong and have caused much distress to some, particularly Kaizen, who was completely unaware of my true identity and intentions during this time. Kaizen was a victim, just like anyone else who was misled and lied to.

When my lies were first exposed, it came through a fabricated email sent from one of my sockpuppet accounts, directed solely to Kaizen, 'exposing' Tess to be another made-up persona. Almost nothing in that email is true; I was merely shifting my lies. Naturally, Kaizen forwarded this email to the admins and senior team for transparency.

I made an announcement in ATL about needing personal time and leaving the server to halt my communication with all its members, except for Kaizen; which was my initial intention. During this time, Kaizen and I continued to talk; she believed my new lies and unknowingly informed other senior staff about what she perceived as my “real” identity. Throughout this entire period, no one at ATL, including Kaizen, was aware of who I truly was.

This went on for weeks until she noticed inconsistencies and began to investigate, ultimately leading to my true dox, after which again she informed ATL’s core management about what had happened.

To address some of these completely new accusations (after nearly 10 months), I first want to categorically state that any claims suggesting there was a romantic relationship between Kaizen and myself are entirely baseless and untrue. Any form of ‘flirtatious’ behavior happened many weeks or months after I left ATL, and we had never talked about dating or entering a romantic relationship. It simply did not happen. You will also find that many of the accusations regarding a 'breach of trust' from Kaizen are rooted in this baseless foundation. As stated before, Kaizen has never knowingly deceived or lied to the moderation team about my situation.

Secondly, there seems to be some confusion with my crossover in the Debian Community server at the time. Just to clarify, Aristocat was not aware of my real identity even many months after the ATL admin team had already found out. So needless to say that he did not “make Kaizen aware” of any sort of deceit or malintent from me. He simply didn’t know, and wasn’t involved throughout any of this.

Claim - Paid outsourcing

Claim - Misuse of donations for payment of admin assistant

The truth:

Here we present another case of information that had been completely skewed in bad faith.

The referenced "third-world payroll" claim relates to a former assistant admin who was compensated from Kaizen’s personal funds out of their own generosity, not organizational donations or funds.

owuawoo, was a friend of Kaizen’s outside of ATL going back years prior through Kaizen’s previous freelance work. On September 17th, 2024, owuawoo contacted Kaizen personally seeking help regarding employment to afford room and boarding during medical school.

Kaizen agreed to help them in exchange for her providing support around the server for various one off secretary/admin assistant-like tasks. owuawoo was the first admin assistant and mostly came to existence due to a very busy schedule on Kaizen’s part while the server was growing at a rapid pace.

A formal statement from owuawoo:

Hello everyone,

This is owuawoo, former admin assistant on ATL. I am issuing this statement in light of recent discussions and allegations involving Kaizen.

I would like to clarify that while I was compensated for work related to ATL, the payments I received were not sourced from ATL’s funding or donations. Rather, they were paid directly from Kaizen’s personal finances.

Kaizen and I have known each other for a long time and I regard her as a trustworthy friend. At a time when I was facing significant personal and financial difficulties, I reached out to her for help and asked if she knew of any job opportunities. In response, Kaizen kindly offered me a position under ATL, functioning in a role similar to that of a personal virtual assistant.

To be clear, Kaizen did not hire me to work on ATL but rather to help improve her own quality of life, by assisting with reminders, to-do lists, and helping her keep track of important tasks and deadlines regarding ATL.

Although I acknowledge that I did not consistently fulfill the responsibilities expected of me in that role, Kaizen continued to support me financially, again, from her own personal funds, for nearly a year. I am deeply grateful for the generosity, patience, and kindness she extended to me during that challenging period.

Additionally, I want to address the false and harmful claims regarding Kaizen and me "e-dating" or talking on WhatsApp. These allegations are entirely baseless and 100% false. Kaizen and I have only ever communicated through Discord, and our relationship has always been strictly platonic.

I hope this statement provides clarity on the matter and highlights Kaizen’s goodwill and personal commitment to ATL.

Respectfully,
Owuawoo

Claim - Kaizen pocketing funds

Claim - Kaizen pocketing funds and poor spending

The truth:

In the following messages above, it is claimed that Kaizen has been “pocketing” donations for personal gain/profit. Later on, the group does seem to come to senses somewhat about the seriousness of these allegations. All donations to All Things Linux go immediately to a bank account which is registered in the name of All Things Linux with transactions monitored and only used for the direct expenditures of All Things Linux. Kaizen has never once and never will use a dime of donor funding for personal gain.

While we do take ownership and accountability for not staying on top of transparency regarding financial activity for the last year, claims like these are nothing more than shallow attacks on character.

Starting by EOY/2026Q1, quarterly transparency reports will be provided publicly to ensure there is never any doubt regarding ATL financials moving forward. We aim to supplement this by a live ledger of financial transactions by the organization for active transparency and accountability of everything we do with your generous donations.

As a show of full transparency, all financial statements between 2024Q4 and 2025Q4 as of the 10th of October 2025, have been exported and are viewable and downloadable here:

Checking - 1186_09-20-2024_10-15-2025

The second point to be cleared is the following statement by ILOVECANADA (aka Base).

• “Where do you think all the donations are going? To our 20 different overpriced VPSs?”

This claim is entirely false and over dramatic. As of the 12th of October 2025, ATL has never had more than 10 VPS’s at once. For the longest time, we only had one dedicated server and 3 VPS each with specialist purposes. After the recent DDoS attacks in August 2025, we decided it was best to rebuild our infrastructure with a focus on separation of concerns and isolation of each individual group of services to maximise integrity, availability and reliability with an entirely new approach to security, networking and administration. You can learn more about our infrastructure changes on our blog post here.

For further transparency, all VPS’s are rented from Hetzner Cloud and nearly all VPS are at the minimum or second minimum tiered plan in terms of billing and are strictly only scaled to have the resources they need to minimise the cost per month. As it currently stands we have 10 machines, with one in the process of being deprecated, they are listed below with a short summary of its purpose. As of the 12th of October 2025, we have the following machines, and as per the financial statements above it costs $154.44 a month with the “mothership” being the largest expense. Once we deprecate the “mothership” we expect expenses to drop to roughly $90 a month.

1. Dedicated VPS (aka “Mothership”), this server is in the process of being deprecated by EOY. It only hosts mail.atl.tools and is used for high traffic operations with our ISO archive project.
2. atl-dev-tux, this is a low resource VPS in the ashburn area solely running our self-hosted in house discord bot “Tux”. It is the only server in that region to improve latency to Discord’s API.
3. atl-network-bastion, this is another low resource VPS which serves as a secure gateway for our SSH access to our machines, this was a part of our DDoS response to ensure maximum availability.
4. atl-tools, this machine hosts our set of self-hosted tools from atl.tools, excluding mail. We hope to expand the offered services on this machine in the coming months and we welcome suggestions.
5. atl-dev, this machine hosts some of our inhouse projects such as our stats backend for stats.atl.dev and our eventual goal is to use it to provide a shared resource for hosting community run projects.
6. atl-services, this machine hosts essential infrastructure such as are in progress metrics stack as well as other discord bots such as TuxGPT and our personal shortlink system atl.sh
7. atl-chat, this machine is being used to host our IRC and XMPP bridges and servers which are in active development, you can see more progress on GitHub: XMPP & IRC
8. atl-wiki, this machine hosts our wiki, atl.wiki, along with all the supplementary services such as Valkey, its Discord bot and OAUTH backend.
9. atl-wiki-db, to separate concerns and maximise availability and integrity the wiki’s database is run on a separate machine, this machine is low resource due to its minimal overhead.
10. atl-sandbox, a low resource VPS which is used as a testing environment for all our projects before we bring them live.

We hope in the future we can share more about our infrastructure to the community to improve our transparency behind it. We always try our best to minimise expenses but in our aims of ensuring the maximum integrity and availability of our resources

Claim - Tux slander

Claim - Tux slander and personal jabs

The truth:

A Wakatime report of Kaizen’s personal contributions and activity to the Tux repo can be found here:

report-2023-2025-tux-55743535-48ee-40eb-b4fa-feb19d903b16.pdf

How Wakatime works:

WakaTime plugins track development time based on actual keyboard activity and file editing—not idle time or time spent with the editor open. The system operates as follows:

• Active Coding Detection: Plugins only send "heartbeats" when actively typing, editing files, or moving cursor during file changes
• Automatic Timeout: Tracking automatically stops after keystroke timeout period (5 minutes default for this account) of no activity.
• No Idle Time: Reading documentation, leaving editor open, or being away from keyboard generates ZERO tracked time.
• File Change Based: Each heartbeat represents actual file modification, cursor movement in changed files, or active editing.
• Precision: Accurate to microsecond level based on actual keyboard and editor events.

Source: https://wakatime.com/faq

WakaTime data provides irrefutable, mathematically certain proof of dedicated human led development clearly unrealistic with AI generation claims. The 649+ hours of tracked active coding time represents real human work that cannot be faked, inflated, or generated artificially.

Repository data conclusively disproves AI generation claims through documented evidence of multi contributor collaboration, detailed code review processes, complex architectural decisions, and sustained development effort over 23 months. When Tux was started, agentic AI was not even a thing yet let alone quality auto completion plugins.

Contributor statistics for Tux can be found showing a wide range of involvement across 40+ people:

• https://github.com/allthingslinux/tux/graphs/contributors

Additional insights such as commit activity and code frequency for the last year can be found here:

• https://github.com/allthingslinux/tux/pulse

Clarification on AI usage

With all of the above being said, by no means is this a declaration of not using AI throughout the development of Tux. As many of you may know and have your own opinions around, AI usage is an incredibly controversial topic lately. Whether you support or do not support it, you are free to hold such opinions; that is the beauty of free speech and individuality as a human.

AI is a tool, and with all tools, it matters how you use them. We will not get into the nuances or debate around this within the scope of this document but it is undeniable that AI can be used positively and productively.

Example scenarios include:

• Strategic decision making around architecture design based on proven patterns and models
• Writing unit tests and brainstorming end to end professionalism
• Auditing of codebase for edge and race conditions
• Docstring and comment generation
• Repetitive refactoring and tedious changes
• Fixing linter/formatter errors
• Auditing of codebase by direct reference to library source code and docs

To simply dismiss the activities above as mindless “vibe coding” would not only discredit our work and those involved, but also disrespect the time spent ensuring we have a quality project we can be proud of.

Direct doubt towards skill and credibility

What brings this all together unfortunately, is not only was there accusation around the project, but personal jabs to those involved.

Kaizen has nearly 10 years of experience professionally working with numerous companies, brands, startups, and influencers. Additionally, Kaizen has taken on numerous consulting and freelance roles, attended a rigorous 1000+ hour full stack software development bootcamp, and spent 8 years working within the music and digital marketing/social media industry.

When personal jabs are thrown for the sake of self desire, irony shows itself through hurting the credibility of those who speak such jabs.

Claim - CoC/Handbook slander

Claim - CoC/Handbook slander

The Truth:

A claim was made in which one of the group members said ”I’m 90% certain it [the Code of Conduct] was made [largely by] using AI”.

This is categorically false. Whilst some AI was used to audit weaker areas of the document and readability at later stages, the vast majority of the document was written and structured by hand.

The Code of Conduct, initially referred to as the Constitution, started being formed merely 4 days after the creation of the server in November 2023. At this point, generative AI had not yet been routinely popularised to the extent of today.

Attached below are various links evidencing the hard work that was contributed by individual members, the staff team and so on. This includes early forum posts, which detail initial thoughts and new ideas, and the git PR history - right from the very first #1 PR, each highlighting the changes made to the Code of Conduct over time - from grammar to spelling.

This proves the claim as unequivocally false.

Inspiration for the Code of Conduct (where you will find some notable similarities), was derived from many different sources, from various contributors such as Jerp, golang and more.

All GitHub contributors are all listed below so that you can see each of the individuals who dedicated their time and effort towards the project.

Claim - No progress being made

Claim - Kaizen does nothing and no progress is being made

The truth:

Kaizen's Direct Evidence: Work Verification

In response to claims of inaction and incompetence, Kaizen has provided notable detailed evidence of her contributions to projects run by All Things Linux:

• 650+ hours logged on Tux development
• 40+ hours logged on xmpp.atl.chat repo
• 40+ hours logged on irc.atl.chat repo
• 30+ hours logged on infra planning repo
• 100+ hours logged on atl website repo
• 1,800+ total commits across ATL GitHub repositories in 2025 alone
• Comprehensive Discord server management (roles, permissions, auto-mod, channels, emojis)

• Personal donation of thousands of dollars to ATL (pre and post-nonprofit)
• Onboarding/training of 40+ staff members across the span of ATL

• Tux codebase complete rewrite and refactoring for v0.1.0 release (over 400+ commits)
• Fibery project management implementation for transparency
• Post DDOS infrastructure migration
• Infrastructure preparation for mono-repo and infrastructure-as-code migration

This evidence directly contradicts claims of "nothing gets done" with verifiable, quantitative data.

A Wakatime report and an extensive audit of Tux specifically has also been included in this package, as presented earlier.

• https://docs.google.com/document/d/1gf2m0WNO3XlIxMA3UItAnh3vpnqSLd-GvCKvx5ovC-U/edit?tab=t.xq1s08rposw0

Changelog

A changelog has been compiled from all ATL blog updates since its inception.

You can find it listed in the sidebar here:

• https://docs.google.com/document/d/1gf2m0WNO3XlIxMA3UItAnh3vpnqSLd-GvCKvx5ovC-U/edit?tab=t.e2p9agp9su3s

Further Evidence of Progress

atl.chat:

• https://github.com/allthingslinux/xmpp.atl.chat
• https://github.com/allthingslinux/irc.atl.chat

atl.wiki:

• https://github.com/allthingslinux/atl-wiki-link
• https://github.com/allthingslinux/atl.wiki-configs
• https://atl.wiki/Special:RecentChanges

tux:

• https://github.com/allthingslinux/tux
• https://github.com/allthingslinux/tux/tree/v0.1.0
• https://github.com/allthingslinux/tux/pull/1020

Miscellaneous:

• https://github.com/allthingslinux/iso.atl.dev
• https://github.com/allthingslinux/stats-frontend/tree/feat/cf-worker-build
• https://allthingslinux.org/blog/notices/8-25-ddos
• https://github.com/allthingslinux/code-of-conduct/commits/main/ 

Changelog

All Things Linux: Organizational Changelog

Purpose: Comprehensive timeline of organizational achievements, infrastructure development, and community milestones
Period Covered: November 2023 - August 2025 (22 months)
Source: Official monthly roundup blog posts from allthingslinux.org

2023: Foundation Year

November 2023 - Launch Month

Community Milestones:

•  Community founded (November 9, 2023)
•  Acquired discord.gg/linux vanity URL
•  Reached 200+ members in 12 days
•  Exchanged 100,000+ messages in first 12 days
•  Made front page of Top.gg

Infrastructure & Features:

•  Code of Conduct v1 drafted collaboratively on GitHub/Google Docs
•  Ticketing system implemented (Helper.gg integration)
•  RSS feeds added for #news channel
•  Initial roles system (programming, distros, DE/WM, colors)
•  Standardized bot prefixes and nicknames

Projects Initiated:

•  Tux bot development begins (seeking Python developers)
•  Moderation recruitment process established
•  Directory listings on Discadia, Disboard, Discord Chat, Discord Home

Governance:

•  Server focused on Linux-related discussions (community poll)
•  Archival system for inactive channels

December 2023 - Early Expansion

Community Milestones:

•  Reached 700 members
•  350,000 messages exchanged
•  1 million+ total messages milestone

Community Engagement:

•  Super Tux Kart Saturday gaming event (first community event)
•  1K member giveaway (Nitro subscriptions to 3 winners)

Infrastructure & Features:

•  Special achievement roles launched (@Top 10 Text, @/dev/tty0 for first 128 members)
•  Monthly color rotation system (Tokyo Night palette)
•  #ricing/wallpapers channel added
•  Activities and Voice ping roles introduced
•  Forum channel opened for persistent discussions
•  30 boosts secured for vanity URL maintenance

2024: Growth and Professionalization

January 2024 - Rapid Expansion

Community Milestones:

•  Reached 1,000 members (major milestone)
•  Set goal: 10,000 members by year end

Infrastructure Development:

•  IRC server deployed (irc.atl.tools #general with SSL)
•  XMPP server operational (atl.tools MUC at conference.atl.tools)
•  Self-hosted mail server testing initiated
•  Community VPS exploration (XMPP, Pastebin, Git frontends)

Community Features:

•  @FOSS Contributor role for verified open-source contributors
•  New roles added (Slackware, Asahi, Budgie, Nano, Micro, Helix, Assembly, /bin/zsh, /bin/bash)
•  Web dev forum channel opened

February 2024 - Event Development

Community Engagement:

•  Super Tux Kart Saturday event (collaboration with STK discord, filmed event)
•  New moderators joined (@Eternal, @eve)

Infrastructure:

•  Two Tempo music bots deployed
•  Last.fm scrobbling via fmbot
•  @Revive role for chat engagement

Features:

•  New roles (Fedora Atomic, RHEL, Plan 9, Clojure, /bin/dash)

March 2024 - Safety and Structure

Community Milestones:

•  Reached 2,000 members

Governance:

•  Code of Conduct migrated to GitHub for transparency
•  SFW standards reinforced
•  Low-effort/low-quality content prohibition clarified

Team Expansion:

•  New moderators: @Pseudify, @Amilie, @Leah

Features:

•  #support-info channel added
•  @R-Lang role added
•  Gartic bot integrated for community games
•  #reviews channel opened for community feedback

Projects:

•  Tux bot development continued
•  Group project ideation phase
•  Mod application form system established

April 2024 - Community Maturation

Community Events:

•  Super Tux Kart Saturday continued
•  Permanent SuperTuxKart server fork deployed

Team Growth:

•  New Junior Mod: @Gurov

Infrastructure:

•  Tux /tldr command added (Linux command quick reference)

Features:

•  New roles (LXQt, GDScript, Nim)
•  #reviews channel made fully public

Governance:

•  Code of Conduct updates for discourse quality standards

May 2024 - Major Milestone

Community Milestones:

•  Reached 3,000 members
•  3K member Nitro giveaway

Infrastructure:

•  Anonymous reporting via /report command
•  Catppuccin Frappe color roles

Team Expansion:

•  New Admin: @Miyu
•  New Junior Mod: @Tess

Partnerships:

•  Partnership with The Debian Den server

Features:

•  New roles (CachyOS, Swift)
•  Continuous Junior Mod applications accepted

June 2024 - Infrastructure Launch

Major Developments:

•  allthingslinux.com domain acquired (generous community donation)
•  Raised $500 in one week (first major donation milestone)
•  atl.chat domain acquired

Infrastructure:

•  IRC and XMPP services migrated to new domain (irc.atl.chat, atl.chat)
•  Minecraft 1.20.6 Java Edition server launched (mc.atl.tools)
•  Email server live with ~70 accounts registered

Projects:

•  Community wiki initiative planning (#wiki-chat)
•  Wiki platform voting and decision process

Team Growth:

•  Mod promotion: @tess
•  Junior Mod promotions: @flatbread, @green

Features:

•  #donations channel created
•  #vip-lounge launched
•  #wiki-news channel
•  #mc-chat for Minecraft discussions
•  ATL RISC-V RADIO music bot
•  Tux /xkcd command added
•  @Universal Blue role
•  Donor roles system (Donor Legend, Super Donor, Donor+, Donor)

July 2024 - The Tux Games

Community Milestones:

•  Reached 4,000 members
•  @/dev/tty4096 role for milestone

Major Event:

•  The Tux Games (August 9-10) - Weekend competition event

• Art Contest
• Manual Arch Install Speedrun
• Super Tux Kart Racing Bracket
• Minecraft Hunger Games Tournament
• Founder speech

Transparency:

•  Airtable financial ledger launched (public donations/expenses visibility)

Infrastructure:

•  Email server operational at atl.tools (70+ accounts)
•  Minecraft server hardware upgrade

Features:

•  Privacy roles (@Ask To DM, @Closed DMs, @Open DMs)
•  New channels (#bsd/unix, #engineering, #showcase, #wallpapers)

Projects:

•  Tux bot: 9,000+ lines of code, 20+ contributors, 1,000 commits, 89 closed issues, 235 closed PRs

August 2024 - Event Success

Community Milestones:

•  The Tux Games executed successfully
•  Art contest winner: @devobass
•  Event winners across all competitions

Infrastructure:

•  IRC/XMPP blog post update published
•  Creative Team formation initiated

Projects:

•  Tux bot development server launched
•  Modern tech stack: Python 3.12, strict typing, Sentry, Supabase, CI/CD

Team:

•  Event volunteers recognized (Atmois, Amilie, electron271, dc7341, MelonOof, tess)

September 2024 - Refinement

Community Milestones:

•  Reached 4,500 members
•  3.2 million messages total

Infrastructure:

•  Role icon refresh (consistent theme by @Juniiii)
•  Statbot dashboard integration

Features:

•  New ping roles (@Polls, @Support for forum posts)
•  GPU roles (@AMD, @Nvidia, @Intel)
•  @Dart language role
•  New channels (#server-meta, #quick-support, #media, #donors)

Team Promotions:

•  Senior Mod: @tess
•  Mod: @arkannon, @pocki
•  Junior Mod: @bee, @estralia

Projects:

•  Tux development: 75+ stars, 20+ contributors, 1,200+ commits

October 2024 - Pre-Anniversary

Community Milestones:

•  Approaching 5,000 members
•  Preparing for one-year anniversary (November 9)

Infrastructure:

•  Role consolidation (approaching Discord limits)

• Merged: Arch-based, Ubuntu-based, Fedora-based, *BSD, Universal Blue categories

Features:

•  #forum channel for off-topic discussions
•  #submit-a-report for easier ticket access
•  Leveling system launched with XP roles:

• Level 5+: Grublet
• Level 10+: Terminal Tinkerer
• Level 15+: Daemon Wrangler
• Level 20+: Penguin Prodigy

•  Level 20+ auto-qualified for @atl.tools email

Team Growth:

•  Mods: @atmois, @estralia, @bee
•  Admin Assistant: @owuawo
•  Creative Team formation (@pseudify, @juniiii)

Projects:

•  Tux: New leveling system, custom automod
•  Minecraft server revamp (Towny, improved plugins, better hosting)

November 2024 - One Year Anniversary & Nonprofit Status

Major Achievements:

•  501(c)(3) nonprofit status officially recognized
•  Reached 5,500 members
•  4M+ messages total
•  40K+ voice chat hours
•  Team growth: 0 to nearly 40 staff members over one year

Infrastructure:

•  Website launched at allthingslinux.com
•  atl.wiki accepting public contributions (approval required)
•  IRC services revived (irc.atl.chat/6697)
•  Web IRC deployed (webirc.atl.chat)
•  Signal chat launched (signal.atl.chat)

Projects Announced:

•  atl.tools server revamp planned
•  atl.chat (IRC/XMPP) improvements planned with sysadmin team
•  atl.dev (free cloud storage/VPS, pubnix ecosystem) in development
•  Tux v0.1 formal release planned

Community Events:

•  Logo design contest ($100 prize)
•  Raspberry Pi 5 Thanksgiving giveaway (winner: @kant)

Documentation:

•  Internal documentation development
•  Moderator Handbook creation
•  Onboarding presentations
•  Standard operating procedures formalized

December 2024 - Partnership Expansion

Community Milestones:

•  Surpassed 6,000 members

Major Acquisitions:

•  allthingslinux.org domain acquired (new primary domain)
•  US Bank nonprofit account established

Partnership Benefits Secured:

•  Google Workspace: 2,000 accounts + 100TB storage
•  GitHub: Advanced features (CI/CD, packages, codespaces)
•  Canva: 30 pro accounts (no cost)
•  Okta SSO: 50 accounts (no cost)
•  Stripe & PayPal: Discounted processing fees

Legal Compliance:

•  Privacy Policy implemented
•  Cookie Policy deployed
•  Terms & Conditions updated
•  GDPR, CPRA, LGPD compliance (via iubenda.com)

Team Promotions:

•  Senior Mod: @estralia
•  Mods: @imnotpolar, @ilovecanada
•  Junior Mods: @vuks, @electron271, @glocean
•  Admin Assistant: @green

2025: Expansion and Maturation

January 2025 - Steady Growth

Community Milestones:

•  Grew from 6,262 to 6,843 members
•  12,500 messages per day average
•  50 hours voice chat per day average

Infrastructure:

•  Wiki upgraded to MediaWiki 1.43
•  Major internal wiki overhauls for contributor experience
•  ISO Archival Project: 7TB documented

Team Expansion:

•  New Moderators: @Glocean, @Electron271, @Vuks

Projects:

•  ISO preservation effort with volunteer recruitment

February 2025 - Infrastructure Overhaul

Community Milestones:

•  Grew from 6,900 to 7,500 members
•  12,500+ messages per day sustained
•  75 hours voice chat per day average

Major Infrastructure:

•  Full backend revamp initiated:

• Mail separation to dedicated servers
• Automated backup systems
• Enhanced security implementation
• Improved monitoring infrastructure
• Ansible standardization
• Dotfiles and user group configuration

Projects:

•  Projects forum launched for showcasing personal work
•  TuxGPT instance deployed (Level 15+, donors, boosters)
•  Official blog launched on website
•  Historical monthly roundups compiled (all announcements archived)

Features:

•  Blog platform supporting guides, tutorials, technical deep dives, community opinions

March 2025 - Public Recognition

Community Milestones:

•  Grew from 7,500 to 8,000 members
•  12,000 messages per day average
•  120 hours voice chat daily (new peak)

Infrastructure:

•  ATL Stats platform relaunched (stats.atl.dev)

• Auto-deletion on server leave
• Opt-in system
• Privacy policy integration

•  Status monitoring deployed (status.atl.tools/status/public)
•  Public Grafana dashboards (grafana.atl.tools)
•  URL shortener deployed (atl.sh)

Projects:

•  Tux featured on YouTube (livestream with 25k+ viewers)

• Docker refactoring highlighted
• Showcased alongside AgentGPT (33k+ GitHub stars)
• Recognition for quality community development

Infrastructure:

•  Website overhaul at allthingslinux.org
•  New staff application forms (replaced Google Forms)
•  Wiki database migrated to secure dedicated server
•  Apache to NGINX migration for performance
•  Short URLs implemented (atl.wiki/Page_Title)

Team:

•  Systems team addition: @Thanos
•  Admin Assistant promotion: @Atmois

Governance:

•  Code of Conduct updates (Rules 1.1, 1.2, 1.3)
•  Departmental structure refined (Community/Moderation, Management/Admin, Creative/Content, Systems/Development)

Features:

•  #projects forum channel

April 2025 - Explosive Growth

Community Milestones:

•  Grew from 8,000 to 8,900 members (500+ joins in final week)
•  20,000 messages per day average
•  100+ hours voice chat daily

Public Recognition:

•  Featured by Brodie Robertson - "Useful Resources Every New Linux User Needs" (25,000+ views)
•  Surge in activity: 20,000+ messages for 4 days straight following video

Infrastructure:

•  Channel reorganization for improved usability:

• #polls archived (moved to #random)
• Wiki category cleaned up
• #wiki-changelog → /var/logs
• #wiki-chat → /home/atl/atl-wiki
• @/mnt/archives role for archived channel access
• #dj-booth for music bots

•  Onboarding options expanded (Logs role)
•  Channel layout refined (#linux, #general-tech, #off-topic, #random)

Projects:

•  Wiki Guide section soft-launched (prep for May release)

Team Expansion:

•  Admin Assistant: @Redkey
•  Junior Mods: @Jess, @Storm, @Dyl, @Arm, @Abby
•  Systems Team: @Fr3sh, @Wilbur

Features:

•  New roles (Solus, COSMIC, Ed, Zed)
•  Level unlocks system adjusted

Governance:

•  Code of Conduct updates (Rules 1.7, 2.3, 3.4)

May 2025 - Historic Growth

Community Milestones:

•  Reached 10,000 members (major milestone achieved 5 months ahead of original goal)
•  Grew from 8,800 to 10,600 members (fastest growth ever)
•  60+ new users daily average
•  15,000 messages per day average
•  80+ hours voice chat daily (peaks over 125 hours)

Major Community Events:

•  10K ThinkPad Giveaway announced (Lenovo ThinkPad T14 Gen 3)
•  Podcast with Brodie Robertson recorded (founder interview)
•  Twitch debut: Live countdown to 10K members stream
•  Twitch channel officially launched

Team Promotions:

•  Admin Assistants: @FarCotton, @Hunter
•  Senior Mod: @Vuks
•  Junior Mods: @armv8, @abby

Features:

•  TuxGPT access expanded (Terminal Tinkerer Level 10+ users)

• Image understanding capability
• Text file processing
• 50-message conversation chains
• Linux and ATL culture trained

•  Holographic username styles for @Donors, @Helpful, @ally@atl, @FOSS Contributor
•  Server tag system launched (profile customization)

Projects:

•  Guild tag system deployed (ATL tags for members)

June 2025 - Sustained Momentum

Community Milestones:

•  Grew from 10,764 to 12,064 members
•  15,001 messages per day average
•  93.48 hours voice chat daily

Major Event:

•  10K ThinkPad Giveaway executed (T14 Gen 3 delivered to winner)

Team Expansion:

•  Moderators: @storm, @bghs, @Ryna
•  Returning: @Khrozma (after break)
•  Systems Team: @Ela, @ikci, @waffles, @Clemthealien

Governance:

•  Code of Conduct updates

Projects:

•  Wiki 1.0 preparation underway

July 2025 - Continued Growth

Community Milestones:

•  Reached 13,084 members

Team Updates:

•  Mod return: @miyu
•  Mod promotion: @ryna (Junior → Mod)
•  Systems Team: @joetroll

Infrastructure:

•  Crypto donations launched (wide variety of cryptocurrencies supported)

• Payment gateway: atl.sh/crypto

Projects:

•  ISO Archival Project: 12TB+ ISOs preserved (led by @wilbur)

Features:

•  EndeavourOS role returned
•  C/C++ roles split for specificity

August 2025 - Crisis and Resilience

Community Milestones:

•  Passed 14,520 members (approaching 15,000)
•  15,795 messages per day average
•  109 hours voice chat daily

Major Incident:

•  DDoS Attack Response (August 3-14):

• Multi-day coordinated network flood attacks
• Emergency mitigation implemented (Cloudflare security, IP rotation, firewall)
• Complete infrastructure migration to distributed architecture
• Zero data integrity compromise throughout
• Cloudflare Alexandria protection secured for critical domains
• Enhanced security protocols deployed
• All services restored with improved resilience

Major Launch:

•  atl.wiki 1.0 officially released (August 2025)

• Full infrastructure rebuild (MediaWiki from scratch)
• Database migrated to dedicated secure server
• Apache → NGINX migration for performance
• Short URLs implemented
• Homepage redesigned
• Staging wiki for safe testing
• LTS version policy adopted
• Guides section launched
• Expanded policies and guidelines
• Revamped page moderation
• Cloudflare Turnstile bot protection
• SSO integration
• TOTP 2FA for users
• 3,000 edits across 200+ pages from 130 users

Infrastructure:

•  Security page deployed (allthingslinux.org/security)
•  Distributed server architecture (multi-VPS separation)
•  Multi-layered firewall strategy
•  SSH bastion implementation
•  Comprehensive monitoring restructured

Features:

•  #security-privacy channel launched
•  Color roles updated with hex codes for accessibility
•  Channel descriptions updated (Easter eggs included)

Claim - Nonprofit status is useless

Claim -  Nonprofit status is useless and we’re always going to be just a Discord server

The truth:

Core claims from staff communications:

1. The nonprofit status is "useless" and "rubbish"
2. It was obtained only for "brownie points" or ego gratification
3. It's only used to justify strict rules
4. ATL is "just a Discord server" that doesn't need nonprofit structure
5. The organization hasn't done anything substantial with the status
6. The "legal entity part is mostly bullshit and quite useless"

These claims here above represent a fundamental misunderstanding of both the organization's long-term vision and the substantial tangible benefits already realized. The information below provides comprehensive evidence demonstrating that the 501(c)(3) status is not only valuable but essential to ATL's mission and operations.

Organizational Mission and Strategic Direction

All Things Linux operates under a clearly defined three-pillar strategy that extends far beyond a Discord community:

Three Core Pillars:

1. Education - Comprehensive educational resources including wiki development, tutorials, blog content, and community-written documentation to bridge knowledge gaps for users at all skill levels.
2. Community - Multi-platform community infrastructure serving as the foundation for collaboration, support, and knowledge sharing across Discord, IRC, XMPP, and future platforms.
3. Technology - Development and provision of open-source tools and self-hosted infrastructure that empowers users to explore, learn, and contribute to the Linux ecosystem.

Looking Ahead:

All Things Linux’s long-term vision models itself similarly to organizations like the Linux Foundation, Electronic Frontier Foundation and Hack Club.

Example Initiatives:

• House multiple open-source projects under one nonprofit umbrella
• Provide fiscal sponsorship to emerging projects that cannot afford separate 501(c)(3) status
• Support smaller open-source projects (desktop environments, system tools, applications)
• Support individual developers, particularly those in challenging economic circumstances
• Provide free hosting infrastructure and web space to developers in need
• Offer technical resources at no cost to qualifying projects and contributors
• Develop and fund grant programs for open-source development
• Create educational programs and content at scale
• Facilitate community-driven development initiatives
• Maintain neutrality and community trust through nonprofit governance

Thinking Realistic:

ATL approaches growth and impact as a multi-year journey rather than seeking immediate results. Substantial nonprofit infrastructure requires 2-5 years minimum to establish. Foundation-building in Year 1-2 enables major programs in Years 3-5. Professional infrastructure must be built before scaling charitable activities.

Phase 1 (Year 1 - Current): Foundation Building

• Establish legal structure and compliance framework
• Build technical infrastructure and development practices
• Secure nonprofit benefits and partnerships
• Develop internal processes and documentation
• Grow community to sustainable size

Phase 2 (Years 2-3): Expansion

• Clarify brand identity and messaging

• Launch major projects (Tux 1.0, Portal, atl.dev, atl.sh)
• Establish comprehensive pubnix services
• Implement public financial transparency systems
• Expand multi-platform presence and partnerships
• Tighten internal leadership and team management

Phase 3 (Years 3-5): Mission Fulfillment

• Seek press and marketing related opportunities

• Begin fundraising via larger corporate/government sponsorships/grants

• Provide fiscal sponsorship to smaller FOSS projects
• Offer free infrastructure to developers facing economic barriers
• Launch grant programs for open source development
• Launch community events and educational programs

Expecting full charitable program delivery within 11 months represents unrealistic expectations, not organizational failure.

Tangible Benefits Already Achieved

Through ATL's 501(c)(3) nonprofit status, the organization has secured numerous discounts and sponsorships that make operations financially viable.

• Google Workspace for Nonprofits provides 100TB storage, 2,000 user accounts, and professional email infrastructure valued at $216,000/year retail, while an additional $120,000/year Google Ads grant awaits strategic deployment for community outreach.

• Enterprise tools include Okta SSO for 50 accounts ($4,800/year value), Canva Pro with 30 design seats ($3,600/year), and QuickBooks Advanced accounting software ($3,125/year savings through nonprofit pricing).

• Payment processors PayPal and Stripe granted 20-43% fee reductions for donation processing

• Cloudflare provides Pro-tier services with advanced DDoS protection and enterprise features ($2,000+/year value).
• GoodStack and TechSoup partnership verification provides streamlined access to technology partner programs.
• Digital Ocean infrastructure credits ($2,000) will enable enhanced DDoS protection for alternative networking platforms.

What’s shared above is not even 100% of the benefits we have been able to take advantage of already.

Without nonprofit status, ATL would require $50,000-80,000/year to operate at current capacity while current donation income is approximately $3,000/year, making the organization financially insolvent without its 501(c)(3) designation and associated partnership benefits.

While some services provide capacity beyond current usage and some could be replaced for cheaper or less extensive alternatives, the essential infrastructure (Google Workspace, Okta, Canva, QuickBooks, Cloudflare, payment processing) is actively utilized and would be completely unaffordable at full commercial pricing.

Redeclaration

A Redeclaration of Vision and Mission

All Things Linux is a 501(c)(3) non-profit organization with a mission to empower the Linux ecosystem through education, collaboration, and support.

Mission

All Things Linux is a volunteer-driven 501(c)(3) that empowers people to explore, master, and shape Linux by combining open education, self-hosted tooling, and a friendly social hub.

We exist to:

• Welcome everyone—from first-time tinkerers to kernel hackers;
• Provide clear, community-written resources and real-time support;
• Cultivate open-source projects (tux, atl.wiki, atl.tools, and more) in the open;
• Demonstrate that a transparent, member-funded model can keep free knowledge, free infrastructure, and free culture thriving.

Vision

We envision the world’s most trusted and energizing Linux community—a place where millions come to learn, collaborate, and celebrate open source, where the infrastructure is community-owned, the governance is transparent, and every contribution, be it a line of code or a line of encouragement, moves Linux and its people forward.

Our Values

The values and principles that ground our organization and community. We may have failed to fulfill all of them in the past but we are committed to ensuring we follow through on all of them in the future.

Community

We connect Linux enthusiasts through collaboration and knowledge sharing. We run community projects to strengthen it with the goals of providing events to bring the community together.

Mutual Respect

Mutual respect is key as outlined in our Code of Conduct, stressing the importance of treating everyone with kindness and consideration, free from discrimination.

Inclusivity

We are committed to creating an environment where all members, irrespective of their background, differences, or skills, feel welcomed and empowered to engage in meaningful discussions.

Collaboration

Our community thrives on collaboration, fostering creative teamwork and open-source contributions. We engage in collaborative projects including our wiki, Discord bot, and self-hosted tools.

Support

We offer a dedicated space for members to seek help and guidance, with experienced users actively responding in our support forums. We aim to cultivate a culture of understanding and helpful support.

Education

Learning and growth are our priorities. We encourage members to share their knowledge, resources, and insights, particularly in our support forums and educational channels.

Integrity

Accountability and honesty are essential to our community, with both staff and members encouraged to acknowledge and learn from their mistakes. Our commitment to integrity sets us apart.

Transparency

Openness in community operations is vital, including accessible moderation logs, transparent spending, and regular community decision voting. We believe that transparency fosters trust.

Closing Statement

Closing Statement

The following report presents verified facts as they are, based on the evidence available at this time. It contains no opinions, speculation, or emotional framing. Where interpretation is unavoidable, it is clearly identified and supported by documented sources.

We ask all readers to evaluate this information on its merits, refrain from assumptions or negative judgment, and avoid attributing motives not supported by evidence. Please review everything in full before drawing your own conclusions.

We remain committed to transparency, accuracy, and respectful discourse. If new, verifiable information emerges, we will update the record accordingly and correct any errors without delay.

We hope to move on from this stronger and to improve from our mistakes. We have made them before and will make more again, but it just proves our humanity as nothing is or will be perfect. We are committed to our community to improve in every way possible from the concerns raised not just by the group but by everyone.

We want to reinforce our core values of Community, Mutual Respect, Inclusivity, Collaboration, Support, Education and Transparency throughout everything we do. We did not get here alone, we had all of you here with us supporting us every step of the way through donations, contributions and your time here and we are eternally grateful for it and we hope to see you with us for the many bright years ahead of us.

Contact and Feedback

To reiterate from the introduction, we welcome constructive feedback and questions through all our official channels:

Email: admin@allthingslinux.org

Discord: https://discord.gg/linux

• To create a ticket, use /ticket within the server.

• To submit a suggestion, visit the #suggestions channel.

Signed by: