Currently the right hand side of the perl6.org website "Recent Blog Posts" is dependent on an external system "pl6anet.org" via
https://github.com/perl6/perl6.org/blob/master/fetch-recent-blog-posts.pl
This system will be closing down in about 30 days time and will need someone to work on a replacement if the "Recent Blog Posts" box is to continue.
Hosting a replacement is easy and details are at
@stmuk: thank you for supporting this service all of this time.
I will take over the hosting.
@stmuk: Are you the owner of the domain and can we take over it as well?
Without takeing a closer look, there is no data to migrate, right? These feeds are all still available an it's just aggregated. (?)
@rba I'm the domain owner via Namecheap and it's about to expire. I can probably transfer if anyone wants it. You are correct about it just being datafeed based.
@stmuk I think we should continue it, as is for the moment. I've using gandi.net as my current registrar with a separate handle for perl6-infra. I will take over the domain if this is ok for you. Please "unlock" for transfer. (https://www.namecheap.com/support/knowledgebase/article.aspx/258/84/what-should-i-do-to-transfer-a-domain-from-namecheap)
@rba I have unlocked and have an auth code.
@stmuk Thanks for letting me take over the domain. The transfer is finished. I've change DNS servers too. pl6anet.org is still pointing to your current hosting ip atm. Will move the build+hosting in the next few days. Update follows.
Thank you, @stmuk and @rba.
@rba Thanks for all this!
I'll be shutting down the service in about a week on the current server.
migrated!! rba++
@rba when will the new service be online, I want to update my URL for my blog.
@cbk The service is online. Please update https://github.com/perl6/pl6anet.org/blob/master/perlanetrc directly (or via PR).
Thank you.
Sent from my iPhone
On Oct 6, 2019, at 11:10 PM, Roman Baumer notifications@github.com wrote:

@cbk The service is online. Please update https://github.com/perl6/pl6anet.org/blob/master/perlanetrc directly (or via PR).—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Most helpful comment
@stmuk: thank you for supporting this service all of this time.