Fix maintainers

[ternaus]

Fixes: #2006

Summary by Sourcery

Update the maintainers' information in the documentation and adjust the Python version requirement. Add a new MAINTAINERS.md file to list current and emeritus team members.

Documentation:

• Add a 'Current Maintainer' and 'Emeritus Core Team Members' section to the README.md to clarify the roles of contributors.

Chores:

• Update the Python version requirement from 3.8 to 3.9 in the installation instructions.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the README.md file to reorganize the authors section, updates the minimum Python version requirement, and adds a new MAINTAINERS.md file. It also updates the pre-commit configuration.

Class diagram for README.md structure update

classDiagram
    class README {
        +"Current Maintainer"
        +"Emeritus Core Team Members"
        +"Installation"
        +"Documentation"
        +"A simple example"
    }

Loading

Class diagram for MAINTAINERS.md addition

classDiagram
    class MAINTAINERS {
        +"Current Maintainer"
        +"Emeritus Team Members"
    }

Loading

File-Level Changes

Change	Details	Files
Reorganized the Authors section in the README	Added 'Current Maintainer' and 'Emeritus Core Team Members' subsections Moved Vladimir I. Iglovikov to 'Current Maintainer' Moved other authors to 'Emeritus Core Team Members' Removed job titles from author descriptions Fixed a typo in Eugene Khvedchenya's name	README.md
Updated minimum Python version requirement	Changed minimum Python version from 3.8 to 3.9	README.md
Added new MAINTAINERS.md file	Created a new file listing current maintainer and emeritus team members	MAINTAINERS.md
Updated pre-commit configuration	Updated mypy version from v1.12.1 to v1.13.0	.pre-commit-config.yaml
Updated Table of Contents in README	Added entries for 'Current Maintainer' and 'Emeritus Core Team Members'	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ternaus - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}