Mixing
![Should a company be hiring people who are related? [closed]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjbpfN9tAutmK93bJRC3ZoROZzi2TJDms5n8_qJuhgE0a9b52OOHayv3NGT8igAdFL7byXNst-_1DZK5SjrIJ28_6RQPUpBROqMs5s6jo-ZsjX8kjDwfxJufIitH3TaQRXWaGSQKRQib-f/s72-c/1.jpg)
Ex-Employee Published Entire Source Code on GitHub 3 Years Ago - How do we Get it Down? [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
3
down vote
favorite
Roughly 3-4 years ago, we hired a PHP developer and tasked them with building small "satellite" websites. They didn't stay long, and we had largely forgotten about them.
Fast-forward to today, one of the sites became big - we've since rewritten the whole thing in another language and open-sourced it on GitHub.
However, now we've found the entire PHP source code of the old site on GitHub, uploaded to the ex-employee's personal account at a time when they were still working with us.
Nobody at the company knew about this or authorized it, not even my boss. It's likely that the ex-employee uploaded it as a "test" without fully realizing what GitHub was. There is no LICENSE or README in the repository.
It would be very difficult to contact the ex-employee, and they might not remove it anyway - so how do we get GitHub to take it down quickly?
employees intellectual-property
asked Mar 11 '16 at 9:51
glcheetham
16317
closed as off-topic by Lilienthal♦, keshlam, Dawny33, paparazzo, gnat Mar 11 '16 at 12:35
- This question does not appear to be about the workplace within the scope defined in the help center.
 |Â
show 6 more comments
up vote
3
down vote
favorite
Roughly 3-4 years ago, we hired a PHP developer and tasked them with building small "satellite" websites. They didn't stay long, and we had largely forgotten about them.
Fast-forward to today, one of the sites became big - we've since rewritten the whole thing in another language and open-sourced it on GitHub.
However, now we've found the entire PHP source code of the old site on GitHub, uploaded to the ex-employee's personal account at a time when they were still working with us.
Nobody at the company knew about this or authorized it, not even my boss. It's likely that the ex-employee uploaded it as a "test" without fully realizing what GitHub was. There is no LICENSE or README in the repository.
It would be very difficult to contact the ex-employee, and they might not remove it anyway - so how do we get GitHub to take it down quickly?
employees intellectual-property
asked Mar 11 '16 at 9:51
glcheetham
16317
closed as off-topic by Lilienthal♦, keshlam, Dawny33, paparazzo, gnat Mar 11 '16 at 12:35
- This question does not appear to be about the workplace within the scope defined in the help center.
12
File a DMCA notice with GitHub - help.github.com/articles/dmca-takedown-policy
– Moo
Mar 11 '16 at 9:55
1
Have you tried asking the former employee?
– rath
Mar 11 '16 at 9:58
2
Rather than asking us to tell you if it's likely, ask them to tell you what's needed. We can't read their minds, we can only read their docs (as @Moo has done).
– keshlam
Mar 11 '16 at 9:59
5
I'm voting to close this question as off-topic because your interaction with Github is not within the scope of this site. It's likely off-topic on the entire SE network.
– Lilienthal♦
Mar 11 '16 at 10:39
1
You can extract email addresses from git commits - though this assumes the employee used their personal email address for committing the code rather than a company one.
– yuikonnu
Mar 11 '16 at 11:05
 |Â
show 6 more comments
up vote
3
down vote
favorite
up vote
3
down vote
favorite
Roughly 3-4 years ago, we hired a PHP developer and tasked them with building small "satellite" websites. They didn't stay long, and we had largely forgotten about them.
Fast-forward to today, one of the sites became big - we've since rewritten the whole thing in another language and open-sourced it on GitHub.
However, now we've found the entire PHP source code of the old site on GitHub, uploaded to the ex-employee's personal account at a time when they were still working with us.
Nobody at the company knew about this or authorized it, not even my boss. It's likely that the ex-employee uploaded it as a "test" without fully realizing what GitHub was. There is no LICENSE or README in the repository.
It would be very difficult to contact the ex-employee, and they might not remove it anyway - so how do we get GitHub to take it down quickly?
employees intellectual-property
asked Mar 11 '16 at 9:51
glcheetham
16317
Roughly 3-4 years ago, we hired a PHP developer and tasked them with building small "satellite" websites. They didn't stay long, and we had largely forgotten about them.
Fast-forward to today, one of the sites became big - we've since rewritten the whole thing in another language and open-sourced it on GitHub.
However, now we've found the entire PHP source code of the old site on GitHub, uploaded to the ex-employee's personal account at a time when they were still working with us.
Nobody at the company knew about this or authorized it, not even my boss. It's likely that the ex-employee uploaded it as a "test" without fully realizing what GitHub was. There is no LICENSE or README in the repository.
It would be very difficult to contact the ex-employee, and they might not remove it anyway - so how do we get GitHub to take it down quickly?
employees intellectual-property
asked Mar 11 '16 at 9:51
glcheetham
16317
asked Mar 11 '16 at 9:51
glcheetham
16317
asked Mar 11 '16 at 9:51
glcheetham
16317
asked Mar 11 '16 at 9:51
glcheetham
16317
16317
closed as off-topic by Lilienthal♦, keshlam, Dawny33, paparazzo, gnat Mar 11 '16 at 12:35
- This question does not appear to be about the workplace within the scope defined in the help center.
closed as off-topic by Lilienthal♦, keshlam, Dawny33, paparazzo, gnat Mar 11 '16 at 12:35
- This question does not appear to be about the workplace within the scope defined in the help center.
12
File a DMCA notice with GitHub - help.github.com/articles/dmca-takedown-policy
– Moo
Mar 11 '16 at 9:55
1
Have you tried asking the former employee?
– rath
Mar 11 '16 at 9:58
2
Rather than asking us to tell you if it's likely, ask them to tell you what's needed. We can't read their minds, we can only read their docs (as @Moo has done).
– keshlam
Mar 11 '16 at 9:59
5
I'm voting to close this question as off-topic because your interaction with Github is not within the scope of this site. It's likely off-topic on the entire SE network.
– Lilienthal♦
Mar 11 '16 at 10:39
1
You can extract email addresses from git commits - though this assumes the employee used their personal email address for committing the code rather than a company one.
– yuikonnu
Mar 11 '16 at 11:05
 |Â
show 6 more comments
12
File a DMCA notice with GitHub - help.github.com/articles/dmca-takedown-policy
– Moo
Mar 11 '16 at 9:55
1
Have you tried asking the former employee?
– rath
Mar 11 '16 at 9:58
2
Rather than asking us to tell you if it's likely, ask them to tell you what's needed. We can't read their minds, we can only read their docs (as @Moo has done).
– keshlam
Mar 11 '16 at 9:59
5
I'm voting to close this question as off-topic because your interaction with Github is not within the scope of this site. It's likely off-topic on the entire SE network.
– Lilienthal♦
Mar 11 '16 at 10:39
1
You can extract email addresses from git commits - though this assumes the employee used their personal email address for committing the code rather than a company one.
– yuikonnu
Mar 11 '16 at 11:05
12
12
File a DMCA notice with GitHub - help.github.com/articles/dmca-takedown-policy
– Moo
Mar 11 '16 at 9:55
File a DMCA notice with GitHub - help.github.com/articles/dmca-takedown-policy
– Moo
Mar 11 '16 at 9:55
1
1
Have you tried asking the former employee?
– rath
Mar 11 '16 at 9:58
Have you tried asking the former employee?
– rath
Mar 11 '16 at 9:58
2
2
Rather than asking us to tell you if it's likely, ask them to tell you what's needed. We can't read their minds, we can only read their docs (as @Moo has done).
– keshlam
Mar 11 '16 at 9:59
Rather than asking us to tell you if it's likely, ask them to tell you what's needed. We can't read their minds, we can only read their docs (as @Moo has done).
– keshlam
Mar 11 '16 at 9:59
5
5
I'm voting to close this question as off-topic because your interaction with Github is not within the scope of this site. It's likely off-topic on the entire SE network.
– Lilienthal♦
Mar 11 '16 at 10:39
I'm voting to close this question as off-topic because your interaction with Github is not within the scope of this site. It's likely off-topic on the entire SE network.
– Lilienthal♦
Mar 11 '16 at 10:39
1
1
You can extract email addresses from git commits - though this assumes the employee used their personal email address for committing the code rather than a company one.
– yuikonnu
Mar 11 '16 at 11:05
You can extract email addresses from git commits - though this assumes the employee used their personal email address for committing the code rather than a company one.
– yuikonnu
Mar 11 '16 at 11:05
 |Â
show 6 more comments
1 Answer
1
active
oldest
votes
up vote
18
down vote
accepted
If you do not have a relationship with the developer, or cannot contact them in any way, then the best route for you to take is to issue a DMCA takedown notice.
This absolves GitHub of all legal responsibility for the takedown, and will probably result in the removal of the repository until such time as the account owner files a counter notice. Without legal responsibility being absolved, it merely becomes a "he said she said" argument which GitHub will not get involved in, as it opens them up to legal issues.
If the account owner files a counter notice, it becomes a legal issue between you and the owner of the account, as they have asserted a claim of copyright ownership or another right which allows them to post the work. But at least that will clarify the situation for you, and make it obvious what steps you need to take next.
https://help.github.com/articles/dmca-takedown-policy/
answered Mar 11 '16 at 9:58
Moo
5,90041723
suggest improvements |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
18
down vote
accepted
If you do not have a relationship with the developer, or cannot contact them in any way, then the best route for you to take is to issue a DMCA takedown notice.
This absolves GitHub of all legal responsibility for the takedown, and will probably result in the removal of the repository until such time as the account owner files a counter notice. Without legal responsibility being absolved, it merely becomes a "he said she said" argument which GitHub will not get involved in, as it opens them up to legal issues.
If the account owner files a counter notice, it becomes a legal issue between you and the owner of the account, as they have asserted a claim of copyright ownership or another right which allows them to post the work. But at least that will clarify the situation for you, and make it obvious what steps you need to take next.
https://help.github.com/articles/dmca-takedown-policy/
answered Mar 11 '16 at 9:58
Moo
5,90041723
suggest improvements |Â
up vote
18
down vote
accepted
If you do not have a relationship with the developer, or cannot contact them in any way, then the best route for you to take is to issue a DMCA takedown notice.
This absolves GitHub of all legal responsibility for the takedown, and will probably result in the removal of the repository until such time as the account owner files a counter notice. Without legal responsibility being absolved, it merely becomes a "he said she said" argument which GitHub will not get involved in, as it opens them up to legal issues.
If the account owner files a counter notice, it becomes a legal issue between you and the owner of the account, as they have asserted a claim of copyright ownership or another right which allows them to post the work. But at least that will clarify the situation for you, and make it obvious what steps you need to take next.
https://help.github.com/articles/dmca-takedown-policy/
answered Mar 11 '16 at 9:58
Moo
5,90041723
suggest improvements |Â
up vote
18
down vote
accepted
up vote
18
down vote
accepted
If you do not have a relationship with the developer, or cannot contact them in any way, then the best route for you to take is to issue a DMCA takedown notice.
This absolves GitHub of all legal responsibility for the takedown, and will probably result in the removal of the repository until such time as the account owner files a counter notice. Without legal responsibility being absolved, it merely becomes a "he said she said" argument which GitHub will not get involved in, as it opens them up to legal issues.
If the account owner files a counter notice, it becomes a legal issue between you and the owner of the account, as they have asserted a claim of copyright ownership or another right which allows them to post the work. But at least that will clarify the situation for you, and make it obvious what steps you need to take next.
https://help.github.com/articles/dmca-takedown-policy/
answered Mar 11 '16 at 9:58
Moo
5,90041723
If you do not have a relationship with the developer, or cannot contact them in any way, then the best route for you to take is to issue a DMCA takedown notice.
This absolves GitHub of all legal responsibility for the takedown, and will probably result in the removal of the repository until such time as the account owner files a counter notice. Without legal responsibility being absolved, it merely becomes a "he said she said" argument which GitHub will not get involved in, as it opens them up to legal issues.
If the account owner files a counter notice, it becomes a legal issue between you and the owner of the account, as they have asserted a claim of copyright ownership or another right which allows them to post the work. But at least that will clarify the situation for you, and make it obvious what steps you need to take next.
https://help.github.com/articles/dmca-takedown-policy/
answered Mar 11 '16 at 9:58
Moo
5,90041723
answered Mar 11 '16 at 9:58
Moo
5,90041723
answered Mar 11 '16 at 9:58
Moo
5,90041723
answered Mar 11 '16 at 9:58
Moo
5,90041723
5,90041723
suggest improvements |Â
suggest improvements |Â
12
File a DMCA notice with GitHub - help.github.com/articles/dmca-takedown-policy
– Moo
Mar 11 '16 at 9:55
1
Have you tried asking the former employee?
– rath
Mar 11 '16 at 9:58
2
Rather than asking us to tell you if it's likely, ask them to tell you what's needed. We can't read their minds, we can only read their docs (as @Moo has done).
– keshlam
Mar 11 '16 at 9:59
5
I'm voting to close this question as off-topic because your interaction with Github is not within the scope of this site. It's likely off-topic on the entire SE network.
– Lilienthal♦
Mar 11 '16 at 10:39
1
You can extract email addresses from git commits - though this assumes the employee used their personal email address for committing the code rather than a company one.
– yuikonnu
Mar 11 '16 at 11:05