Assuming that we will continue to the pattern of posting each weekly dev agenda in the forum. Here is the agenda for next week and a forum topic where it can be discussed.
Weekly office hours
Bring your questions to our weekly virtual office hours, every Wednesday. Everyone is welcome.
Recent topics
Posted 1 week 1 day ago by (stpaultim) in How-To and Troubleshooting
Posted 1 week 3 days ago by (stpaultim) in Weekly Meetings
Posted 1 week 4 days ago by (NormPlum) in Other
Posted 1 week 4 days ago by (NumerousHats) in How-To and Troubleshooting
Posted 1 week 4 days ago by (gwolf) in Other
Recent comments
Tried and successfully applied DrAlbany's method with the form https://www.drupal.org/sandbox/grobot/2105379stickman hook. I also encountered the same situation. Thanks DrAlbany
Ubercart - Auto increment SKU
Since before migration you need to prepare the Drupal site - disabling and removing all modules, disabling themes, as part of the preparation you can clear the cache and logs, delete the search...
Trimming the size of my database for D2B_migrate not to error out (Request Entity Too Large / 504 Gateway Time-out)
QuickTabs is now available!!! But does not work as expected, already reported (https://github.com/backdrop-contrib/quicktabs/issues/14). Maybe an alternative solution using Views...
Quick Tabs (or method to simulate)
Great, I just accessed the report here: https://github.com/backdrop-contrib/quicktabs/issues/14 geometry dash
Quick Tabs (or method to simulate)
SKU = Stock Control Unit... meaning an easy way to identify stock... Depending on the type of stock item you have, would dictate the SKU. So, for example, in the IT industry,...
Comments
It seems I was too late adding my item to this week's agenda, so here it is for next week instead:
Item for discussion/feedback: Weekly dev meeting purpose/format
https://github.com/backdrop-ops/backdrop-community/issues/6
I'm suggesting another infrastructure topic. Not urgent - only if there's enough time.
There have been some experiments to switch from Zen.CI to Github actions, but the performance was just too bad.
An idea that came to my mind today: split into multiple jobs, so several runners run in parallel. As an example: 5 to 10 core modules per runner.
I'm not sure if this is feasible or if there's an upper limit by Github for running jobs at the same time (per project). But it seems worth a try.
Here's the related core issue (#4753).