To inject some actual numbers into this discussion, for the work reported above, this worker has been paid ~$3250 USD in BTS. Of that, BlockTrades plans to charge $700 for the work we've done (this includes more than just the time we spent on the windows build and issue 251, as we've had to spend time learning and discussing ways to improve the current workflow). Given the work that CNX did during this period, I think it's quite reasonable for them to charge $2550. SVK's feelings aside, I don't think we're likely to see CNX doing development work for free. The best I think we can hope for is that they give us a discounted rate, which I think this represents.
I certainly plan to increase the amount of time we can devote to this worker, but I know our next week is booked with updating our web site for our public offering, so I plan to make no charges during that time for BT. The one exception to that is if we wind up working on this issue:
https://github.com/cryptonomex/graphene/issues/591.
It's been suggested that we should report what issues we plan to work on, but this really isn't a simple thing to do reliably. Priorities of issues rapidly change as well as available people to work on them. It's much easier and more reasonable, IMO, to report what was done and what was charged. I'll evaluate what is done by CNX and us over the next period, then distribute accordingly, including returning funds if less was done than the worker provides for.
However, it is important that programmers know what issues other programmers are working on to avoid work duplication. For programmers, the answer for this is addressed in a new document I wrote recently to describe our updated workflow plans:
https://github.com/cryptonomex/graphene/wiki/Graphene-GitHub-GuidelinesTo answer abit's question, we did not have a chance to look at the "mobile spam" issue yet. From preliminary discussions with Theo and BM, we understand the nature of the problem, and the most likely solution will be one of examining the flow of data and coming up with some heuristics to reduce the flow. In other words, there's no simple "clean" solution. We're still planning to address this issue when we have a chance, but if you want to take a crack at it, assign it to yourself. If you can make a significant reduction, report it to us and we can work out some way to pay you for the work.