Jambunathan K <kjambunat...@gmail.com> writes: > How do you interpret the following block extracted from my assignment > > ,---- > | 2. Developer will report occasionally, on Developer’s initiative > | and whenever requested by FSF, the changes and/ or enhancements > | which are covered by this contract, and (to the extent known to > | Developer) any outstanding rights, or claims of rights, of any > | person, that might be adverse to the rights of Developer or FSF > | or to the purpose of this contract. > `----
Well, the FSF's intention here is to make sure that contributors report back when they change employers, and the new employer doesn't want that his employees contribute to some GNU project (maybe because that project is in the same business as the company). So I think of that more of a safety measure in order not to run into long-running, painful lawsuits. > FSF clearly side-steps the important question - when is a work > actually assigned. Assignment is not a process but an event tied to > specific time and date. As far as I understand it (just after reading one of my FSF CAs), the changes you apply to a program where you've assigned past & future changes are assigned as soon as they are written. They don't need to be published, distributed, placed in a special repository location, etc. Bye, Tassilo
