A new home for Google Open Source
61–70 of 71 posts
Re: A new home for Google Open Source
#62It looks like some of these projects repos link to GitHub, while others are hosted on this new platform. Is this a signal that Google is moving away from GitHub, or something else entirely? Edit: Ah, here's the relevant blog post: https://opensource.googleblog.com/2017/03/a-new-home-for-goo...
No, we're deeply committed to continuing to release projects on Github.
Re: A new home for Google Open Source
#63here we go again, at some point google "deprecated" code.google.com which was great for developers in china because of the gfw. now they're going back to a google source control service, this means that i have to develop with a vpn which is a simple pain in the ass.
Re: A new home for Google Open Source
#64Re: A new home for Google Open Source
#65Earlier quoted context omitted.
Errr,it's completely and totally unrelated to that. It's because we have tons of temps, vendors, and contractors, and don't want to have to owe them source code to internal systems. The other alternative (remember that google is a monorepo) would be to somehow police them differently. That is literally not worth the cost.
I don't see how having "some proprietary code that they would like to keep proprietary" is "completely and totally unrelated to" "not want[ing] to have to owe [someone/anyone] source code to internal systems"?
Re: A new home for Google Open Source
#66Earlier quoted context omitted.
I don't see how having "some proprietary code that they would like to keep proprietary" is "completely and totally unrelated to" "not want[ing] to have to owe [someone/anyone] source code to internal systems"?
What's going on with the names of you all?
The others were just created, presumably to be reddit-level-hilarious
Re: A new home for Google Open Source
#67Earlier quoted context omitted.
The problem is that we have over 2,000 projects, so simply listing them all on one page doesn't work very well. Hence why we built this directory, which allows browsing by category, by tag, by language, as well as full text search.
If only there were some way to search such a vast number of project listings. Some type of engine, perhaps.
Re: A new home for Google Open Source
#68Earlier quoted context omitted.
Agree. Over use of animation. All these are good examples. If Google has 50+ projects, then it's best to just have a page with multiple rows, each row is a category, and upon click can expand down to what #3 looks like. Or perhaps just GitHub README... it's pretty nice to read. [1]: https://netflix.github.io/ [2]: http://twitter.github.io/ [3]: http://etsy.github.io/
The problem is that we have over 2,000 projects, so simply listing them all on one page doesn't work very well. Hence why we built this directory, which allows browsing by category, by tag, by language, as well as full text search.
The Debian Project last I checked (a year or two back) had over 60k software packages. It's got an interface for delivering those. Actually, several interfaces, and the ones I prefer and use are commandline and filter through grep, if they don't provide their own search interfaces.
And those are platforms which are noted ... for their relative lack of software availability. (I think that criticism is ... misguided in several ways, but on a sheer quantitative basis, there are some pale merits.)
If Google cannot figure out how to manage, organise, present, and offer useful search interfaces to a measely 2,000 pieces of software, then, with all due respect, get the fuck out of the way for someone who can.