3 ms·

I found this title very confusing. I thought it was the equivalent of their non-profit being absorbed by GitHub. Meaning, the corporate structure." Why don't t

by atonse 8y ago

I found this title very confusing. I thought it was the equivalent of their non-profit being absorbed by GitHub. Meaning, the corporate structure." Why don't they just say that Apache will officially host their repositories on GitHub moving forward?

nevi-me 8y ago
I agree, also find it confusing. I thought this meant moving from JIRA to GH, but I suppose this announces something that users and contributors of Apache projects wouldn't have thought of; that the was an active decision to move to GitHub. The move is confusing also because I thought Apache were migrating to their own git server, I think late last year or early this year.
- TallGuyShort 8y ago
  They just finished migrating to Gitbox, but GitHub mirrors have been used for a long time and some projects have been using pull requests more in lieu of reviewing patches on JIRA.
jwilk 8y ago
The ASF press release (https://blogs.apache.org/foundation/entry/the-apache-software-foundation-expands https://blogs.apache.org/foundation/entry/the-apache-softwar...) title is better: The Apache® Software Foundation Expands Infrastructure with GitHub Integration
nimbius 8y ago
Because the writer, Bryan Clark, is Director of Product for OSS Maintainers and is trying to contextualize the move to feature the company he works for, not the code thats been around for far longer. "apache moves to github" makes it sound like apache made a rote and boring switch, which this sort of is. They just as easily could have moved to sourceforge or gitlab. joining a team has implications that github (c) works together with open source. while it certainly hosts a lot of it, github isnt open source. Headlining this as your "open source community" also helps avoid the uncomfortable issue of an open source product moving to a completely proprietary system for CI and development.
- svnpenn 8y ago
  > while it certainly hosts a lot of it, github isnt open source. Yep. This was something that surprised me https://github.com/github/markup/issues/1266#issuecomment-484293407 https://github.com/github/markup/issues/1266#issuecomment-48...

by atonse 8y ago

nevi-me 8y ago

I agree, also find it confusing. I thought this meant moving from JIRA to GH, but I suppose this announces something that users and contributors of Apache projects wouldn't have thought of; that the was an active decision to move to GitHub. The move is confusing also because I thought Apache were migrating to their own git server, I think late last year or early this year.

TallGuyShort 8y ago
They just finished migrating to Gitbox, but GitHub mirrors have been used for a long time and some projects have been using pull requests more in lieu of reviewing patches on JIRA.

jwilk 8y ago

The ASF press release (https://blogs.apache.org/foundation/entry/the-apache-software-foundation-expands https://blogs.apache.org/foundation/entry/the-apache-softwar...) title is better: The Apache® Software Foundation Expands Infrastructure with GitHub Integration

nimbius 8y ago

Because the writer, Bryan Clark, is Director of Product for OSS Maintainers and is trying to contextualize the move to feature the company he works for, not the code thats been around for far longer. "apache moves to github" makes it sound like apache made a rote and boring switch, which this sort of is. They just as easily could have moved to sourceforge or gitlab. joining a team has implications that github (c) works together with open source. while it certainly hosts a lot of it, github isnt open source. Headlining this as your "open source community" also helps avoid the uncomfortable issue of an open source product moving to a completely proprietary system for CI and development.

svnpenn 8y ago
> while it certainly hosts a lot of it, github isnt open source. Yep. This was something that surprised me https://github.com/github/markup/issues/1266#issuecomment-484293407 https://github.com/github/markup/issues/1266#issuecomment-48...