Community

for help and friendly advice

Discord

You are invited to join us at the Raku Discord server, which is is also bridged to the IRC.

Internet Relay Chat (IRC)

Much discussion happens on #raku, our IRC channel. This is the fastest way to get help.

The IRC chats are logged here. A family of friendly bots (the "Whateverables") are there to help.

Weekly

The Rakudo Weeky News is a great way to keep up to date on the latest core developments and module releases.

Stack Overflow

Many questions and answers are marked with the Raku tag.

Social

• Bluesky: #rakulang

• Mastodon: @rakulang

• Reddit: Join the r/rakulang subreddit

• Facebook: Join the Raku Group

• Twitter: Follow @raku_news

Blogs

• Perl and Raku Weekly Challenge

• Raku Blog Aggregator

• Rakudo Weekly News – Weekly changes in and around Rakudo

• Raku Advent Calendar - help for contributors

Raku® is optimized for fun! Audrey Tang coined the phrase that Raku is optimized for fun, short -Ofun. Raku has a fun-driven community: writing a Raku compiler is fun, developing applications too, and most of all dealing with friendly, intelligent people.

I may have left Raku development for a long time, but the community still keeps the culture alive, and together a production-ready Raku (then called Perl6) release was delivered on Christmas 2015 — in the spirit of Optimizing for Fun.

The Raku core development teams release the specification, compilers, and documentation they develop under the Artistic 2.0 license.

This is the same license established by Perl and most CPAN modules and has been adopted by almost all OS distributions.

The broader development community is of course not required to use this license, but there is a large uptake among the community.

The Steering Council is a 7-person committee with many responsibilities, including maintaining the quality and stability of the Raku language, its compilers, and its ecosystem. Also to make contributing and learning Raku as accessible, inclusive, and sustainable as possible.

The Problem Solving repository contains issues that impact Raku which require consensus to resolve. The RSC is responsible for guiding any deadlocked issues to completion.

Raku has a more than 20 year long history, much of it as "Perl 6". In this timeframe, many people have been involved in the project and have written blog posts about it. Sadly, some of these have already been lost in the mists of time.

On the other hand, the syntax and semantics of the Raku Programming Language has seen several shifts and changes, so at leat some of the blog posts are now providing examples that will not run in the latest version of Raku.

Finally, from a search engine optimization perspective, the Raku Community could benefit from an immediate source of up-to-date blog posts of the Raku Programming Language, as opposed to out-of-date Perl 6 blog posts.

The Raku CCR project intends to remedy this situation in three stages.