Last month we started a community-maintained fork of the Tildes codebase. A lot has happened since then.

The biggest change: @Bauke and I have been added as maintainers to the official Tildes repo! As a result, we're moving the community fork to the backburner for now, as we focus on nearer-term changes that will directly improve the main website. Later on it's possible we'll pick up the fork again, where it will likely serve the purpose of self-hosting your own Tildes spinoff sites.

Deimos still has the final say on what makes it to the website. Bauke and I can't deploy changes directly. However, this arrangement is still much more streamlined than before, because we now have a lot more code review bandwidth for accepting outside contributions. Deimos has less work to do now: mostly testing out the live code on a staging server, and scanning over the code for security/privacy issues—but not full code reviews which often involve a lot of back-and-forth communication and reading and testing code.

What work have we done this past month?

It's mostly been setting up foundational stuff like configuring the GitLab repository, fixing the development environment, and writing docs.

More recently we have started fixing actual website bugs too: a bug when escaping a user mention (making sure \@talklittle doesn't turn into a link), and hiding <details> content in collapsed comments. Starting small but we've found a good rhythm and will work on more and bigger issues soon.

Big props to @Bauke for setting up a staging server! Currently at https://testing.tildes.community/ — This server will be instrumental in getting new code in a testable state in a live environment, which makes it easier to approve new features before deploying on the real Tildes site.

So we shouldn't submit code to the community fork?

No, please don't. We'll use the official Tildes repo from now on. I'll update last month's post to reflect this.

Is Docker support coming to the official repo?

Yes, very likely. Deimos has warmed up to the idea. Bauke and I have been using the Docker development environment and ironed out a lot of bugs this past month.

The official repo looks the same as before?

Our next steps are to port the community fork changes back upstream to the official repo. In addition to the master branch, we plan to add staging and develop branches. develop will be where development happens, while master will reflect what is currently deployed on Tildes.net.

How do I contribute to Tildes development?

Check this document: https://gitlab.com/tildes/tildes/-/blob/master/CONTRIBUTING.md

*Update (Feb 3, 2025): We've been added as maintainers on the official Tildes repo!

Much of the below is outdated now. Bauke and I will be helping out on the official Tildes repo instead, and the community fork is paused now.

See the new topic.

Original post below

It's happening: We're launching a community-maintained Tildes source code fork!

Link: https://gitlab.com/tildes-community/tildes-cf

@Bauke, as one of the top Tildes open source contributors, is on board as a co-maintainer, alongside myself. I hear @cfabbro is willing to help manage the issue tracker as well, continuing their long term efforts from the official repo.

Tildes' admin, @Deimos, has direct access to the repository as well. Although he is not expected to take an active role in maintaining this community fork, he will have visibility into everything going on with the fork.

Why?

Deimos has a lot going on outside of Tildes. We want to keep the Tildes codebase well maintained and remove some burden from him.

Back when he founded Tildes, Deimos was working as a fulltime unpaid volunteer on it, continuing that way for a few years. Not just code, but on everything administrative and financial; public relations, as in communicating officially inside the community and beyond; moderating the community; system administering the systems. Basically a ridiculous amount of effort for one person.

Now Tildes is a side project, and he has a day job, and there is not physically enough time for a (human, non-drug-reliant) owner to do all those things.

How will this new fork affect the Tildes website?

The hope is that Tildes can merge relevant changes back into the official upstream repository. If we implement things useful and desirable for Tildes, it should be possible to get those improvements onto the website.

Why not just add maintainers to the official repository?

There are some features that may be desirable for the community, but not relevant to Tildes itself. This includes things like a Docker development environment, which code contributors may find convenient, but are an extra maintenance burden on the official Tildes repo, as Tildes does not use Docker in any way (AFAIK).

Adding us to the official repository would also create a different dynamic, where there'd be an implicit endorsement by Deimos of all changes. This means the burden would essentially remain on the Tildes administrator to review, critique, and greenlight every single change. However, the entire point of this endeavor is that there isn't free bandwidth for that.

Also this fork opens up possibilities like making the code reusable for self-hosting entirely new websites based on the Tildes source code. While I don't personally have any specific plans regarding such, self-hosting has been a repeated request ever since Deimos open sourced Tildes years ago.

Is "Tildes Community Fork" good enough of a name?

Thanks for reading this far! The fork needs a name. It will live in the "Tildes Community" GitLab group at https://gitlab.com/tildes-community/.

For now I've simply called it "Tildes Community Fork" and put it at https://gitlab.com/tildes-community/tildes-cf.

Any better naming ideas? It's not too late to change.

Next steps: We'll start migrating GitLab issues over

I think we're ready to start copying any "low-hanging fruit" issues from the official issues to the new community fork issues. If you have an issue you think qualifies as such, especially if it was ever labeled as "Approved" in the past, please feel free to copy it to the new issue tracker. Please link back to the original too.

It's still a side project for us

Please keep in mind it's still a side project for us. Although we're excited to push the project forward, please keep expectations in check. We're doing this as volunteers. Please be polite and don't rush us!