Project Browser Initiative Sitebuilder Meeting for August 23, 2022 [#3329612]

Welcome to the weekly Project Browser Initiative - Site Builders Subcommittee meeting. This meeting:
➤ happens right here every Tuesday at 1pm PT | 4pm ET | 9:00pm UTC
➤ is chat only (no audio or video)
➤ happens in threads (please add threads to propose an additional discussion topic)
➤ will be exported as a transcript and posted to the agenda issue

1️⃣ Say hello when you join the meeting. If you are new to this meeting, let us know what your interest is and we will make sure to help you learn how you might want to become involved. Please add your drupal.org user name to your intro.

hestenet (he/him)	Tim from the DA swinging by briefly
fjgarlin	Fran here (fjgarlin), checking threads
Libbna	Hi Libbna from India.This issue is marked as postponed but Issue summary has been updated by the reporter .[#3303328]There is an issue related to position with copy button. Should I start working on this?
Libbna	@timplunkett (he/him)

2️⃣ What BoF topics would be helpful to have at DrupalCon Prague? Cleaning up categories, getting maintainers involved in cleaning up project data, redesign of the project pages? Other ideas?

chrisfromredfin	I would think that this would make the most sense looking at the d.o project page, and the PB project detail page... look at them as two things serving two different purposes, and see what kind of feedback we can gather on "everyone likes this" vs. "everyone wants this at their fingertips" vs "no one even looks at this"
chrisfromredfin	It would be cool to do a HotJar/heatmap of project pages............
chrisfromredfin	@drumm is that something in the realm of possibility or too tricky with privacy laws, etc?
drumm	I really disagree with the idea that Drupal.org project pages should be over-complicated and project browser should be dumbed down. They have the same audience and purpose.
drumm	Sure, there are some different secondary purposes - project browser likely won’t have as many people who might contribute back. The primary purpose, helping site builders evaluate projects is the same.
leslieg	It’s more about making the project pages more consistent in where folks can find things and maybe not showing everything in the project browser detail pages, but definitely having links back to drupal.org project pages.
chrisfromredfin	Yeah, and I think the idea of making them consistent in layout is helpful, for sure. I was just wondering if we could run HeatMaps or something to see what people use/don't use on the existing pages.
drumm	I would like to see some measurement, not sure if heat maps are the best, but maybe it’s the best can do. Would have to look at each individual project page with a heat map, right? How much traffic would be needed for each one to have decent data?
drumm	And a lot of evaluation is looking at things, not necessarily clicking on them.
chrisfromredfin	hmm yeah of course... like eye tracking is really what's needed...
drumm	There is probably some information architecture design to do, or continue doing. For example, regardless of how much people look at it, we’d still show security advisory policy coverage, since we know it’s a good project quality signal. The question is how prominently to show it and where it stacks up against everything else.
chrisfromredfin	Absolutely; I assume there's some "non-negotiables" in there
drumm	The Drupal.org pages are going to get a lot more simple when the “Issues for …” block is replaced with more-basic links to GitLab. And test results will inevitably be a basic pass/fail, if we can do that. So there’s going to be some convergence.

3️⃣ What topics should we concentrate on during Prague contributions? We will continue work on the Top 100 modules - short description, best 3 categories and logo design. What else would folks like to work on or think that others would be interested in working on? I’m thinking UX and site builder options right now, but add any you think would be good for the general Project Browser group as well (edited)

chrisfromredfin	I would love it if there were a really good flowchart for handling contributions at Prague. Like "oh, you're here and want to work on something? [code] [ui]" if ui, then you can just be like "here's your module; do the three things for the top 100 for that module" or something... might have to ask them about design skill or anything like that.
chrisfromredfin	but some way to just get through that top 100. it's a slog, but it's actually light work... and many hands make light work. we just need to get committed folks to power through
leslieg	Good idea - let me think about that. I usually just ask design minded folks to take the logo child tickets and others to take the short description and categories tickets. Rarely can 1 individual do all three for a module. They put in a comment to say they are working on the ticket as part of DrupalCon Prague so no one else also starts that ticket.
chrisfromredfin	But I think we could get some good energy if we had like a good kanban board going or something... "abbey y did this, now it needs review, jon q will review abbey's description" etc
chrisfromredfin	so we as leaders could be managing the flow and triaging and people could be making their contributions
leslieg	yes, definitely agree with that thinking
AmyJune (volkswagenchick)	I would love to see three tables in the mentor room. One set of folks reviwing logos, another description, and so on