The herds have been deprecated by the Council and are being replaced by projects. For this reason, please decide on the fate of the herd stated in the summary and update [1] or state the request here. The common choices are: 1. Map the herd to an existing project (in this case all packages in the herd will be maintained by the project) -- let us know which project to use. 2. Create a new project for the herd -- create the wiki page, let us know the new mail alias name to be created, create the wiki page and let us know about it. 3. Decide to disband the herd -- just let us know (but keep it for now in herds.xml!), we'll replace it with individual maintainers when herds are removed. [1]:https://wiki.gentoo.org/wiki/Project:Metastructure/Herd_to_project_mapping
I would suggest using toolchain@gentoo.org as the project name for project "Toolchain" and making the toolchain a subproject of base-system. However the project members are NOT inherited from base-system.
(In reply to Anthony Basile from comment #1) > I would suggest using toolchain@gentoo.org as the project name for project I mean for the project email address which, if I recall correctly, is used as the identify for GLEP67.
There are also already packages using toolchain@g.o directly as maintainer.
I'd like to have gcc-porting as a sub-project of toolchain so I'm adding a blocker to that bug.
(In reply to Anthony Basile from comment #1) > I would suggest using toolchain@gentoo.org as the project name for project > "Toolchain" and making the toolchain a subproject of base-system. However > the project members are NOT inherited from base-system. I have created the toolchain project like this.