Juan Julián Merelo Guervós

My solution for this would be to simply remove `p6doc` from the ecosystem. As a developer, there's nothing really useful there since all business logic has moved elsewhere. There's the...

Additionally, we should probably change the name to something like Raku::Doc

Alternatively, we could substitute it by a kinda-rakubrew that would download the documentation, Documentable and install it in your system, if you so want...

I guess design would be a priority.

@AlexDaniel OK. I'm good with design being second.

Are all these domains transferred now? Or are they mirroring the existing infrastructure?

Long story short: We should try and designate some version along the year a LTS version, and support it for 5 years or whatever is thought to be reasonable. At...

Every ecosystem evolves, but you still know which versions are the ones that work with your application. Imagine however that you have your application working with Foo 2.3.1 and Rakudo...

Quite clearly this would need resources. How many, however, will depend on the bug-fixing strategy. Probably the best would be to prepare patches for the bugs based on the first...

Containers are precisely what is bringing me here. I can't seem to be able to install zef in the [container environment created in 2017.05](https://hub.docker.com/repository/registry-1.docker.io/jjmerelo/alpine-raku/builds/007c94f6-6780-41eb-913c-257044f505da). Quite clearly if I had built...