> it's somewhat interesting that we don't consider the source code history in our OSS licenses Developing is in the burden of the single developer/project and

> it's somewhat interesting that we don't consider the source code history in our OSS licenses Developing is in the burden of the single developer/project and which kind of version control system is used to produce releases can hardly be mandated by copyright law. It is only one reason to use a F/L/OS/S license for contributing back, that is taking part in the development project. So on the other hand, it sort of does consider that, but it's merely then in the social interaction. What so hurtfully happened here is that a collaborator tried to break the ties (forcefully) and was powerful enough to do so. Sure, this renders the OSS license less effective, and I guess this can be seen or felt by many developers.