Contributors mailing list archives
Re: DMCa take downby
I would instead recommend that you delete your fork entirely and then recreate. Otherwise you will all need to send a counter claim to GitHub after rectifying on your end.-Dave Lasley
On Jan 25, 2018, at 06:47, Yannick Vaucher <yannick.vaucher@camptocamp.
com> wrote:Individuals need to check their own fork to ensure they don't have still a badly copyrighted source code.You want to delete especially your old 7.0 and 8.0 branches. And update to the last commit on 9.0 and 10.0.Cheers,On 25 January 2018 at 14:32, Joël Grand-Guillaume <joel.grandguillaume@ camptocamp.com> wrote:@Frederik: It has been claimed by GNU Health. We'll provide a post-mortem when we'll have the time. We should have fixed the issue today, so no real help would be needed here. Thanks for offering !@Robert: In this case, it happened through Github DMCA process. So basically anyone can claim it and you then have 24 hours to fix what was requested, do nothing or claim it is not true. In the second case, your repo is taken down. In the third, you have I think 14 days to bring proof form a court issuance.On Thu, Jan 25, 2018 at 11:17 AM, robert rottermann <email@example.com> wrote:
what is the workflow in such a case:
You get the take down request, execute it, and then ask what is the impingement and proceed accordingly
You get the request, ask what the infringement is and when the involved parties do not provide a sensible answer in due time you execute the take down and proceed ..
robertOn 25.01.2018 09:46, Joël Grand-Guillaume wrote:We'll keep you posted.Dear contributors,I inform you that we have received a DMCA Takedown for OCA/vertical-medical repository. We have contacted the PSC leads in order to clarify the situation as soon as possible. OCA takes license attributions very seriously.Regards,Joël for the OCA board