This is generally true right up until you accept patches from outside the company. At that point, unless there was copyright assignment, you need to get those contributors permissions to switch their code over to your new proposed license. That's usually a dicey process as half the time you can't reach the people in question at all and there's usually not a big incentive for them to allow you to close source their works. This is one of the big that larger projects are more often making contributors sign copyright assignments prior to allowing their code to be committed to the tree.
While there tends to be a nerd slant, I think the general lean is towards stories that matter to people. There are numerous examples of historical stories that didn't have a tech lean where there were still extremely interesting and informative discussions that followed.
This new concept fascinates me. We can take these individual blocks of code. Let's call them "libraries", and join them together with some kind of programmatic glue and potentially reuse them to make some kind of application. This is definitely cutting edge thought. I'm not sure it will catch on though.
VACM can provide all the functionality you're looking for and more... It provides the ability to monitor machines at both the hardware and software level.
Slashdot Mirror
It would be super cool if there was some kind of technology that allowed you to provide a link to the source material for discussion...
http://queue.acm.org/detail.cfm?id=2508864
This is generally true right up until you accept patches from outside the company. At that point, unless there was copyright assignment, you need to get those contributors permissions to switch their code over to your new proposed license. That's usually a dicey process as half the time you can't reach the people in question at all and there's usually not a big incentive for them to allow you to close source their works. This is one of the big that larger projects are more often making contributors sign copyright assignments prior to allowing their code to be committed to the tree.
While there tends to be a nerd slant, I think the general lean is towards stories that matter to people. There are numerous examples of historical stories that didn't have a tech lean where there were still extremely interesting and informative discussions that followed.
This new concept fascinates me. We can take these individual blocks of code. Let's call them "libraries", and join them together with some kind of programmatic glue and potentially reuse them to make some kind of application. This is definitely cutting edge thought. I'm not sure it will catch on though.
Zac