You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really sure where to put this but I just wanted to say thank you to everyone involved in getting the licensing issue resolved as quickly as it did. It was a complicated/tense situation and it was handled admirably.
We were literally sitting on a call wondering what to do with the nokogiri version and just like magic (no pun intended with the gem name ;) ) '0.3.8' popped up when we refreshed rubygems and it solved our build issue.
I also applaud the decision to make the error about the missing DB file on install. I was reading what the solution to be able to get back to an MIT license and was wondering what would happen if that file wasn't there. I got a little antsy when our build just started working and I didn't know if our environments had that file or not. Once I installed it on a fresh system and got the install error I breathed a BIG sigh of relief because that was a strong indicator we wouldn't have any regression issues with the new loading strategy.
Good job, good rally, and I learned a lot!
Thanks!
The text was updated successfully, but these errors were encountered:
I'd also like to sincerely offer my thanks to @jellybob for resolving the license havok gracefully and with haste ☺️
I'd also like to wish for strength for the maintainers for handling the comments that are bound to come for some time caused by this ecosystem-level earthquake. 💞
Hey,
Not really sure where to put this but I just wanted to say thank you to everyone involved in getting the licensing issue resolved as quickly as it did. It was a complicated/tense situation and it was handled admirably.
We were literally sitting on a call wondering what to do with the nokogiri version and just like magic (no pun intended with the gem name ;) ) '0.3.8' popped up when we refreshed rubygems and it solved our build issue.
I also applaud the decision to make the error about the missing DB file on install. I was reading what the solution to be able to get back to an MIT license and was wondering what would happen if that file wasn't there. I got a little antsy when our build just started working and I didn't know if our environments had that file or not. Once I installed it on a fresh system and got the install error I breathed a BIG sigh of relief because that was a strong indicator we wouldn't have any regression issues with the new loading strategy.
Good job, good rally, and I learned a lot!
Thanks!
The text was updated successfully, but these errors were encountered: