Well, I certainly don't dispute that we've dug ourselves into a conceptually messy situation. I suppose our own individual forks would have the ability to act with all the needed authority / capability. I'm comfortable with it. The only thing that remains, from my perspective, is understanding how maintenance flow looks and documenting it.
First cut off the top of my head: 1. I fork github.com/apache/cordova-ios 2. I make a few fixes and send a pull req 3. that pull req mails this list 4. ppl review it 5. looks good, I merge it to the apache.org git repo 6. changes are reflected on gh mirror Sound about right? On Fri, Jan 13, 2012 at 1:21 PM, Filip Maj <f...@adobe.com> wrote: > >>> 1. can we be org members w/ the apache mirror, comment, admin, etc w/ >>> the same capabilities provided by having our own org? do we maintain >>> the mechanism for pull reqs and review? not clear on this yet. who >>> maintains the github.com/apache owners list? >>> >> >>My thinking is that we have no presence at GitHub except the shadows that >>Apache maintains. It would be nice if folks, including us, can fork those >>and work out of them if there are GitHub-y things we want to do with our >>forks. That would include pull requests doing something interesting. > > My thoughts exactly. On top of that, sending a pull request to the > github.com/apache mirrors sends an email to the dev list, so hopefully > that is "interesting" enough in terms of pull request handling :) >
