EBook of documentation

Hi to everyone. We have reformatted all the documentation into an EBook! It is now available from the docs.raku.org website. Click on More, then EBook, read the popup and download the book. THIS IS A FIRST DRAFT, so there's things wrong and help is needed to get it right. Why have

New search for Raku documentation page

Hi everyone, A new search facility has been developed for the Raku documentation site. It would be useful to get some feedback. The new search can be tested at 'https://new-raku.finanalyst.org'. Try clicking on the 'i' button next to the search panel for information.

Re: Upcoming documentation meetings

Team - I'm going to cancel the call scheduled for this Saturday - we've had great success in the past month coordinating via email (last resort), and irc and github (preferred). We've made a lot of progress, got the site live, closed/transferred probably 50+ tickets, setup milestones on raku/doc &

Re: Upcoming documentation meetings

Team - I missed the call! My back has been troubling me the last day after traveling for business this week and I spent the day unplugged and half asleep. I’ll do a write up of what I’ve been working on recently and post it on the wiki. Thanks to everyone who has been working on getting us to our

Re: Upcoming documentation meetings

Hey, you thought right! We were just doing a little testing (or at least offered to do) so that functionality concerns can be checked. By the way, I brought up the example of the Rakudo classes were Jitsi kind of failed us and the second occasion was moved to Zoom. It could be that something s

Re: Upcoming documentation meetings

I thought it was for 2nd Saturday, which is the 11-th On 04/02/2023 23:13, Ralph Mellor wrote: That's super short notice but if you mean EST, so 5pm UK time, it would work for me. On Fri, Feb 3, 2023 at 7:07 PM Will Coleda wrote: I can do a test tomorrow at noon if there's interest. On Fri,

Re: Upcoming documentation meetings

D'oh. Time for sleep. Hopefully see or hear y'all next Sat. On Sat, Feb 4, 2023 at 11:21 PM Will Coleda wrote: > > Yes, Eastern- but the time had already passed, sorry. > > On Sat, Feb 4, 2023 at 18:13 Ralph Mellor wrote: >> >> That's super short notice but if you mean EST, so 5pm UK time, >> i

Re: Upcoming documentation meetings

Yes, Eastern- but the time had already passed, sorry. On Sat, Feb 4, 2023 at 18:13 Ralph Mellor wrote: > That's super short notice but if you mean EST, so 5pm UK time, > it would work for me. > > On Fri, Feb 3, 2023 at 7:07 PM Will Coleda wrote: > > > > I can do a test tomorrow at noon if there

Re: Upcoming documentation meetings

That's super short notice but if you mean EST, so 5pm UK time, it would work for me. On Fri, Feb 3, 2023 at 7:07 PM Will Coleda wrote: > > I can do a test tomorrow at noon if there's interest. > > On Fri, Feb 3, 2023 at 10:27 AM Parrot Raiser <1parr...@gmail.com> wrote: > > > > I think I had prob

Re: Upcoming documentation meetings

Ok,we joined at noon eastern but only two of us were there. We'll see folks next week! On Fri, Feb 3, 2023 at 2:06 PM Will Coleda wrote: > > I can do a test tomorrow at noon if there's interest. > > On Fri, Feb 3, 2023 at 10:27 AM Parrot Raiser <1parr...@gmail.com> wrote: > > > > I think I had p

Re: Upcoming documentation meetings

I can do a test tomorrow at noon if there's interest. On Fri, Feb 3, 2023 at 10:27 AM Parrot Raiser <1parr...@gmail.com> wrote: > > I think I had problems finding the audio options on Jitsi, and wasted > a couple of meetings doing so. I'd suggest a "test" setup meeting, > where the whole agenda is

Re: Upcoming documentation meetings

I think I had problems finding the audio options on Jitsi, and wasted a couple of meetings doing so. I'd suggest a "test" setup meeting, where the whole agenda is ensuring that everyone has all the settings right. Maybe set up a static video shot with background music to give feedback? On 2/2/23,

Re: Upcoming documentation meetings

> On 2 Feb 2023, at 21:11, Ralph Mellor wrote: > My internet is flakey when humidity is around 80%+ and the weather > forecast suggests it may be but with luck I'll be "there" 5pm UK time > (noon EST, 9am US west coast time) Saturday Feb 11. If you switch off your camera, you will reduce the need

