Very exciting that you're willing to move things forward more
aggressively, and i personally also appreciate the stance towards code
review. :)
My Github id is wchristian and my pubkey is:
ssh-rsa
AAAAB3NzaC1yc2EAAAABJQAAAQEAkkUw2DyZfgRfGi4tAfbdxeSNWm6jYVRi4MjK1MeqJB93rfyraBxIWaP1H5zhzBvMh8mYhY+bax2n+DBxI4yuJzDIrYExPApX+Lh2r839xz4yTYDmw9aYYFmEUqoZNmUMtG/GnKrsY02hw2Inh5nbPziN6U5a9WIBc5DEd+5GK//JKp7uFWG32T9q7ByOHetBJn02tMjLCGmgnGtVoPQIRQKlUr2QSIXBjkA4UymmM4UX7ERSt3HrmRrWLoZNUKuGrrIY1OkI6XXGlO4jVZPj6yyR3BLq8jJT0gHhOXb3lpaw8kcqUdlQA4b9SkiZUazG+JXrFpJRPUvTEl6h/fbuCw==
rsa-key-20170216 2048 Christian Walde
As for a meeting, i'm very flexible and happy to join anytime Ruth and
Scott have time.
Something to also be considered is roping in BINGOs
https://metacpan.org/author/BINGOS who has offered help, and if you
don't know him yet, he runs servers that produce a lot of cpantesters
smoke reports, as well as various other services for the perl community
and is a "sysadmin with 30 years experience of managing data centre
infrastructure including physical and virtual hardware of various
operating systems, Windows and UNIX".
--
With regards,
Christian Walde
On 17/04/2025 05:51, Doug Bell wrote:
I can get y'all set up in the CPAN Testers GitHub organization if you
send the GitHub ID I should use for that. Most/all of the current
development happens there and is deployed from Rexfiles in the
individual repos. I'll make sure I haven't left any in-progress dev on
my laptop here.
Those deployments use SSH, so I can set those accounts up tomorrow. I
have Scott's SSH key already, so I'll need Ruth's if she also wants one.
It's not a necessity, but it would increase coverage of folks who can
poke the thing when something's wrong.
In general, I don't need SSH for anything outside of deployment and
debugging. It's all test-driven development with locally-built SQLite
databases to help ensure database portability in the hope of a Postgres
migration. Likely we can figure out some PR/merging processes, as I
personally like having someone else give my code a look-over to keep
myself accountable (and spread the blame for crashes ;)
If we can adapt anything y'all have already done to the Mojolicious
frontend app (https://github.com/cpan-testers/cpantesters-web <https://
github.com/cpan-testers/cpantesters-web>), I think it'd be worth it: The
UI in there right now is a bare-bones Bootstrap 4 setup with basically
no actual style (though I was experimenting with Web Components for
partial page updates and have been pleased with the results so far). The
only interesting UI thing I've been able to put together was a proof-of-
concept w/ charts: http://beta.cpantesters.org/chart.html?dist=Log-
Any&version=1.714 <http://beta.cpantesters.org/chart.html?dist=Log-
Any&version=1.714> . I dunno why it says the CORS headers are bad, but
if I refresh it enough it finally works... :p
We can schedule some kind of real-time meeting next week if y'all want.
I'll be free from Tuesday on. In the meantime I can gather up my notes
on things outstanding / in-progress (but mostly it's the data problem
and a replacement for the e-mailed report sender).
Doug Bell
d...@preaction.me <mailto:d...@preaction.me>
On Apr 6, 2025, at 3:14 PM, Scott Baker <sc...@perturb.org
<mailto:sc...@perturb.org>> wrote:
Doug:
I just want to re-iterate what Ruth said: we want to work *together
*with you /and /the community make CPT the rock solid, reliable tool
that the community is used to. As a module author CPT is an invaluable
tool to know how things perform in the "real-world" beyond my local
machine.
There have been multiple conversations on IRC #cpantesters-discuss
with people expressing concern and offering help for CPT. It's a
very /well regarded /tool in the Perl community. Would you be amenable
to a mini-meeting on IRC (or Zoom) prior to PTS to talk about the
health and status of CPT as it stands today? It might be helpful to
get everyone at least on the same page prior to PTS so we can maximize
the in-person time to coming up with solutions.
I setup remote monitoring of CPT using Nagios <https://
www.perturb.org/nagios/vshell/services.php?
host_filter=cpantesters.org> (user/pass: readonly) so the community
would have some historical reporting about CPT's uptime. If I check it
right now I can see that the API has been down for the last four
hours. Is there is anything I can do short term to help with the
system, I'd be happy to donate some of my time.
I am the Senior System Administrator for DirectLink. I've been doing
Linux system administration for 20+ years now. If there is anything I
can do on the server side to help take some of the burden off of you
please let me know. I would be happy to help with system tasks. I run
our local OSS mirror: https://mirror.web-ster.com/. I can also spin up
some compute VMs for CPT if there is need for that. There was also
some discussion about getting some VMs donated by the FSF as well.
If you're open to some help my SSH key is: ssh-ed25519
AAAAC3NzaC1lZDI1NTE5AAAAIOwvHmHSRjm3i6d1O5Se9RuiV9Te3OCihJuScS1IV1zX
bak...@basement.web-ster.com
-- Scottchiefbaker
On 4/6/2025 11:45 AM, Ruth Holloway wrote:
Doug,
Thank you so much for your well-thought-out response in this thread.
The Perl Magpie team--at the moment--is composed of Scott Baker and
myself; we were riffing on IRC about how to provide more consistent
access to test results, and the idea for the Magpie running in
parallel to the existing system as a source of test results was
born. There's been some prototyping done, with some happy successes,
but it is by no means a production-ready product. Scott had shown
off those results in the IRC channel, and there were a few folks who
made suggestions, and a few offers of assistance. That's the history,
as it stands now.
[snipped]
