Thanks, @ianwalter. We plan on having a public feedback repo soon - but in the meantime, if you want to submit ideas, please check out https://support.github.com/contact/feedback.
Thank you! We couldn't have said it better ourselves. Let us know if you have any other feedback on what we can provide you to plan better. And thanks for your use of GitHub!
Thanks for the feedback on this. We are rebuilding Explore and improving the feeds on it soon, and would love to chat with you if you’re interested. Drop me a line (shankuniyogi at github.com).
Hi all, this is Shanku Niyogi. I run the Product team at GitHub. I sincerely apologize for this post. We screwed up. This post was made in error, and we are retracting it. We are always looking to improve our programs for developers, and are working on improvements. But this is not the way to make changes. And it is NOT a goal to end our program. Sorry for the confusion.
Very relieved to hear this, thank you for clarifying. A lot of us would've been very disappointed to see this program go.
Speculating a bit, I am guessing it was something like this that happened?
1) You are planning to take down the GitHub Developer Program (not the regular API as many in this thread are mistakenly thinking, but just the part where you provide enterprise licenses to developers to test their integrations on GitHub Enterprise)
2) You are potentially bringing back a way for developers to get enterprise licenses in a better way in the future(?)
3) This post was written in anticipation of that inevitability, but poorly communicated the two key points above and perhaps was published early by accident
Otherwise if the program really isn't intended to go away at all, I would be surprised this post was written in the first place
Disappointed the link now 404s. You could have at least put up a placeholder page saying it's being rewritten. As it stands this only confuses your stance further.
I'm confused? What is just a GIF link? Are you saying the original link is just a GIF? I can't confirm that (Wayback Machine doesn't have it indexed) but that sounds unlikely from the tone of the comments.
Parent is suggesting to post a gif of Steve Ballmer of Microsoft screaming "Developers, developers, developers" because MS owns GitHub now, and that was a widely derided moment in Microsoft's history.
If possible, it might be helpful to share a little detail on how it happened. You can imagine that it did happens signals at the very least that someone with power/influence got this post out there in the first place.
They've agreed to deprecate the program but once the post was out and got terrible feedback, they realized that deprecating a developer program is not the best idea for something like GitHub, let alone announcing it as such. So instead of admitting they've made a mistake in deprecating the program, they're blaming the messenger and pretending it never happened. They went as far as getting the archive.org pages blacklisted/hidden apparently, which shows somewhat clearly the mindset involved.
That is a very reasonable ask. I'll be doing a post-mortem, and talking to all the individuals involved - and will do a followup post on it on the same blog. Please stay tuned. And, again, our sincere apologies.
As an FYI, I have heard from a moderator that enough flags will move a post back a couple hundred places so that it is effectively buried. So aside from upvoting this comment for visibility, flagging the submission may help to prevent further disinformation.
With the interactive CLI, we set out with a similar mission as other cloud CLIs - our first priority was helping users use the GCP CLIs including gcloud and gsutil. With our Interactive CLI, we’ve tried to build something that doesn’t just help new users discover what they can do, but also helps make more advanced users productive, for scenarios such as piping between commands, and shell redirection for read-edit-write workflows. The Interactive CLI provides a full shell environment, and isn’t restricted exclusively to the use of GCP tools.
Interactive CLIs like are a little different than a "cloud shell", which provides a fully cloud-hosted CLI environment. If you want a fully curated cloud-hosted option, check out https://cloud.google.com/shell/. Note that the Cloud Shell includes the Cloud SDK.
Hi all, the Google Cloud SDK team here. The Interactive CLI feature is currently in Alpha, but part of our overall Cloud SDK. The SDK is very much in GA, but we continue to look for your feedback on what we can do to make the SDK experience better and easier to use. If you’ve got feedback, we have a built-in mechanism in the SDK. Just enter ‘gcloud feedback’, and let us know.
Thanks, @ianwalter. We plan on having a public feedback repo soon - but in the meantime, if you want to submit ideas, please check out https://support.github.com/contact/feedback.