Grimoirecon North America
Using the context of OSCON next May in Austin, we will celebrate our GrimoireCon North America.
We want to take the advantage of having lot of our customers there to show them our newest updates for our metrics and dashboard, such as having Slack integration. We will show also use cases and practical workshops for developers, community managers, project managers and for anyone interested on monitoring open source!
Full agenda will be published during next days, but we can announce today that Ben Lloyd will join us as speaker.
His talk will show how he uses quantitative metrics generated with GrimoireLab to evaluate the strategic value of open source projects and their communities, and it will cover how Samsung is planning to use this information to inform its overall strategy. How effective are internal open source engineering teams at getting code upstream? Does the community incorporate new features and fix bugs and security flaws adequately to meet the needs of the company? What companies and organizations exert the most influence over the community? Is the overall health of the community adequate to meet the needs of the company? How diverse is the developer ecosystem and are there ideal candidates for hire? We’re seeking to answer these questions and more.!
Tickets are available now! Get your early bird before the 20th of April.
Perceval is the Grimoire Lab tool that gives the first step for allowing Grimoire to gather automatic and incremental data for almost any tool related with contributing to Open Source.
Grimoire Lab Architecture (draft). Some pieces still under heavy development
Perceval goes on the quest to retrieve and gather data from git, GitHub, Bugzilla, JIRA, Gerrit, mbox, pipermail, StackExchange, Discourse, etc. for producing valuable indices, with GrimoireELK.
New release: Perceval 0.7.0
The new release increase the brunch of sources supported, gaining accuracy for the tracking of the project.
New features and improvements:
- New set of backends added (some of them sponsored by our clients):
RateLimitError exception added for handling rate limit errors.
- Code was cleaned to follow most of the PEP8 style guidelines.
- retry calls on SSH commands were added to avoid temporal server errors
HTTP 404 errors are managed when user’s organizations are fetched
RateLimitError exception is used
- In Mediawiki backend, the log messages written when a revision is not found were set to ERROR when the real level should have been WARNING.
- The URL used to fetch jobs in Jenkins was not common to all servers.
- When UUIDs are generated with some input data, some errors may be raised due to problems encoding invalid characters on the input. To avoid these problems, a surrogate escape control error has been set when data is encoded to UTF8. (#123)
- Handle Meetup requests rate limit. (#126)
We want you to test Perceval and Grimoire following the under development tutorial. If you are a GitHub user you might try The Cauldron for free to analyze some GitHub organizations. And of course, feedback, issues and pull requests are always welcome!!!
We are so excited about starting the new year with our contribution and participation at FOSDEM 2017.
FOSDEM is the strongest reference event for developers and geeks to meet and know the hottest incoming tech topics since 17 years ago.
In 2000, Raphael Bauduin, a Linux fan from Belgium, decided to organize a small event for Open Source developers. He named it ‘Open Source Developers European Meeting’ (OSDEM). From the second edition OSDEM became FOSDEM and every year host more than 5000 developers and Open Source geeks.
FOSDEM is our natural environment. We have joined it in a lots of editions and we are very proud to come again this year as speakers. We are also going to set up a stand for chatting with all our friends with special gifts for our community.
These will be our contributions to FOSDEM 2017:
To celebrate 25 years of Linux kernel development, we at Bitergia have produced the Linux development history dashboard. This dashboard visualizes the current Linux git repository from two points of view: the history of all commits (changes to the source code) up to now, and the history of all lines in the current version. The dashboard visualizes the main parameters about the development (the who, when and what) are visualized, and allows for drilling down in the data, for example finding the specific commits that lead to a specific part of the code.
Do you want to learn about when the lines in the current kernel were authored? Who has participated in specific areas of the kernel? How many files have remain untouched for more than 10 years? Play with the dashboard and find your own interesting details!
The dashboard was produced using only free, open source software tools (among them, GrimoireLab, our tookit for software development analytics). If you want to learn more details, check the slides I intended to use for my presentation at LinuxCon, which unfortunately I couldn’t attend. Those provide some more insight about how it was produced, some examples about how it can be used, and some curiosities found by exploring it.
Inner Source (or Inner Sourcing) is a term coined by Tim O’Reilly in 2001 that referenced to the,
“use of open source techniques within the corporation”.
Although more that 25% of the deployee code in the most influential IT companies was Open Source in 2015, IT departments didn’t show much interest in collaboration or innovation process. (Gartner, 2015).
But recently there are so many mainstream IT firms that are allocating resources to Open Source contributions, not only for the benefits of the code, but the benefits of the methodology brought to the organization such as collaborations, innovation and quality control.
Inner Source takes the lessons learned from developing Open Source software and applies them to the processes that companies follow to develop software internally.
Innersourcing’s benefits for the company
One of the first tasks done by a developer during the day is to choose where to go and what to fix. Backlogs are quite useful for this purpose, either using Kanban and directly having a look at the open issues waiting lists project by project as in the case of GitHub, or using any other manual or automated method.
For this engineering focus we have started to produce some panels whose main purpose is to help developers to make decisions. As this is still in its first stages there is room for improvement, but this hopefully shows how powerful this could be. The displayed panel is part of the open analytics panel produced for the CoreOS community.
CoreOS Pull Requests / Issues Backlog panel
This panel aims at providing information at three main levels:
On Monday, June 20th, our colleague Jesús will be in Berlin for OPNFV Design Summit to present The Quantitative State of OPNFV.[Update]: slides available, Jun, 20th, 2016.
OPNFV is one of the open source projects hosted by Linux Foundation and we have been working for them for almost a year, deploying and maintaining a Metrics Grimoire based Bitergia Dashbobard and detailed quarterly reports. But, meanwhile, we have been developing the new GrimoireLab toolkit, so we have some new things to show in Berlin for our OPNFV friends…
OPNFV MetricsGrimoire and GrimoireLab based dashboards
We have built a GrimoireLab based dashboard for OPNFV, but with some extra goodies!