I was fortunate enough to experience the eclipse while under parachute up in Madras, OR. There were a total of 23 of us on the flight. In comparing notes to the people that were on the ground we had one additional experience that they missed - we could see the passage of the umbra across the ground as totality started and ended
Given that the most appropriate response to a politician is "go and f*&k yourself", I'm not a bit surprised that this phenomena is showing up in the Potomac.
I say we set up a PayPal donation fund for the research team to spend a few weeks in the Capitol building.
Thanks for all of the input. There are a few people that homed in on the real question - which is simply how do we structure a legal agreement that will protect both their interests (proprietary IP) and my interests (generic framework code available for OSS licensing).
Let me give a more specific example - Let's say a month from now the client comes to me and says "Hey, we want the UI layer to be able to dynamically generate UI from XML screen definitions. I would make an argument that this is non-business specific, and therefore belongs in the framework, while they may make the argument that it was their idea, and should be considered part of their proprietary IP.
If we do disagree, what measuring stick do we use to determine if the proposed code is framework or proprietary? And if we still disagree, what is the process for arbitrating a final decision?
Just in the interests of keeping everyone up to date we have agreed to the following:
1) Any enhancements to functionality that is already represented in the framework will remain part of the framework.
2) When new functionality is introduced during the course of the project it will be evaluated to determine if it should be in the framework or remain proprietary. The employer would have final say on where the line is drawn (I can always walk away if I really feel strongly about it).
Slashdot Mirror
I was fortunate enough to experience the eclipse while under parachute up in Madras, OR. There were a total of 23 of us on the flight. In comparing notes to the people that were on the ground we had one additional experience that they missed - we could see the passage of the umbra across the ground as totality started and ended
Given that the most appropriate response to a politician is "go and f*&k yourself", I'm not a bit surprised that this phenomena is showing up in the Potomac. I say we set up a PayPal donation fund for the research team to spend a few weeks in the Capitol building.
If you go to the WOW site (www.worldofwarcraft.com) and look at their beta dictionary you will find most of the terms identified.
And here I am still trying to get all of the paint washed off from my rendesvous with Jessica Rabbit...
Let me give a more specific example - Let's say a month from now the client comes to me and says "Hey, we want the UI layer to be able to dynamically generate UI from XML screen definitions. I would make an argument that this is non-business specific, and therefore belongs in the framework, while they may make the argument that it was their idea, and should be considered part of their proprietary IP.
If we do disagree, what measuring stick do we use to determine if the proposed code is framework or proprietary? And if we still disagree, what is the process for arbitrating a final decision?
Just in the interests of keeping everyone up to date we have agreed to the following:
1) Any enhancements to functionality that is already represented in the framework will remain part of the framework.
2) When new functionality is introduced during the course of the project it will be evaluated to determine if it should be in the framework or remain proprietary. The employer would have final say on where the line is drawn (I can always walk away if I really feel strongly about it).