Shared publicly  - 
 
London developers,

I'll be talking about the Google Drive SDK at the London GTUG on the 8th of June from 6:30 to 7:30pm. Come to learn how to integrate your web applications with Google Drive!

Details: http://www.london-gtug.org/Venue/google-drive-sdk
Registrations: http://www.eventbrite.co.uk/event/3642986270
14
12
Danial Klimkin's profile photoRich Hyndman's profile photoSam Dutton's profile photoSilvano Luciani's profile photo
26 comments
 
How about Google learn to integrate Google Drive with Linux first before you go tracking all over the world to show others how to integrate Google Drive? #DriveForLinux
 
I see, so Google simply handed Windows, Mac, Andorid, iPhone, and iPad users the API and told them to go do it themselves?

Nice to see that Google has so much 'respect' for the Linux community ... didn't even bother to mention Linux in the release, then when +DriveForLinux started to trend on G+ they said it was on the way ... since then not a single word out of Google about #DriveForLinux..

Bah ... no wonder China made Google sign that open source promise.
 
+David Landry Not sure why you are tolling :) we announced that we are working on a Linux sync client - and I confirm. We are also working on many more things. Just be patient!

Also isn't the China thing about Android? Not sure what this has to do with Google Drive though.

To come back to the main point, this talk will be about the Google Drive SDK and will show how web apps can integrate with Google Drive (it won't be about how to develop sync clients which currently use Documents List API) similar to what some companies have already implemented such as Floorplanner, Pixlr, Autocad, Mindmeister, Balsamiq etc... Check the full list: https://chrome.google.com/webstore/category/collection/drive_apps

Cheers!
 
Trolling? I took an opportunity to get some information out of Google regarding the Linux client from someone who would seem to be connected with the Google Drive development process ... yes, there have been some Googlers that have said they were 'working on a Linux client' .. two I can think of, but when pressed on details they all seem to run and hide.

"Just be patient"? What does that mean? How about Google just be open and honest and give up some details?

What does "working on it' actually mean? Is there a repository we can have a look at to see how things are going? Is there at least a time line estimate - a month, 3 months, a year? Does "We are working on many more things" actually mean "Not going to happen in this life time"?

The Google business model owes a lot to the Linux and Open source communities .. I don't think it is too much to be asking for a little bit of common decency and respect out of Google towards those communities and keep us 'in the loop' ... or if you haven't actually started development on the Linux Client, then at least be honest
 
Googlers in general won't tell you about upcoming features because we have a general policy not to discuss them publicly. But, trust me, each Googlers would love to let you know what is coming up and what he is working on!

There are many reasons as to why lots of [big] companies have this policy, just to list a few: keeping a competitive advantage, avoiding any backlash if not delivering the promised feature for any reasons - reasons could be: lack of ressources, shift in priority, legal, privacy, patented, deal with third party falls off, staff quitting... This policy is usually taken quite seriously and a person's job would be on the line (+eventual lawsuits for loss of business) if he unveiled an upcoming product or feature without having this cleared beforehand.

Now there are many cases, product or features where this doesn't really apply nor makes sense and there are no risks of not delivering and no loss of competitive advantage. It might even be beneficial to talk about unreleased feature in some case. However, in many companies it's not usually possible to trust every single one of their employees to have the overview that would allow them to mesure if that's the case. Therefore, since there is too much at stake, it's usually safer to simply have a general policy not to discuss upcoming feature and to be secretive. Also as companies gain in scope it is usually harder and harder to gauge if secrecy is necessary and would usually need approval from a large number of people (PR, Legal, PM...). So, as external interest/demand for information grows for popular companies, it is not always worth the effort to ask permission to discus each particular cases.

Also about Deadlines, in the case of companies such as Google, it's not generally good to give any as they are usually very hard to measure because of the many code dependencies and things that can come-up internally, (for instance illness of the few staff working on the feature) but also because that allows to keep an agile way of working and avoid loosing time "measuring" in advance how much time things are going to take. So since there is no real obligation to give a deadline, it's usually preferable not to give one as a precaution to avoid any disappointment (and associated backlash) when not meeting them for whatever reasons.

Now given all this, it's a good sign that we announced publicly that we are working on a Linux client, and that typically means that we are committed to it and that we are already working on it. (Otherwise we would have sticked with a canned response such as "we appreciate your feedback... we are always working on improving Google Drive ... The linux community is very important to us etc..." or at least the wording would have been different). That basically meant we cared enough to cleared this up with with a lot of people and take the "risk" to pre-announce something.

As for public repository, currently the Google Drive sync clients, unlike our API Client libraries, are not open source. But "This is something we are taking into consideration as we are always looking to improve Google Drive" ;) More seriously there can be many reasons why companies are not open-sourcing things, first there are some overhead in doing so (maintaining the external repo, external project, patches, writing nice code) and also we wouldn't be able to use 'hidden' yet-unreleased APIs (not saying it's the case here).

