Log in
announcements

Issue and feature bounties

Announcing new bounty program for our Tuist contributors

Financing open source projects is hard. Therefore, we value every dollar you send our way to keep this project going after many years now. But we also want to ensure that the money is used to move the project further. This is why we’re introducing issue bounties. But first:

Thank you!

I’d like to call out all of our current public sponsors, you deserve a round of applause 👏:

But we value as much all the past financial contributors and anybody who spent their free or company time on the project, helping others with questions, features, or issues 💜

Announcing bounty system

Our budget is no secret and you can see our expenses at Open Collective. We have recently been able to cut down our monthly recurring bills which left us wondering how we can best use the financial contributions. We value the free time contributors are putting into tuist and so we want to reward them.

We will experiment with a bounty system – our Tuist Core team will select issues and assign rewards to them. You will find the list here. We will regularly update the list and you are free to add your suggestions there. If you have yourself an issue you’d like to see resolved, you can send a donation to our project and we will declare a bounty for you.

If you are a contributor and you are interested in getting one of the bounties, just declare in a given issue you plan to work on it, implement it, and we’ll send you the bounty via GitHub Sponsors or OpenCollective 🎉

You might also like

Dynamically generated Info.plist files with Tuist 0.15.0
Tuist 0.15.0 extend the beauty of generation to Info.plist. From this version on you'll be able to define the build settings as part of your manfest and let Tuist infer the default values for you. Furthermore, we extended the API to support customizing the generation of default build settings in your projects and targets, added the generation time to the 'tuist generate' command, and added support for defining custom schemes.
Interview with Kamil Pyć - With Bazel we were able to reduce build times by 70% on clean builds
In this interview, we talk with Kamil Pyć, Senior Mobile Developer at Allegro. Allegro is one of the few companies that have undertaken replacing Xcode's build system with Bazel, and that led them to an improvement in build times of roughly 95%. In this interview, Kamil shares more about Bazel's adoption, and some other insights about their project and teams.
Tuist turns 1.0
Today we are pleased the first major release of Tuist, 1.0. We have achieved an important milestone in helping teams scale up their projects, making defining projects easy, and for that reason we are releasing this one as major. This blog post describes what that has been for the project, and what are our ambitions for Tuist 2.0.

Supercharge your app development

Get started