Project Browser Initiative Meeting for March 9, 2022 [#3269575]

Welcome to the Project Browser weekly meeting! If you're here, send a wave and let us know your d.o handle if different from your Slack handle.

cathwaldron	:wave:
AmyJune (volkswagenchick)	AmyJune (volkswagenchick) - mostly lurking to keep up for the Discover Drupal graduates.
shaal	:blob_wave: coming late

1️⃣ Update on spinning project browser issue.

chrisfromredfin	The way this was architected, it populated compatible modules into the database form a .fixture file on .install. After installing, whenever you would pull up the project browser main interface, it would then connect and try to download any changes that have happened since the fixture was updated. This led to long spinning times when initially loading the PB interface, especially as the fixture got more and more outdated.
chrisfromredfin	I have moved the logic of updating the local data from Drupal.org to a drush command. For development purposes, it is adequate for now to work from a mock Drupal API that could be a month old. If absolutely necessary you can run the Drush command to update locally. We still plan on updating the fixture monthly.
chrisfromredfin	Doing it this way significantly improves the usability of the demo and the testability of the prototype at the expense of up-to-the-minute project data.
chrisfromredfin	Work was in this issue, and on the currently 1.0.x branch. #3267658: Move update-since-fixture logic to a Drush command
leslieg	Thanks @chrisfromredfin for fixing this. Having the latest prototype up and running is very helpful to the Project Browser Site Builder subcommittee
chrisfromredfin	p.s. I also did update the fixture for March - #3267661: Update fixture: March 2022
chrisfromredfin	so the data as of today is still pretty current.
chrisfromredfin	yes @leslieg I saw more listening sessions come in, which is great.
AmyJune (volkswagenchick)	I session is done and 3 more are on the schedule..

2️⃣ I was finally able to review WIP from hooroomoo from the November sprint. While not complete, it was a HUGE step in the right direction for our UI, so I merged that: #3240318: Streamline "teaser" (card) view of projects

chrisfromredfin	If you spin up the demo now, you will notice a much simpler card view for these projects.
chrisfromredfin	I also filed a couple of child issues related to the UI that were discussed in the Fixed 'streamline' ticket, so we didn't lose that info.
chrisfromredfin	#3267685: Poor UI when > 3 categories for a module
chrisfromredfin	and
chrisfromredfin	#3267678: Use icon to assist with understanding of maintenance status
chrisfromredfin	for the latter, anyone with some graphic experience may be able to suggest something else?
chrisfromredfin	maybe @Nico Grienauer (he/him)??
fjgarlin	maybe it should follow the same icons that are used on d.org?for minimally maintained it’s a grey triangle.for actively maintained there is no icon.--edit: I’ll add that to the issue (edited)
chrisfromredfin	The one small difference being that we're representing several statuses with the one "shield+wrench" so I wouldn't want to co-opt one icon, unless there is iconography on d.o somewhere that is representative of the category as a whole? But still good thoughts - being consistent would be great.
fjgarlin	Current icons can be found here: https://git.drupalcode.org/project/drupalorg/-/tree/7.x-3.x/drupalorg/im...(I don’t think there is a grouping for the different maintenance statuses)And the logic for the icons is here: https://git.drupalcode.org/project/drupalorg/-/blob/7.x-3.x/drupalorg_pr...(no icon for actively maintained projects, then grey triangle or alert triangle for minimally maintained and no longer maintained)

3️⃣ I have been doing a TON of work on refactoring the backend code to abstract sources for Project Browser data to a plugin system, of which you can choose only one. This is very much WIP but I am making great strides. I have abstracted the Drupal.org Mock API into its own plugin implementation that ships as a sub-module of project browser. Eventually, the real drupal.org plugin will ship right inside the module, but can be overrideable/switchable to a separate backend. If anyone is interested in testing this or poking around, it's here https://git.drupalcode.org/project/project_browser/-/tree/plugins (branch called "plugins")

chrisfromredfin	My intention here was simply to have a cleanly-swappable system for people to work with. That is, while we can ship with the mock api as the default, it will help us to continue to work, WHILE people actually start developing the real one. Similarly, this lets someone provide their own endpoint which merges sources from their own custom repositories PLUS, ex.g. an approved list from Drupal.org, etc.
chrisfromredfin	My next two steps on this are to abstract the front-end API calls to the Drupal site into something more generic and less "Drupaly" (ex.g. a "categories" property instead of a "taxonomy_vocabulary_33" property.
chrisfromredfin	Similarly, then the next big step is to keep working with our Mock API module and refactoring it until it defines the API we actually want from Drupal.org. All of the "fixture" stuff has been moved into the "drupalorg_mockapi" submodule since the intention is that is a similarly temporary solution.
fjgarlin	this is a great step. some applications only allow for some modules to be added (ie: no alpha releases) and this means that if you don’t like the default offered by the module, you can always custom-build a curated set.
fjgarlin	@hestenet (he/him) - tagging you here as this update is probably the most relevant regarding d.o. No action from your side, just keeping you in the loop of things.

4️⃣ Final intentions for DrupalCon are mostly that I'll be spending the majority of the time representing project browser in the coder lounge, and @leslieg doing similar in the new-to-Drupal contribution lounge/room/whatever it's called. @leslieg I may be wrong on some of these things, please let me know what else. I know there's a BoF but am not sure of its timing or topic off the top of my head.

leslieg

Yes we will have contribution opportunities in both the General Contribution area and the Mentored Contribution area at DrupalCon. I am leading a BoF on the project details page. Since there won’t be an initiative keynote we plan to add another BoF for the Project Browser initiative, what is the PB initiative, where we are and where folks can get involved. Once we have dates/times for the BoFs we will share them with this group

5️⃣ One thing I'm not getting to as a result of working through this big refactor (see 3️⃣) is I still haven't replaced drupalci with GitLab CI. Looking for anyone who may be comfortable taking that on. @irinaz may have some info on how to do this. I honestly think there is an easy first step of grabbing a template from like DrupalSpoons or something and dropping that in. See last week's meeting for more info on that! Please and thank you anyone willing to drop some time in.

chrisfromredfin	Doh, I also realize that there's no issue for this. I will create one.
chrisfromredfin	Issue: #3268636: Convert to GitLab CI
irinaz	@chrisfromredfin, I can add template from drupalspoons to the project, just to see how GitlabCI will work with new code.

6 @leslieg and I came up with a good clean approach to addressing our top 100 modules and trying to clean up Drupal.org project data to the betterment of Project Browser. See yesterday's SBS meeting for an update on that, and more of what they're up to. I think they're about to make a big push and we should see lots of good activity on that front (esp with DrupalCon coming up)

7️⃣ I'm opening an issue to clean up the README and I'll tag it Novice maybe (@AmyJune (volkswagenchick)?

chrisfromredfin	#3268626: Update README
AmyJune (volkswagenchick)	Great!
AmyJune (volkswagenchick)	I think this will be a great issue for the students. Do you mind if I snag it?
chrisfromredfin	take it away please! :slightly_smiling_face: https://git.drupalcode.org/project/project_browser/-/blob/1.0.x/README.md
chrisfromredfin	I'll be happy to review it whenever they want. I think the 'issue fork' flow and using GitPod will make this super easy from a "nuts and bolts" perspective.
chrisfromredfin	But if you're doing patch flow, that's also fine.
AmyJune (volkswagenchick)	We are learning MRs… so we’ll see.But we may default to patching. Thanks
AmyJune (volkswagenchick)	It’s perfect timing for them as they learning MD last week and created issues and MRs.Thanks alot.
AmyJune (volkswagenchick)	@jjcs227 @Nadia Faucon @prodigyjoe @Devon Ek I mentioned this in the DD channel.