I'm glad you bring out this distinction between product and project. I was recently making a flow chart for a website I will be developing. I have it split into 2 distinct categories: Public Sections, and Authorization Required (AR) Sections. It seems that it would be beneficial for OSS websites and such to have two distinct categories: project and product. The project side would be the developer info. The product side would be the marketing stuff.
I think it all comes back down to the fact that GNU/Linux and related software started out generally being made of geeks, by geeks, and for geeks. Many project maintainers don't like the idea of commercializing their software. We need a second league of people in the OSS community: the marketers. (think Mozilla) People that don't necessarily know much of anything about coding would be great. People say "we can code free (in both ways) software, but marketing costs money." We could market it for the same price for which we developed it (time). Look at the incredible OSS software we've got now. We're now ready to market it.
Learn about Linux
Download Linux
Get Linux help
Distinction bewteen "Project" and "Product"
Posted by: hosh on March 01, 2005 03:36 AMI think it all comes back down to the fact that GNU/Linux and related software started out generally being made of geeks, by geeks, and for geeks. Many project maintainers don't like the idea of commercializing their software. We need a second league of people in the OSS community: the marketers. (think Mozilla) People that don't necessarily know much of anything about coding would be great. People say "we can code free (in both ways) software, but marketing costs money." We could market it for the same price for which we developed it (time). Look at the incredible OSS software we've got now. We're now ready to market it.
Josh
#