Hacker News new | ask | show | jobs
by bobajeff 737 days ago
>This change will allow Swift to expand its reach to more platforms and use cases, sparking fresh possibilities and broadening Swift’s impact across the technology landscape.

How does having a GitHub organization tangibly impact the implied goal of making Swift more impactful outside of apples devices?

5 comments

Beyond the pure signaling value, I would imagine Apple has internal GitHub tooling which maintains particular invariants for repos hosted under github.com/apple. Those invariants can potentially be relaxed or discarded altogether for a different org much easier. (Special-casing particular repos within the repos is technically possible, but (a) is harder and (b) probably runs into policy issues with legal.)
It does sound a bit silly on its face; apparently the repositories are in Apple’s org which limits access to GitHub-isms to members of Apple GH teams, and so it sounds reasonable if their goal is to extend the community beyond those limits on the GH platform.
Having non-apple members in the language organization in GitHub seems like a nice improvement.
GitHub org permissions aren't very granular, especially with an org that is tied to enterprise SSO. Makes it hard to grant certain permission to outside members.
They're certainly wearing their heart on their sleeve there.