KaajalAminSharma
commented
2 months ago Hi Paula,
Apologies, I did not realized you can subscribe to notifications on issues - perhaps we can bring this up on the next SIG in case others are not aware to ensure the group see the messages.
I do agree we need to strive for a way of better engagement. Rimma and the panelists of the Bias in AI talk at OSFF yesterday did a call out for new members to join the DEI SIG so hopefully we get some new members and ideas in the group.
Unfortunately I won't be able to attend the next 2 DEI SIG calls but happy to connect offline with anyone else who is interested in how best to proceed.
Kaajal
I'm currently serving as co-chair of the FINOS DEI SIG. Based on my participation and review of the SIG GitHub project since March 2024, I wanted to suggest a modification to the SIG to better align and integrate DEI activities throughout FINOS.
Currently, the monthly DEI SIG calls have low attendance, and the GitHub project board has low engagement. Not running the DEI SIG using the standard FINOS GitHub template risks losing sight of required regulatory notices if we grow engagement, but for various reasons the SIG has not fully adopted GitHub for raising ideas, prioritizing activities, assigning ownership, and discussing progress on monthly calls.
Lack of engagement in the DEI SIG GitHub project leaves the SIG without structure or ability for participants to contribute asynchronously to tasks in GitHub. Given these challenges, we can move in a different direction and still drive engagement and positive outcomes.
Reviewing the DEI SIG Project board in GitHub, the majority of the tasks are related to marketing (including activities such as a DEI microsite #48 - this item does not have an owner) and events. There is one project related task (establishing DEI.md files in projects, #60 - this item has an owner), and an item around establishing DEI metrics and best practices (#33 and #44 - these items do not have owners).
The activities on the DEI SIG project board could be re-assigned to Marketing, Ambassadors, Projects, and the TOC, where there could be more engagement and direct ownership. Keeping these tasks in a siloed DEI SIG risks having the work of diversity fall to those in underrepresented groups; spreading them throughout the related groups in FINOS is a step towards embedding DEI in all aspects of FINOS and making DEI part of everyone's remit. The current co-chairs and participants could engage in regular discussions with Marketing, Ambassadors, TOC, and FINOS projects to champion specific activities.
Like all open source efforts I hope this generates great discussion and ideas for alternatives that improve the engagement and participant experience for the DEI SIG.