[email protected] (David A. Greene) writes: > Going forward, I would like to do the main feature and bug fix work on > GitHub and periodically subtree-merge to git's main repository under > contrib when the code has stabilized and we are reasonably confident > interfaces are stable. This will allow us to experiment with new ideas > while keeping a stable codebase for end users. > ... > Does this mode of operation work for the larger git community? Are > there suggestions of how to make this work as smoothly as possible?
As a reasonably well-known and mature project, I'd actually welcome the idea of git-subtree graduating from my tree and standing on its own, managed in the way its developers and users prefer using the workflow they choose to use. If it is a good idea to keep a copy in contrib/, that will stay to be slightly to moderately stale depending on the phase of the "upstream" development, by periodically accepting code dumps? I do not have a strong opinion on this. It is not too much work for me personally to do so, but - I think git-subtree no longer needs the "contrib/ bump" to sustain its userbase and community; otherwise you wouldn't be sending out the message I am responding to. - Seen from the world outside the Git world, it may be confusing if two different "sources" of git-subtree exist; the users and the distro packagers want fewer choices in things like this. So I do not have a good answer to what should be done to the copy in contrib/, at least not yet, but I think it is a good idea to separate it out as its own development project with its own community.
