The heartbeat of open source projects can be heard with GitHub data

The heartbeat of open source projects can be heard with GitHub data

The heartbeat of open source projects can be heard with GitHub data

GitHub released charts last week that tell a story about the heartbeat of a few open source, giving insights into activity, productivity and collaboration of software development.

Why are these important? Enterprises increasingly define software development as a top priority to gain competitive advantage or defend against disruption. They often turn to open source software because it is fast and agile. Enterprise IT decision makers should understand GitHub because it is the backbone of most open source projects.

Open source lets enterprises collaborate with all the other interested outside developers to create software that exceeds their internal capabilities. But it also means much of the collaboration takes place outside of the enterprise. Unsafe and disturbing it’s not because of controls, transparency and analytics.

Salted throughout the GitHub website are analytics, and there is an application programming interface (API) that data-driven enterprises can use to create their own analytics to measure the progress and health of any public open source projects important to them. A dashboard displaying the project’s heartbeat could be built with the API.

Read Also:
To Foster Innovation, Connect Coworkers Who Share Aspirations

The majority of the project activity is commenting. It’s not too far removed from Facebook posts, except the comments are tersely written and often have code changes attached.

Think of GitHub as a crowdsourced public book editing system where an author submits a draft book to his or her editors and the public interested in the book. Editors and anyone interested can download a copy of the book. They can comment, rewrite or submit additional paragraphs pages and chapters. All of the changes can be sent back to the public book editing system or, using GitHub terminology, with a Pull Request.

A Pull Request means the proposed changes have been sent, the author and editors notified, but the changes have not been merged. The editors review all of the submitted changes, check them for proper spelling, grammar, and accuracy, and curate the best. The curated changes are merged with the original work into a final bestseller.

Read Also:
How Big Data and Internet of Things Builds Smart Cities

A translation of a recent event on one of the projects that GitHub reported about, Microsoft’s Roslyn project, is a useful introduction before turning to the data. GitHub usernames are used in this example.

This change to the project’s main body of code started last December when tmat suggesting a new feature in the Issues list. He might have written the software to implement the new feature to accompany his Issue—as GitHub contributors often do—but in this case, he didn’t.

After some clarifying revisions, user davkeen added tmat’s feature request to the priority backlog in February. Davkeen previously had been given the permissions by the project’s owner to accept issues into the backlog list.

 



Chief Analytics Officer Europe

25
Apr
2017
Chief Analytics Officer Europe

15% off with code 7WDCAO17

Read Also:
3 Ways to Use Data for More Successful Digital Ad Campaigns

Chief Analytics Officer Spring 2017

2
May
2017
Chief Analytics Officer Spring 2017

15% off with code MP15

Read Also:
Harnessing the power of the ‘Four Opens’
Read Also:
3 Ways to Use Data for More Successful Digital Ad Campaigns

Big Data and Analytics for Healthcare Philadelphia

17
May
2017
Big Data and Analytics for Healthcare Philadelphia

$200 off with code DATA200

Read Also:
Google's Deepmind Is Going Public for Researchers

SMX London

23
May
2017
SMX London

10% off with code 7WDATASMX

Read Also:
The New IT: Driving Business Innovation With Tech

Data Science Congress 2017

5
Jun
2017
Data Science Congress 2017

20% off with code 7wdata_DSC2017

Read Also:
Seeking Privacy in a City of Sensors

Leave a Reply

Your email address will not be published. Required fields are marked *