I'd like to know the project administrators' policies on accepting
contributions to CppTasks, either as patches or by admitting a new
CppTasks works, I like its design, and I see a LOT of potential (i.e. room
for improvements that could make it the best cross-platform builder), but I
don't see it evolving at a pace that would make me feel comfortable to use
it in all of our organization's long-term projects.
My organization is about to standardize our build process using Ant, even in
our C++ projects. We have dozens of projects, all of them cross-platform,
some using pure C++ and others using Qt.
If we are to use CppTasks we'd be willing to contribute to its development,
and we already have some small patches to submit. Two weeks ago I made a
feature proposal of a 'package' system for cpptasks; I've already developed
that system by subclassing CCTask, but I had to change two methods. CCTask
is not easily extensible, and it could be made so with little effort.
Extensibility is always nice; we could then offer our cpptasks 'add-ons'
separately if it's not suitable to the main distribution.
I can certainly help with Qt (3 and 4) and VS.NET 2005 related development.
The author of the above post would probably make a good contributor as well.
What happened to him? By reading Curt Arnold's reply it seems that the
project admins are short on time and can't give much attention to the
project anymore. If this is the case, PLEASE admit new developers, it's
always better than let the project fade.