Documentation Channel for #raku | This channel is logged | Roadmap:
Set by [Coke] on 23 May 2022.
[Coke] complaints that there is an "issue issue" are not helpful. Yes, I know we have a backlog. 00:00
NemokoschKiwi and that's the unironic part of the "let them come up with suggestions themselves"
[Coke] we just fixed the single most important blocker to that backlog that we've had for some time, even before JJ left - getting updated content into prod was very slow, or (later) impossible.
I don't know what you mean by "suggestions"
We are now actually starting to get through the backlog. 00:01
cfa++ has done many updates recently!
NemokoschKiwi why does this feel so defensive... 00:02
[Coke] I am defensive. Please trust me, I've toned it down several levels before typing. 00:03
so far, your complaint itself is not actionable.
cfa NemokoschKiwi: i'm not clear what you're asking? 00:04
[Coke] excellent question.
NemokoschKiwi I haven't opened an issue for it, though, I'm just saying. It hurts no one to acknowledge.
cfa my understanding is that there are issues that have been prioritised for q1; as always, issues require volunteers to address them
[Coke] acknowledge what?
That we have a large backlog? agreed. 00:05
Geth doc-website/at_timezone_to_footer: df182159ec | finanalyst++ | Website/plugins/ogdenwebb/ogdenwebb-replacements.raku
Add time zone to creation time.
NemokoschKiwi That these issues are hard to address, and therefore are highly unlikely to be finished by any deadline.
[Coke] That a newbie isn't going to be able to pick up a random ticket and work on it? agreed.
No, disagree. I specifically picked tickets that I think I can close in that timeframe even with no volunteers except for those particularly assigned to someone else. 00:06
NemokoschKiwi They are mostly hard to address because it's often not clear what the reporter wants to be solved
Geth doc-website: finanalyst++ created pull request #173:
Add time zone to creation time.
[Coke] and with those assigned to someone else, it's a request they prioritize, since this is all just volunteer work.
No, that's not true.
I specifically chose ones that I feel can be done in that time frame, and that the request is clear.
NemokoschKiwi accidentally, I didn't point at a single one assigned to you
[Coke] So, I disagree with your assertion. Even if you were right, your best bet to help things get done is to pick tickets that *you* think are actionable and work on those. 00:07
I would prefer you did not reach out to folks on tickets that you're not assigned to, because you have a way of coming off as confrontational, and I'd rather not have our users deal with that. 00:08
but if you want to pick one, confer with me, talk about it before talking to the user, that's fine, happy to get another volunteer.
NemokoschKiwi As things stand, that would basically mean that I would be refraining from most activity 00:09
[Coke] Sure.
like I said, if you want to dig through the tickets and find one you think is actionable, go for it.
if that's too much effort, I completely understand. the backlog is pretty big. 00:10
NemokoschKiwi Anyway, I don't think this is the right time to talk about that. You know what is confrontational now - to act as if I just said I murdered someone, when I really just pointed out something very apparent about the nature of these issues.
cfa unrelated to all this: i think my css update was noisier than it ought to have been because i have a slightly different version of sass installed
[Coke] cfa - whoops
cfa there were a series of whitespace changes that probably wouldn't have occurred if i had the node rather than ruby one
[Coke] nope. I didn't act that way. You're overreacting.
NemokoschKiwi Or you are, who knows
[Coke] But please feel free to file an issue with the appropriate RSC committee. 00:11
coleman cfa: what's the formatting command? we can add it to CI 00:12
maybe even fail the build if there's a diff (assuming we can get it to be reliable)
or is this literally the compiled CSS output
[Coke] hard to know what's an intentional diff and what's not intentional
coleman youre right. It's not really a source code formatter. It's a compiler :D 00:13
cfa: disregard 00:14
NemokoschKiwi I'd much rather file an issue for you to chill down. All is fine; probably most of those issues won't be finished any time soon but it's not like anyone is to blame for it. Perhaps it would be good if certain knowledgeable people opened better described issues.
[Coke] Open an issue about... the issues?
That will no doubt get closed as "not intended".
I mean, it depends on the ticket, but if it's the same as this conversation, I don't expect it will be actionable. Again, please feel free to surprise me. 00:15
cfa re: sass, 00:16
coleman: maybe relevant? ^
[Coke]: we can always diff -w 00:17
coleman Perfect. Thanks!
cfa but yeah, this is my faul
i didn't twig that maybe the version difference resulted in spacing differences
NemokoschKiwi Tbh I still don't see how it's not actionable to ask people in the core community to actually come up with a suggestion at least about the "where" part of the "write the docs"
cfa if we clarify the correct version, i propose a commit that just updates the css again to reformat correctly
but... we ought to figure out the "green theme" issue before making any css changes 00:18
NemokoschKiwi does the "green theme" still persist?
cfa i defer to coleman and [Coke] 00:19
coleman I think it's probably still going to happen until we implement some sort of cache-busting strategy at build-time
But I suspect there's some deeper reason that cache-busting might just mask 00:21
[Coke] green mode went away in less than a day 00:23
might have been a cache that finally expired, no idea.
guessing richard's stuff won't be 100% before tomorrow, so no prod rollout tonight. I also just pushed a branch to raku/doc that moves pod6 to rakudoc, but looks like I missed a commit so there's a conflict. I'll deal with that tomorrow. 00:25
NemokoschKiwi anyway, so far so good, I would say. Most new issues are related to the search, some to mobile, that's not surprising
did anybody check Mastodon?
[Coke] afk
00:34 NemokoschKiwi left
Geth ¦ doc: cfa self-assigned Document trap: `use lib` with a huge directory is super slow 01:52
02:33 rf left 02:57 samebchase2 joined 02:58 samebchase left, samebchase2 is now known as samebchase
Geth ¦ doc: coke self-assigned Change document extension from .pod6 to .rakudoc 03:11
doc/main: 7a54ae3f3f | (Will Coleda)++ | 5 files
remove unused utils

