Be warned. I've been down this road. Announcing new projects too early will end up with pissed off crunchers, project reputations ruined, and bad feelings all around. It happens almost every time. And there is blow-back.

This project is a perfect example. They are running batches of tasks to solve for x. When solved, they cancelled all the remaining tasks...including the tasks already in progress. An innocent mistake, and they are going to change that in the future. Only tasks not already started will be cancelled. But precious crunching time was wasted this round. And these were fairly long running tasks, many hours in length. I myself lost about 120 hours of crunching just with this one little learning mistake by the project.

Fair enough. That's the price of being an early adopter.

But many who *want* to be early adopters really don't have the mind-set to deal with the consequences. And then the complaining and bad-mouthing begins, and the project gets a bad reputation. All before the project was really wanting publicity to begin with. Loose-loose.

People who are actually suited to the new projects know how to find them, and will make the effort. No need to announce.