No harm at all, I guess. In my case, was just a practical thing, I have the opinion that we need to take this as a long term project, because there are many issues to solve. For example, ZW ships xorg 7.2, I dont know what vers of glibc, qt, wx* and other fundamentals libs are they using, not all the others are following slack step by step, and I dont know how this can affect the building-package process.
I dont know why the paid support thing ran fast, and I have no manner to know. I guess people who takes the decisions were interested. IMO, a common repo could be a big impact, bigger than any other project. As I said when I proposed it, I think the success of several debian based distros is they can use the hughe kanonikal/*buntu repos. Slack based distros are dividing efforts, and debian based are joining them. In addition, we dont need to agree in everything, just in some standards to build packages (i guess, may be i am wrong). So this is a good point to start a merge. But cant be done in a blink, I am not saying "dont do it", I am saying lets work some before talk with others, we really dont know even if it is possible at all. We were just "thinking at loud", a lot more if needed to start a project of this kind.
About the big projects running now and the manpower needed to do them (may be including this one), I think could be good to have a wiki, with a page for each project, and one page for each work area of the distro, where you can read the goals of the project, the name of the project leader, the name of colaborators, the resources needed, the stage of the project, what kind of help is needed, etc. May be in that way we could get more help in a more efficient way, mostly in no-critic areas, and minor tasks now taken by main devs. The ways we can join to the devs efforts are not documented at all, and that is a mistake. I think there is many ways to help than the financial way, and we have our focus on just that way. In addition, people with an interest in common could start a new project in an organized way (for example, the projects of our gambas-devs, a new web-site for vl6, new contents of the site, new flavors on graphical/desktop design, new apps or systems to implement, migration and/or upgrades of fundamentals libs, and other nice ideas that you can see in the forum).
The only thing agains this kind of wiki for projects is the wiki itself is a project, so we need a wiki for the wiki project, and a wiki for the wiki...ad infinitum
Just my $ARG 0.02 (1 US$ = 3.08 ARG$)