CHAOSS Weekly Newsletter

By May 28, 2019August 28th, 2019No Comments

 Weekly Newsletter


CHAOSS is participating in the 2019 Grace Hopper Open Source Day ( Sean and Carter from the Augur team will lead a session on October 3, 2019. This is a great opportunity for CHAOSS to be involved in this fantastic event!

The next CHAOSScon will be on August 20, co-located with the Open Source Summit North America in San Diego, CA. The CHAOSScon Call for Proposals is open. Submit your talk proposals now!

Thanks to everyone who is helping to coordinate this event, it certainly couldn’t be done without you. We look forward to seeing everyone there.


Over the next few weeks, the working groups are advancing metrics for the first CHAOSS release ahead of OSSNA. Of interest, the D&I working group is going to be doing a metrics hack-a-thon on June 3 and June 10 (9:30am US Central) to make their push for a candidate release by mid-June. If you want to follow along, check out the tracking spreadsheet here:

Don’t forget → look at the file to help with framing the requirements for metrics release at: 


CHAOSScon CFP closes:

May 31, 2019



August 20, 2019


Evolution WG Meeting:

May 29, 2019

9:30am US Central

Common WG Meeting:

May 30, 2019

10:00am US Central

Value WG Meeting:

May 31, 2019

11:00am US Central

D&I WG Meeting:

June 3, 2019

9:30am US Central

Risk WG Meeting:

June 3, 2019

1:00pm US Central

CHAOSS Community Call:

June 4, 2019

11:00am US Central

All meetings at: 







Working Groups

Common Metrics WG

Diversity & Inclusion WG

Evolution WG

Risk WG

Value WG


With respect to Augur, they launched a version using its new `Broker Architecture` for data collection. Augur’s new broker architecture includes a new database schema that models the entirety of the open-source ecosystem in a platform-agnostic way. Augur will continue to support existing `GHTorrent` API endpoints and user interfaces for backward compatibility.  

The Augur team created 3 workers in the new architecture last week. One of these workers retrieves and stores badge information from the Linux Foundation’s Badging API endpoint. The other worker is for the GitHub api, and when given a github url, it can retrieve and store information about contributors and issues.  The data stored for issues, issue comments and contributors is noted in the new Augur schema: 

The third worker created is the Facade worker. Here, they substantially refactored Brian Warner’s facade into component parts responsible for discrete tasks (8 components, in total). The Facade worker also now puts data into the Augur schema. The refactored and updated version of Facade was tested against a set of 100 open source repositories and produces identical analysis in our “worker” version and the original version. Next up will be our release of a “TimeStamped” commit version of Facade.

Finally, they created a new broker and housekeeper components last week. The broker is now able to receive tasks and manage workers’ queues, and is able to hand out tasks to suitable workers. The housekeeper is now able to routinely give the broker a task that is intended to be handed out to workers on a repeated schedule, and it is able to have multiple synchronous schedules.

With respect to Grimoire Lab, Perceval had three bugs for Slack, GitHub, and GitLab fixed. The first bug was due to some Slack messages having timestamps with more than 6 decimals. The second bug was affecting the list of reviewers returned for GitHub enterprise instances and it was fixed by an external contribution. The last bug was from a recent change within the GitLab API, which for efficiency reasons doesn't include the attribute `last` in the pagination responses for endpoints (e.g., for issues and merge requests) with more than 10,000 results.

A bug in ELK was also fixed which caused identities not to refresh in the Gerrit enricher and improved the Jira and GitLab enrichers. The former is now able to store in the same index data coming from more than one Jira server, while the latter includes milestone start and due dates.

Finally, Sigils had updated panels such as the overview, the ones for GitHub and Jira to use the field `grimoire_creation_date` as datetime field. Also, the GitLab index pattern to handle the new information about milestones was also updated.


CHAOSS Community Minutes/Agenda:

Common Minutes/Agenda:

D&I Minutes/Agenda/Repository:

Evolution Minutes/Agenda:

Risk Minutes/Agenda:

Value Minutes/Agenda: 

CHAOSS on YouTube:

CHAOSS on the Web: 

CHAOSS on GitHub: 

CHAOSS on Community Bridge: