No, if you fork it, then you have your own copy of it and you can work on your own copy of it, and leave the original behind forever too. You should fork it. That's how the whole GitHub thing works!jasolo wrote: ↑Thu Feb 15, 2018 8:09 amI prefer not to fork it. So I make pull requests and push commits, but if Wolfsblvt has not the time to approve them, I will need write access and Wolfsblvt has offered it.
Just suppose I fork the extension. What happens if in the future Wolfsblvt comes back and does not like my changes? then there will be two extensions with the same name. In that case renaming the extension would be a good idea. But as I said, I prefer to use the original repository. I am a newbie in GPL things so maybe I am wrong.
If Wolf comes back later he will not know anything about your changes, because all you've done has been on your own repository...totally independent of his. Your fork, your repo, your own version of the extension.