Skip to content

Looking for maintainer #58

Open
Open

Description

@emilk

egui_plot was originally written by me, then added to by a lot of people, including @Bromeon and @EmbersArc.

However, there is too many PRs for me too keep up with.

I wanna help

Awesome! Please start out by helping to review PRs and issues at https://github.com/emilk/egui_plot.
That is the primary job of a maintainer, and a good way to show you care!

Activity

  1. added
    bugSomething isn't working
    help wantedExtra attention is needed
    and removed
    bugSomething isn't working
    on Jun 25, 2024
  2. pinned this issue on Jun 25, 2024
  3. samitbasu commented on Jul 8, 2024

    @samitbasu

    I have a vested interest in egui_plot, as I use it quite extensively. So I'd be willing to take make an attempt at being the maintainer (with some hand holding from @emilk ). Of course, I would defer to anyone else who wants to take it on. I definitely don't want to step on any toes. Just want to help out.

  4. emilk commented on Jul 8, 2024

    @emilk
    OwnerAuthor

    Nice! I think a good first step would be for me to move out egui_plot to its own repository and then invite you as co-maintainer. I'll try to get to that in the next few weeks. I definitely think this could be a "the more, the merrier" situations, with multiple co-maintainers.

  5. mkalte666 commented on Jul 10, 2024

    @mkalte666
    Contributor

    I use this for a commercial project at work - and for now without patches :D - but i have quite a few things that i was thinking about adding here. So even if i am not sure i can or even should be a maintainer (considering my lack of other contributions here) - i can definitely see myself spending work-time on testing out PRs and running at least the internal dev builds off of main instead of the latest release.

  6. vini-fda commented on Jul 11, 2024

    @vini-fda

    I'm using this to visualize SAR Images at my current internship. I'm not very knowledgeable on the egui internals but I'd also be willing to help you guys out :)

  7. emilk commented on Jul 15, 2024

    @emilk
    OwnerAuthor

    I've created a Discord channel for egui_plot at https://discord.com/channels/900275882684477440/1262451253095567462

  8. added a commit that references this issue on Jul 15, 2024
  9. unpinned this issue on Jul 15, 2024
  10. added a commit that references this issue on Oct 9, 2024
  11. bircni commented on Dec 3, 2024

    @bircni
    Contributor

    Would really like to help out if you want to :-)

  12. pinned this issue on Dec 4, 2024
  13. transferred this issue fromemilk/eguion Dec 4, 2024
  14. changed the title [-]`egui_plot`: looking for maintainer[/-] [+]Looking for maintainer[/+] on Dec 4, 2024
  15. emilk commented on Dec 4, 2024

    @emilk
    OwnerAuthor

    @bircni awesome, thank you! I primarily want and need help with reviews of PRs and issues, so please start there 🙏

  16. mkalte666 commented on Dec 4, 2024

    @mkalte666
    Contributor

    @bircni awesome, thank you! I primarily want and need help with reviews of PRs and issues, so please start there 🙏

    I'd be up for that as well, if you'll have me :D

  17. michalsustr commented on Nov 30, 2025

    @michalsustr
    Collaborator

    I reached out to Emil and become a maintainer. But if others are willing to help too, please do not hesitate!

  18. KushalLukhi commented on Mar 24, 2026

    @KushalLukhi

    Hi maintainers — I'm Kushal (@KushalLukhi). I'd like to volunteer as a maintainer/contributor for this project.

    I can help with:

    • issue triage and reproduction
    • reviewing/fixing open bugs
    • dependency/security updates
    • release/support chores

    Happy to start with PR-based contributions and earn trust progressively. If you're open, please share the preferred onboarding path and first tasks.

  19. eldertek commented on Nov 16, 2026

    @eldertek

    Hi @emilk and @michalsustr,

    Following up on #58, I see there are still open PRs and issues waiting for triage. Under @eldertek, I would like to help out regularly starting strictly with code review and issue reproduction, for example cleaning up and verifying #257 on the lint script and comparing the two log-scale PRs (#244 and #251) to summarize edge cases for you. Let me know if that kind of review pass would be helpful.

    Best regards,
    Théo

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

    help wantedExtra attention is needed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions