I have to be careful with the licensing. Zed is dual-licensed per crate. In the fork there are 28 Apache-2.0 crates and 198 GPL-3.0-or-later crates. The split is clean: • Apache-2.0: the whole gpui family (the UI framework), plus our gpui_aros backend, plus gpui-component. • GPL-3.0-or-later: Zed's actual editor crates (editor, language, lsp, project, workspace, and zed itself).

Nothing is stopping you from compiling and using GPL licensed software in aros. You just have to be careful not committing GPL code into the aros codebase (although there are examples where it is present i.e. AHI, but then the license headers are included). If you look in the ports repo you see that the normal practice is to create a diff file with the changes needed to run it on aros which is applied after downloading the sources, most of the time from github releases, and before compiling.

I appreciate the feedback, I've updated my rules, but I also plan to distribute binairies or Macaros and Feraille, so that strategy will not be enough if I understood correctly.