Re: Upcoming documentation meetings

On Thu, Feb 2, 2023 at 6:10 AM Bruce Gray wrote: > > On Feb 1, 2023, at 6:00 PM, Elizabeth Mattijsen wrote: > >> On 2 Feb 2023, at 00:53, Ralph Mellor wrote: > >> It required an international phone call. > > ??? I've never had to make *any* phone call to be able to use Jitsi. > To clarify, usin

Re: Upcoming documentation meetings

> On 2 Feb 2023, at 07:10, Bruce Gray wrote: > Also, like Zoom and many other video conferencing services, Jitsi allows you > to call a phone number, to listen and speak (audio-only) on in the video > meeting room: But if you have internet, you can also participate with audio-only in Jitsi. S

Re: Upcoming documentation meetings

> On Feb 1, 2023, at 6:00 PM, Elizabeth Mattijsen wrote: > >> On 2 Feb 2023, at 00:53, Ralph Mellor wrote: >> I looked at Jitsi when vrurg suggested it for their Core class. >> It required an international phone call. > > ??? I've never had to make *any* phone call to be able to use Jitsi.

Re: Upcoming documentation meetings

> On 2 Feb 2023, at 00:53, Ralph Mellor wrote: > I looked at Jitsi when vrurg suggested it for their Core class. > It required an international phone call. ??? I've never had to make *any* phone call to be able to use Jitsi. And the RSC uses it every 2 weeks or so. Liz

Re: Upcoming documentation meetings

On Tue, Jan 24, 2023 at 9:50 PM Polgár Márton wrote: > > Since there is a public Jitsi link, I don't think this would get cancelled > because of personal problems. This is my "unofficial opinion" but I > think whether the proposed dates (noon Eastern time, second > Saturday of February, March an A

Upcoming documentation meetings

Hi, since the broader topic of Raku documentation came up on a SF Raku Study Group meeting - and there have been various important news since - it seems fitting to announce the planned schedule for the next couple of documentation meetups, as it became publicly available at https

Re: How can I get Raku documentation on one page?

> On Sep 8, 2022, at 4:54 PM, Steve Dondley via perl6-users > wrote: > > At one point, someone generated all the documentation for Raku onto one page: > https://docs.raku.org/perl6.html > > However, this Raku documentation is badly out of date (the language is st

How can I get Raku documentation on one page?

At one point, someone generated all the documentation for Raku onto one page: https://docs.raku.org/perl6.html However, this Raku documentation is badly out of date (the language is still called Perl6). I’d like to generate or find an up-to-date version of raku’s docs and have it all on one

Re: fixing the documentation

cribió: > >> Hello, >> >> > The best would be if you propose a PR or open an issue at >> > https://github.com/Raku/doc. Any help with the documentation would >> > most certainly be appreciated as people working on the docs project >> > are overloade

Re: fixing the documentation

hello, Le Fri, Nov 19, 2021 at 07:12:13AM +0100, JJ Merelo a écrit : > Thanks a lot. well ... not sure who should thank someone here .. i meant: you spent so much more time on the raku ecosystem than i did ... thanks everyone.

Re: fixing the documentation

Thanks a lot. Cheers El vie, 19 nov 2021 a las 0:08, Marc Chantreux () escribió: > Hello, > > > The best would be if you propose a PR or open an issue at > > https://github.com/Raku/doc. Any help with the documentation would > > most certainly be appreciated as pe

Re: fixing the documentation

Hello, > The best would be if you propose a PR or open an issue at > https://github.com/Raku/doc. Any help with the documentation would > most certainly be appreciated as people working on the docs project > are overloaded. Sorry I was late on this because I wasn't sure how to

Re: fixing the documentation

Hello Marc, The best would be if you propose a PR or open an issue at https://github.com/Raku/doc. Any help with the documentation would most certainly be appreciated as people working on the docs project are overloaded. Best regards, Vadim Belman > On Aug 25, 2021, at 8:09 AM, Marc Chantr

fixing the documentation

hello people, D526P: https://docs.raku.org/language/5to6-nutshell#index-entry-PERL6LIB-PERL6LIB DFIM : https://docs.raku.org/language/modules#Finding_installed_modules DLIB : https://docs.raku.org/programs/03-environment-variables#index-entry-RAKULIB This D526P is deprecated and some RAKULIB de

