Good policy. Then I can just watch for people to go on vacation via their Instagram, and while they're out I'll contact GitHub and say "Hey this person is unreachable! Give me control of their projects!"
I think that what anilgulecha meant by ownership is that there are probably quite a few committers. So they are not just some random people taken from the street. It's not so clear cut, but there is something to it. It would not be good for your contributors to take the carpet from under your feet, but at the same time part of the project already belongs to them.
Those details don't really matter, because the point it's not realistic to expect a company with so many projects and users like GitHub to be making those kind of individual calls.
You don't really own part or any of the project if you don't have administrative access to it. It's that simple. If you feel like you should, then you need to arrange that with the person who currently does.
These are project organizational issues that GitHub shouldn't be expected to waste their time on.
it's not realistic to expect a company with so many projects and users like GitHub to be making those kind of individual calls
While I agree with that logic on some level, this sounds exactly like the same arguments that every tech company uses to detach itself from the social consequences of the service it provides.
Especially because they have so many projects and users they are expected to make individual calls. GitHub is the home for many open source projects and should care for the needs of their community.
The organization on GitHub was registered by an individual on behalf of the open source project. Now that the person can no longer be contacted, control needs to be transferred to someone else representing the open source project. It's that simple.
Comments
Good policy. Then I can just watch for people to go on vacation via their Instagram, and while they're out I'll contact GitHub and say "Hey this person is unreachable! Give me control of their projects!"
Brilliant.
I think that what anilgulecha meant by ownership is that there are probably quite a few committers. So they are not just some random people taken from the street. It's not so clear cut, but there is something to it. It would not be good for your contributors to take the carpet from under your feet, but at the same time part of the project already belongs to them.
Those details don't really matter, because the point it's not realistic to expect a company with so many projects and users like GitHub to be making those kind of individual calls.
You don't really own part or any of the project if you don't have administrative access to it. It's that simple. If you feel like you should, then you need to arrange that with the person who currently does.
These are project organizational issues that GitHub shouldn't be expected to waste their time on.
While I agree with that logic on some level, this sounds exactly like the same arguments that every tech company uses to detach itself from the social consequences of the service it provides.
Especially because they have so many projects and users they are expected to make individual calls. GitHub is the home for many open source projects and should care for the needs of their community.
The organization on GitHub was registered by an individual on behalf of the open source project. Now that the person can no longer be contacted, control needs to be transferred to someone else representing the open source project. It's that simple.