Trying to gather a group of people to do this is exactly what I am trying to do. I think I must be going the wrong way about this. I have had to think long and hard about what I am doing here, and the only answer I seem to be able to come up with is this: just make the solutions, and the people will come. I am wasting my time asking questions, although steevc gave enough of an answer to get me moving on the right path. It sounds like I will have to make additions to the piston codebase to create a way to do this. It doesn't matter if it 'takes a long time' to get the data. That's what a computer is for, to perform time consuming tasks that are difficult to perform manually.

I am not directly interested in this at the moment because my particular projects do not require this until quite some time later in their development. I will focus on what is in front of me and document my solutions as I go, and maybe I will both find people who have the open development attitude I have been used to in the open source community, as well as winning fans from those who are coming up just behind me.