<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div dir="auto">
<div dir="auto">Hello Ildiko, Matt, Ray, Georg and the chaoss gang!</div>
<div dir="auto"><br>
</div>
<div dir="auto">I just realized that your goodbye messages werent answered in 2019. Of course, it has been a pleasure for me also to meet and collaborate with you. I often think about you all!</div>
<div dir="auto"><br>
</div>
<div dir="auto">I truly hope that you and your lovedones are doing well in those strange days or should I say months...</div>
<div dir="auto"><br>
</div>
<div dir="auto">All the very best,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Josianne Marsan </div>
<div dir="auto"><br>
</div>
<div id="x_composer_signature" dir="auto">
<div dir="auto" style="font-size:85%; color:#575757">Envoyé depuis mon téléphone intelligent Samsung Galaxy.</div>
</div>
<div dir="auto"><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>-------- Message d'origine --------</div>
<div>De : Ildiko Vancsa <ildiko@openstack.org> </div>
<div>Date : 19-08-31 15 h 01 (GMT-05:00) </div>
<div>À : Josianne Marsan <Josianne.Marsan@sio.ulaval.ca> </div>
<div>Cc : CHAOSS Members <chaoss-members@lists.linuxfoundation.org> </div>
<div>Objet : Re: [Chaoss-Board] CHAOSS Board Meeting Minutes Draft </div>
<div><br>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi Josianne,<br>
<br>
It was great working with you on the CHAOSS board, I also really enjoyed our interview and chat at the Open Source Summit in Prague not long after the project started.<br>
<br>
I wish you all the best with your new challenges!<br>
<br>
Best Regards,<br>
Ildikó<br>
<br>
<br>
> On 2019. Aug 26., at 8:58, Georg Link <linkgeorg@gmail.com> wrote:<br>
> <br>
> Josianne,<br>
> <br>
> Thank you for your service.<br>
> Good luck with your new endeavors!<br>
> <br>
> Best,<br>
> Georg<br>
> <br>
> On Sun, Aug 25, 2019, 20:18 Raymond Paik via Chaoss-members <chaoss-members@lists.linuxfoundation.org> wrote:<br>
> Josianne, <br>
> <br>
> Thanks from me as well. Too bad we didn't have a chance to meet in person over the past years.<br>
> <br>
> Best of luck!<br>
> <br>
> Ray<br>
> <br>
> On Sun, Aug 25, 2019 at 11:35 AM Matt Germonprez <germonprez@gmail.com> wrote:<br>
> Hi Josianne, <br>
> <br>
> Thanks for the note and good luck with your new endeavors. We certainly appreciate your time and effort over the years :)<br>
> <br>
> Matt<br>
> <br>
> <br>
> On Sun, Aug 25, 2019 at 10:21 AM Josianne Marsan <Josianne.Marsan@sio.ulaval.ca> wrote:<br>
> Hi Matt and CHAOSS board member,<br>
> <br>
> <br>
> <br>
> I hope you are all going well.<br>
> <br>
> <br>
> <br>
> Since I don’t see it mention in the minutes, I guess the message I had written in my answer to the meeting invitation has not make it to Kate. Here it is:<br>
> <br>
> <br>
> <br>
> “I think I saw a point in the meeting agenda about board membership. If you discuss who wants to stay and who prefers to leave, could you inform the others that I will have to resign, for two reasons. First, I have created a new research center on IT & Business
last May and I am running it since, currently recruiting students and collaborators. Second, I have decided last month to run to become the new vice-dean of research at FSA ULaval next year. A colleague in the Marketing department is running to become the
next dean and he has asked me to join his team. I am excited, but also stressed by the learning curve ahead. Therefore, I will have even less time for external service such as being on boards. Thus, I prefer to leave my place to someone who will have more
time to put on the CHAOSS board. My colleagues from SECOHealth are cced in case they are interested in the position.”<br>
> <br>
> <br>
> <br>
> I wish you all success and happiness in your lives and projects.<br>
> <br>
> <br>
> <br>
> See you soon again!<br>
> <br>
> <br>
> <br>
> Josianne Marsan<br>
> <br>
> <br>
> <br>
> Josianne Marsan, Ph.D.<br>
> <br>
> ________________________<br>
> josianne.marsan@sio.ulaval.ca<br>
> Full Professor<br>
> <br>
> Department of Management Information Systems <br>
> Faculty of Business Administration <br>
> Université Laval<br>
> CANADA<br>
> <br>
> <br>
> <br>
> De : chaoss-members-bounces@lists.linuxfoundation.org <chaoss-members-bounces@lists.linuxfoundation.org> De la part de Matt Germonprez<br>
> Envoyé : 25 août 2019 09:06<br>
> À : chaoss-members <chaoss-members@lists.linuxfoundation.org><br>
> Objet : [Chaoss-Board] CHAOSS Board Meeting Minutes Draft<br>
> <br>
> <br>
> <br>
> Hi everyone,<br>
> <br>
> The board meeting minutes from last week's OSSNA meeting are available below and via this link:<br>
> <br>
> <a href="https://docs.google.com/document/d/1dhYjE0e7tHdNJXYAHPuQK-7kpxxmpPswx962iYrWhg4/edit?ts=5d5d5d47">
https://docs.google.com/document/d/1dhYjE0e7tHdNJXYAHPuQK-7kpxxmpPswx962iYrWhg4/edit?ts=5d5d5d47</a><br>
> <br>
> I will be sending these minutes to the CHAOSS mailing list on September 6th, 2019. If you have changes you would like to make to the minutes, please email me changes or track your changes in the provided link.
<br>
> <br>
> Of particular note:<br>
> - Email Matt with CHAOSS Board co-chair nominations by August 31st.<br>
> - Email Matt with CHAOSS Board new member nominations by August 31st.<br>
> <br>
> Thanks to everyone who took notes during the meeting :)<br>
> <br>
> Regards,<br>
> Matt<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> CHAOSS Governing Board meeting <br>
> August 21, 2019<br>
> <br>
> <br>
> Attendees: <br>
> Present in room: Brian Proffitt, Dawn Foster, Jose Manrique Lopez de la Fuente (ex officio), Georg Link, Sean Goggins, Matt Germonprez, Kate Stewart, Jesus Gonzalez-Barahona, Ray Paik<br>
> Present on Zoom: Ben Lloyd Pearson, Andrea Gallo, Don Marti, Ildiko Vancsa, Daniel German<br>
> Absent: Wayne Beaton, Josianne Marsan<br>
> <br>
> <br>
> CHAOSS Budget<br>
> · Spent $s for stickers, poker chips, and CHAOSScon so far<br>
> · Matt is working to move funds from GSoC into Community Bridge<br>
> · Deprioritize travel assistance for now<br>
> · Meetup/events: <br>
> o Rather than GraceHopper better option may be SCALE & FOSDEM<br>
> o Have booths at SCALE and FOSDEM in 2020. <br>
> · Mentorship: Explore funding an intern via Outreachy<br>
> o AI Matt: Explore participation in Outreachy<br>
> · Issue bounties/consulting/workshop<br>
> o Can we do consulting engagements and not jeopardize out non-profit status? There is a precedent with Fossology training.
<br>
> Board Membership<br>
> · Annual review of Board Membership<br>
> · Board size: 7(min)-15(max), currently at 15<br>
> · Jesus GB will step down from board<br>
> · If you miss 3 consecutive board meetings, Matt will do an outreach and check on things
<br>
> · There was a discussion on the need to formalize co-chair roles<br>
> o Discussion on removing representation from Software & Metrics committees for co-chairs.
<br>
> § AI Kate: start a Google Doc for charter updates<br>
> o Maybe do staggered elections with two year terms for Co-chairs for continuity<br>
> § Motion to nominate Matt for another 1 year term: <br>
> · VOTE: approved unanimously<br>
> § Another nomination for a 2 year-term. Email Matt with nominations by August 31st. Ray will run a Condorcet vote for the Co-chair election.
<br>
> · Nominees so far<br>
> o Sean<br>
> o Georg<br>
> o Dawn <br>
> § Also open for suggestion for a new board member by August 31st<br>
> <br>
> <br>
> Thanks to community members for the first CHAOSS release. Next release will be around the CHAOSScon-Europe in 2020.
<br>
> <br>
> <br>
> Software updates (summary also available in the slide deck) <br>
> <br>
> <br>
> Augur Update: <br>
> Augur is an increasingly robust, systematically designed data collection, analytical and notification system for making sense of the health and sustainability of open source software project health and sustainability. We maintain our identity as a prototyping
system, and expect the innovations we have developed in the past year will inspire other projects, and are proud of the organizations, open source program offices, and open source community managers we have helped through our work. Remy DeCausemaker from Twitter
is a tireless, friendly source of inspiration and constructive critique that influenced our choice to evaluate and reconstruct the hear of Augur this year. Our Google summer of code students Parth and Bingwen worked hard with our core Augur team of Gabe Heim,
Carter Landis, Derek Howard, and Jonah Zukowsky through the summer to make our new vision for Augur real. New team members, Elita Nelson, Carolyn Periciniaro, Paul Orton and Sean's computer science undergraduate students are a part of Augur's growing core
contributors. Proof, in a sense, that we are learning how to onboard new contributors more effectively.<br>
> <br>
> Augur Accomplishments, 2018-2019: <br>
> <br>
> 1. Working with CHAOSS's stakeholder community we designed and implemented a comprehensive, unified data model that brings together insights from Brian Warner's Facade Project, Libraries.io, GHTorrent, DOSoCs (now "chaoss/augur-sbom"), Brian Proffit's,
Dawn Foster's and GrimoireLab's insights about individual identity and organizational affiliation complexity. A single data model that stores system-specific software engineering synonyms for "commit", "issue", "pull request", and other constructs.<br>
> 2. The unified data model accelerates analysis of open source ecosystems, and projects that are managed in heterogeneous .git infrastructure.<br>
> 3. To collect data, Augur now relies on a federated broker-worker system. Six workers are presently deployed and operating against over 15,000 repositories for a diverse group of open source stakeholders. Each worker continuously collects data, and sends
it to the broker, who stores the data. A Housekeeper makes sure every worker keeps doing their job.<br>
> 4. A new design of our API endpoints follows a common :repo_id/name and :repo_group(project)_id/name standard that eases the implementation of customized, organization specific distribution of Augur data.<br>
> 5. Augur's front end is completely redesigned and rewritten using Typescript instead of Javascript, which is lowering our change and maintenance costs.<br>
> 6. The number of Augur deployments continues to grow, and our newcomer experience is significantly improved since March, 2019.<br>
> 7. Our collaborations with the Grace Hopper Conference, including an Augur workshop, is helping to push these advances forward.<br>
> 8. We now use machine learning and statistical algorithms to identify events buried in the 60+ metrics endpoints our restful API now supports.<br>
> 9. The resulting insights are provided via push notifications in Slack, email and other messenger clients.<br>
> 10. Augur's front end and back end are now independently deployable, meaning that new users can use Augur only for API's it uses to feed their own systems, or begin to work with our front end.<br>
> <br>
> Augur Goals, 2019-2020: <br>
> <br>
> 1. Integration of HyperLedger/Indy for federated, secure single sign on.<br>
> 2. Continued advances in the deployment of our machine learning anomaly detection, and push notification system.<br>
> 3. Creating CHAOSS metrics from the 24 Augur endpoints that are not currently defined as CHAOSS metrics.<br>
> 4. Implementation of our value workers based on the COCOMO model of software engineering labor and cost estimation<br>
> 5. Implementation of test coverage metrics from the Risk working group.<br>
> 6. Providing technical infrastructure to enable diversity and inclusion working group process aims to be supported in context with Augur's whole system.<br>
> 7. Incorporating important content directing Augur users to resources for risk management, value assessment, diversity and inclusion awareness and organizational and individual developer information.<br>
> 8. A user configurable mechanism for deriving user directed "dashboard indicators" of comparative health within their ecosystem.<br>
> <br>
> GrimoireLab Update:<br>
> <br>
> The development around Grimoirelab never stops, it spans from maintenance tasks which aim at improving the quality of the platform, to new development lines that are setting the basis for brand-new features.
<br>
> Since March 2019, under the umbrella of maintenance tasks it is worth mentioning the support for GDPR compliance (a topic that is becoming more and more important) and Mozilla Lead Data initiative, plus some enhancements on the data retrieval (Perceval) and
enrichment (ELK).<br>
> Perceval is now able to use multiple tokens to fetch GitHub data, supports OAuth tokens for GitLab and Meetup backends, and collects statistics (e.g., number of forks and watchers) for GitHub repositories.
<br>
> On the other hand, the enriched data produced by ELK includes information about:
<br>
> (i) patchsets, approvals and comments for Gerrit reviews, <br>
> (ii) creator, assignee and reporter for Jira issues. <br>
> In terms of upcoming features, new development lines have been created to <br>
> (i) allow managing identities using GraphQL (SortingHat), <br>
> (ii) provide an administrative interface for GrimoireLab (Raistlin), <br>
> (iii) simplify the management of dashboards (Archimedes)<br>
> (iv) simplify the way of storing the data retrieved by Perceval (Citadel).<br>
> Together with this effort, a special attention is being given to documentation (a restyling of the tutorial is ongoing) and the way of deploying the platform.<br>
> And last, but not least, we have started to develop a new version of Cauldron, a PoC of GrimoireLab served as SaaS, to include latest updates of GrimoireLab and playing with potential new technologies to be integrated in Bitergia products. You can check it
online in <a href="https://alpha.cauldron.io">https://alpha.cauldron.io</a><br>
> Cregit Update:<br>
> <br>
> · Journal paper available at <a href="https://github.com/dmgerman/papers">
https://github.com/dmgerman/papers</a> <br>
> · New interfaces for displaying hierarchical information has been deployed on
<a href="https://cregit.linuxsources.org/">https://cregit.linuxsources.org/</a><br>
> · Work ongoing for tracing provenance of code between repositories. <br>
> · Extending work on linking the email threads to code, and doing sentiment mining of the data focused on the linux kernel.
<br>
> <br>
> <br>
> <br>
> Google Summer of Code Update:<br>
> <br>
> <br>
> · Most successful year. All four students made significant contributions to the project.<br>
> · Encourage everyone to check out blog posts from interns<br>
> · Discussion on creating a page on CHAOSS website to recognize interns<br>
> <br>
> <br>
> D&I metrics<br>
> · Talk to foundations including the LF (Angela for events), ASF, etc. <br>
> <br>
> <br>
> Advisory group to review CHAOSS release artifacts ~twice a year<br>
> <br>
> --<br>
> <br>
> Mutual of Omaha Professor<br>
> <br>
> Information Systems <br>
> <br>
> College of Information Science & Technology <br>
> <br>
> University of Nebraska Omaha<br>
> <br>
> he / him / his<br>
> <br>
> <a href="https://goo.gl/E87KdK">https://goo.gl/E87KdK</a><br>
> <br>
> <br>
> <br>
> <br>
> <br>
> -- <br>
> Mutual of Omaha Professor<br>
> Information Systems <br>
> College of Information Science & Technology <br>
> University of Nebraska Omaha<br>
> he / him / his<br>
> <a href="https://goo.gl/E87KdK">https://goo.gl/E87KdK</a><br>
> <br>
> _______________________________________________<br>
> Chaoss-members mailing list<br>
> Chaoss-members@lists.linuxfoundation.org<br>
> <a href="https://lists.linuxfoundation.org/mailman/listinfo/chaoss-members">https://lists.linuxfoundation.org/mailman/listinfo/chaoss-members</a><br>
> _______________________________________________<br>
> Chaoss-members mailing list<br>
> Chaoss-members@lists.linuxfoundation.org<br>
> <a href="https://lists.linuxfoundation.org/mailman/listinfo/chaoss-members">https://lists.linuxfoundation.org/mailman/listinfo/chaoss-members</a><br>
> _______________________________________________<br>
> Chaoss-members mailing list<br>
> Chaoss-members@lists.linuxfoundation.org<br>
> <a href="https://lists.linuxfoundation.org/mailman/listinfo/chaoss-members">https://lists.linuxfoundation.org/mailman/listinfo/chaoss-members</a><br>
<br>
</div>
</span></font>
</body>
</html>