Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CALL FOR MAINTAINERS #431

Open
aehlke opened this issue Jul 8, 2022 · 5 comments
Open

CALL FOR MAINTAINERS #431

aehlke opened this issue Jul 8, 2022 · 5 comments

Comments

@aehlke
Copy link
Owner

aehlke commented Jul 8, 2022

Hi, I don't use this anymore and would like to find a few people to join as maintainers!

I'd prefer if you can highlight previous open source you've had stewardship over, or what your stake in taking ownership of this library is, just as a simple due diligence for this long-overdue open call

I think this is still an attractive option for its use case but has a few fundamental quality issues to resolve. And could be turned into something extra special in the right hands

Thanks

@jzohrab
Copy link
Collaborator

jzohrab commented Aug 26, 2023

This is an old issue, but it's still a good library.

As a relatively rookie js dev, I'm probably not the right guy for this task, but I'm still interested in seeing it move forward as I'm currently using it! So, a few questions:

Most important question: is this project still worth maintaining? The last PRs are from 2021, and the last issues from 2022. Is there another up-to-date and active project that should be recommended instead? If this project is having problems finding maintainers, than a pointer to a replacement, and clearly retiring this project, is probably the best route to take. (OTOH, maybe this project does some things better than other projects!) I know that retiring a project can be discouraging for the project author(s).

If this project is still a viable option -- i.e. it has features that existing libraries don't have:

  • what are the fundamental quality issues that should be resolved?
  • how could this project be covered with automated test cases? IMO that's almost always a missing component in OSS.
  • should the existing PRs be closed, merged? Without tests it's hard to say what's good vs not.

Cheers, jz

@aehlke
Copy link
Owner Author

aehlke commented Aug 26, 2023

You're on the right track. I'm making you a maintainer if pursuing any of those points is valuable to you, including the option of marking the repo as an archive and discouraging use.

@jzohrab
Copy link
Collaborator

jzohrab commented Aug 26, 2023

Hi @aehlke -- I posted a question to Reddit and was told a few times that tagify is considered tag-it's replacement. Some stats on tagify:

  • 3k stars
  • 400 forks
  • lots of activity and releases
  • main dev/maintainer is actively replying

My feeling is that this repo should be archived, with a README note pointing people to tagify. Thoughts? If you'd like I can add a note to the README, and archive the repo. Then you should celebrate with tag-it being "retired" :-)

@aehlke
Copy link
Owner Author

aehlke commented Aug 26, 2023

That sounds like the right move :)

@jzohrab
Copy link
Collaborator

jzohrab commented Aug 28, 2023

OK @aehlke, I've opened a PR, and you can mark this repo as archived (I'm not able to). Would you like me to do anything with the open PRs and issues? Perhaps we should add another pinned issue saying that this project is now archived. Cheers! jz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants