3 ms·
They didn't in this case: https://news.ycombinator.com/item?id=31033758 https://news.ycombinator.com/item?id=31033758
by dmezzetti 2y ago
They didn't in this case: https://news.ycombinator.com/item?id=31033758 https://news.ycombinator.com/item?id=31033758
- ffsm8 2y agoThat's a foss tool though, elastic is a for profit company and might be willing to pay money to have it restored/might already be a paying GitHub customer. And GitHub might have implemented something that let's them restore it after it wasn't possible before, as it's been 2 yrs since. Lots of possibilities that might change the outcome if elastic is lucky
- dmezzetti 2y agoFrom the referenced article: "In our case, however, they refuse to do that, citing undesirable side effects and the cost of resources. We even offered GitHub financial compensation for any resources required. But, sadly, they declined. They have other priorities than resurrecting the community of one of the oldest and most popular community projects on their platform." Certainly possible they implemented a way to do this over the last 2 years.