Hacker News new | ask | show | jobs
by parsimo2010 604 days ago
"As part of an internal change task" is the justification listed. Maybe this is a genuine accident.

Someone paranoid might think that the for-profit management at Elastic is trying to pull some of their previously free software behind a paid-for product. Perhaps they accidentally marked all repos private when they only intended to make a few of them private. They have had beef with AWS in the past where they changed their licensing due to things AWS was doing. So I'll fully believe that it was a genuine accident if all the formerly public repos become public again.
1 comments
winddude 604 days ago
unlikely, over the summer they announced that they were going to be more opensource, <https://www.elastic.co/blog/elasticsearch-is-open-source-aga...>
link
xeraa 604 days ago
It's a configuration error (sorry!). Also with thousands of forks this would be a pretty pointless operation. Once something is out (and that includes a license), you cannot just take it back — it will be there forever.

[I work for Elastic]

link