The difference matters very much. Compiz is already a developed compositor (program) that needs maintenance, not a maintenance program that needs development. I had mentioned in some of the threads that we could perhaps port unity to wayland! Now that would be a development project that would need a lot of maintenance how ever far fetched the idea may be.
One of the ways I am trying to tackle this is to get committed persons to code and do maintenance. If I have 10 persons committed to 4 hours a week then that is one utility 40 hour volunteer work week, not only in theory , but, in practice. So far we are doing quite well. This will give developers, who are committed to other projects, more freedom to offer assistance and do bug triaging in the background and others may be attracted to this type of working template where they are not bound in the chair for 30 hours a week (I am currently doing 20+ hours but I can take timeouts for two days at a time and work when it is convenient, mostly in the wee hours, and burn the midnight oil.
So this building of the team is not going to happen overnight. It’s one day at a time. This is a community project that consists mostly of volunteers and is receiving a lot of valued guidance from Canonical persons and for that I am grateful, no matter what the outcome. We don’t want to have a case of “compizitis” meaning that we have to focus all our efforts on compiz. There are other components that need love and attention as well, the new X11 for example! Our priority is to stay focused and stay positive. We do not want potential contributors to be turned off by a constant and negative mindset that scandalizes the current default DE, gnome3+wayland, and wails over the keelholing of the unity8+convergence project. I am confident that our mindset as a team, from testers to wiki editors to devs to critiques will prevail over such negativity and we will succeed in giving something beautiful back to the community, that, which Canonical has so freely given us.