From https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/conf-researchr-org/dFtUeJpXxYs/KV89oHCdBQAJ :

ECOOP and ISSTA 2018 are co-located and share the following tracks: doctoral symposium, posters, summer school, and workshops. The way I set things up is to add those tracks to the super-conference ECOOP/ISSTA (https://conf.researchr.org/home/ecoop-issta-2018).

However, if somebody is only interested in attending ECOOP, for example, and goes to its webpage (https://2018.ecoop.org), she won’t find a track for Workshops. This will mislead ECOOP attendees that there won’t be a workshop track at ECOOP, while in fact, there is one. It’s just shared with ISSTA 2018.

The current solution that I thought of is duplicate all those tracks to the sub-conferences ECOOP and ISSTA. But then this process is more error-prone, and I’d have to duplicate committees, CFPs, etc. And I think that might also mess up the program because there will be duplicate slots for the same track.

I think having inherited tracks is a useful features now that many conferences are co-located (PLDI/ECOOP 2017, ECOOP/ISSTA 2018), and probably more conference might have this model of having “shared tracks”.

Submitted by Elmer van Chastelet on 12 October 2017 at 10:31

In next release, one can make a track shared with sub-conferences. Shared tracks can be inherited by the sub-conferences. This will make the track’s information such as committees, call for contrib(s), important dates and schedule, available in the context of a sub-conference.
Both the editors of the shared track, and the editors of sub-conferences can choose to inherit a shared track or not.