When working with ON I'm faced with an interesting complication at times in that I need to identify the license to a patch. A situation where this already exists in ON is with krb.. Some (most) is MIT, but the Sun parts are licensed under CDDL.. (Not the concern here at all and just an example) However, one of the reasons I think that Sun *must* currently have copyright to all new patches from external contributors is so that they can track the legalities of code in case of the need for future vetting/lawyer bs.. etc..
To be honest.. I'm not proposing this feature be included in ON now or any time in the future.. However.. with my side work everything will be readily available to those interested.. (Such as trying to maintain a diff from mit-krb vanilla vs the Sun patches) Another side affect of this will possibly be better long term manageability/auditing for the larger packages. (perl. etc..) I ramble too much.. bottom line: Is being able to track a license to a patch valuable to anyone else? yes/no Thanks ./C ps. (yes I assume this is already somewhat available by referencing patches in some external/internal bug tracker, but with my build changes I can enforce policy which would block the code from buliding entirely)