Re: Module Documentation

On Tue, Mar 16, 2021 at 05:20 Elizabeth Mattijsen wrote: > > On 16 Mar 2021, at 04:22, Matthew Stuckwisch > wrote: > > I'm on board with this. I also use App::Mi6 after I saw from Elizabeth how much it helps with module development (and maintenance!). And from almost the beginning with mi6 I

Re: Module Documentation

> On 16 Mar 2021, at 04:22, Matthew Stuckwisch wrote: > > So here's my 2¢, which will probably be followed up with some actual > development of stuff (I do put my money where my mouth is… although it might > take me a while to save up to spend it ha). Some of the minor details could, > of cou

Re: Module Documentation

they should be different). Perhaps as larger projects like Red or Intl document extensive/larger documents, we can see what patterns might emerge and evaluate. (2) Just as we have /t, /lib, and /bin as standard module folders, use /doc[s] as a default space for documentation. For those that pr

Re: A problem case for the site documentation search: the "^methods" method.

Jo, For what its worth, the search page on http://raku.finanalyst.org now takes you to ^methods Previously, a search on '^methods' found the reference, but hide the location, so the link could not be clicked. That is fixed now. Regards, Richard On 10/03/2021 15:42, Joseph Brenner wrote:

Re: A problem case for the site documentation search: the "^methods" method.

JJ Merelo wrote: > This is a bug in Documentable. Generated an issue there > https://github.com/Raku/Documentable/issues/149 Thanks for the report. And thanks for opening the issue.

Re: A problem case for the site documentation search: the "^methods" method.

This is a bug in Documentable. Generated an issue there https://github.com/Raku/Documentable/issues/149 Thanks for the report.

Re: A problem case for the site documentation search: the "^methods" method.

> > > >https://docs.raku.org/language/classtut#Introspection > > > > Every other entry in that drop down menu is a red herring. > > Particularly bad is the "search entire site" because it uses > > Google, and they don't treat characters li

Re: A problem case for the site documentation search: the "^methods" method.

bad is the "search entire site" because it uses > Google, and they don't treat characters like '^' as significant > (once upon a time they had a "code search" feature, but it's > long gone). > > There *are* other place whether "^methods" i

Re: documentation of internals

> I think it is best if you open an issue for this, so that it will not fall > through the cracks. Okay, fair enough: https://github.com/rakudo/rakudo/issues/4245 On 3/7/21, Elizabeth Mattijsen wrote: >> On 7 Mar 2021, at 00:16, Joseph Brenner wrote: >> >> Is there anything like an equivalent

Re: documentation of internals

> On 7 Mar 2021, at 00:16, Joseph Brenner wrote: > > Is there anything like an equivalent of "man perlguts" for Raku/rakudo? > > There are things like this, but they seem to be very out-of-date: > > https://github.com/rakudo/rakudo/blob/master/docs/architecture.html That is indeed severely ou

documentation of internals

Is there anything like an equivalent of "man perlguts" for Raku/rakudo? There are things like this, but they seem to be very out-of-date: https://github.com/rakudo/rakudo/blob/master/docs/architecture.html

A problem case for the site documentation search: the "^methods" method.

e" because it uses Google, and they don't treat characters like '^' as significant (once upon a time they had a "code search" feature, but it's long gone). There *are* other place whether "^methods" is mentioned in the documentation, but to find them I needed t

Re: Alternative view of Raku Documentation

'virtual' files. These virtual files do not exist in the > Raku/docs directory, but are generated by the software developed to > render the POD6 files, namely Documentable. Personally, I think having > links to virtual files is fragile, and it does make the development of &g

Re: Module Documentation

On Tue, Mar 2, 2021 at 11:13 AM Tom Browder wrote: > On Tue, Mar 2, 2021 at 08:42 Daniel Sockwell > wrote: > >> Richard Hainsworth wrote: >> > My suggestion is that some formal decision is made about documentation >> for Raku modules, that some >> &g

Re: Module Documentation

On Tue, Mar 2, 2021 at 08:42 Daniel Sockwell wrote: > Richard Hainsworth wrote: > > My suggestion is that some formal decision is made about documentation > for Raku modules, that some > > documentation good practices are put together and included in the > Modules page. >

Re: Module Documentation

