[wp-trac] [WordPress Trac] #54504: Update Requests library to version 2.0.0

[WordPress Trac]

#54504: Update Requests library to version 2.0.0
-------------------------------------------------+-------------------------
 Reporter:  jrf                                  |       Owner:
                                                 |  SergeyBiryukov
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  External Libraries                   |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  php80 php81 has-patch has-unit-      |     Focuses:
  tests early early-like-actually-early          |
-------------------------------------------------+-------------------------

Comment (by azaozz):

 Replying to [comment:83 jrf]:
 > The repo was moved (not forked) - at my request - to lessen the risk
 of...
 >
 > That and that alone was the reason to look for a new home for the repo.

 Thanks for the clarification!

 Not sure it makes any difference whether it was moved, forked, copied or
 transferred (the latter is the official GitHub term afaik). The important
 bit is that it is now part of the WordPress repo, just like all the rest
 of the core related projects/repos there.

 > It was never discussed nor implied that the status of the project as
 external dependency would change and in my opinion, it hasn't changed,
 we've just ensured that the "one key to the castle" risk was mitigated.

 Yes, this is where all differences come from. As far as I understand when
 something is part of the WordPress repository and GitHub account it is
 also part of the WordPress Open Source project which takes ownership of
 it. In that case the WordPress core team carries certain responsibilities
 for it (maintenance, support, preventing misuse, etc.) and has certain
 rights like for example to archive a repository if it's forked,
 transferred, or the project has ended, etc. In that terms all
 (sub)repositories under https://github.com/WordPress should uphold the
 project's values, philosophy and abide by the project's rules.

 Since there are different opinions, I think it would be best to follow
 @peterwilsoncc's advice and "agree to disagree" for now. As this seems to
 perhaps have some legal implications (project ownership) I'll try to
 follow up and get some advice. Hopefully that will result in clarifying
 the status of software added to the WordPress Github repository, and any
 guidelines will perhaps be added to the contributor handbook.

 With this I'd like to consider that matter closed for now. Sorry this is
 sooo much off-topic here.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54504#comment:84>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform