[Matiiss]

These credits are very very old and don't get updated and probably never will get updated.
They also take up a significant portion of the README.

[coderabbitai]

📝 Walkthrough

Walkthrough

Credits and acknowledgments have been moved from README.rst to a new docs/LEGACY_CREDITS.rst file. A Dependencies section documenting version requirements for CPython, SDL, SDL_mixer, SDL_image, and SDL_ttf has been added to README.rst.

Changes

Cohort / File(s)	Summary
README Documentation Restructuring README.rst	Removed Credits/acknowledgments section (57 lines) and two legacy documentation anchor references. Added a new Dependencies block with tabular version requirements for CPython and SDL libraries.
Legacy Credits Documentation docs/LEGACY_CREDITS.rst	New file containing relocated credits and acknowledgments with multiple contributor sections, including patch submitters, documentation contributors, and community acknowledgments with reStructuredText hyperlink targets.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: moving the Credits section from README.rst to docs/LEGACY_CREDITS.rst, which matches the file modifications shown in the changeset.
Description check	✅ Passed	The description is directly related to the changeset, explaining the rationale for moving credits (they are old and take up significant README space) which aligns with the changes made.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

docs/LEGACY_CREDITS.rst (1)

42-49: Batch doc wording/grammar polish (optional).

A few phrases read awkwardly (“There’s many…”, “Many thank you’s…”, “thanks for people creating games…”). Consider a small wording pass to tighten grammar and flow in this paragraph group.

💡 Example phrasing (batched)

-There's many more folks out there who've submitted helpful ideas, kept
+There are many more folks out there who've submitted helpful ideas, kept
 this project going, and basically made our life easier.  Thanks!

-Many thank you's for people making documentation comments, and adding to the
+Many thanks to people making documentation comments, and adding to the
 `pygame documentation`_ and the `pygame-ce documentation`_.

-Also many thanks for people creating games and putting them on the
+Also many thanks to people creating games and putting them on the
 pygame.org website for others to learn from and enjoy.

Based on learnings: “For the pygame-community/pygame-ce repository, batch similar documentation or terminology improvements together in a single comment rather than pointing them out individually.”

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[damusss]

What about the credits in different languages of the README?

[Starbuck5]

Thanks!

I don't see translations as an issue @damusss, they're supposed to be updated by people who care about them and it's not a big deal if they still have this info.

[damusss]

@Starbuck5 makes sense, and I suppose since they're legacy anyways it's not an issue if they're only available in English.

[damusss]

(see comment above)
Thanks matiiss