How to become the maintainer of this repo

[pgrimstrup]

Describe your question

New to github and open source development. Not new to the industry (27 years development experience).
I have used ChartJS in a couple of projects, and Blazor looks to be the framework we will be using going forward, so I am keen to take on the maintainer role for this github repo.

Which Blazor project type is your question related to?

• Client-Side
• Server-Side

Which charts is this question related to?

all charts

JavaScript equivalent

n/a

Additional context

Q: So what is the best process for taking over the maintenance of this repo?
Q: So far I have forked the repo, and fixed one issue. There is now a PR waiting. Who actually does the merge?
Q: Am I able to get write access to this repo?
Q: Should I update the readme to indicate that this repo is not-maintained and point to my repo? Once again, who does the merge of the edits I make?
Q: Is someone with write access able to transfer all issues to my repo?

I am keen to get this project updated to ChartJS 3 and .NET Core 5.

[Joelius300]

Thank you @pgrimstrup for your commitment and interest to take over this project!

I was in a similar situation about two years ago when I started to work on this great but close to unmaintained project.
Back then I was given write-access but I'm not actually the owner of the project and I can't give you write-access nor can I transfer ownership or anything of the sorts.

So what is the best process for taking over the maintenance of this project?
My suggestion is the following:

• Try to get at least one active partner that can help you especially with all the open source and GitHub stuff (biggest takeaway from when I was in your shoes)
• Continue work on your fork and address issues on the original repo with a comment that you've fixed/done them in your fork
• (I'll) add a notice and link to the top of our readme which directs users to your fork

I'm not in a position to talk about transferring ownership but if you'd like you can try to reach out to Marius for that. If you're really committed this would be the best option since you could also take over the NuGet package which has quite a bunch of downloads already. Unfortunately, I've struggled a lot with getting into contact with Marius but I wish you the best of luck. If you decide to go through with this option, please make sure to have someone with open source knowledge by your side.
This option would also work as a great next step after your fork has been worked on for a while and you're ready to go big :)

If you'd like to hop on a call to talk about some takeaways from my maintainership of ChartJs.Blazor and maybe an intro to the open source basics, I'll gladly reach out to arrange something.

Finally, let's go over the remaining questions:

Q: So far I have forked the repo, and fixed one issue. There is now a PR waiting. Who actually does the merge?
A: Any person with write-access can do the merge. Since there's no maintainer on this repo (and this won't change unless Marius comes around), it doesn't make sense to accept PRs here.

Q: Am I able to get write access to this repo?
A: No, unless Marius comes into play since only he has the privileges to add new collaborators.

Q: Should I update the readme to indicate that this repo is not-maintained and point to my repo? Once again, who does the merge of the edits I make?
A: Either I update it directly or your submit a PR with the update which I would then accept. We should talk about this once your fork is ready.

Q: Is someone with write access able to transfer all issues to my repo?
A: Not via GitHub but there are other ways to do it. I would however suggest that you just address the issues here and work with comments which you can always create. Some issues will keep popping up here anyway.

I'm excited to work with you and to ensure the future of this project! ❤️