Richard Hainsworth wrote: > My suggestion is that some formal decision is made about documentation for > Raku modules, that some > documentation good practices are put together and included in the Modules > page. I think that this is a great idea (and that your suggestions afte

Module Documentation

Hi, I want to create a system that will show documentation about Raku Modules that I have installed. There does not seem to be a Documentation standard, or best practice, for Raku modules. Hence the following post. In the Modules documentation in the Language section of the Raku

Alternative view of Raku Documentation

le, and it does make the development of an alternative system of viewing the docs more difficult. 2: The inheritance diagrams in the standard documentation system are not cited in the official Raku docs, but are "sewn in" by Documentable based on a single text file that describes rel

Re: LTA documentation page

On 2021-01-06 yary wrote: > I have been going through quite a few contortions to look at the > source code for installed modules in raku, and would very much like > rakudoc to have an option similarly to perldoc -l showing the cached > path and hashed local file names of installed modules. zef d

Re: LTA documentation page

In the Perl world, I use perldoc all the time to view the exact documentation for the installed module I’m working with. And on a regular basis, it’s useful for me to inspect the source code of the installed modules. I have been going through quite a few contortions to look at the source code for

Re: LTA documentation page

We have a Google Summer of Code project to work on rakudoc, and the latest version of rakudoc points to "noisgul" 's repo. But ... rakudo aka p6doc was intended to work in the same way as perldoc. At the time the p6doc project was started, there was actually very little documen

Re: LTA documentation page

Can you try 'mkdir' manually beforehand to create the desired '/usr/share/perl6/site/doc' directory, then run 'zef install p6doc' ? Just wondering... . I note your other comments with great interest. Best, Bill. On Tue, Jan 5, 2021 at 9:02 AM Gianni Ceccarelli wrote: > On 2021-01-05 William Mi

Re: LTA documentation page

nline version of the documentation (or to build it themselves via Documentable) Thanks anyways for the checks, cheers El mar, 5 ene 2021 a las 18:02, Gianni Ceccarelli () escribió: > On 2021-01-05 William Michels via perl6-users > wrote: > > Raiph's suggestion works for

Re: LTA documentation page

On 2021-01-05 William Michels via perl6-users wrote: > Raiph's suggestion works for me (on rakudo-2020.10). I mean, p6doc > installs Oh, that points to new, different, problems. https://modules.raku.org/search/?q=p6doc links to https://github.com/Raku/doc which does not contain a ``p6doc`` scrip

Re: LTA documentation page

On Tue, Jan 5, 2021 at 5:10 AM Ralph Mellor wrote: > > I googled rakudoc and that led to: > > https://github.com/Raku/rakudoc > > which says it's forked from: > > https://github.com/noisegul/perl6-p6doc > > So I tried that in m.r.o and it's listed: > > https://modules.raku.org/search/?q=p6doc > >

Re: LTA documentation page

And here it comes again, the common mess about Raku and Rakudo. :) The point is that Rakudo doesn't come bundled with documentation about Raku because the former just implements the latter. It's not like it is with perl where `perl` binary and `Perl` are the same and `perl -v` is yo

Re: LTA documentation page

On 2021-01-05 Brad Gilbert wrote: > There really shouldn't be that much difference between what the > documentation says and how your version works. I've worked on machines stuck with perl 5.8 when the online documentation was for 5.26 I'd like to live in a world where:

Re: LTA documentation page

There really shouldn't be that much difference between what the documentation says and how your version works. The biggest thing would be new functions that you don't have yet. (Which you could just copy the code from the sources into your program if you need them.) Even if rakudoc d

Re: LTA documentation page

On 2021-01-05 JJ Merelo wrote: > Gianni is basically right. rakudoc has not really been released yet > into the ecosystem, and p6doc will get you the documentation itself, > which you will have to build then. So LTA is true, and there's some > work to be done. There's pro

Re: LTA documentation page

Gianni is basically right. rakudoc has not really been released yet into the ecosystem, and p6doc will get you the documentation itself, which you will have to build then. So LTA is true, and there's some work to be done. There's probably an issue already created, but it will pop up if

Re: LTA documentation page

I googled rakudoc and that led to: https://github.com/Raku/rakudoc which says it's forked from: https://github.com/noisegul/perl6-p6doc So I tried that in m.r.o and it's listed: https://modules.raku.org/search/?q=p6doc So, perhaps you can zef install p6doc? Maybe the doc you read mentioning

LTA documentation page

https://docs.raku.org/programs/02-reading-docs says to use ``rakudoc`` to read the documentation of installed modules. I don't have it installed:: $ rakudoc -bash: rakudoc: command not found Not a problem, that same page says to use zef:: $ $ zef install rakudoc ===> Searc

Re: Rakudo+ versions quoted in the documentation

On 7/4/20 3:07 PM, Parrot Raiser wrote: I just happened to look at the raku.org and raskudo.org download pages, and noticed that both quote 2020.01 as the most recent versions. https://rakudo.org/downloads has the 2020.06.01 binary download for linux but the Rakudo Star bundle page only offer

Re: Rakudo+ versions quoted in the documentation

Wouldn't the responsibility be on the web pages to keep up-to-date? That would be more a matter of agreement on the place to watch?

Re: Rakudo+ versions quoted in the documentation

On Sat, Jul 04, 2020 at 09:10:58PM +0200, Elizabeth Mattijsen wrote: > Yes. Sadly we don't have a procedure for that in place yet :-( > > > On 4 Jul 2020, at 21:07, Parrot Raiser <1parr...@gmail.com> wrote: > > > > I just happened to look at the raku.org and raskudo.org download > > pages, and

Re: Rakudo+ versions quoted in the documentation

Yes. Sadly we don't have a procedure for that in place yet :-( > On 4 Jul 2020, at 21:07, Parrot Raiser <1parr...@gmail.com> wrote: > > I just happened to look at the raku.org and raskudo.org download > pages, and noticed that both quote 2020.01 as the most recent > versions. > > Patrick Spek'

Rakudo+ versions quoted in the documentation

I just happened to look at the raku.org and raskudo.org download pages, and noticed that both quote 2020.01 as the most recent versions. Patrick Spek's dist.tyil.nl/raku/rakudo-star/ has both 2020.03 and 2020.05 for download following that. Should the sites be synchronised, preferably with a mech

Re: RFE: ini documentation

in the README of Config. Linking to random formats that aren't supported seems like a weird addition to the documentation. According to modules.raku.org[1], there's three implementations, which are included in the README already: - Config::Parser::toml - Config::Parser::yaml - Config::Pars

RFE: ini documentation

Dear Config, https://modules.raku.org/dist/Config:cpan:TYIL Would you please consider add the following reference to your web page: https://en.wikipedia.org/wiki/INI_file It gives a wonderful description of INI files. And there are folks out there that do not realize that INI files are standa

Re: Bug in the documentation

I already did. It's a rather nasty bug in the graph generation module. Will take some time. El mar., 14 ene. 2020 a las 18:16, ToddAndMargo () escribió: > > >> El lun., 13 ene. 2020 22:33, ToddAndMargo via perl6-users > >> mailto:perl6-us...@perl.org>> escribió: > >> > >> Hi All, > >> > >>

Re: Bug in the documentation

I'd be grateful if you (or someone) raised this issue in the doc repo. El lun., 13 ene. 2020 22:33, ToddAndMargo via perl6-users < perl6-us...@perl.org> escribió: > Hi All, > > https://docs.raku.org/type/UInt > > Type Graph > Type relations for 404 > > The chart is 404 missing > > To fix this, Ra

Bug in the documentation

Hi All, https://docs.raku.org/type/UInt Type Graph Type relations for 404 The chart is 404 missing To fix this, Raku can use the chart from https://docs.perl6.org/type/UInt https://docs.perl6.org/images/type-graph-UInt.svg Picky, Picky, Picky :-) -T

Re: A grand idea on the documentation

On 2019-12-10 07:31, Tom Browder wrote: On Mon, Dec 9, 2019 at 12:49 Peter Scott <mailto:pe...@psdt.com>> wrote: ... Developers need reminders, in the most succinct form, to minimize time, of data that they should not need to memorize.  The documentation satisfies that ne

Re: A grand idea on the documentation

On Mon, Dec 9, 2019 at 12:49 Peter Scott wrote: ... Developers need reminders, in the most succinct form, to minimize time, > of data that they should not need to memorize. The documentation > satisfies that need in the same way that a phone book satisfies the need > to look up someone

Re: A grand idea on the documentation

