nxadm

> FWIW, I have been toying with the following idea: > > If you do `use pre-production` in your code, it will **warn** about unpinned versions in `use` statements (`use...

> +1 one it being enforced by fez Core functionality should not be handled by external tools. Or fez or fez-like should be pulled into core (and probably handled by...

> Ecosystem is not a core functionality. The rules (interfaces) and, in this case, their enforcement is a core functionality in my eyes. The contents of the ecosystem is not,...

~~advertisements about~~

> Stefan suggested introducing the [5-3-1 rule](https://github.com/Raku/problem-solving/issues/200#issuecomment-633507296), to prevent the pumpkin from burning out Preventing the pumpkin (or technical lead) to burn out is something very important, not only for...

> Marketing and user experience lead (this would subsume web presence, I guess, or maybe a different thing. I don't know. Maybe "web presence" should be "web infraestructure" and marketing...

> I would appreciate it if someone who knows the internals could assess the feasibility of a slang replicating the exact current `:P5` adverb, so that support can continue to...

> We could, however, document what it _does_ support, or something like "includes everything supported by Perl 5.8" or some such. That's the honest truth, but it's also means "support...

When I was looking on how to create rakudo packages, OBS was the first thing I looked at. Huge platform support, backed by a FOSS company, etc. However, I found...

I don't think this is a viable solution due to the dynamic nature of the ecosystem. I think the way forward is packaging an application and its dependencies together, maybe...