Racket Package Index and Framagit

General
1

Hi Everyone,

I'm currently using the free git service framagit.org (a provider in France). I moved from github to my own git self hosted service to codeberg. But now they are banning AI assisted coding. And I do use AI, currently into creating skills for ChatGPT to make it's coding style for racket more readable. Also learning to be more supervisory about design and architecture.

So I moved back to my self hosted gitea instance, but eventually want a stable open source hosting provider. Now framagit is using a different URL layout for direct access to files, which poses a problem with readme.md; e.g.:

The racket-makefile package points to Sign in · GitLab, but framegit needs https://framagit.org/racket/racket-makefile/-/blob/main/README.md.

Is there something that I can do about it?

2

I'm not sure I understand your question. The URL in the package catalog should be like one you might pass to git clone: it is not supposed to point to A README file, or any other file, in a particular web UI.

3

The package indexer creates a link to README.MD all by itself. So the package resolves to the git url, no problems there and it is installable using raco/drracket. But If one browses the package index and tries to open readme with the readme button, the package site links to a wrong url.

For example here:

afbeelding
afbeelding1872×1325 166 KB

If you click the README button, it will try to go to this page.

B.t.w. I'm moving back to my self hosted environment.

4

Someone replied to a topic you are Watching.

But now they [codeberg] are banning AI assisted coding.

My read of the announcement (https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html) is somewhat more nuanced than that, but regardless I encourage folks to take a look and judge for themselves if they were considering any kind of strong reaction to the word "ban."

5

You are completely right about this. I didn't read this good enough, was triggered by an article on tweakers.net, which I see as a trustworthy source. Thanks for the nuance.

6

Oh, I see what you mean now.

That button is generated as part of the web UI, not the core “package catalog protocol,” so, as you say, the package is still installable etc.—but still, generating broken links is definitely a bug in the website.

The code that tries to find and link to a README is here:

Per the comments, it started from the assumption of a Github-like layout. It would be good to figure out:

  1. How this wrong URL made it past the existing checks; and
  2. How to adapt the code for some other well-known layouts of repository web UIs.