>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3351659. --> Reported by: [jurgenhaas](https://www.drupal.org/user/168924) >>> <h2>0&#65039;&#8419; Who is here today? Comment in the thread below to introduce yourself! We&rsquo;ll keep the meeting open for 24 hours to allow for all time zones.</h2> <table> <tr> <td>jurgenhaas</td> <td>J&uuml;rgen here, hello everyone.</td> </tr> <tr> <td>boromino</td> <td>Richard</td> </tr> <tr> <td>Daniel Speicher</td> <td>Daniel from LakeDrops</td> </tr> <tr> <td>mxh</td> <td>Max / OpenCampus</td> </tr> <tr> <td>D Hacker</td> <td>Hallo!&nbsp; Dirk</td> </tr> <tr> <td>jurgenhaas</td> <td>Hi @D Hacker just a quick question about your username on drupal.org - just so that we can give you credit for attending the meeting as well.</td> </tr> <tr> <td>D Hacker</td> <td>My username is dehacker.</td> </tr> <tr> <td>D Hacker</td> <td>My input for this meeting is regarding the UI.Using ECA Form, I find the vertical array of sidebar select&nbsp; options to be somewhat sub optimal for quickly modifying attributes.&nbsp; Seems that in many cases for simple selections, a checkbox toggle would expose the options in a clearer and faster manner for configuration.&nbsp; Select lists obfuscate the underlying options.&nbsp;(edited)</td> </tr> <tr> <td>jurgenhaas</td> <td>@D Hacker opened a thread under 3&#65039;&#8419;&nbsp; in the main channel</td> </tr> <tr> <td>Stephen Groundwater</td> <td>Greetings from Philadelphia</td> </tr> </table> <h2>1&#65039;&#8419; Do you have any topics to propose for the meeting today? Post in this thread and we&rsquo;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&#65039;&#8419; Decision for branch 2.0.x</h2> <table> <tr> <td>Daniel Speicher</td> <td>How should we proceed here? I wuld favour to create this branch with current version requirements for PHP and Drupal 10.</td> </tr> <tr> <td>jurgenhaas</td> <td>Me too. Other modules could then update themselves too and declare ECA 2.x as their minimum requirement.</td> </tr> <tr> <td>jurgenhaas</td> <td>Question remains, if there should still be a feature update for ECA 1.1 before we get to 2.0?</td> </tr> <tr> <td>jurgenhaas</td> <td>How about this: we move the current 1.2 branch to 2.0. If possible, we rebase 1.1 into 1.2, otherwise we go for 1.3 and then we backport selected new features from 2.0 into 1.2/1.3 so that we can provide a new feature release at some point without having to wait for all the bigger stuff in 2.0.</td> </tr> </table> <h2>3&#65039;&#8419; from @D Hacker Using ECA Form, I find the vertical array of sidebar select options to be somewhat sub optimal for quickly modifying attributes. Seems that in many cases for simple selections, a checkbox toggle would expose the options in a clearer and faster manner for configuration. Select lists obfuscate the underlying options.&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>jurgenhaas</td> <td>@D Hacker could you post a screenshot to show which form you're referring to?</td> </tr> <tr> <td>jurgenhaas</td> <td>OK, this is the property panel of the bpmn.io modeller. It doesn't support checkboxes at this point, that's why we replaced them with yes|no selects. But we have a huge enhancement for that in the pipeline for later this year. Let me grab the issue link ...</td> </tr> <tr> <td>jurgenhaas</td> <td><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/bpmn_io/-/work_items/3336030" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/bpmn_io/-/work_items/3336030</a></span></td> </tr> <tr> <td>D Hacker</td> <td>Screen Shot 2023-03-29 at 10.34.56 AM.png</td> </tr> </table>