Posted on 05-24-2013
I'm increasingly finding a company's approach to using Github, a vital signal of the health of a company, their team, and the products and services they are delivering.
An example of this is with social data platform, DataSift's new open source area. DataSift has thrown up a Github page which re-enforces the company's commitment to consuming and producing open source software, as well as a list of important, Github driven signals:
- Latest Updates - The latest repository updates acorss all of DataSift's repositories
- API Client Libraries - Java, Python, Ruby, PHP and other client libraries for the DataSift API
- Public Github Repos - Other tools and utilities that are avaiable via DataSift Github repositories
- Job Vacancies - A listing of current job openings at DataSift
I think DataSift approach is a very meaningful demonstration in the potential of being "open". As a company, DataSift provides access to valuable social signals, that any company can access via their interface and API, allowing them to develop insight and intelligence. If you look closely at their approach to deploying their Github hosted, open source site, it provides four very critical signals. API client libraries, open source code projects, job openings and updates across the company's Github profile.
Think about it. The number of platforms supported for an API, the number of public open source code projects and the number and type of job postings for a company are pretty significant signals regarding the health of a company these days. These can be pretty difficult areas to fake, and in many cases will quickly show the activity, growth and stability of a company.
I like DataSift's approach to their Open Source area. It doesn't just provide code and tools for developers to be successful, it provides us a deeper look into how DataSift operates.
Of the 1,640 tech companies I monitor, 751 of them have Github accounts. I think many of these companies can learn a lot from DataSift's approach to open source and how you can put Github to use.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Where Do We Start With APIs At The University of Oklahoma?
- What I Would Look For When Hiring a Modern API Developer?
- The U.S. International Trade Commission Includes APIs In Latest Report
- Thank You @3Scale For Investing In The Community With @APIStrat
- Introducing API.Report, A Community API News Site
- Extract Knowledge From Audio And Video Using The Clarify API
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions