Skip to content

Request to Transfer Maintainer of the fa.react.dev Repository #464

Closed

Description

@mrbadri

Hello React Team,

As a small member of the Persian-speaking developer community, I am creating this issue regarding the fa.react.dev repository.

This repository appears to have been inactive for a long time, and the current maintainers are no longer actively managing it.

Given the importance of having official React documentation available in Persian, I kindly request that the Maintainer of this repository be transferred either to me or to another active contributor approved by the React team.

The goal is to help grow the React community among Persian-speaking developers and to improve access to accurate and up-to-date resources.

I am confident that the professional React team will carefully consider this request and continue to show the same respect and support for various language communities as it always has.

Thank you for your attention.

Best regards,
Mohammad rza badri

Activity

  1. mrbadri commented on May 13, 2025

    @mrbadri
    CollaboratorAuthor

    We are actively trying to revive the fa.react.dev repository in this issue.
    Join us and show your support: reactjs/react.dev#7786

  2. rickhanlonii commented on May 14, 2025

    @rickhanlonii
    Member

    @rezvani2647 @seven-deuce @sJJdGG @sorousht @zahrajoulaei are any of the current maintainers currently active and willing to help review PRs and/or add additional maintainers to help make progress translating the docs?

  3. sJJdGG commented on May 15, 2025

    @sJJdGG
    Contributor

    @rickhanlonii I'm willing to help

  4. mrbadri commented on May 15, 2025

    @mrbadri
    CollaboratorAuthor

    Hi @rickhanlonii , @sJJdGG 👋

    I have created the following pull requests:

    I would appreciate it if you could review these pull requests. 🙏

  5. rickhanlonii commented on May 15, 2025

    @rickhanlonii
    Member

    @sJJdGG thanks! cCould you review those PRs, and consider adding new maintainers if needed tom help make progress?

  6. sJJdGG commented on May 15, 2025

    @sJJdGG
    Contributor

    Yeah, let's start by adding maintainers. I'm ok with adding @mrbadri PRs as a maintainer.

    BTW @rickhanlonii , if we maintainers of the local translation decide to use AI for automations, would that be ok with you?

  7. rickhanlonii commented on May 15, 2025

    @rickhanlonii
    Member

    @sJJdGG if it's reviewed by the maintainers that seems fine

  8. rickhanlonii commented on May 15, 2025

    @rickhanlonii
    Member

    @mrbadri added you as a maintainer.

    @masoud-bahrami is the only admin maintainer who can add more, @masoud-bahrami are you able to manage invites or should I add a new admin?

  9. mrbadri commented on May 15, 2025

    @mrbadri
    CollaboratorAuthor

    Thank you, @rickhanlonii, for your attention and support on this.
    I look forward to contributing and being helpful to the project. 🙏

  10. mrbadri commented on May 15, 2025

    @mrbadri
    CollaboratorAuthor

    @rickhanlonii ,
    Pull requests require approval from a reviewer.
    Does this also apply to maintainers?

    Currently, I am the only active maintainer, and there is no one else to approve my own pull requests.

    Who can approve my pull requests?

    Also, is there any document or guideline about the process and rules for pull requests?
    I’d be happy to review it if available.

    #466

  11. sJJdGG commented on May 16, 2025

    @sJJdGG
    Contributor

    @mrbadri you can merge your own PR as a maintainer

  12. mrbadri commented on May 16, 2025

    @mrbadri
    CollaboratorAuthor

    @sJJdGG Could you please tell me how I can do this?

    Image Image Image
  13. mrbadri commented on May 16, 2025

    @mrbadri
    CollaboratorAuthor

    @sJJdGG Could you please tell me how I can do this?

    Image Image Image

    @rickhanlonii @sJJdGG Could you please help me with this part? I would appreciate your guidance.

  14. sJJdGG commented on May 16, 2025

    @sJJdGG
    Contributor

    @mrbadri I also can't approve your PR. Same error as you
    @rickhanlonii Seems like we're locked out

  15. rickhanlonii commented on May 17, 2025

    @rickhanlonii
    Member

    The check_maintainer job is unrelated, the failing check is via the repo branch settings, which requires an approval:

    Image

    So one of the other maintainers needs to approve the PR. The only approval is from a person who doesn't have write access:

    Image

    As maintainers, you can choose to turn this option off so you can merge/approve your own PRs (we have this off in the main repo), but it's up to you all what processes you want to enforce.

  16. rickhanlonii commented on May 17, 2025

    @rickhanlonii
    Member

    As an example, I've approved #466, and it's now green to merge.

  17. mrbadri commented on May 17, 2025

    @mrbadri
    CollaboratorAuthor

    I currently do not have access to the branch protection settings.

    To proceed, we have two possible options:
    1. Modify the branch protection rules to allow maintainers to approve and merge their own pull requests.
    2. Add another active maintainer with the appropriate permissions to handle approvals.

    Please let me know which course of action you’d prefer to take. @rickhanlonii

  18. rickhanlonii commented on May 17, 2025

    @rickhanlonii
    Member

    @mrbadri maybe it wasn't clear but @sJJdGG is an active maintainer but they didn't approve your PR so that's why it couldn't merge. I think what you need is an additional admin, which is why I pinged @masoud-bahrami above. I'd see if you can get ahold of them to help manage maintainers/settings or to add additional admins.

  19. rickhanlonii commented on Oct 31, 2025

    @rickhanlonii
    Member

    Looks like this is settled, let me know if there's anything else.

  20. sJJdGG commented on Nov 3, 2025

    @sJJdGG
    Contributor

    @rickhanlonii @mrbadri Sorry about inconvenience I may have caused by my inaction.

    @rickhanlonii Thank you for handling it, if anything I'd argue having more collaborators and consequently more activity would be top priority for reactjs/fa.react.dev even in the face of all possible non-desired outcomes since any move forward would be a positive outcome at the current status of the repo. as we say in Persian "به راه بادیه رفتن به از نشستن باطل" meaning “To set out upon the desert path is better than sitting idly and in vain.”

  21. rickhanlonii commented on Feb 3, 2026

    @rickhanlonii
    Member

    No worries, thanks for getting back to us!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions