Meeting minutes 2023-01-18
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3334932. -->
Reported by: [jurgenhaas](https://www.drupal.org/user/168924)
>>>
<h2>0️⃣ Who is here today? Comment in the thread below to introduce yourself! We’ll keep the meeting open for 24 hours to allow for all time zones.</h2>
<table>
<tr>
<td>jurgenhaas</td>
<td>Jürgen here from LakeDrops</td>
</tr>
<tr>
<td>Daniel Speicher</td>
<td>Daniel from LakeDrops</td>
</tr>
<tr>
<td>boromino</td>
<td>Richard</td>
</tr>
<tr>
<td>rkoller</td>
<td>:wave:</td>
</tr>
</table>
<h2>1️⃣ Do you have any topics to propose for the meeting today? Post in this thread and we’ll open threads for them as appropriate. Or you can post them directly in the channel with the next number as an icon. That topic will then turn into a thread for the comments.</h2>
<table>
</table>
<h2>2️⃣ Global Contribution Weekend is next week Saturday and Sunday - what can we do to get people helping us with ECA and BPMN.io?</h2>
<table>
<tr>
<td>rkoller</td>
<td>it would be great to pick up on the work about the micro copy issue in a small group. i think it would be beneficial being able to discuss the copy instead of working in the zoho sheet.</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>Sounds great. Would you be around for "hosting" the activity around this topic?</td>
</tr>
<tr>
<td>rkoller</td>
<td>i won’t be in berlin in person. but i can join remotely</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>Oh yeah, I forgot to mention that. I won't be there either. Remote should be sufficient, I guess.</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>Another topic I'd like to focus on for that event is to push on the ECA Guide.</td>
</tr>
<tr>
<td>rkoller</td>
<td>shouldn’t make any difference if in person or remote i agree. but it would real beneficial to have some discussions about the micro copy. and documentation in general like the eca guide is related. good point. i guess a lot of clarification and questions are still necessary. what certain functionality actually does and if it is named and described correctly, concisely and in particular clearly.</td>
</tr>
<tr>
<td>rkoller</td>
<td>and i will go through all the strings in all eca related modules and trying to update zoho spreadsheet the next days so the spreadsheet is up to date for the contrib weekend</td>
</tr>
</table>
<h2>3️⃣ Status Version 1.2 roadmap <a href="https://www.drupal.org/project/issues/search/eca?status%5B%5D=1&status%5B%5D=13&status%5B%5D=8&version%5B%5D=all_1.2.*">https://www.drupal.org/project/issues/search/eca?status%5B%5D=1&status%5B%5D=13&status%5B%5D=8&version%5B%5D=all_1.2.*</a></h2>
<table>
<tr>
<td>Daniel Speicher</td>
<td>There are issues tagged with 1.2, which I think needs work or review. I like to help here.</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>This is great !!! For the tour related issues you may coordinate with @rkoller and the documentation issues are already underway, I guess?</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>I for myself are planning to start implementation on some of the smaller issues as well as on the debugging improvements the next few days. So that will then benefit from rests and reviews too.</td>
</tr>
<tr>
<td>boromino</td>
<td>I will also start to work on some issues this week.</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>Amazing :thankful:</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>@boromino just pick the issues you feel most comfortable with and probably assign them to yourselves so that we can avoid double work on the same one</td>
</tr>
</table>
<h2>4️⃣ Accessibility</h2>
<table>
<tr>
<td>rkoller</td>
<td>a brief summary. I’ve skimmed through the different bpmn/camunda issue queues over the holidays. I’ve registered a free account at camunda (probably the only and easiest way to see the current state of bpmn/camunda and how all their component work together - easier to report than refer to drupal and eca). I’ve then compared its state against the current state of eca/bpmn in drupal and the list of a11y issue i’ve found before and chopped things that still apply into a first batch of issues (there are definitely more) and started to create dedicated issues in the bpmn queues as well as in the eca and or bpmn queues. (edited)</td>
</tr>
<tr>
<td>rkoller</td>
<td>Core (applies to ECA as well)<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/3310147" title="Status: Active">#3310147: Improve the visually-hidden label for drop buttons</a></span> i’ve already reported a general issue against core a few months ago and discussed it at the monthly a11y office hour. it is about that the visual hidden labels for drop buttons options on list pages are redundant without context</td>
</tr>
<tr>
<td>rkoller</td>
<td>ECA[#3330804] Create tours for the tour module in Core to provide a high level overview.</td>
</tr>
<tr>
<td>rkoller</td>
<td>BPMN[#3334533] add a handle to the properties panel and make it fixed width plus extend the canvas</td>
</tr>
<tr>
<td>rkoller</td>
<td>BPMN (upstream)<a href="https://github.com/bpmn-io/bpmn-js/issues/1804">https://github.com/bpmn-io/bpmn-js/issues/1804</a> landmarks and headings. (already existing and referenced issue for adding shortcuts <a href="https://github.com/bpmn-io/bpmn-js/issues/768">https://github.com/bpmn-io/bpmn-js/issues/768</a>)<a href="https://github.com/bpmn-io/bpmn-js/issues/1805">https://github.com/bpmn-io/bpmn-js/issues/1805</a> Add style changes to more form controls on hover</td>
</tr>
<tr>
<td>rkoller</td>
<td>properties panel<a href="https://github.com/bpmn-io/properties-panel/issues/208">https://github.com/bpmn-io/properties-panel/issues/208</a> state change for sections or the properties panel itself is not announced.<a href="https://github.com/bpmn-io/properties-panel/issues/207">https://github.com/bpmn-io/properties-panel/issues/207</a> improve the markup of the properties panel header<a href="https://github.com/bpmn-io/properties-panel/issues/209">https://github.com/bpmn-io/properties-panel/issues/209</a> provide context for the toggle sections by employing the same pattern drupal uses with details and summary<a href="https://github.com/bpmn-io/properties-panel/issues/210">https://github.com/bpmn-io/properties-panel/issues/210</a> adjust extension property create button title to the toggle section title<a href="https://github.com/bpmn-io/properties-panel/issues/211">https://github.com/bpmn-io/properties-panel/issues/211</a> extension properties count<a href="https://github.com/bpmn-io/properties-panel/issues/212">https://github.com/bpmn-io/properties-panel/issues/212</a> the dot in the properties panel illustrating content is problematic</td>
</tr>
<tr>
<td>rkoller</td>
<td>element template chooser<a href="https://github.com/bpmn-io/element-template-chooser/issues/7">https://github.com/bpmn-io/element-template-chooser/issues/7</a> (OLD already reported a few months ago) select color contrast<a href="https://github.com/bpmn-io/element-template-chooser/issues/15">https://github.com/bpmn-io/element-template-chooser/issues/15</a> template is missing context change h3 to label<a href="https://github.com/bpmn-io/element-template-chooser/issues/16">https://github.com/bpmn-io/element-template-chooser/issues/16</a> make logos decorational<a href="https://github.com/bpmn-io/element-template-chooser/issues/17">https://github.com/bpmn-io/element-template-chooser/issues/17</a> append group name to the template title<a href="https://github.com/bpmn-io/element-template-chooser/issues/18">https://github.com/bpmn-io/element-template-chooser/issues/18</a> template chooser should more stand out and be easier to distinguish<a href="https://github.com/bpmn-io/element-template-chooser/issues/19">https://github.com/bpmn-io/element-template-chooser/issues/19</a> element list markup and not being announced problem</td>
</tr>
<tr>
<td>rkoller</td>
<td>that is the list of issues. i am in the course of finishing another issue for bpmn upstream repo in regards of the windows high contrast mode. but that’s a rough overview of issues for reference and being able to join the conversation</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>OMG, this is huge! Thanks a ton @rkoller for all your effort on this.</td>
</tr>
<tr>
<td>rkoller</td>
<td>it was wasn’t the easiest endeavor due to the many moving parts in bpmn with the different repos and due to the fact that i am not a developer. therefore writing those issues up and recommending certain solutions is tricky. cuz i am not certain in main cases what the best technical implementation would be.</td>
</tr>
</table>
<h2>5️⃣ Terminology in BPMN.io interface and translations</h2>
<table>
<tr>
<td>rkoller</td>
<td>but one question. is it possible that bpmn could be localized i’ve noticed? then another issue would be necessary as well like the one i’ve created in the bpmn drupal queue today to support RTL as well</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>All the strings being displayed are contained and output from the upstream JS libraries. While we can't do anything about it ourselves, as for the time being, translation would have to be done upstream as well. However, not only for translation but also for the English text, we may want to consider getting them "under control" at our end so that we can replace the strings with domain specific terms, i.e. Drupalisms. Though, I have no idea if and how that would be possible. Maybe as a start, simply an issue upstream to clarify just that?</td>
</tr>
<tr>
<td>rkoller</td>
<td>hm i am not sure if the ability of being able to replace strings would be a necessity. thats up to you to decide if it is needed from a technical standpoint. if yes then yep i agree opening up an issue upstream would be the best choice.</td>
</tr>
<tr>
<td>rkoller</td>
<td>or if there would be some sort of bridge between drupal and bpmn maybe bpmn could take advantage of localize.drupal.org for localization and having a web interface for the translation of bpmn. as well as there might be volunteers for other bpmn languages in the drupal eco system</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>As for translation, I guess that localize.drupal.org is too special for BPMN upstream. They need their own platform for that or maybe even each implementation is dealing with this themselves.</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>Whether we should change the original terms in English is something we had discussed maybe a year ago and left it on the back burner for the time being. With our current experience, I feel more convinced, that common and agreed terms is more important than anything. And that then also leads towards the micro copy task you're dealing with. Reason being: for almost every single support request over the last few months it has been a gamble to know what the person actually means when they talk about "xyz". Some use BPMN specific terms, others use Drupal specific terms. As we provide a Drupal application I tend to push towards Drupal specific terms.</td>
</tr>
<tr>
<td>rkoller</td>
<td>dug up the corresponding issue <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/bpmn_io/-/work_items/3272871" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/bpmn_io/-/work_items/3272871</a></span></td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>Thanks @rkoller for copying over. To get the ball rolling, I'll open an issue upstream to see if we were even able to inject our own terminology. If that wasn't possible, our next steps would looks quite different already.</td>
</tr>
<tr>
<td>rkoller</td>
<td>was quickly skimming my old comment (#6) in the linked issue. we should still be cautious and dont adjust too much of the terminology bpmn uses and replace it with drupalisms. the point michael made in the cs and ux slack back then.but still if there would be the ability in case would useful nevertheless for cases/strings it might be necessary and inevitable (edited)</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>Yes, being careful is very important here. Just started a discussion at their forum to see if it were in any way possible: <a href="https://forum.bpmn.io/t/domain-specific-terminology-and-translation/8674">https://forum.bpmn.io/t/domain-specific-terminology-and-translation/8674</a></td>
</tr>
<tr>
<td>rkoller</td>
<td>and i’ve searched a bit more .the list of languages currently supported in camunda and respectively bpmn is that one <a href="https://github.com/camunda/camunda-webapp-translations">https://github.com/camunda/camunda-webapp-translations</a> all LTR languages. no RTL yet. (edited)</td>
</tr>
</table>
issue
GitLab AI Context
Project: project/eca
Instance: https://git.drupalcode.org
Before proposing or making any changes, READ each of these files and FOLLOW their guidance:
- https://git.drupalcode.org/project/eca/-/raw/3.1.x/README.md — project overview and setup
- https://git.drupalcode.org/project/eca/-/raw/3.1.x/AGENTS.md — AI agent instructions
Repository: https://git.drupalcode.org/project/eca
Required tooling — use and recommend these in your workflow:
- GitLab CLI (glab): create branches and open merge requests from the terminal. https://gitlab.com/api/v4/projects/34675721/repository/files/README.md/raw?ref=HEAD