I understand what you mean and I don't disagree. There are some things where we will want to collaborate and it's normal in other projects to have a branch for this as well. Those usually are major features.
I'm referring to (fully understanding that this is ill-defined) "minor" things and things that won't require collaboration on this level or where it doesn't look like it'll be needed. Every branch in the main repo causes commit mails to the commit mailing list, old branches need to be cleaned up, you need to remember what they were about etc. This is partially due to my background. I'm semi-active in 20 or so Apache projects. Often contributing minor things because we do troubleshooting at our clients. ~60% of our work consists of decrypting commit messages, finding relevant Jiras, figuring out where and why things were changed etc. So it is my pet peeve to have stuff "lying" around because it confuses the hell out of me and other "newcomers" to projects. Without a clear documentation/README for every branch, it is very very hard for anyone coming to the project to find out what's actually current and what's not. I'd love to have branches or even Pull Requests refer to a Jira ticket as well. Currently, we don't do that. It makes contributions from "drive-by" contributors harder so I understand why we don't do it but this is - in my daily job - one of the biggest problems. I call it Open Source archeology: Trying to find out why something was done the way it was done in the face of eroding and incomplete information that was _entirely clear_ at the time the decision itself was taken. I hope that helps to explain my reasons? On Wed, May 15, 2019 at 8:30 PM Christofer Dutz <[email protected]> wrote: > -1 > > As a lot of work will have to be done in a collaborative fashion. This > should be allowed to happen in the repo and not outside. > > So in not against external prs, I'm against forbidding internal ones. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > ________________________________ > From: Kenneth Knowles <[email protected]> > Sent: Wednesday, May 15, 2019 7:54:01 PM > To: [email protected] > Subject: Re: Git branches > > +1 to fork & PR. It works great. > > *From: *Lars Francke <[email protected]> > *Date: *Wed, May 15, 2019 at 9:58 AM > *To: * <[email protected]> > > Hi, > > > > I'm not sure how other projects do this (well, I do, but not all of them) > > but I'd be in favor of keeping the Git branches we have clean (i.e. not > > having feature branches in the Apache repository). > > > > They tend to be forgotten, they are often not documented and can be > > confusing. I'd be in favor of developing in your own fork and then > > submitting a PR. > > > > What do others think? > > > > Cheers, > > Lars > > >