On 2019-12-09 07:00, Elizabeth Mattijsen wrote: For some odd reason, some folks thought I was calling him an actual dog (canine). Would you have been similarly offended if I had called him a "gatekeeper"? If you call someone a dog I did not. It is a figure of speech. Please stop twisting

Re: A grand idea on the documentation

On 2019-12-09 07:28, Curt Tilmes wrote: On Mon, Dec 9, 2019 at 10:08 AM Simon Proctor > wrote: I find both the implications of "guard dog" and "gatekeeper" unfair ways to talk about anyone on the community especially JJ. I understand that the intent wa

Re: A grand idea on the documentation

jobs. If you're trying to get rid of the people who write Raku documentation (who, contrary to your labeling, are not teachers but developers, and either way, unpaid), you're making fine progress. Oh good lord no. I am not trying to get anyone fired! I am trying to get the docs

Re: A grand idea on the documentation

, I actually got rid of two bad teachers.  Ya, I am a bit of jerk over teachers that take my money and don't do their jobs. If you're trying to get rid of the people who write Raku documentation (who, contrary to your labeling, are not teachers but developers, and either way, unpai

Re: A grand idea on the documentation

On Mon, Dec 9, 2019 at 10:08 AM Simon Proctor wrote: > I find both the implications of "guard dog" and "gatekeeper" unfair ways > to talk about anyone on the community especially JJ. > I understand that the intent was derogatory, but I would encourage JJ to take it as a compliment. He is a belo

Re: A grand idea on the documentation

> On 9 Dec 2019, at 15:26, ToddAndMargo via perl6-users > wrote: > > On 2019-12-09 03:47, Elizabeth Mattijsen wrote: >>> On 9 Dec 2019, at 10:32, ToddAndMargo via perl6-users >>> wrote: >>> On 2019-12-09 00:33, JJ Merelo wrote: >>>> T

Re: A grand idea on the documentation

On 2019-12-09 06:41, Simon Proctor wrote: I find both the implications of "guard dog" and "gatekeeper" unfair ways to talk about anyone on the community especially JJ. Hi Simon, JJ is indeed a great guy. That is not up for debate. He is just a little too protective when he is on duty. "guard

Re: A grand idea on the documentation

On 2019-12-09 06:23, Elizabeth Mattijsen wrote: On 9 Dec 2019, at 14:45, ToddAndMargo via perl6-users wrote: On 2019-12-09 01:39, Tom Blackwood wrote: It's rude on a public list to speak that. Did you seriously think I was calling him a real dog (canine)? So what did you intend to convey wi

Re: A grand idea on the documentation

> >> On 9 Dec 2019, at 10:32, ToddAndMargo via perl6-users < > perl6-us...@perl.org> wrote: > >> On 2019-12-09 00:33, JJ Merelo wrote: > >>> The Raku community has got a community documentation. It's called the > official documentation, and it's done

Re: A grand idea on the documentation

On 2019-12-09 03:47, Elizabeth Mattijsen wrote: On 9 Dec 2019, at 10:32, ToddAndMargo via perl6-users wrote: On 2019-12-09 00:33, JJ Merelo wrote: The Raku community has got a community documentation. It's called the official documentation, and it's done by the community. You wan

Re: A grand idea on the documentation

> On 9 Dec 2019, at 14:45, ToddAndMargo via perl6-users > wrote: > On 2019-12-09 01:39, Tom Blackwood wrote: >> It's rude on a public list to speak that. > Did you seriously think I was calling him a real dog (canine)? So what did you intend to convey with the use of the word "guard dog"? That

Re: A grand idea on the documentation

On 2019-12-09 02:48, JJ Merelo wrote: No, it's not. I simply tried to direct you to raise an issue to where it would actually be heard by the people that maintain that. For you that don't know what JJ and I are talking about here, you can read it over at zef requires git https://github.com/rak

Re: A grand idea on the documentation

;re lost". They never, however, convert their inability in understanding something in a judgment on the quality of the material used for learning, which has probably been evolved through generations of other fellow students, so it's as good as it needs to be. You don't want to learn

Re: A grand idea on the documentation

On 2019-12-09 01:39, Tom Blackwood wrote: It's rude on a public list to speak that. Did you seriously think I was calling him a real dog (canine)? JJ! I do not think you are a canine. -T

Re: A grand idea on the documentation

> On 9 Dec 2019, at 10:32, ToddAndMargo via perl6-users > wrote: > On 2019-12-09 00:33, JJ Merelo wrote: >> The Raku community has got a community documentation. It's called the >> official documentation, and it's done by the community. You want to write >>

Re: A grand idea on the documentation

ió: > > > > On 2019-12-09 00:33, JJ Merelo wrote: > > > The Raku community has got a community documentation. It's called > > the > > > official documentation, and it's done by the community. You want > to > > > write y

Re: A grand idea on the documentation

On 2019-12-09 01:52, JJ Merelo wrote: El lun., 9 dic. 2019 a las 10:34, ToddAndMargo via perl6-users (mailto:perl6-us...@perl.org>>) escribió: On 2019-12-09 00:33, JJ Merelo wrote: > The Raku community has got a community documentation. It's called the

Re: A grand idea on the documentation

El lun., 9 dic. 2019 a las 10:34, ToddAndMargo via perl6-users (< perl6-us...@perl.org>) escribió: > On 2019-12-09 00:33, JJ Merelo wrote: > > The Raku community has got a community documentation. It's called the > > official documentation, and it's done by the c

Re: A grand idea on the documentation

On Mon, Dec 9, 2019 at 5:34 PM ToddAndMargo via perl6-users < perl6-us...@perl.org> wrote: > On 2019-12-09 00:33, JJ Merelo wrote: > > The Raku community has got a community documentation. It's called the > > official documentation, and it's done by the community.

Re: A grand idea on the documentation

On 2019-12-09 00:33, JJ Merelo wrote: The Raku community has got a community documentation. It's called the official documentation, and it's done by the community. You want to write your own and help yourself and maybe others, there're lots lof places you can do that: dev.to

Re: A grand idea on the documentation

The Raku community has got a community documentation. It's called the official documentation, and it's done by the community. You want to write your own and help yourself and maybe others, there're lots lof places you can do that: dev.to, Medium, your own blog. Even the "o

Re: A grand idea on the documentation

On 2019-12-08 18:05, ToddAndMargo via perl6-users wrote: Hi All, I have a "grand idea" on how to fix up the documentation I would like to pitch to the community: > Lets create our own community documentation Wikipedia. I would like "Community Documentation&quo

A grand idea on the documentation

Hi All, I have a "grand idea" on how to fix up the documentation I would like to pitch to the community: Raku's documentation is pretty much unusable for newbies and regular users do to its culture: IEEE-eese like "method contains(Cool:D: |c)" and so on and so forth. S

Refactoring of the documentation system.

General notification! The community members working on the documentation system are deploying a new refactored system. Hopefully, no one will notice a difference on the docs.perl6.org page. When the next Rakudo Star is released p6doc will be working. However, murphy rules! So some warning

Re: documentation translation effort ?

hello, On Tue, Jul 09, 2019 at 11:28:29PM +0200, Laurent Rosenfeld via perl6-users wrote: > I have updated the Wikipedia page linked in Marc's message. @Marc: please > check it and let me know if you see any remaining issues. reading the fix, i realized i mixed up the errors of the linuxfr page

Re: documentation translation effort ?

I have updated the Wikipedia page linked in Marc's message. @Marc: please check it and let me know if you see any remaining issues. @JJMerelo: I have devoted a lot of efforts translating various P6 documentation into French over the last 5 years or so, including perl6intro, and probably 2

Re: documentation translation effort ?

hello, > There have been some efforts to translate perl6intro; but as Laurent says, > we can hardly say the documentation is complete, so diverting resources to > translation is probably not such a good idea. yeah. when laurent spoke about a moving target, i gave a look at the doc repo

Re: documentation translation effort ?

ing the whole Perl 6/Raku documentation is a totally different > game. It's just too big (and it's a moving target), I won't undertake that. Having the official documentation translated could be a really good thing for the perl6 adoption in France so i think we have to think about i

Re: documentation translation effort ?

There have been some efforts to translate perl6intro; but as Laurent says, we can hardly say the documentation is complete, so diverting resources to translation is probably not such a good idea. El mar., 9 jul. 2019 a las 21:53, Laurent Rosenfeld via perl6-users (< perl6-us...@perl.

  1   2   3   4   5   6   >