v6.73.w3x map Of course it's fine to explain prominently on the fork's home page that it descends from the original program, and even that it hopes to supplant it, Just don't make users' lives harder by forcing them to untangle an identity dispute. Finally, you can get things started on the right foot by automatically granting all committers of the original project commit access to the fork, v6.73.w3x map including even those who openly disagreed with the need for a fork. Even if they never use the access, your message is clear there are disagreements here, but no enemies, and you welcome code contributions from any competent source. an v6.73.w3x map The license you select probably won't have a major impact on the adoption of your project, as long as the license is open source. Users generally choose software based on quality and features, v6.73.w3x map on the details of the license.