- Issue created by @hestenet
A point of clarification, is this about Drupal Core adding a DEI.md specifically? Or is it also about badging and a markdown file for each contrib project?
Personally, I think it's counterproductive to add badging and DEI.md to each contrib project, because it takes a portion of already scarce development time from contributors and maintainers from developing the "product" (software solution and its value to users) and puts it towards trying to create a markdown file and get a badge. That markdown file also wouldn't, in most cases, affect how the project itself is developed. For example, how would a diversity statement affect (positively or otherwise) the development of a project meant to create file entities, or delete nodes after a certain amount of time? They aren't related clearly, so it's hard to say.
I did some reading and scanning of the CHAOSS website, and the addition of DEI.md is compared to the CODE_OF_CONDUCT.md markdown file. A code of conduct makes some sense, as it guides how the development process goes in terms of communication and comments on issues. But it doesn't really apply as much to the code solution itself, the problem it aims to solve on behalf of users. I think a DEI.md is the same way. It doesn't apply as much to the writing of code for most contrib projects. So, I'm of the opinion that, for contributed projects at the very least, it could be detrimental to the quality of the code of contrib projects if writing the DEI.md would take priority over solving issues raised by users, contributing patches, or performing other triage or maintenance tasks.
Regarding Core itself, the Drupal Association already makes clear that it's committed to DEI. Core, like contrib, also has a limited amount of developer time and resources at its disposal. There is a tradeoff if adding this markdown file is made a priority, but still, if it's just Core, then that's quite different than trying to do it for all contrib.
Anyone else have thoughts on this? Personally, I think Drupal as a product, as well as the Drupal Community, would be better served if we focused on the product/code and the functionality, UX, UI, issue queue, etc. Something like Project Browser, or adding tests for issues, automatic updates, and more are all tangible improvements to the core product. To me, it seems like badging could become a distraction.
- 🇺🇸United States hestenet Portland, OR 🇺🇸
I think for the scope of Drupal it makes more sense for the DEI.md to be in core and to be understood to apply to all of the ecosystem under its governance.
I am not so much considered about prioritizing this against the innovation and other code projects, because we have talented folks in the community for whom this is a strength area, moreso than code.
The template can also be pretty light weight:
https://github.com/badging/badging/blob/main/Template.DEI.md?plain=1For the upcoming announcement:
https://gitlab.com/gitlab-com/marketing/developer-relations/open-source-... - 🇺🇸United States dww
Huge +100 to doing this. I agree that we should have it in the core repo (and possibly the infra repo that lives directly on gitlab.com, per @hestenet), and that it would "be understood to apply to all of the ecosystem under its governance".
Re: #2: I strongly disagree that this is a "distraction" from the "real work" of making Drupal "the product" better. It's essential for the health and well-being of the contributor community (developers or otherwise) that we think about the issues of diversity, equity and inclusion, and make our community more welcoming to underrepresented voices and perspectives. That will absolutely improve the quality of both Drupal "the product" and the community itself. The broader and more representative of the vast experiences around the world our contributors are, the better Drupal will become. (Re)committing ourselves to think about these issues, and to try to measure our progress with quantifiable metrics, is not a "distraction".