I think we should differentiate between structure and content. I agree that the LSC should define the structure and syntax of the config file, just like they do for parts files. But we don't expect the LSC to review/control the content of every part file, so why the config files.
I see the maintenance of ldconfig.ldr as an authoring exercise, although unlike parts files, we only really need one author - and Scott is doing a good job in that respect. I don't see a problem with Scott handling the review process independently of the Parts Tracker with those known to have a strong interest in this area.
The current release process is to post updated versions on the server for individual download, and incorporate the updated version into the subsequent parts update.
I see the maintenance of ldconfig.ldr as an authoring exercise, although unlike parts files, we only really need one author - and Scott is doing a good job in that respect. I don't see a problem with Scott handling the review process independently of the Parts Tracker with those known to have a strong interest in this area.
The current release process is to post updated versions on the server for individual download, and incorporate the updated version into the subsequent parts update.
Chris (LDraw Parts Library Admin)