add comments to remaining items so we know what they're for.
Closes #3906
¦ doc: coke assigned to codesections Issue util/list-missing-methods failure 04:36
¦ doc: coke unassigned from taboege Issue Checklist for 2019.03 04:38
doc/main: a6f46aeffc | (Daniel Green)++ | CREDITS
Add myself to the credits
05:33 melezhik joined
melezhik [Coke] and the team - greate work with a rakudoc new website! 05:33
05:41 melezhik left 05:43 melezhik joined 06:00 melezhik left 09:10 sena_kun joined 09:50 sena_kun left 10:14 sena_kun joined 10:18 sena_kun left 10:55 sena_kun joined
sena_kun wow, so the new website is already up 11:54
thanks to everyone who contributed to this!
Geth ¦ doc-website: Altai-man assigned to finanalyst Issue Mobile/small display optimized styling 12:08
doc: tbrowder++ created pull request #4224:
Correct the intended zero-width index entries
12:56 jjatria left 13:01 jjatria joined
[Coke] melezhik: I appreciate the callout, but it's mostly team and only a little [Coke]. :) 14:11
Geth ¦ doc: coke unassigned from Scimon Issue Proc::Async Example needs to be modified to run on Windows 10 14:12
¦ doc: coke self-assigned Proc::Async Example needs to be modified to run on Windows 10
¦ doc: coke assigned to tbrowder Issue update humorous subtitle 14:18
¦ doc: coke self-assigned Differentiate clearly "version" and "release" 14:21
¦ doc-website: Altai-man self-unassigned Put “Raku” in page titles 14:23
[Coke] sena_kun: sorry about that, should have unassigned before transferring. 14:36
sena_kun no worries
[Coke] updated doc wiki (we should get those updates here, but not in #raku 14:41
not sure how to configure geth for that, or if it can.
updated language about the site (now live) and quarterly milestones (now in effect)
14:43 Altai-man joined 14:44 sena_kun left
[Coke] monthly call coming up next weekend (10 days) 14:57
Let's go into the call with an agenda. (but let's not wait for the call to address items)
coleman: my impression is that it should be safe to push to prod, do you agree? 14:58
15:26 rf joined
[Coke] deployed. now working 15:30
Geth ¦ doc-website: coke assigned to finanalyst Issue Create 404 page 15:34
cfa thanks [Coke] 15:48
Geth doc-website/404-text: 04a15f556c | (Will Coleda)++ | Website/structure-sources/404.rakudoc
Simplify/update text for 404 page

Part of #164
doc-website: coke++ created pull request #178:
Simplify/update text for 404 page
[Coke] ^^ I have, based on some email convos with Richard & Coleman, enabled "require approval" on PRs to main for doc-website. 16:35
Now that we're live, seems prudent.
Starting with mine that I just submitted.
Geth doc-website/remove_generated_rakutm: ff7fcdd8bd | finanalyst++ | 6 files
addresses issue #162

  - Remove git-reflog plugin altogether
  - Remove 'generated' and `rakutm` popups.
  - Leaving License as a popup for the time being.
