When I talk to people who tried to install GrimoireLab, I get one consistent answer. It is difficult and our GrimoireLab tutorial is too complicated. I believe this status quo is hurting the adoption of GrimoireLab software and CHAOSS metrics. This blog post is about how to make it easier for anyone to start using GrimoireLab.
Now that CHAOSS Metrics Version 1 has been released, tracking how those metrics are being used in tooling and community programs is a next step. All the work that has been done by Working Groups and Software Teams has been amazing. We’ve come a long way in the last year and we are now in a great position to consider how our work can and is making an impact. Forward!
Attending CHAOSScon? Consider participating in the day’s activities by giving a lightning talk. We’re going to have 30 minutes dedicated to lightning talks. Each talk is 5 minutes in length, just letting people know what you or your organization is up to with respect to open source community health.
Regarding GrimoireLab, Over the last week, the most activity in GrimoireLab was related to improve KingArthur, the retrieval data scheduler. Version 0.1.16 of this component was released which includes several features: user-defined queues to run tasks, tasks lifetimes, custom event handlers and a better REST API to get information about tasks and jobs. Among other activity in GrimoireLab, some critical bugs were fixed, especially the ones related to GitLab merge request retrieval [perceval/#53] and Jira analysis [grimoire-elk/#656].
The candidate metric comment period is coming to an end very soon. Thanks for the discussion and comments. The latest push of work has been on standardizing (or at least creating consistency) in the candidate metric headings. May not sound terribly exciting but it’s good work.
We are excited to announce the two keynotes for CHAOSScon NA in August.
Head of Open Source Strategy
Amazon Web Services
More information, including titles and the full schedule will follow very shortly.
Regarding Augur, there were many small bugs that were run into while running the GitHub worker and encountering rare cases. The Augur team updated the worker to handle all these cases that they ran into and the worker is nearly running perfectly smooth. They have changed the way they create GitHub API requests to include user authorization. Other changes were GitHub made to the worker in order to query issues of all states (open and closed), and of all the pages available (by default, the GitHub API only returns the first page of issues).