Free projects from IT companies (2)

Avoid the vaporware effect; don't announce or publish projects until there is something to play with, a bad first impression can keep a lot of people away from a project for a long time
Provide human resources: if the software is going to be used by the company there has to be someone in charge of the project who is able to review and integrate patches and handle releases (or at least keep the company's branch under control)

Avoid the vaporware effect; don't announce or publish projects until there is something to play with, a bad first impression can keep a lot of people away from a project for a long time