doc-website: finanalyst++ created pull request #179:
addresses issue #162
cfa it looks like the css for (bullet) lists need to be updated 17:06
we currently have ul { list-style: none; } 17:08
take a look at, for example
Geth doc/finanalyst-patch-1: 1da99fc750 | (Richard Hainsworth)++ (committed using GitHub Web editor) | doc/Language/community.pod6
Update community.pod6

Remove reference to as it no longer exists
doc: finanalyst++ created pull request #4226:
Update community.pod6
doc/main: ade0e7f024 | (Richard Hainsworth)++ (committed using GitHub Web editor) | doc/Language/community.pod6
Update community.pod6 (#4226)

Remove reference to as it no longer exists
doc-website: cfa++ created pull request #180:
Document the correct `sass` version, refresh CSS
doc/finanalyst-patch-3: ec9a23baad | (Richard Hainsworth)++ (committed using GitHub Web editor) | doc/Language/faq.pod6
Update faq.pod6

edit the zef url so that it is recognised by remove reference to p6doc, which is not being found there,
doc/finanalyst-patch-1: 2147d8e975 | (Richard Hainsworth)++ (committed using GitHub Web editor) | doc/Language/modules.pod6
Update modules.pod6

The example changed. So make the link work.
doc: finanalyst++ created pull request #4228:
Update modules.pod6
doc/finanalyst-patch-4: a80750c26d | (Richard Hainsworth)++ (committed using GitHub Web editor) | doc/Language/modules-extra.pod6
Update modules-extra.pod6
doc: finanalyst++ created pull request #4229:
Update modules-extra.pod6
doc/finanalyst-patch-5: f5b68eb63f | (Richard Hainsworth)++ (committed using GitHub Web editor) | doc/Type/DateTime.pod6
Update DateTime.pod6
doc: finanalyst++ created pull request #4230:
Update DateTime.pod6
18:10 Altai-man left
[Coke] BTW, all raku/doc PRs show as failing tests, hoping we can fix our CI in the next few weeks. 18:25
If you'd otherwise approve one of the PRs, don't let that stop you. I'm running the tests locally whenever someone commits to main and will catch out anything there before a prod push 18:26
Geth doc/main: a575049cda | (Richard Hainsworth)++ (committed using GitHub Web editor) | doc/Language/modules.pod6
Update modules.pod6 (#4228)

The example changed. So make the link work.
doc: cfa++ created pull request #4231:
Document potential performance penalties for filesystem repos (#2199)
doc/main: 160b0cfd87 | cfa++ (committed using GitHub Web editor) | 2 files
Document potential performance penalties for filesystem repos (#4231)

Closes #2199.
[Coke] BTW, coleman - I think self merge is OK as long as someone else approved the PR. I assume you meant that a single person shouldn't submit and merge with no feedback. 18:43
19:17 sena_kun joined
Geth doc: cfa++ created pull request #4232:
Clarify the role of META6.json in filesystem repos
doc/main: 60c752d207 | cfa++ (committed using GitHub Web editor) | doc/Language/traps.pod6
Clarify the role of META6.json in filesystem repos (#4232)

Relates to #2199 and comments on #4231.
coleman [Coke] I agree 21:16
[Coke] Hey, the site looks very broken. 21:42
looks like all the CSS was missing. I opened the console, did a refresh, now it's back 21:43
anyone else seeing issues?
before opening the console, I soft refreshed several times, still just plain text.
sena_kun [Coke], cannot confirm 21:48
rf Google still points to a lot of non .html files, for example, if you search for given on google you'll be given a dead link 21:54
[Coke] non html files work now 21:55
note that isn't there either.
Please open a ticket for that one, rf.
That's actually missing. 21:56
coleman: even if we can't get direct access to the logs yet, can you extract the 404s for us and throw them in a gist? 21:57
I imagine there's quite a few of these issues, be nice to get them fixed before we get tickets.
Geth doc-website/main: 751ae087a3 | (Will Coleda)++ (committed using GitHub Web editor) | Website/structure-sources/404.rakudoc
Simplify/update text for 404 page (#178)

Part of #164
¦ doc-website: coke assigned to finanalyst Issue Some .html files aren't being generated 22:12
[Coke] rf, updated the ticket and assigned it 22:13
rf No problem! 22:14
23:14 sena_kun left
Geth doc/main: 68ea242952 | (Will Coleda)++ | 2 files
run duplicate check on more files.

  ... fix the bug that prompted this
doc/main: 0f59e32295 | (Will Coleda)++ | 2 files
pass 'make xtest'