Please provide CLEAR announcement about moving Requests to WordPress

[i-tabu]

I have used this library in my project, today for some reason (probably for the sack of documentation) I came to github and found WordPress (instead of some weird prefix rmmc... something (pun intended). And I was surprised, if I am at the right library or not...

Then I googled, I found https://requests.ryanmccue.info/
Here no where mentioned WordPress (apart from git clone :p)

Later I asked Chatgpt (even Google aka Gemini, "Is php request the same as Wordpress Request" and it replied..clear No, both are different and blah blah..

Then I used chatgpt's deep research. Chatgpt found the changelog, etc..blah blah, to confirm it is indeed transferred..

In a nutshell, why is it so hard to even figure out if this library is transferred to WordPresss? I do understand that for backward compatibility the namespace in composer is maintained, but on the top of the composer and also on the library website, you should mention the announcement about the transfer, so a dev coming from an ancient past could understand and adopt, instead of wasting half an hour or so. I am making this issue out of frustration and also out of my empathy (to save other devs to waste their time),
so actionables could be:

1. On github readme please mention a note
2. On composer mentioned the note
3. on the lib website mention the note,
   Or whatever else a better u can find.

C ya,
Tabu :)

References:
https://chatgpt.com/share/67d2d491-6c8c-8003-9f7c-4668215bd63f
https://requests.ryanmccue.info/
https://packagist.org/packages/rmccue/requests

[jrfnl]

I'm not sure what your point is. The Packagist package clearly links to this repo and the Packagist package name has not changed, so it should be evident that this is the rmccue/requests package.

To give you the historic context: the original author/maintainer of the package abandoned it. As the WordPress project depends on Requests, the repository has been adopted by (and transferred to) the WordPress organisation to prevent it from going into total disrepair.

That's all there is to it.

[i-tabu]

My point is, that I went to github for checking the docs, and I got confused if it is rmcue / request or not. You (plz with all due respect do not take personally) have taken few assumptions instead of looking from perspective of someone who dont know anything about history etc, and just want to use the library and need a CLEAR understanding about the transfer.

[jrfnl]

@i-tabu Not taking things personally, but having trouble understanding what is causing the confusion. I mean, the repo home page links to the same documentation:

The composer.json file is clickable from that first page as well and would confirm.

If you think it would help if the README has a (small) section giving that historic context, feel free to submit a PR.
When writing it, please keep in mind that the README is also published as the homepage of the documentation website, so can't refer to "this repo" or anything.