I voted repo and VASM/installer.
In particular, I'd like to see the wall between SOHO and Standard torn down, and LiveCD too if possible. Develop concurrently, release concurrently.
I'd like to be able to start with an installation of Standard, add KDE and other SOHO apps, and end up with the same system as if I'd started with SOHO and added Xfce and other Standard apps. In practice it doesn't quite work like that today.
Get all the install packages from both versions in one repo, and then build the ISOs directly from those packages. I'd like to be able to use something like Jigdo
to build my own ISO from the repo. Heck, maybe even use it for the official ISOs? Alphageek's Sligdo
script/template for using Jigdo to build Slackware ISOs from the repo would probably be a good place to start.
I've also been wondering if a common 'clean' environment for building packages with checkinstall would be helpful. Something that would start with only the packages common to the common versions of both Standard and SOHO and then builds from there. I'd like to easily be able to start it up, install the dependencies, build the package itself, shut it down, and have the install still be 'clean' for the next use. The clean base itself would probably be read-only, and then use UnionFS or something to bring a writable drive in. Obviously that's a lot like how LiveCDs work, so a LiveCD would probably be a good candidate for the clean base. Otherwise, a separate install on a read-only partition, or maybe even something like VirtualBox or VMware could be used for the build environment. The build environment should have access to the local package cache and install CD, since every time you use it it's only going to have a very minimal set of packages installed.