Originally Posted by Olaf Barthel
Ahem. Please do not assume that the people involved were negligent or otherwise unfit to attend to the task at hand.
When the leak occured, the contents of the archive had to be assessed: what had leaked, had the AmigaOS4 source code repository been compromised?.
You misunderstand me. I am not talking about the reactive defense of the Amiga property, as you are. I am talking solely about a simple demonstrated lack of interest in proactively defending the property.
The archive I found on the day of the twitter "leak" was in an open web directory, with a modification date of 2013. It was trivially locatible via google, given it's filename. I'm not the only one who noted this.
It should be very achievable to set up a google alert, or some similar thing to notify of the appearance of archives named similarly to 'amiga os source code 3.1.tar.bz2'. Or even to google it once in 3 years. It certainly got taken down fast after the twitter announcement.