For general language problems there is special repo on github where one can raise a matter: https://github.com/perl6/problem-solving <https://github.com/perl6/problem-solving>. Note though it's not a bug-reporting resource, but more information about it's purpose can be found in repo's README.
Obviously, rakudo compiler issues goes into https://github.com/rakudo/rakudo/ <https://github.com/rakudo/rakudo/>. This would be the best place to open a ticket when one doesn't know where exactly the problem belongs to. Some tickets serve as a ground for new tickets in other repos, where they actually belong. Now, as you specifically mention zef and the question has seemingly arisen as a part of R* discussion, it should be noted that zef is a personal project of Nick Logan and can be found at https://github.com/ugexe/zef <https://github.com/ugexe/zef>. Respectively, for any other module from the ecosystem it's repo could be located. I usually just google for it, but also https://github.com/perl6/ecosystem <https://github.com/perl6/ecosystem> could serve as a source of information. Best regards, Vadim Belman > On Nov 6, 2019, at 9:48 AM, Parrot Raiser <1parr...@gmail.com> wrote: > > Raku is the product of collaboration by many people. Some of these are > well known, but there are many parts of the ecosystem whose mavens are > anonymous or obscure. When a problem arises, it would be nice to be > able to direct them to someone knowledgeable, rather than essentially > yelling them in public and hoping someone responds to the noise. > > Do we have any kind of resource, (web page or whatever), indicating > who might be authoritative on a particular issue? Some names are > fairly well-known, (and may wish they weren't), but topics like the > internals of zef are hard to link to a person or group. >
