> "This is being a part of a community, bringing something to the table and sharing it without expecting anything in return." this is also a good one. i think

> "This is being a part of a community, bringing something to the table and sharing it without expecting anything in return." this is also a good one. i think it's ok to expect community in return, and to try to engage (nicely) with others who want to be secretive. the main point, though, is to see oneself in an ecosystem that benefits from exchanging knowledge and goods. far too many developers are afraid that their project will get swiped if they share their code. it is more likely that everyone else is already too busy. i would also like to think that by being open, others are more likely to collaborate with you, or bounce ideas off you, or learn from your code. distrust results from fear, and most fears are irrational. the result of the desire for secrets and power is serious harm. there are many shining examples of open developers, companies and communities, so i know this can work in certain situations. the thought that one defector can ruin it for everyone--other than some risks being worth taking purely to stand on principle and strive for goodness against the dark--i'm not sure how to handle. perhaps there is a middle ground. i don't have enough data to be rational here ;-)