bsd-ac
Precisions about contributing guidelines
Hello,
I maintain my own overlay for wayland related ebuilds and would be interested in contributing them here. (or at least some of them) Can you enlighten me about your policy on :
- ebuilds that are derivated from the ones main gentoo repo (notably solaar, waybar, and alacritty)
- ebuilds that are partly generated partially by automation tools (namely cargo-ebuild for rust related ebuild)
- anything to check for (besides the copyright and license header) before opening a pull request
This could potentially go into a CONTRIBUTING.md file for later reference.
Upon further analysis, I found out that all ebuilds in the main repo are Licensed under GPLv2 and derivatives for wayland specific changes thus won't be eligible to be merged here.
This leaves the question of tool-assisted ebuild generation
It will depend on the tool and their licenses. Someone more knowledgeable in licensing will have to take a look at that.
I have raised the licensing issue directly on cargo-ebuild's repo since it's the only one I used: https://github.com/gentoo/cargo-ebuild/issues/37
cargo-ebuild is no longer maintained an i've stopped using it for assisting with writing ebuilds.