On Wed, May 15, 2019 at 11:54 PM Justin Mclean <[email protected]> wrote:
> Hi, > > -1 > > We shouldn't be doing work outside of the offical repos. The commit > messages leave an important paper trail that are required for legal reasons > / ASF policy. > I don't understand: Isn't that what you do Justin? You prepared your PRs in your own fork and commits and commit messages don't get lost. I don't see the connection. This is also the "standard" model for basically all ASF projects I know: You prepare your work outside of the repository and then submit a patch or PR. Also: Most people don't have the privilege of being able to create branches in the official git repository. Only committers/PMC which is a tiny subset of everyone out there. It's much easier to give some external not-yet-committer access to some "private" fork to collaborate. Isn't this the whole idea of git being distributed? > It also makes it (as Chris said) much harder to collaborate on stuff. Even > worse you may not know these branches exist or are being worked on until > the PR pops up and that can result in duplicated work or people going off > in incompatible different directions. Even if it it is for “minor” stuff, > an extra set of eyes of work in progress can help or encourage > contributions. > For Work-in-progress stuff Github has a WIP features for PRs. One option is to delete branches after they have been merged into master so > they are not lying about. But I'm not sure why you care abut a branch > after it has been merged into master anyway? For branches that get > abandoned, I think it's better that hey are in the main repo as someone, > someday may find something useful in them or decide to pick up on where it > left off. If it outside the ASF then it may be lost forever. > I explained why in my last mail: Having hundreds of branches gets confusing VERY fast in my experience. To someone coming along in a year it's not obvious _at all_ why a branch exists, what its status is etc. > > Thanks, > Justin
