| 27 May 2024 | |||
| lizmat | re github vs gitlab: some people do not want to be involved with Github anymore because of MS | 14:04 | |
| and we have to accept that | |||
| tbrowder | lizmat, we don't accept behavior we don't like, so, in some way, what is the difference? imho, we should be trying to unify the community to grow use of raku. splintering into little-used infra doesn't help. | 14:42 | |
| i love raku. i want to see if grow. | |||
| *it | |||
| the avg age of users is not decreasing | 14:43 | ||
| lizmat | true, but we're all volunteers, and if a volunteer decides to open source their project on a different place than that we're used to | 14:44 | |
| there's not a lot we can do but to kindly ask them if they'd be willing to move | |||
| and that question has been asked in the past, and the answer was no | 14:45 | ||
| so we will have to either live with it, or set up a similar service of your own | |||
| I chose live with it :-) | |||
| tbrowder | sigh..., ok then, thnx | 14:46 | |
| jjatria | FWIW, I think I'm on the record as saying that I don't really care where the code is hosted, but that it would be a pity if we got to a point where things _had_ to be hosted on a specific platform for them to work | 16:43 | |
| In that sense, I'm more against monopolies than I am against MS | |||
| But if there's a feature someone would want to implement on RL, and they prefer the GH interface, I'd be happy to review a GH fork and make sure the code ends up where it needs to be, even if we don't move away from GL | 16:44 | ||
| coleman | GitLab even lets you log in with a GitHub account. It's quite accessible. | 17:43 | |
| jjatria: if you haven't already, a GitLab->GitHub read-only push fork could aid discoverability. Then, if you are willing, people could indeed fork that and you could review the diffs if you so choose. But to be honest, I think we are too concentrated on GitHub, but it is hard to unwind, because we use GitHub authorization groups to govern some important stuff. | 17:45 | ||
| Actually, a pull-fork from GitHub might be easier... | 17:47 | ||
| Ah it looks like GitHub doesn't do automatic mirroring | 17:54 | ||
| 11 Jul 2024 | |||
| Hetzner is reporting an incident. But it is unclear why it would affect us. | 18:09 | ||
| 22 Jul 2024 | |||
| sjn | \o | 18:15 | |
| 2 Aug 2024 | |||
| jjatria | sjn: o/ | 14:53 | |
| coleman | \o/ | 17:39 | |
| sjn | hey, are any of you up for having a chat about metadata in raku.land? | 22:25 | |
| well. raku.land, and the packages it helps distribute | 22:26 | ||
| (what zef outputs may also be relevant, btw) | 22:27 | ||
| sjn has done a somewhat sizable work on this topic on behalf of the CPAN Security Group, in preparation of those new regulations coming all over the place (US, EU, Singapore and Japan for now), and I'm thinking having a sync around the Raku package ecosystem is probably a good idea | 22:29 | ||
| if someone wants to/has tuits/cares about such things, of course | |||
| 5 Aug 2024 | |||
| tonyo | is there concern or just wanting info? | 16:45 | |
| sjn | tonyo: well, "changes are afoot", one could say. :-) | 20:59 | |
| I'm happy to share some of my findings (and I think these are likely to be super useful and/or interesting in addition to important and reqiured) – if someone here is interested :-) | 21:00 | ||
| there several concerns to be aware of regarding metadata fields, their whys and whats, and on how this metadata should be updated and later made available to the different actors/roles/services found throughout the ecosystems and supply-chain | 21:02 | ||
| jjatria | sjn: raku.land only aggregates data from other sources (mainly, the META files from the distributions uploaded to the various ecosystems, and the author / org data exposed by zef). So we will reflect the changes in the data upstream | 21:11 | |
| I'm interested in the work of the CPAN security group in general, but I might find it difficult to find time to talk soonish (I've got a newborn at home) | 21:12 | ||
| sjn | jjatria: no hurries, though some of the material may require a good think/discussion :-) | 21:35 | |
| jjatria: are you planning on attending LPW? | 21:37 | ||
| 6 Aug 2024 | |||
| jjatria | sjn: I am! I'll be giving a talk about my Perl OpenTelemetry work. We should be able to catch up there if not sooner | 14:41 | |
| sjn | ok, cool | 15:19 | |
| sjn needs to submit a talk too | |||
| and find a place to stay, and a flight to catch... | |||
| lizmat | jjatria: I'm seeing some updated of modules on gitlab, e.g. raku.land/gitlab:stmuk/Task::Galaxy | 16:34 | |
| the only reason I think this was done, is that I left an issue there that it would not be updated anymore | |||
| gitlab.com/stmuk/p6-task-galaxy/-/issues/2 | 16:35 | ||
| seems like adding an issue triggers "new module" logic? | |||
| tonyo | i'd be interested to know too since i make available the metadata authors would like public via zef eco | 18:36 | |
| lizmat | jjatria: Interested in taking over Terminal::WCWidth, or shall I move it to the Raku Community modules? github.com/bluebear94/Math-Random/...2271825298 | 19:59 | |
| 7 Aug 2024 | |||
| jjatria: Terminal::WCWidth now in raku community modules with your patch applied | 15:24 | ||
| 18 Aug 2024 | |||
| jjatria | lizmat: will look into the GitLab updated logic snafu, and thanks for looking into that Terminal::WCWidth distro! I had forgot about my patch :P | 20:45 | |
| Also: newborns are a lot of work 💦 | |||
| JRaspass | I suspect/hole there's a different field we can use in the Git{Lab,Hub} GraphQL to get the last commit rather than last change | 20:49 | |
| *hope | |||
| 24 Aug 2024 | |||
| coleman | best of luck jj :) | 17:17 | |
| 27 Aug 2024 | |||
| jjatria | Thanks! | 19:56 | |