Repository navigation
Looking for maintainers #310
Description
Hi everyone,
Thanks for your continued support to my repository for the last 4 years. During this time, I have been able to expand my repository to include a lot of awesome tutorials from all over the internet thanks to your contributions. Sadly, this past year I have had a lot of personal issues that prevent me from paying attention to this project. As a result, I have basically neglected it and caused frustration for everyone. I'm slowly getting back to this and looking at the growing backlog of PRs, but by myself it would be difficult. Therefore, I am requesting your help in keeping this alive.
Please comment if you're interested in becoming one of the maintainers and I'll work out the logistics.
Thanks all <3
Tu
Activity
jjangga0214 commentedon Aug 16, 2021
Oh, it's unfortunate to hear that (including divided resource/effort by fork, possibly).
First, thanks for maintaining this great repo until now :)
I was interested in content getting updated as time elapses, so I've watched this repo for a pretty long time from my inbox.
Therefore I understand how many requests it gets.
(Like, for example, dozens of notifications are there for just a few past hours )
I am not an expert on every area this repo includes.
I can say I know javascript (main skill), dart(flutter), python, and java related topics, etc.
However, if I can and you can gladly trust me as a maintainer, I'd like to help!
I can merge/argue very deliberately, hearing as much feedback/opinion from other people as possible, with respect.
Anyway, I hope your, and our(!), balance between personal schedule and opensource contribution would be getting better and better.
Thanks.
enkeyz commentedon Aug 16, 2021
Hey @tuvtran ! I tried to contant you via email weeks ago. and got now answer, so I figured that you're not able to maintain this repo anymore. Thanks for showing interest again, and I'm sorry about your issues(hope you figured it out).
So how you do think this would work? Because the correct way doing this would include setting up an organization for this project only, and inviting people as collaborators: you'd need a core team.
About me: I'm a backend engineer, and could be helping with most of the backend project resources, also doing some generic work - maintaining the repo as a whole, improving the tooling, etc.
I also started to checking out the backlog, so we can start dealing with PRs asap.
rubiin commentedon Aug 23, 2021
Here, if you want someone to maintain I would love be of some help
tuvtran commentedon Aug 23, 2021
Hi @enkeyz , I have transferred this repo to https://github.com/practical-tutorials/project-based-learning/. Will work on adding a core team next
enkeyz commentedon Aug 23, 2021
Nice!
Also, you could set-up a comm channel here: https://gitter.im/ But only you can do it, as the project's owner.
tuvtran commentedon Aug 24, 2021
I'm gonna look into it. In the meantime I have added you to the organization
enkeyz commentedon Aug 24, 2021
Thanks! As the member of the org, I could set up a gitter channel: https://gitter.im/practical-tutorials Also check your email, @tuvtran
booleanhunter commentedon Aug 26, 2021
Hi @enkeyz and @tuvtran , I'd love to help you in maintaining this repository. Thank you for the great work so far in putting this together!
I'm a full-stack web developer and I work as a developer relations engineer - so I can say that I know a little on full-stack JavaScript, ReactJS, MongoDB and PostgreSQL. I also have some knowledge on Python and machine learning.
Some of my own tutorials are in this project, and I have some experience in maintaining my own code repositories over the years. So if you feel that I'd be a good maintainer for this one too, please let me know!
enkeyz commentedon Aug 27, 2021
Keep the discussion to the topic of this issue. Thanks.
tuvtran commentedon Aug 28, 2021
@jjangga0214 @booleanhunter happy to get you guys onboarded. I'll add you two to this repo as maintainers and our dev gitter.im channel later
11 remaining items
haseemajaz commentedon Sep 15, 2023
interested in becoming one of the maintainers 😊
sydhsn commentedon Sep 18, 2023
I am always available for help and becoming one of the maintainers
Himanshu495-rada commentedon Dec 2, 2023
I have experience of working in Java, Python, and Javascript. I would like to help you maintaining this repo.
Makeey1996 commentedon Dec 2, 2023
ima-bhi commentedon Dec 18, 2023
I've worked as a Backend Developer and want to work as a contributor /maintainer in this project.
Thanks
firatbezir commentedon Dec 19, 2023
Hi, i see there are many volunteers for maintaining this repo. I myself following this for a while and i must say this work is future-promising. I am not an expert on anything but interested working with .NET framework using c# mainly, also have front-end experience with JS, CSS, React, Vite, Next, also some other stuff that i do not take too much text-space with those.
I can happily want to contribute to all these effort if it's acceptable.
Thanks.
yenaingtun-dev commentedon Jun 7, 2024
@tuvtran Hello i want to help you maintain to this repo if it is still available.
robert-viquez commentedon Sep 10, 2024
Hi @enkeyz @tuvtran I'd love to help maintain this project in my spare time. I've already contributed with PR #626 and would love to contribute more. Let me know!
calcsam commentedon Nov 17, 2024
Gatsby co-founder here. Would love to be a maintainer!
KushalLukhi commentedon Mar 24, 2026
Hi maintainers — I'm Kushal (@KushalLukhi). I'd like to volunteer as a maintainer/contributor for this project.
I can help with:
Happy to start with PR-based contributions and earn trust progressively. If you're open, please share the preferred onboarding path and first tasks.
Huaian666 commentedon Jun 17, 2026
been using this for a while and the DX just keeps getting better. props to the maintainers
mustafa-zidan commentedon Jun 22, 2026
I am late to the party but if you still looking I would like to.
amandeavor commentedon Aug 28, 2026
Hi — I would like to earn a sustained maintenance role through concrete work. My strongest starting lane here would be backlog and pull-request triage: checking submissions against the contribution rules, validating links and project descriptions, identifying duplicates or outdated entries, and helping contributors get focused changes merge-ready.
I can begin with a maintainer-selected category or backlog slice and document every review so the work is easy to verify. My public profile includes a merged external contribution and several regression-tested contributions under review.
If maintainership is still open, which category or group of pending PRs would be most useful for me to own first?
amandeavor commentedon Aug 30, 2026
I started with a concrete review pass rather than another general follow-up. I reviewed #944, ran the repository validator, checked every replacement archive URL, compared its scope with #943, and left an approval with two small cleanup suggestions. I am happy to keep working through the current review and dead-link queue consistently.