I hope this clears things up as to why we behave like we behave, and I think this applies to most [big] companies in general and totally understandable given the over-competitive, legalistic, patented ;) climate surrounding the tech industry now.

PS: Sorry this was a little long :) And sorry for not telling you more about the Drive sync client for Linux, but as you now probably understand: I can't (but I will ask the team if we can tell more) :)
 
Well, then maybe you can pass it on to the powers that be that there are some Linux community members that are getting pretty PO'd st Google's seeming disrespect towards Linux.

I personally am in the process of moving my email (ready), calendar (ready), cloud services (soon) 'in-house' ... just waiting for owncloud to get a complete Android sync client, and if Google doesn't have a Linux client by then I will be moving off of all the Google services I can. I admit I am stuck on G+, but other that that, if Google is not going to provide timely support for Linux, I see no need to support Google any more than I 'have' to.
 
Wow! Awesome answers! May I translate them into Russian and post in one tech blog? This information is really important for people.
 
+Gennadiy Gordeev Sure feel free! :)
+David Landry Don't do it! :D While the idea is nice it will be lots of efforts to maintain such a system. It's fine if it's for the challenge of it :) But keeping your home internet connection up at all time, dealing with hardware issues & backups & updates! Or setting up EC2 to host that. Doesn't seem worth the effort to me for purely practical purposes. But if you just want to have fun setting this up I completely understand ^^
 
+Nicolas Garnier I understand the effort required, but since Google doesn't seem to respect the Linux community I figure if in order to use Google services going forward I would have to spend effort writing to Google APIs to create Linux software that Google should be creating themselves, then I would be better served devoting any effort I 'have' to expend finding ways to get off of Google. (Which is why I find comments about "build your own client' so offensive ... if I need to 'build my own' anything it will be to service my needs, not Googles.)

I would really hope that more and more Linux/opensource community resources would start to see that spending their efforts to do free work for a company that in turn shows total disrespect for that same community is a waste of effort (now it may just be a matter of Google not delivering the client but providing the API ... but will the disrespect for Linux get worst or better in the future? Will there be cases where even the API will not be available and Linux will be totally left out of the loop?) ... if they have to spend effort anyway they might as well spend it building services for the Linux community and not covering the missing bases for Google.

Besides, it's already 80% 'done', mostly tested, backed up, and a couple of old spare laptops standing by in case of hardware failure ... all I am waiting for as I said is for owncloud to release their next version of the Android client ... after that if Google has still not delivered a Linux client (or at least given a clear time line on when one will be available) then Google has lost a data source, and gained a 'roll your own' evangelist.

P.S.

Thanks for the other information and I appreciate the effort of writing it .. but, let's be realistic here .. this is a sync client of which Google has already created 3 or 4, and being released to a community that is only 1 or 2 percent of the total community ... I don't think Google is of any legal or competitive risk by giving out more than a cryptic "we're working on it, be patient' response .... we're not asking for your secret sauce, just some actual real sign that Google still has a modicum of respect for the Linux community .. if Google can't be bothered doing that, then fine, just be a little bit 'courageous' and let the 1 or 2% know where we stand and we can move on from there.
 
Nicolas, any plans to livestream the event, we are based out of India and would love to attend over a hangout.
 
+Nicolas Garnier Why on earth didn't Google release Drive For Linux at the same time as the other clients? Seems so odd, and then be surprised that there is pushback?!
 
What I would like to know... we know what platforms GoogleDrive was released for and know what platforms Google had intended to release future support for at the release, but when the blowup happened with #DriveForLinux we get a small inkling of "it's coming" but as an unofficial nod in a pseudo-chatroom which most people would have not seen it if there hadn't been any sort of news coverage about it from third parties. Yet when you go to the welcome page still (to this day), there is not one change in the list of "coming soon support". Still no official mention of Linux at all.

So, my only request... update the page to state "Linux (Coming soon)" so we can at least get an official nod for #Linux .
 
+Stephen Allen I actually really don't know why. But I could only guess that it was left out by lack of human resources. Developers are a scarce resources at Google and each projects have to make decisions on what to work on as a priority to launch and this is often Metrics based... (Just guessing, I truly don't know).

+Kent Seaton Can you send me the link to the page? I can ask if it would be possible to update it.

+Soham Mondal Can you please check that parallel post: https://plus.google.com/u/1/105037104815911535953/posts/ZSm9gTe9YPd and contact +Mark Lunney about this? He is the GTUG lead that is hosting me for this talk.

+David Landry Basically my point was more to excuse Google on the short answer it gave and explain we are not used to communicating about unreleased features at all (so we might just not do it the best way when it happens :)). And about me bringing up the API, sorry about that, I did not mean to be offensive. I'm in Developer Relations and it's my job to push for the usage of the Google APIs to build an ecosystem. I was definitely not trying to mean that smaller communities should do all the work themselves.

Also guys, just to let you know probably 95% of the engineers at Google use a Linux workstation as their main dev machine so trust me we are all part of the community and we would really like to see this coming too :)
 
+Nicolas Garnier Thank you for looking into this: https://drive.google.com/start?continue=https://drive.google.com/%23#home Also, if they need alpha or beta testers... you know where to find me.

Side note: I know a few Googlers, and one of the top devs at the NYC office personally. I can easily vouch for the number of people there who use Google Linux derivatives. I almost became the proud owner of a coveted noogle beanie... but that's another story for another time.
 
+Nicolas Garnier Thanks for the update of what you know about the situation (but really, someone with authority should get off their butts and let Linux users know where we stand.)

I appreciate that Google developers are up to their chins in Linux, but in my experience it's not the platform that the developers use that sets the level of 'respect' shown to any particular platform, it's up to the direction given by management, and how well they enforce any policies that relate to that direction ... so in other words if 100% of the Google devs used Linux it would not matter one wit, as as long as the management sets direction away from Linux, the disrespect is still very real and felt.

I understand the situation as even though our company actually has an official policy to support and push Linux, we are in a situation were one internal productivity app (well, probably more than one) that doesn't fully support Linux has been officially deprecated and officially replaced with one that does fully support Linux .. but because of legacy issues (damn Windows) no one uses the new app --- so Linux users have to constantly push back at the powers that be to ask them to enforce the policies they put in place .... Google developers need to do the same thing.

So, I appreciate that you and thousands of Google developers may have all the respect in the world for Linux and the community, but it doesn't mean a thing unless 'Google the corporation' shows it as well.


P.S.
Sorry for hijacking the thread, but it's not often I see a Googler associated with Google Drive 'rear their heads' on G+ (maybe for good reason ;-)
 
If google didn't respect the Linux community, then why would we have Chrome and Chromium, which are the best browsers for Linux? 

With that said.. I can't wait for a google released Google Drive client for Linux. Is there an ETA or some time frame? 
 
+Kent Seaton Thanks I will forward!
+Stephen Allen Yay for this cool project (I knew this API thingy was going to be useful ^^)
+Ben Kevan As I explained above, unfortunately I can't communicate on any ETA about this!
 
+Ben Kevan Chrome was Windows only and a pretty mediocre browser until Google released it as open source Chromium, and it was the open source community that built most of the support needed for Linux and Mac, and at the same time adding back to the updates for Google to use with their Chrome broswer.

Linux and the OS community already had Firefox, and was well on the way to browser dominance ... that was given up to help Chrome ... which is not a bad thing, but certainly not anything like a one way act of charity from Google to Linux.

If anything Chrome is a reason that Google should show even more respect to Linux and the open source community, and not the other way around.
 
Google build Android on Linux...and made dollars on it...and then forgot Linux Client on the most important innovation GDRIVE ahahahahahahahah LOL or tears ??? I'm a linux user
 
The side worked until friday, and i Also send email and he answered me, but now the site doesn't work
Add a comment...