OpenAI to Acquire Astral (maker of uv, ruff) (openai.com)

submitted 1 month ago* (last edited 1 month ago) by wjs018@piefed.social to c/python@programming.dev

50 comments fedilink hide all child comments

Today we’re announcing that OpenAI will acquire Astral⁠, bringing powerful open source developer tools into our Codex ecosystem.

Astral has built some of the most widely used open source Python tools, helping developers move faster with modern tooling like uv, Ruff, and ty. These tools power millions of developer workflows and have become part of the foundation of modern Python development. As part of our developer-first philosophy, after closing OpenAI plans to support Astral’s open source products. By bringing Astral’s tooling and engineering expertise to OpenAI, we will accelerate our work on Codex and expand what AI can do across the software development lifecycle.

you are viewing a single comment's thread
view the rest of the comments

[-] Aatube@lemmy.dbzer0.com 1 points 5 days ago

uv is under an MIT license, so every fork is free to relicense themselves as GPL and prevent openai's gobblies.

[-] Brummbaer@pawb.social 1 points 5 days ago

Do you have more on that?

I'm not sure you can relicense the MIT code under GPL if you are not the author or it doesn't say so in the MIT license, that relicensing is permitted.

[-] Aatube@piefed.social 1 points 4 days ago

The MIT is what's called a permissive license.

Copyright

Permission is hereby granted , free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense , and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

That's the entirety of the text. You can do pretty much anything as long as you make sure the first line is still visible somewhere (and if you're not incorporating/relicensing it into GPL, you have to include the MIT license text as well; I'm less sure about how this parenthetical works but I do know an MIT project relicensed to GPL needs not include the MIT text), which in GPL it is.

https://choosealicense.com/licenses/mit/

https://www.gnu.org/licenses/license-list.html#:~:text=Expat)-,This%20is%20a%20lax%2C%20permissive%20non%2Dcopyleft%20free%20software%20license%2C%20compatible%20with%20the%20GNU%20GPL.,-Some

[-] Brummbaer@pawb.social 1 points 3 days ago

Thanks for the info.

So you can relicense MIT to GPL without the MiT parts staying MIT?

[-] Aatube@piefed.social 1 points 3 days ago* (last edited 3 days ago)

yes, you're creating a derivative work that is entirely GPL. note that this doesn't stop anyone from consulting the original since FOSS licenses do not have revocation. if they use none of the GPL derivative work they can still only abide by MIT. however, your changes would only exist in the GPL work, and they must be used with GPL.