The discussion Flavia started about the process around the proposed wildfly-ai-feature-pack[1] got me thinking a bit about how we are using wildfly-extras. The basic concept when we started that was it would be used for: 1) Projects that are incubating. 2) Some vague idea around the notion of things that are out of the mainstream for the overall WildFly project. Perhaps something meant for more specialized use, etc. But now we have some things in there that are not incubating and are very mainstream. In particular, WildFly Glow now maintains knowledge of a set of feature packs it uses when making suggestions, and that includes feature packs housed in wildfly-extras. Is it time to move some things to the main 'wildfly' organization, particularly these feature packs Glow uses? Going forward should that be a criteria for inclusion in Glow recommendations? (At least that we have decided something is ready to be moved. The actual move is just a detail.) I don't know if cleaning this up would provide any greater freedom to experiment with things in wildfly-extras without following the feature dev process. Probably not, at least not for things that the WildFly project in general will be promoting. [1] https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers/to... Best regards, -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His