(I’m personally working on Bazel rules and contributions to lib/Syntax. If you find that exciting, please get in touch! :)
Don't see a problem.
This posting let you know their intention. Isn't it newsworthy?
- I was worried about Google's intention, but I didn't claim one.
- I chose the word "fork" because it was what actually happen.
I tried to be dry as much as possible to deliver just a fact.
Making people confused was not my intention.
Anyway, I'm sorry for that confusion.
- I didn't think the word "fork" is abusive or bad wording at
the point of posting. I simply forgot the other
meaning of "fork" at the point of posting.
Now I remembered how it's different.
- Now I agree that the word "fork" could make you
(and many other people) confused.
- If the wording "fork" made you confused, I think you also need
to blame Github for why they didn't use the word "clone"
on their website.
- I blame Github because this is major reason of why I forgot
the other meaning of "fork" nowadays.
- You are telling me to find out before posting this to here, but how?
At the point of posting, there was literally no one was
discussing on this. No one around me could explain Google's intention.
I googled, and there was no result.
If you know a good place to ask, please let me know.
I'd love it.
- Google engineers came and explained their intention.
IMO, this posting ended up in the best way it could.
But good that they explained. Forking is a common strategy on Github, if one has no write access, to submit a pull request.
In general, corps only fork a repo when they want end users to use their repo.
In the case of development by corp's developers, they just generally fork it themselves and submit PRs from their accounts.
so I can see the confusion.
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.
Facebook people also contribute to Swift but Facebook has no fork in their repository instead the person who contributes have in their own repo.
I have read somewhere steve jobs was very unhappy with this event and that is the reason they make their technologies close.
Swift is hard work of lot of people and Swift community, I really love the openness it brings in Apple. These types of incidents make them to rethink their decision and let developers like us to not involve in their choices.
Chris Lattner has done wonderful job to make community like this and if google misuse and made their own language out of hard work of swift community I do not think it is good for any of us.
I read google have not forked so I take my comment back as I cannot delete it.