51–60 of 78 posts
Earlier quoted context omitted.
I also worried having two different languages -- Google Swift and Apple Swift.
Maybe you should have tried to find out what this is about before posting it with a completely made up title?
Earlier quoted context omitted.
This still leaves open speculation for why Google developers are working on Swift.
I guess that's true, so i'll be explicit about that too: These Google developers are working on Swift because they are part of a team that supports internal-facing IOS tooling. (there really is nothing down this rabbit hole, FWIW)
Can we change the title to “google forked the swift GitHub repo” or somesuch? The current one is rather misleading!
Earlier quoted context omitted.
I guess that's true, so i'll be explicit about that too: These Google developers are working on Swift because they are part of a team that supports internal-facing IOS tooling. (there really is nothing down this rabbit hole, FWIW)
Oh, that's way less exciting than what I was thinking. Thank you Mr. Bee for that bubble burst.
If we were trying to keep something major under wraps, this would be an exceptionally bad way of achieving that.
The public docs we have even show that we discourage private github repos for various reasons. Our general internal answer would be "don't stage it on github at all unless you are willing to see it leak"
Hi! I’m one of the engineers on this. We’ve got some work we’re collaborating on - all of which is going upstream - and we wanted a shared place to stage it while we prepare PRs. I’ll be pushing a statement to our fork tomorrow. (I’m personally working on Bazel rules and contributions to lib/Syntax. If you find that exciting, please get in touch! :)
Thank God. Otherwise this seemed like a very Microsoft/Java strategy.
But good that they explained. Forking is a common strategy on Github, if one has no write access, to submit a pull request.
Sorry for this language but I do not want it to be at google home.
You guys do not respect others.
Hi! I’m one of the engineers on this. We’ve got some work we’re collaborating on - all of which is going upstream - and we wanted a shared place to stage it while we prepare PRs. I’ll be pushing a statement to our fork tomorrow. (I’m personally working on Bazel rules and contributions to lib/Syntax. If you find that exciting, please get in touch! :)
Not other way around. You create fork and try to push and if they does not agree with you. You will say ok we are having our own fork.
Earlier quoted context omitted.
Maybe you should have tried to find out what this is about before posting it with a completely made up title?
Made-up title? Github says "google/swift forked from apple/swift". Is that wrong?