> - What is the best practice to define if you should PR the original repo or fork from it ? It depends the context, if you aim to deeply modify the project by

> - What is the best practice to define if you should PR the original repo or fork from it ? It depends the context, if you aim to deeply modify the project by taking another direction, better to fork, in the other hand if you aim to participate to a bugfix or a new feature better to do a PR. > - What is the Etiquette to maintain the original authors rights when forking ? How can you define his contribution ? is it based on the code yo exactly copied, the idea, the architecture ? IMO it is a good thing to declare that the base work of the fork is taken from somewhere and is owned by his original author. Then if you plan to make changes you create a file where you list all your own contributions that are owned by you. > - How to handle cases when there are no license information attached ? In that case it is a good thing to ask the author in case there is no license. Otherwise you cannot do anything with it. > - How to handle PRs/forks when you work merges/combines more than one original repo ? There are some tools that can manage this by highlighting the possible conflicts among all the PRs (Jenkins for example), I don't know for the forks. > - How to handle cases when conflicting licenses are used across repos that you have referenced ? Unfortunately you cannot really do something, as legally if a license does not allows you to do something you cannot go against. A solution might be to talk with the respective authors of the conflicting repos.