Quote:
Originally Posted by itsnotabigtruck
What is "well closed project" even supposed to mean?
Open-source benefits the community, and it also comes back and benefits you. Furthermore, it gives users reasonable and well-defined rights instead of arbitrary edicts that leave users not knowing what to expect.
My advice: get an account on Google Code, Launchpad, SourceForge, or any one of the other code sharing sites, and use the version control features they give you to share and track your code. That way, your code is backed up and safe, you can share the code both with your team and with anyone else, and everyone can see the progress that is being made.
|
He meant a "good" closed source project. As for the difference, they both have benefits and drawbacks:
-Closed source: Tend to work best for companies trying to turn a profit. Works best with a skilled and dedicated team working on a single product or aspect of a product.
-Open source: Tend to work better for community projects. Works better with a number of widespread developers who are simply looking to create a working product, not necessarily a perfect or fiscally wise one
For our purposes, open source makes more sense. Your advice about having more than one site to release code on is a wise one.
