Johannes Müller

I had wondered about this as well. However, so far only members have worked on the building setup so this wasn't an issue. Having an easy path for external contributors...

> Because all circle ci runners would be run on behalf of Contributors, it would garantie that secrets from crystal org are not shared or leaked. I suppose we would...

Moving release CI here seems like a good idea. It's probably gonna take some time, though. But we can simply start by setting up the CI workflows in this repo....

Currently, test_ecosystem clones and checks out all shard repositories from a central script: https://github.com/crystal-lang/test-ecosystem/blob/94560278641b6295441c7bce6d4d715ff05e808b/scripts/10-clone-repos.sh This means when adding a new test, you need to add a bats test and also...

> I find it odd the proposal to user a shard.yml to do that The main motivation for this is that it allows to easily lock versions by checking in...

Yeah, I don't think we need to do anything about this. Homebrew has tools for that. And technically it's also not our core reponsibility to update the brew package. It's...

We officially endorse using the homebrew formular and support it with advice as well as contributions. But I don't think we can consider it an official distribution package. Perhaps we...

The Crystal formular is automatically updated by the Homebrew project. There's no need to do anything on our end.

Yes, that's already tracked in #126. That doesn't mean we shouldn't have to update the readme, though.

The Docker hub has been manually updated to include information about tag naming schemes. Automatically updated information about available tags (via https://github.com/crystal-lang/crystal-dist/pull/14) would be a nice enhancement.