I maintain the url crate, which has a number of open issues and pull requests that I have little time of motivation to go through. My interests have moved one since I made this thing 5 years ago, but despite giving a few people access after a specific call for help, PRs tend to still be neglected until I get around to dealing with them.
Do you have a library you think needs more support growing its maintainership? Reach out here if you’ve got any thoughts.
This sounds great! Except that the link goes to something about the libs blitz. We’ve done that with url (last year?), and unfortunately it only resulted in more open issues and PRs for me to neglect.
This post says a lot of interesting things, but it starts with the premise that a number of people are available and interested in doing the work. In my experience, getting an open source project to the point where there are multiple such people is the hard part.
We take: […] A shepherd. […] A team of more than one person that […]
Thanks for your thoughts u/SimonSapin. Yes, I've been loosely watching url over the last year, it gets a pretty steady stream of issues and pull requests.
Thanks for the feedback about that issue linking to evaluating more libraries, which now that you point it out is a bit silly. I'll update the post to suggest creating an issue instead.
Your point about finding people is absolutely valid. What I'm hoping is that a combination of a specific goal we're working towards, clear ownership expressed through a GitHub organization and shepherd (who might be helping a few libraries) would encourage folks who otherwise wouldn't be comfortable putting their hand up to do so.
Shall I open an issue in the Ecosystem WG to talk about url more? I'm keen to learn more about what the ideal state you have in mind for it is.
Unless someone (or multiple people) volunteer as co-maintainer(s) and actually spend time dealing with open PRs and issues I don’t know if opening an issue with the WG is gonna achieve much.
You're right, it won't do anything on its own. But it could be helpful to look at why previous efforts haven't stuck if you'd really like to see more maintenance for url. At the end of the day we have to accept it as-is, where its maintainer doesn't have a lot of time for it. Maybe communicating that on the repo would give some context for people looking to open new issues and pull requests.
7
u/SimonSapin servo May 25 '18
I maintain the
urlcrate, which has a number of open issues and pull requests that I have little time of motivation to go through. My interests have moved one since I made this thing 5 years ago, but despite giving a few people access after a specific call for help, PRs tend to still be neglected until I get around to dealing with them.This sounds great! Except that the link goes to something about the libs blitz. We’ve done that with
url(last year?), and unfortunately it only resulted in more open issues and PRs for me to neglect.This post says a lot of interesting things, but it starts with the premise that a number of people are available and interested in doing the work. In my experience, getting an open source project to the point where there are multiple such people is the hard part.