Hi all, I'd like to propose a further tidyup of definitions. Recently we moved most things out of the top-level directory, to get to d--------- clusters d--------- extensions d--------- install-files d--------- migrations d--------- schemas d--------- scripts d--------- strata d--------- systems I suggest we go further, and separate out example integration sets into their own directories. So for example: d--------- agl d--------- baserock d--------- cip d--------- clusters d--------- extensions d--------- genivi d--------- gnome d--------- install-files d--------- migrations d--------- openstack d--------- openwrt d--------- schemas d--------- scripts The idea would be that the baserock dir (for example) would contain d--------- strata d--------- systems and this would include the definitions of our core integration set (build-system*, cross-bootstrap*, devel*, minimal*). Then we could have new directories for openstack, genivi and any other sets we decide to publish over time (eg automotive grade linux, civil infrastructure platform). The openstack dir (for example) would contain systems and strata specific to openstack. Those systems and strata would refer to strata and components from the baserock set (or override them with their own things) as needed. This would mean that we can treat different subdirs in specific ways depending on the requirement e.g. - baserock gets integrated constantly against mainline kernel, systemd and others - genivi gets six-weekly refresh - openstack maybe gets six-monthly release to coincide with mainline etc This approach would also allow us to recommend that downstream users create their own subdirectory or subdirectories, to contain their own custom definitions. If they keep their deltas separate I think this would reduce the incidence of merge conflicts for them. Any thoughts on this? br Paul PS I took a shot at a patch... http://git.baserock.org/cgi-bin/cgit.cgi/baserock/baserock/definitions.gi...