contributions
made better by people who used the tools and said something. every fix, test run and blunt report below came from someone who actually ran the code.
six public repositories, all of them small. the numbers here were counted by hand from github, the commits link straight to the changes.
what's actually there
counted from the six public repositories on 16 october 2026.
commits
every change made to the five tools and this site, all of it public.
repositories
five tools plus this site, all public on github.
languages
shell for the tools, python where it helps, plain html and css for this site.
open issues
nothing waiting right now. if something's broken, that's the first good thing to report.
written down once (not live)
what landed lately
real commits, in plain words. a card here means it's in main, not that it came through a pull request.
the theme menu works again, in a fixed order
the picker had gone dead on six pages at once; it opens again, and the list sits in one order everywhere instead of reshuffling.
the guides page stops scrolling sideways on phones
code blocks were forcing the whole page about 600px wide. the column can shrink now, so only the code scrolls, inside itself.
the launcher window opens in the middle of the screen
it used to pop up wherever the compositor felt like putting it. now it centers itself once the frame size is known.
pull requests now need green tests and a person
the template asks for the check output and the themes you looked at, and says bot-only patches get closed.
want to help build maidware?
you don't need to be an experienced developer, and a little time is worth more here than money ever will be. these three are the ways in, and none of them is big on its own.
fix or add something small
each tool has its own repository and a test suite that runs offline. start with one you already use.
translationswrite a language
english is the only one here, on purpose. a hand-written set of strings beats any machine output.
testingrun it and say what broke
a tool on your distro plus the console output beats a vague report. it gets read.
before you open anything: the full guide is CONTRIBUTING.md. the short version - run the tests, sign your commits, and know what every line does.
we don't take donations
we take help. a small tool stays alive because someone read the code and sent a fix, not because someone paid for it. if you want to keep open source going, your time is the useful thing.
help us do translations
we at maidware project need help with translations, and we want translators to help us. english is the only language here right now, on purpose. we'd rather ship none than machine-made strings that read badly to the people they're for. if you speak another language, a hand-written set of strings is welcome.
say hello, send a patch, or offer a translation: maidwareproject@proton.me
keeping open source alive is worth the effort, and it only works when people pitch in.