Is this really true though, now? With the latest Pkg version, you can have all these good stuff and versioning you want on the basis of essentially replacing “version” with “git commit” (which as far as I understand were always one and the same modulo some relabelling). I don’t want to take this off topic, but I think “accessing Pkg infrastructure” is not a strong enough argument to allow registering anything anymore. We can now do it without registering.
In this discussion I found the comment I resonated the most to be “we need a split in the registry to a General all things go in no questions asked and a more curated one” which has been repeated by several members. But this statement isn’t even directly related with the current topic if you think about it, it is something that has been in discussion for years and I’ve always been a huge fan of, along with many others.
On the topic at hand however, I should also point out my confusion regarding what we are even debating about, with respect to the opening thread. E.g., the comment from Keno:
to me this sounds like that you engaged with the code, tested it in a “real world case”, and potentially will (or already had) improved it over time. This doesn’t sound to me like the definition of “vibe coding” given in the very first post here, that is “building software with an LLM without reviewing the code it writes”. Sounds like you have reviewed if not extensively at least just by using it. When I started reading this thread, the opening definition sounded to me more like “ai slop” while Keno’s comment sounds more like “AI-assisted package development”, and these are different things! So I am not sure if we are all on the same page. I’d definitely agree on limiting “registration of ai slop”. The case that Keno or Chris talks about, I would also agree with them that I see no real reason to limit it, provided the usage of AI is sufficiently disclosed in the package docs/readme?
Perhaps GitHub will soon formalize an “AI statement” for repos, which is prominently highlighted just like the license is, so it is easier to see at a glance what sorts of AI involvement has taken place. This could help a lot with some automations for also registering in the General, e.g., we could say if there is some particularly high level of AI usage, it is flagged in the same way as a problematic name. That is, it doesn’t condenm the package or anything, but it asks the author for some sort of justification or comment.