51–60 of 62 posts
It isn't clear to me what this is. Does anyone mind explaining?
It looks like a good source of information for developers working on products built on top of GitHub's API. (Like Gitpoints, http://gitpoints.com , in my case.)
This fell on deaf ears..
Earlier quoted context omitted.
Cynically I wonder if they are going to start making it more difficult to use the GitHub API if you aren't part of the program.
We currently have no plans to make it harder to use the API if you aren't part of the program. If you are a business that relies on our API, we want to have a better relationship with you because there is a good chance we share a customer base.
Earlier quoted context omitted.
Can you not be added to a team of the said organization ? Or is it that github is not allowing team members of organizations to participate ?
It looks that way, I'm on the owners team of a paid organisation and can't sign up.
> In order to register for the developer program, you must be on a paid plan.
It isn't clear to me what this is. Does anyone mind explaining?
It looks like a good source of information for developers working on products built on top of GitHub's API. (Like Gitpoints, http://gitpoints.com , in my case.)
I'd certainly be interested in knowing what the heck "select features" might be, and what exactly I can do with a development license for GH products... but it's really hard to see whats in it for me with such an uninformative marketing page. I'm not yet making money off of my github integration, so I can't justify jumping to a paid plan just to see what this is all about...
Hate to be picky, but shouldn't it be "kudos are all yours"? I like to think I write decent copy, and am genuinely curious. I'm assuming whoever wrote that actually thought about it, and can probably tell me why I'm wrong
From oxforddictionaries.com[1] Kudos comes from Greek and means ‘praise’. Despite appearances, it is not a plural form. [1] http://www.oxforddictionaries.com/definition/english/kudos
Earlier quoted context omitted.
We currently have no plans to make it harder to use the API if you aren't part of the program. If you are a business that relies on our API, we want to have a better relationship with you because there is a good chance we share a customer base.
I'm still not clear what a developer license to build and test against GHE is. "Take on the enterprise" links to a support form.
I'd certainly be interested in knowing what the heck "select features" might be, and what exactly I can do with a development license for GH products... but it's really hard to see whats in it for me with such an uninformative marketing page. I'm not yet making money off of my github integration, so I can't justify jumping to a paid plan just to see what this is all about...
My guess is that they're trying to build a showcase of all the interesting 'value-adds' around GitHub. They will then use that showcase as part of the sales-pitch for GitHub Enterprise (and allow a chosen few 'developers' to access their Enterprise customers - perhaps via an AppStore model).
This is pretty much how everybody does it when it comes to enterprise sales. Even massive companies like IBM have partners to fill in gaps in their product line. When it comes to enterprise sales, you don't go in with an minimum viable product, you go in with a Swiss army knife. There is a reason why Jira is the way that it is.
By making it easier for others to develop enterprise grade solutions that is tightly integrated with their own, they can say to potential customers "GitHub Enterprise doesn't do that but we work with a company that does". All it takes is one missing feature for a customer to say no, because they usually have the resources to build it in house. Or superglue together a solution that is ugly, but meets the needs of one or more individuals in the purchasing chain.