Long story super short:

Founder restricted access heavily so we (core maintainers) cannot do much at all
Founder disappeared off the face of the earth and we heard nothing
We (core maintainers) raised this internally and asked it be sorted
Nothing was sorted, so @PeterDaveHello has quit maintaining the project
- As part of this, they appear to have disabled our updating automation (I disagree with this action, it harms the existing users of the service)

We have an on-going internal discussion to get this resolved but this is the current state of affairs, nothing has really progressed since we (core maintainers) first raised the access issue internally in late September.

Key immediate issues:

Auto-update bot is offline
~~Core maintainers do not have merge access in this repo (cdnjs/cdnjs)~~
Core maintainers do not have merge access (preferably admin access) to other repos in org
- Such as cdnjs/new-website

Key long-term issues:

Current repo structure is not maintainable
- Repo is extremely large and a pain to work with locally
- Whilst the CI on PRs is good, it requires human intervention still
Auto-update/CI bot lacks some important functionality
- Set of issues opened around this: 🤖 PeterBot
No direct financial sponsorship (or any funding) for core maintainers to work on cdnjs

Update 1:

I reached out again to the founder in question yesterday (October 20th) to see if we can get any progress as we have both Microsoft (in #13500) and Greensock [GSAP] (in my Twitter DMs), who are both "big players", asking what's going on.

I actually got a response that they're going to sort something so that we (core maintainers) at least have access to merge PRs in this repo, nothing more though so far...

Update 2:

We (core maintainers) now (October 22nd) have access to merge PRs on cdnjs/cdnjs but the auto-update bot is still offline (as was originally described in this issue), so merging new and updated package.json PRs will achieve nothing as there is no bot to detect them and pull in new assets. We are still working internally to resolve this.

Update 3:

I followed up internally again on the 29th October regarding the two current key issues (auto-update & repo access). This issue has then made it to the front page of HackerNews (1st November) and still there has not been any progress internally, just radio silence. I'm really sorry we haven't got this sorted yet. :(

Update 4:

One of our founders has reappeared and granted Cloudflare full owner access to the cdnjs org to get things fixed. I believe that Cloudflare are going to have one of their engineers work to get things back up and running again. You can see the full comment from Zack below: #13524 (comment)

Uh oh!

Lack of cdnjs activity #13524

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions