|
00:04
sjn left
00:08
Manifest0 left
01:02
sibl joined
02:46
sibl left
02:47
sibl joined
02:57
sibl left
02:58
sibl joined
|
|||
| disbot4 | <comborico> There's no denying it is cleaner that way. | 03:23 | |
|
03:34
human-blip left
03:35
human-blip joined
03:40
sibl left
03:41
sibl joined
|
|||
| disbot4 | <simon_sibl> Raku makes me feel like everything is possible, but now I have got no project to do to use it ;-; | 04:28 | |
|
04:36
sibl left
|
|||
| disbot4 | <librasteve> well, there’s maybe some ideas here github.com/Raku/raku-most-wanted/b...-wanted.md depends on your interests and skills … | 06:41 | |
| <librasteve> another wee project I have in mind is to rewrite the “X guide to Raku” … ost of the existing ones need a full rewrite and we could use s Lisp to Raku … this is much easier than back in the day since an LLM can get you a long way | 06:44 | ||
|
08:01
dakkar joined
11:01
sjn joined
14:26
librasteve_ joined
16:31
dakkar left
|
|||
| disbot4 | <antononcube> So, you are not ready for Raku... | 16:46 | |
| <comborico> I will definitely take on LISP to Raku. Sounds fun! | 16:48 | ||
| <librasteve> great - suggest you make a PR on the relevant docs repository (there should be a pen icon link on the page) and tag me to review ... I am no Lisp expert so others who can help please step forward | 16:56 | ||
| <comborico> It says I need to be a collaborator. | 17:08 | ||
| <comborico> I was attempting PR from most-wanted. | 17:09 | ||
| librasteve_ | rakudoweekly.blog/2026/06/01/2026-...ast-fruit/ | 17:25 | |
| disbot4 | <librasteve> @comborico ah - i see. please give me a minute | 17:26 | |
| <librasteve> ok, i did these steps (i) go to docs.raku.org/language/haskell-to-p6 (since there is no lisp yet), (ii) click the pen icon to github.com/Raku/doc/edit/main/doc/...6.rakudoc, (iii) go up one level to github.com/Raku/doc/tree/main/doc/Language | 17:29 | ||
| <librasteve> ok YOU should do this (i) go to the docs repo top level github.com/Raku/doc (ii) fork it to your GH account, (iii) navigate to main/doc/language, (iv) make a new file called lisp-to-raku.rakudoc (maybe better to cp the haskell one as a starter), (v) learn rakudoc, (vi) write your guide (you may need to do the usual git clone, git commit, git push) and finally (vii) Create a Pull Request (github.com will show a | 17:34 | ||
| big green button to do this when you push your new guide) | |||
| <librasteve> if this is the first time you have forked and made a PR on github.com - dont worry this is a standard coder workflow and LLMs can prompt you what to do | 17:35 | ||
| <librasteve> it may sound a lot but afterwards you will be experienced in the modern git ways of contributing to an open source code base (this is how I learned it) and we are here to help if you get stuck | 17:36 | ||
| <comborico> Thanks for the detailed help! | 17:47 | ||
| <comborico> When you say learn rakudoc, do you mean stylistic way the docs are written? | 17:53 | ||
| <librasteve> yep … it’s like markdown for raku docs … very easy | 17:58 | ||
| <comborico> Okay. No problem. Looking forward to it. Thanks for the opportunity! | 18:04 | ||