News for hackers. Stuff that matters.
Re:No Maintenance Intended by StavrosK on Tuesday October 22, 2019 @08:09AM (#21322698)
A while ago I started an OSS maintainer community for exactly this purpose, I saw software that was in use, people wanted to contribute, the users were very active, but the developer had abandoned it, creating a hole. We all know how much more difficult it is to create a fork that will be discoverable over the original rather than just merge a few PRs.

I would like to ask anyone who currently has a project they don't want to maintain to spend the minute to add the project to Code Shelter:

https://www.codeshelter.co/

This way, interested people can easily pick up maintenance and at least merge a few PRs/triage a few issues. Also, if you have some spare time or you see a project you'd like to help out with, please join Code Shelter as a maintainer:

https://www.codeshelter.co/membership/

There's no reason to have abandoned projects nowadays, it locks them in a state of "I don't want anyone improving this" rather than "I don't have time to improve it, but feel free to if you want".

Re:No Maintenance Intended by akavel on Tuesday October 22, 2019 @11:24AM (#21324690)
I added one of my projects (https://github.com/akavel/rsrc) some time ago, when codeshelter was announced for the first time; it has a "maintainer" listed; but noone seemed to either contact me or do anything with the repo, ever. It feels weird to me. I can understand that there's no requirement for them to do something; but it still feels weird as it is now — someone seems to claim to (want to?) be a contributor, but didn't seem to even try and reach out to me.

Thinking out loud, maybe there could be some form, where if a candidate maintainer clicks the button to "join a project" (or whatever), they'd have to compose some message that would be sent to the owner, to at least break some first ice and initiate some contact? I don't know what's going on with the person. If there was an easy way, I would be happy to reach out to them and ask them, like, "hey, howdy'a doing?" Also, it would be nice if I was sent an email with a notification when someone "claims" my project, and with a chance to connect with them. Maybe you could try and start contacting people to see how is this working, and if not, to try and dig down on the underlying reasons? maybe this could lead to some now ideas for improvements and helping people work together?

Re:No Maintenance Intended by StavrosK on Tuesday October 22, 2019 @11:31AM (#21324788)
Thanks for the feedback! This was probably later than when you added the project, but we added a "note to maintainers" feature:

https://gitlab.com/codeshelter/note-to-maintainers

It's basically a text file where you describe how you want future maintainers to handle the project, give instructions, caveats, etc (whatever you want, basically).

I assume this specific maintainer situation happened because it's easy to click a button and be added to the project, so maybe the maintainer was planning to do something but didn't get around to it, or something similar.

About the communication, you're right, we encourage maintainers and authors to join our chat server (https://codeshelter.zulipchat.com/) so they can be in contact.

Code Shelter was built with more of a long-term prospect in mind (obviously we can't guarantee that we'll find you a maintainer right away), maybe I should amend the copy to manage peoples' expectations, because I hear from a lot of people that they expected someone to pick up their project and were disappointed when it didn't happen.

Re:No Maintenance Intended by akavel on Tuesday October 22, 2019 @11:41AM (#21324933)
That's... something. But it still feels very passive.

What do you think about the ideas I listed in the post above? I assume you know who are the people on both sides, and that you have their emails, so I'd guess you're in a good position to actively facilitate communication, no? Is there a way how I could actively reach out to a person that's listed as a maintainer on my project? Why not add a form that would let me do that? even without necessarily revealing their email, if they don't want to? though to tell the truth, why wouldn't they want to, if they claim to want to contribute? Similarly, how about a notification, so that I learn that someone joined my project, with their email so that I can reach out with a welcome? why passive encouragement to a chat server instead of an active facilitation of first contact over email?

Re:No Maintenance Intended by StavrosK on Tuesday October 22, 2019 @11:49AM (#21325051)
Oh, I definitely agree with you that communication should be more active, it's just that right now this is more left to the new maintainer to do. On Github, everyone's email is public anyway, so the new maintainer could message the old one.

I don't think Github/Gitlab provide any automated way to send people messages (short of creating a new issue and mentioning people). Actually, creating an issue on a maintainer joining might be a good idea, I will look into it.

Other than that, we have to take many scenarios into account (many people don't want to talk to the new maintainer, for example, because the project is completely abandoned).

We should definitely add something, though. I'll see if we can automatically add issues that will be something like "Introduce yourself" with a body of "Hello @maintainer1, @maintainer2! @newmaintainer just joined, please say hi".

I have opened an issue if you want to contribute: https://gitlab.com/codeshelter/codeshelter-web/issues/34

Re:No Maintenance Intended by akavel on Tuesday October 22, 2019 @11:53AM (#21325107)
Thanks! I'd say "you're welcome to say hi" sounds softer than "please say hi", but other than that, sounds good to me!
Re:No Maintenance Intended by StavrosK on Wednesday October 23, 2019 @10:06AM (#21334735)
I've implemented your suggestion, thanks! Here's a sample issue that is automatically created:

https://github.com/sirodoht/atom-pastery/issues/3

Re:No Maintenance Intended by StavrosK on Tuesday October 22, 2019 @11:56AM (#21325151)
Oh, yes, the copy was just illustrative.
Re:No Maintenance Intended by mncharity on Tuesday October 22, 2019 @04:49PM (#21328365)
> how much more difficult it is to create a fork that will be discoverable over the original

Part of the problem has been GitHub being unable to even show a fork graph for highly-forked projects. If that instrumentation was in better shape, one might imagine there would be more convergence.

A related challenge is the lack of conventions or infrastructure around describing the intent of a fork.

So instead of a transparent single page summary of a repo's forks, their original vision, actual activity, and relationships... individual consumers each do their own exploratory flailing around - "the github dance". In isolated repetition, as there's no convention/mechanism for sharing "I just spent an hour examining all these forks... here's what I learned, to spare you doing the same".

Perhaps a minimalist alternative to a codeshelter, might be linking to some persistent discussion forum thread, to bless an coordination process, rather than one particular result.

Though which forum has adequate properties... Perhaps use an Issue? Perhaps with some naming convention, like "Relationship to other forks"? "Related Work"? "Forks"?

I've felt GitHub started well, was building out needed infrastructure... but then stalled out with much left undone.

I'm just not sure codeshelter has the right shape. I've found people being briefly motivated to take something over, and then vanishing, to be a common case. So is "simply transfer ownership" the right model? Sometimes no one person wants to own it, but several would be willing to variously chip in, but the coordination barrier for that is currently unnecessarily high.

But maybe someone has already created a "github fork network summarizer" service site, and I've just not yet heard of it? Perhaps the transition from a startup, to a "we're not pathological anymore, really truly" Microsoft, has changed the incentives around supporting parasitic services exploring and addressing niche needs? Could "a better github" information design exercises/services become a thing?

Re:No Maintenance Intended by bxparks on Tuesday October 22, 2019 @09:43AM (#21323484)
This is a great idea, thank you for creating it. Could I suggest 2 things?

1) Can you group the projects according to the language or framework (e.g. Python, JavaScript, Node, Arduino, C++, Java, etc).

2) Can you carve out a separate section for projects that currently have no maintainers? I had to scroll through the entire list to see if there was something that I could help with.

(I'm on my phone, so if these sections already exist on desktop, I didn't see them.)

Re:No Maintenance Intended by StavrosK on Tuesday October 22, 2019 @09:46AM (#21323529)
These are great ideas, thank you! I will file the issues now (they'll be at https://gitlab.com/codeshelter/codeshelter-web/issues if you want to track them).
Re:No Maintenance Intended by alangpierce on Tuesday October 22, 2019 @11:45AM (#21324981)
Seems like a great idea. One big worry with handing over ownership is fiascos like https://news.ycombinator.com/item?id=18534392 where the author handed over ownership of an unmaintained project and the new owner released malicious code. I'd love to see a better systematic way to keep projects maintained in a way that the community can trust.
Re:No Maintenance Intended by StavrosK on Tuesday October 22, 2019 @11:52AM (#21325096)
Yep, all maintainers are vetted specifically to avoid that. If Code Shelter existed back then, this (hopefully) wouldn't have happened.
Re:No Maintenance Intended by aflag on Tuesday October 22, 2019 @08:32AM (#21322847)
This is awesome! Have you tried to get in contact with GitHub? It'd be nice if they embraced the project. Maybe adding a new button or tab with a shelter link to the project (they already have a forks view).
Re:No Maintenance Intended by StavrosK on Tuesday October 22, 2019 @08:36AM (#21322879)
We haven't, I'd like to get some more traction (and build a welcoming community) first before expanding to anything else.
Re:No Maintenance Intended by grogenaut on Tuesday October 22, 2019 @10:41AM (#21324113)
Even if you don't get a maintainer for a project, just providing ownership transfer and holding of no longer maintained projects is probably useful. Getting the owner to turn over the keys when they update the readme might be easier than 10 years later.
Re:No Maintenance Intended by StavrosK on Tuesday October 22, 2019 @10:51AM (#21324232)
Yeah, this is one of the reasons I wanted this. The owners have nothing to lose (they aren't maintaining the projects anyway), the maintainers have nothing to lose (there's no time requirement), and at some point you might come across a project that you want to use but that has been abandoned, and you can just click "join" and become its maintainer.
Re:No Maintenance Intended by grogenaut on Thursday October 24, 2019 @03:26AM (#21342444)
Not that I have massively successful projects but one thing I would love is to just hand over keys to someone I can trust to vet the person the keys are handed to. I'd be fine with "verired no malware, no spam, no adware." as a handoff.
Re:No Maintenance Intended by StavrosK on Thursday October 24, 2019 @05:03AM (#21342796)
That's what Code Shelter does (provided you trust us to vet people, I guess).