WEBVTT 48 00:08:11.950 --> 00:08:16.939 benji: welcome. This is the drupal usability meeting for January twelfth, 2024. 49 00:08:17.040 --> 00:08:23.090 benji: I'm Benji Fisher, moderating, and also here are Ralph Kohler, who's sharing his screen 50 00:08:23.580 --> 00:08:27.070 benji: and Simo Helston. So go ahead, Ralph. 51 00:08:28.260 --> 00:08:34.349 Ralf Koller: we're taking a look at issue number 2, 9, 2, 8, 8 52 00:08:34.860 --> 00:08:45.990 Ralf Koller: o, one. Remove hard coded restriction of fire size format into fields named file size. I've 53 00:08:46.070 --> 00:08:47.180 Ralf Koller: prepared 54 00:08:47.290 --> 00:08:54.309 Ralf Koller: 2 instances, one without the patch applied, and one with with the patch of light. 55 00:08:54.600 --> 00:08:55.800 Ralf Koller: I've 56 00:08:58.730 --> 00:09:07.849 Ralf Koller: went through the steps to reproduce basically how to set the issue up. Is you enable media and media library module. 57 00:09:07.870 --> 00:09:12.199 Ralf Koller: Then you add an integer number field 58 00:09:12.560 --> 00:09:16.959 Ralf Koller: and then on the media type for image. 59 00:09:17.890 --> 00:09:22.899 Ralf Koller: Yeah, under the field mapping, I'm like quickly show 60 00:09:25.990 --> 00:09:26.860 Ralf Koller: times. 61 00:09:27.090 --> 00:09:33.060 benji: Show me. Don't tell me. Yep, I realized while I was talking. 62 00:09:33.470 --> 00:09:35.700 Ralf Koller: under file, mapping 63 00:09:36.150 --> 00:09:40.070 Ralf Koller: file size set to the field, called Num. 64 00:09:40.260 --> 00:09:43.550 Ralf Koller: And if you go back 65 00:09:43.750 --> 00:09:45.550 Ralf Koller: to content 66 00:09:45.570 --> 00:09:56.029 Ralf Koller: media. I've already uploaded a thumbnail another thumbnail a file. an image. And as you can see, the 67 00:09:56.560 --> 00:09:57.920 Ralf Koller: file size. 68 00:09:58.210 --> 00:10:06.040 Ralf Koller: the integer value is autocroma automatically populated that field. There, that's the 69 00:10:06.310 --> 00:10:08.740 Ralf Koller: baselines for that. 70 00:10:09.970 --> 00:10:15.240 Ralf Koller: for the steps to reproduce! And from there 71 00:10:15.770 --> 00:10:20.190 Ralf Koller: we go now into the view 72 00:10:20.730 --> 00:10:22.339 Ralf Koller: media page list. 73 00:10:22.660 --> 00:10:25.909 Ralf Koller: and there, at the moment 74 00:10:26.440 --> 00:10:34.280 Ralf Koller: we are on the on the instance without the patch applied. and the instruction is to add, now a field 75 00:10:38.040 --> 00:10:39.010 Ralf Koller: number. 76 00:10:41.230 --> 00:10:42.720 Ralf Koller: add and configure. 77 00:10:42.940 --> 00:10:46.520 Ralf Koller: And now, on configure field media. 78 00:10:46.930 --> 00:10:51.160 Ralf Koller: we are currently there. Select file size for formatter 79 00:10:56.470 --> 00:11:03.459 Ralf Koller: and the use Ui behaves inconsistently at this point, while it preserves the value of formatter selection. 80 00:11:03.470 --> 00:11:09.110 Ralf Koller: formata settings will not be preserved. If you change 1,000 marker to comma 81 00:11:10.270 --> 00:11:19.040 Ralf Koller: at the moment is this eponym it will be non when revisited. Let's make it apply. 82 00:11:20.510 --> 00:11:24.940 Ralf Koller: Let me go in there. It's again Vietnam. 83 00:11:26.690 --> 00:11:36.310 Ralf Koller: and the view will continue to display the file size, value as though the formatter was set to unformat. No file size. Formatting, formatting is applied. 84 00:11:36.990 --> 00:11:42.880 Ralf Koller: and if you go over to the sight with a patch applied. 85 00:11:51.350 --> 00:11:53.770 Ralf Koller: it's now called byte size 86 00:11:55.030 --> 00:12:00.529 Ralf Koller: and no options anymore available. If you apply. 87 00:12:03.380 --> 00:12:06.160 Ralf Koller: save. let's go back. 88 00:12:12.080 --> 00:12:13.460 Ralf Koller: As you can see. 89 00:12:16.980 --> 00:12:22.430 Ralf Koller: the number field is adjusted. Oh, did it? I haven't noticed when I was testing 90 00:12:25.420 --> 00:12:30.900 Ralf Koller: I'm again on the site without, let's say, comma file size. Apply 91 00:12:32.070 --> 00:12:36.890 Ralf Koller: and oops save. And if you go to content 92 00:12:39.580 --> 00:12:40.530 Ralf Koller: media. 93 00:12:42.710 --> 00:12:44.440 Ralf Koller: there's no formatting applied. 94 00:12:48.960 --> 00:12:50.960 Ralf Koller: That's basically 95 00:12:54.190 --> 00:12:55.380 Ralf Koller: but 96 00:12:55.480 --> 00:13:03.430 Ralf Koller: I've considered the difference confusing. And therefore I've also asked on the select thread 97 00:13:04.090 --> 00:13:09.670 Ralf Koller: for someone familiar with a patch, maybe to join. But there was no reply. 98 00:13:12.140 --> 00:13:16.959 benji: Okay, so let me see if I understand the point here. So this is about 99 00:13:18.080 --> 00:13:20.550 benji: applying the 100 00:13:21.850 --> 00:13:24.589 benji: formatter file size formatter 101 00:13:25.720 --> 00:13:27.060 to 102 00:13:28.330 --> 00:13:30.189 benji: a field. That's not a file 103 00:13:30.640 --> 00:13:31.650 Ralf Koller: exactly. 104 00:13:32.280 --> 00:13:34.260 benji: Okay? 105 00:13:35.000 --> 00:13:40.160 Ralf Koller: So basically, if the the media image metadata 106 00:13:41.340 --> 00:13:43.770 Ralf Koller: or fields that are attached to that one. 107 00:13:49.980 --> 00:14:00.880 benji: So in in the example you you've just attached in an integer field media. But it it could be any other field could be a base field on on the media. Right? 108 00:14:00.940 --> 00:14:02.030 benji: That's what you're saying. 109 00:14:02.420 --> 00:14:05.330 Ralf Koller: Oh, no. I wanted to say 110 00:14:09.350 --> 00:14:10.760 Ralf Koller: to a media 111 00:14:12.050 --> 00:14:16.209 Ralf Koller: entity, basically to me, to media type 112 00:14:16.740 --> 00:14:18.920 Ralf Koller: oops. I open that one? Okay. 113 00:14:19.080 --> 00:14:24.430 Ralf Koller: there are, you know. and a media type. or the image meter type. 114 00:14:26.010 --> 00:14:30.270 Ralf Koller: a number field with a format of integer 115 00:14:30.580 --> 00:14:35.629 Ralf Koller: with a file type of in field type of int number. Integer was, added 116 00:14:36.360 --> 00:14:37.020 benji: Brett. 117 00:14:37.260 --> 00:14:44.059 Ralf Koller: And that's the point that that on the view you decide or set 118 00:14:44.140 --> 00:14:47.580 Ralf Koller: the formatting for that number field 119 00:14:55.730 --> 00:14:56.670 Ralf Koller: in Europe. 120 00:15:09.400 --> 00:15:15.500 Simo Hellsten: What? Yeah, I can't see from there. What are the other other? Formatter options? 121 00:15:15.650 --> 00:15:23.959 Simo Hellsten: Yeah, default and unformatted. Yeah. So that's for me. like from for integer. 122 00:15:24.840 --> 00:15:27.709 Ralf Koller: 1 Si go in with the patch applied. 123 00:15:28.350 --> 00:15:35.999 Ralf Koller: Yeah, there's byte size, default and unfrominated. So the same number of formatters available. Just a rewording 124 00:15:37.870 --> 00:15:39.729 Ralf Koller: from file size to bite size. 125 00:15:43.010 --> 00:15:50.150 benji: Okay? So then. so this is about a views formatter. is that right? 126 00:15:51.020 --> 00:15:52.890 Ralf Koller: Yeah, it looks like, yeah. 127 00:15:52.940 --> 00:15:58.070 benji: So when you're when you're when you have a few that's not showing 128 00:15:58.450 --> 00:16:05.960 benji: rendered entities, but shown fields. And you choose how to format a particular field in the view. 129 00:16:06.590 --> 00:16:16.500 benji: and you're demonstrating with the view that comes with core that generates the media listing page. But it it could also be some other view that that you create. 130 00:16:17.680 --> 00:16:22.259 benji: And there seems to be currently a bug that 131 00:16:22.660 --> 00:16:27.090 benji: this formatter doesn't pay attention 132 00:16:27.290 --> 00:16:37.520 benji: to the 1,000 separator and when you try to change it, it doesn't take effect, and it doesn't show up 133 00:16:37.900 --> 00:16:39.750 benji: when you look at the view. 134 00:16:41.810 --> 00:16:46.699 benji: So that seems like a bug. And if we're if we're not going to respect that. 135 00:16:46.810 --> 00:16:53.430 benji: then we shouldn't show it on the form. That that seems pretty clear. said the patches, removing that 136 00:16:55.010 --> 00:17:01.560 benji: the option that it doesn't respect. So that that makes sense. 137 00:17:01.680 --> 00:17:07.739 benji: So so what else is the patch doing? That's change. It's changing the formatter from file size to 138 00:17:08.130 --> 00:17:10.810 benji: bite size or something. Yeah, bite size. 139 00:17:14.940 --> 00:17:18.949 Ralf Koller: But one thing I don't understand 140 00:17:21.060 --> 00:17:27.939 Ralf Koller: is the bug still in place and just hidden, basically by removing the 1,000 marker. 141 00:17:29.690 --> 00:17:33.100 Ralf Koller: Because basically, if you take a look here 142 00:17:33.430 --> 00:17:38.780 Ralf Koller: with byte size, and there you get basically, it's a 143 00:17:39.860 --> 00:17:42.829 benji: the decimal is not. It's not a thousand separator. 144 00:17:45.800 --> 00:17:49.679 Simo Hellsten: and also it's Kilobytes bytes. So it's kind of a 145 00:17:50.490 --> 00:17:55.029 Simo Hellsten: if I don't, I would like to ha have a format for that one. 146 00:17:55.580 --> 00:17:58.649 Simo Hellsten: If if it says byte size, then kind of 147 00:17:58.920 --> 00:18:01.099 Simo Hellsten: I don't know what what the 148 00:18:04.500 --> 00:18:07.420 Simo Hellsten: like. A. If somebody wants to have it 149 00:18:08.640 --> 00:18:19.420 Simo Hellsten: round it up, or something like that. So kind of is that something that comes from elsewhere in core routing up to Kilobytes or with 2 decimals? 150 00:18:24.880 --> 00:18:27.350 Simo Hellsten: Do you have the same file? 151 00:18:28.040 --> 00:18:31.120 Simo Hellsten: in this other, the one that's identical. 152 00:18:31.580 --> 00:18:34.990 Simo Hellsten: And it had like more numbers. So that's rounded. 153 00:18:38.960 --> 00:18:40.850 Simo Hellsten: or is it just? It happened 154 00:18:41.260 --> 00:18:44.040 Ralf Koller: 11,538 155 00:18:56.360 --> 00:18:57.320 Ralf Koller: second. 156 00:19:08.440 --> 00:19:10.770 benji: yeah, 11.2 7 is correct. 157 00:19:11.780 --> 00:19:18.910 benji: If the Helo prefix means 2 to the tenth, means 1,024 rather than 1,000 158 00:19:19.180 --> 00:19:21.720 benji: and 11.2 7 159 00:19:22.560 --> 00:19:29.319 benji: a is to 2 decimal places. The same as 1, 1, 5, 3, 8. 160 00:19:33.160 --> 00:19:36.610 Simo Hellsten: So is it is that one defined by the 161 00:19:36.880 --> 00:19:41.810 Simo Hellsten: touch, or is it somewhere that comes from? Is it somehow manageable? 162 00:19:42.420 --> 00:19:43.739 Simo Hellsten: Because it's kind of a 163 00:19:46.470 --> 00:19:48.510 Simo Hellsten: that's a fixed formatting 164 00:19:49.460 --> 00:19:52.050 Simo Hellsten: now. So replacing 165 00:19:52.270 --> 00:19:55.860 Simo Hellsten: formatting, that doesn't work with something. 166 00:19:58.160 --> 00:19:59.420 Ralf Koller: I just 167 00:20:00.650 --> 00:20:05.459 Ralf Koller: opened the patch. And it's just changing the 168 00:20:06.480 --> 00:20:08.369 Ralf Koller: label more or less 169 00:20:09.070 --> 00:20:11.500 Ralf Koller: and removing one detail. 170 00:20:12.120 --> 00:20:13.230 Ralf Koller: And that's it. 171 00:20:14.880 --> 00:20:15.640 Simo Hellsten: Yeah. 172 00:20:17.150 --> 00:20:19.630 Simo Hellsten: But basically, yeah, so it's 173 00:20:19.680 --> 00:20:21.640 Simo Hellsten: rendering, rendering 174 00:20:22.460 --> 00:20:26.660 Simo Hellsten: and integral with something that already exists. Or. 175 00:20:28.260 --> 00:20:28.960 Simo Hellsten: yeah. 176 00:20:33.580 --> 00:20:45.700 benji: So I think the new label is not a great choice, calling it byte size. If we're going to display it as Kilobytes. If it's over 177 00:20:46.660 --> 00:20:50.310 benji: 1,024, or whatever the limit is 178 00:20:50.640 --> 00:20:53.850 benji: it. 179 00:20:56.650 --> 00:20:59.090 benji: It does seem like an 180 00:21:02.270 --> 00:21:08.479 benji: choice to apply. although II guess there, there could be use cases. You 181 00:21:08.930 --> 00:21:12.349 benji: you you you could be getting 182 00:21:13.110 --> 00:21:15.350 benji: file sizes from 183 00:21:15.690 --> 00:21:20.169 benji: spreadsheet and entering them in your integer field. 184 00:21:20.490 --> 00:21:26.619 benji: and then you you do want to display them as Kilobytes or megabytes 185 00:21:27.050 --> 00:21:31.569 benji: rather than number of bytes. 186 00:21:32.010 --> 00:21:35.229 benji: So I suppose there there could be use cases for this. 187 00:21:35.790 --> 00:21:42.559 benji: but but II don't like calling it bite. Size. 188 00:21:45.180 --> 00:21:47.870 Simo Hellsten: Yeah. I'm also wondering 189 00:21:49.870 --> 00:21:54.419 Simo Hellsten: it. Which which web version it uses for ordering. 190 00:21:54.620 --> 00:22:04.339 Simo Hellsten: Is it using that display version displayed version, or reducing the original value for ordering? 191 00:22:04.600 --> 00:22:06.560 Simo Hellsten: So does it order? 192 00:22:07.200 --> 00:22:11.819 Simo Hellsten: 1 1 kB before or after 2 Byte 193 00:22:13.900 --> 00:22:16.370 Simo Hellsten: or so. 194 00:22:17.350 --> 00:22:20.829 Simo Hellsten: So you're talking about sort order. Yeah, sort order. Yeah. 195 00:22:21.180 --> 00:22:26.479 Simo Hellsten: I don't think that would be effected by a display format. Or 196 00:22:29.690 --> 00:22:32.959 Simo Hellsten: yeah, it definitely doesn't for dates. 197 00:22:38.730 --> 00:22:41.100 benji: Right? That's that's a good comparison. 198 00:22:41.820 --> 00:22:48.630 benji: You, you can format a date as a timestamp, or you can format it as monthly year. 199 00:22:48.970 --> 00:22:52.079 benji: and that's not going to affect how it gets sorted. 200 00:22:53.110 --> 00:22:56.100 Simo Hellsten: But in some cases you might want to have. 201 00:22:57.650 --> 00:22:58.430 Simo Hellsten: So 202 00:23:03.870 --> 00:23:05.760 Simo Hellsten: it sounds like a 203 00:23:06.320 --> 00:23:11.120 Simo Hellsten: rendering something. If it's if you're rendering like out for maybe 204 00:23:11.920 --> 00:23:14.149 Simo Hellsten: referencing a media, then 205 00:23:17.810 --> 00:23:29.089 Simo Hellsten: yeah, well, you shouldn't try to anything rent rendered Media, you shouldn't try to order it. anyway. So you should take that. Some fear done. Then try to order it by that 206 00:23:39.620 --> 00:23:41.510 Simo Hellsten: render Toxon return. 207 00:23:42.940 --> 00:23:44.140 Simo Hellsten: you know. View 208 00:23:46.830 --> 00:23:48.829 Simo Hellsten: that's something that might might be. 209 00:23:57.430 --> 00:24:05.879 Simo Hellsten: Yeah, let's not get and get into that. There. There might be some use cases where rendered like the display version would be the correct one for 210 00:24:06.090 --> 00:24:07.260 Simo Hellsten: sorting. But 211 00:24:08.050 --> 00:24:11.320 Simo Hellsten: it's not something that it's an it maybe 212 00:24:11.700 --> 00:24:13.149 Simo Hellsten: not an issue here. 213 00:24:16.610 --> 00:24:23.910 benji: So what? What is the specific usability question that was raised here? Why, why was it tagged? 214 00:24:25.300 --> 00:24:31.080 benji: Or was a tagged for usability review, or or did since someone's next slide? 215 00:24:31.410 --> 00:24:34.060 Simo Hellsten: it's attacked 216 00:24:35.670 --> 00:24:37.340 1 s 217 00:24:50.980 --> 00:25:08.749 Ralf Koller: referring to comment number 9. I can see that this could be useful for other cases, but I think it should be reviewed by the Usability index exposes a new format option for all integer fields, and for most it won't make sense, especially not as file size. One option could be to change the label. 218 00:25:16.940 --> 00:25:19.760 Simo Hellsten: So the question is, 219 00:25:20.230 --> 00:25:27.000 Simo Hellsten: about if it's byte size for something that's maybe not a file so integr field 220 00:25:27.470 --> 00:25:31.810 Simo Hellsten: or something else that is not seen as a file. 221 00:25:33.590 --> 00:25:38.080 benji: right? And and since then, someone has changed the label from 222 00:25:38.400 --> 00:25:46.960 Simo Hellsten: file size to byte size. Yeah. So let's see. Say, somebody wants to make a list of Internet connections. 223 00:25:47.190 --> 00:25:53.190 Simo Hellsten: Then they have a some speed that's marked as integer. 224 00:25:53.580 --> 00:25:59.559 Simo Hellsten: and somebody wants to format them so. But it will be kilobytes and stuff like that. 225 00:25:59.580 --> 00:26:07.680 Simo Hellsten: So then, if it's called byte size, then this format app would make sense. If it's called file size, it doesn't make sense for 226 00:26:07.760 --> 00:26:13.509 Simo Hellsten: the connection speed. But yeah. connections actually are measured 227 00:26:13.840 --> 00:26:21.350 Simo Hellsten: usually with different but kiple per second. But anyways 228 00:26:21.410 --> 00:26:23.399 Simo Hellsten: so in in certain cases. 229 00:26:24.700 --> 00:26:30.930 Simo Hellsten: But there, there, like, there might be something that measured in bytes. But it's not files. So I think that's the question. 230 00:26:36.950 --> 00:26:40.509 Ralf Koller: And I've added one example just 231 00:26:40.530 --> 00:26:47.179 Ralf Koller: loaded up one other screenshot for megabyte size for comparison. 232 00:26:50.060 --> 00:26:51.840 Ralf Koller: But the field isn't sortable. 233 00:26:52.180 --> 00:26:52.840 Simo Hellsten: Hmm. 234 00:27:01.860 --> 00:27:05.920 benji: you you could make it sortable. That's a a setting in views. 235 00:27:08.580 --> 00:27:09.760 Ralf Koller: Bite size 236 00:27:09.950 --> 00:27:12.310 Simo Hellsten: is that table table 237 00:27:12.390 --> 00:27:17.379 Simo Hellsten: in the like, main main. 238 00:27:17.540 --> 00:27:20.240 Simo Hellsten: yeah. So and then 239 00:27:21.020 --> 00:27:25.179 Simo Hellsten: format. And is it in table or in settings? 240 00:27:25.740 --> 00:27:27.139 benji: Think it's in settings? 241 00:27:30.330 --> 00:27:31.110 Simo Hellsten: Yes. 242 00:27:31.890 --> 00:27:34.009 Ralf Koller: oh, okay. 243 00:27:42.150 --> 00:27:42.929 Ralf Koller: you forgot. 244 00:27:50.000 --> 00:27:57.250 benji: Okay? So the specific usability question is what's called label, which is sort of what what I noticed as as you were 245 00:27:57.440 --> 00:27:58.780 benji: demonstrating it. 246 00:27:59.850 --> 00:28:04.690 benji: and 247 00:28:06.980 --> 00:28:14.100 benji: I don't like byte size, but II can't think offhand. Is there a standard name for 248 00:28:15.230 --> 00:28:20.129 benji: for for this way of rounding a number? 249 00:28:26.350 --> 00:28:32.490 benji: And and it is specifically not not just using the prefixes for for 250 00:28:32.570 --> 00:28:36.190 benji: Kilo and Mega. But it's Kilobyte and Megabyte. 251 00:28:36.930 --> 00:28:41.650 benji: so 252 00:28:47.980 --> 00:28:48.710 Ralf Koller: hmm! 253 00:29:03.250 --> 00:29:08.710 Ralf Koller: And would it make sense to simply say, size that way would be more generic. 254 00:29:13.450 --> 00:29:15.319 Ralf Koller: but also unspecific. 255 00:29:15.660 --> 00:29:22.420 Simo Hellsten: Hmm. I think if if we have wide sized size, then it's possible to expand it to 256 00:29:22.660 --> 00:29:24.310 Simo Hellsten: bit size, or 257 00:29:24.530 --> 00:29:29.360 Simo Hellsten: K. Bits, or something like that. 258 00:29:31.610 --> 00:29:33.439 Simo Hellsten: And so it's it's possible 259 00:29:35.600 --> 00:29:37.450 Simo Hellsten: then to like 260 00:29:39.640 --> 00:29:40.680 Simo Hellsten: I 261 00:29:41.990 --> 00:29:46.370 Simo Hellsten: to have different kind, so so kind of. If it's in bytes, then it's 262 00:29:47.420 --> 00:29:52.559 Simo Hellsten: it's some something that kind of tells what's the basic measure. So it's kind of a 263 00:29:54.140 --> 00:29:56.960 Simo Hellsten: or it could be my size, or 264 00:30:01.130 --> 00:30:06.510 Simo Hellsten: kind of wide size converted to Kilobytes or Megabytes. 265 00:30:07.980 --> 00:30:14.310 Simo Hellsten: that that doesn't have a I don't can't think of a word for that 266 00:30:24.170 --> 00:30:27.460 benji: Hi and offer has just joined us offers all. 267 00:30:31.070 --> 00:30:34.320 benji: So offer we're we're looking at this issue 268 00:30:34.890 --> 00:30:46.219 benji: that says that there are use cases where the file, size formatter might be applied to an arbitrary integer field. 269 00:30:46.680 --> 00:30:54.190 benji: So if you have file sizes, but they're not coming from files on your system, they're just coming from a spreadsheet, and you've entered them 270 00:30:54.970 --> 00:30:57.460 into a numbered field. 271 00:30:57.600 --> 00:31:12.919 benji: Then you might want to use the Kb. And Md. Suffixes when formatting them. and format and integer, as as in this example, so 11.2 7 kb. 272 00:31:13.080 --> 00:31:16.970 benji: Or 1.9 3 MB. And then the question is. 273 00:31:17.220 --> 00:31:21.419 benji: what to call if the formatter. 274 00:31:21.780 --> 00:31:28.109 benji: which is currently called file size. But if you allow it to be applied to any integer field, then. 275 00:31:28.230 --> 00:31:32.780 benji: and file size seems like the wrong label. So what should we call it? 276 00:31:34.020 --> 00:31:45.349 Simo Hellsten: Actually, I think the excess excess word is size. So it doesn't have to mean size. So it's just we convert integer to bytes and kilobytes. 277 00:31:45.500 --> 00:31:48.099 Simo Hellsten: so we could just call it bytes and kilobytes. 278 00:31:53.390 --> 00:31:57.240 Simo Hellsten: And of course it would have been megan terra, but kind of 279 00:31:58.900 --> 00:32:03.520 Simo Hellsten: basically. The format formatter is converting integer into bytes. 280 00:32:04.280 --> 00:32:06.340 Simo Hellsten: So it doesn't have to mean size. 281 00:32:08.960 --> 00:32:09.940 benji: Okay. 282 00:32:19.190 --> 00:32:26.220 benji: offer? You're you're still muted. Do you have any questions about the context. what question. 283 00:32:26.450 --> 00:32:27.679 Ofer Shaal: the thing that's clear. 284 00:32:28.020 --> 00:32:33.500 benji: Got it. That was it just wanted to check that. You weren't having audio problems. Okay? 285 00:32:33.690 --> 00:32:37.799 benji: okay, so just call it bytes. That's 286 00:32:39.230 --> 00:32:48.759 benji: interesting. We II think we don't really have the option of adding description text here. It's one option in a select list. 287 00:32:49.540 --> 00:32:55.090 benji: so we we do have to think of something descriptive 288 00:32:55.270 --> 00:32:56.429 benji: and short. 289 00:32:57.900 --> 00:33:01.920 benji: So just sites interesting. 290 00:33:03.230 --> 00:33:11.350 benji: And and of course it would show up the same when it when it is being applied to a file field. 291 00:33:23.570 --> 00:33:24.459 benji: You know what 292 00:33:25.230 --> 00:33:30.689 benji: what happens if we just use our favorite search engine for inspiration 293 00:33:30.960 --> 00:33:34.519 benji: or or chat. Gpt, if you like. 294 00:33:39.690 --> 00:33:42.330 benji: I just search for file size. 295 00:33:45.730 --> 00:33:47.089 benji: There's a 296 00:33:48.280 --> 00:33:53.940 benji: Wikipedia article. There's a file size calculator. 297 00:34:11.280 --> 00:34:25.420 benji: So in the Wikipedia Page. It mentions typically file size is expressed in units of measurement based on the byte by convention, file size units use either a metric prefix, as in Megabyte and Gigabyte. 298 00:34:25.560 --> 00:34:28.659 benji: or a binary prefix, as in 299 00:34:28.690 --> 00:34:31.350 benji: Methodite and Gibbette. 300 00:34:32.100 --> 00:34:33.889 benji: Whoa! That's 301 00:34:34.100 --> 00:34:36.629 benji: those are not terms that are familiar to me. 302 00:34:38.270 --> 00:34:43.779 Simo Hellsten: I think if we want to make it precise. We could call it prefix bytes. 303 00:34:44.060 --> 00:34:46.520 Simo Hellsten: But that doesn't mean a lot to 304 00:34:47.469 --> 00:34:50.429 Simo Hellsten: the common user. So so we have a 305 00:34:50.580 --> 00:34:56.330 Simo Hellsten: prefix. And then we have the bytes. So 306 00:34:58.810 --> 00:35:00.119 Simo Hellsten: kind of a 307 00:35:01.230 --> 00:35:07.810 Simo Hellsten: when when we talk about those kilo mega giga, we're talking about metric prefixes. 308 00:35:08.820 --> 00:35:11.409 Simo Hellsten: and then we have the bytes 309 00:35:11.700 --> 00:35:18.619 Simo Hellsten: that are displayed like it's the the integrates, the spread played in bytes with metric prefixes. 310 00:35:18.670 --> 00:35:20.560 Simo Hellsten: So that's what we are doing. 311 00:35:21.960 --> 00:35:23.630 Simo Hellsten: What the 312 00:35:24.000 --> 00:35:24.840 Simo Hellsten: kind of 313 00:35:25.440 --> 00:35:29.269 Simo Hellsten: metric prefix. Bytes. It's something that sounds 314 00:35:29.440 --> 00:35:30.370 Simo Hellsten: fairly 315 00:35:32.170 --> 00:35:38.990 Simo Hellsten: difficult to understand when you're like I'll let unless you have a certain background. 316 00:35:39.950 --> 00:35:40.870 benji: Right? 317 00:35:44.360 --> 00:35:49.889 benji: Anyway, I'll I'll share the Wikipedia page I'm looking at in in the chat so. 318 00:35:58.090 --> 00:35:58.930 benji: and 319 00:35:59.830 --> 00:36:06.819 benji: based on what I'm reading there, I'm I'm sort of warming up to seamless suggestion that we just call it bytes 320 00:36:08.100 --> 00:36:16.049 Simo Hellsten: or bytes with prefix, or something like that. So if we want, but because it's not just bytes. But if it's bytes, then it's kind of a 321 00:36:18.310 --> 00:36:22.189 Ralf Koller: or would it make sense to use the singular form by formatting? 322 00:36:23.450 --> 00:36:24.410 Ralf Koller: Simply? 323 00:36:29.880 --> 00:36:30.810 benji: Hmm! 324 00:36:33.460 --> 00:36:36.439 Simo Hellsten: I think bytes, it's I think it's 325 00:36:36.610 --> 00:36:38.440 Simo Hellsten: chlorine is better 326 00:36:39.160 --> 00:36:43.729 Simo Hellsten: cause. It's hardly hardly ever. It's number 8. 327 00:36:44.090 --> 00:36:48.359 Simo Hellsten: So that is, yeah, it's kind of why, it's it's kind of feels better. 328 00:36:53.400 --> 00:36:58.060 benji: It's put into the chat bytes, and then in parentheses with prefix. 329 00:36:58.200 --> 00:36:59.000 Simo Hellsten: Yes. 330 00:37:01.210 --> 00:37:06.070 Simo Hellsten: I would like to see that with prefix as a default option instead of 1,000 331 00:37:06.340 --> 00:37:11.220 Simo Hellsten: separator. So it's kind of a you could have prefix or 332 00:37:11.660 --> 00:37:15.920 Simo Hellsten: like. Well, what what are the kind of formatting for bytes you want? 333 00:37:16.700 --> 00:37:19.229 Simo Hellsten: But it's not in this 334 00:37:19.610 --> 00:37:22.379 Simo Hellsten: the scope. So I think we could call bytes. 335 00:37:22.430 --> 00:37:29.580 Simo Hellsten: and then it could be ex expanded with like getting a detailed version. What what kind of 336 00:37:29.770 --> 00:37:35.559 Simo Hellsten: prefixes? And if you want to have just bytes, or if you want to have a 337 00:37:35.600 --> 00:37:39.620 Simo Hellsten: the one that's currently the default option or the only option. 338 00:37:39.680 --> 00:37:41.739 Simo Hellsten: So if we call it bytes. 339 00:37:41.760 --> 00:37:45.019 Simo Hellsten: and then it could be detailed in another 340 00:37:46.070 --> 00:37:47.380 Simo Hellsten: option. 341 00:37:48.230 --> 00:37:55.219 Simo Hellsten: Like is like, like, currently there is the 1,000 separator. So there could be another choice for 342 00:37:55.270 --> 00:38:02.920 Simo Hellsten: directing how to format the bytes, but it would. The basic vomiting would be bytes. So we could 343 00:38:03.280 --> 00:38:04.829 Simo Hellsten: stick with that. Now. 344 00:38:05.600 --> 00:38:15.980 benji: Yeah, II agree. That one this is out of scope for the current issue, but that 2 there should be more options. So we should have a follow up 345 00:38:16.070 --> 00:38:27.390 benji: issue. So for one I'm American, and I always use a comma as the thousands separator and.as the decimal separator. 346 00:38:27.650 --> 00:38:31.639 benji: But I I'm aware that other people do it the other way around. 347 00:38:31.800 --> 00:38:41.420 benji: And so if we're going to have what what was it? 11.5 8, or whatever we should have the option to use a comma 348 00:38:41.490 --> 00:38:44.300 benji: as the decimal separator. 349 00:38:44.840 --> 00:38:56.780 benji: and then perhaps, some people would want the option to use metric prefixes. So 1,001,000,000 rather than 1,024, and 350 00:38:56.910 --> 00:38:57.960 benji: of 351 00:38:58.090 --> 00:39:00.780 benji: 1048576 352 00:39:00.970 --> 00:39:01.790 benji: as 353 00:39:03.140 --> 00:39:07.369 benji: as the prefixes, so it it so that those are 354 00:39:07.570 --> 00:39:09.740 benji: reasonable options to add. 355 00:39:10.130 --> 00:39:16.299 benji: but not in scope for this issue. So I would suggest that we go with something like 356 00:39:16.420 --> 00:39:19.489 benji: bytes with prefix in the current issue. 357 00:39:19.830 --> 00:39:26.029 benji: and then a follow up issue, could just call it bytes and 358 00:39:26.380 --> 00:39:30.760 benji: and give the options of 359 00:39:31.260 --> 00:39:38.880 benji: not using any prefix or using metric based prefixes or using binary prefixes. 360 00:39:39.020 --> 00:39:40.520 benji: and also. 361 00:39:40.930 --> 00:39:47.020 benji: choose the decimal and 1,000 separators. Does that make sense? 362 00:39:51.580 --> 00:39:55.919 Ralf Koller: Just one comment from my non-developer perspective? 363 00:39:56.900 --> 00:40:00.220 Ralf Koller: And also not a native speaker perspective ever. 364 00:40:00.670 --> 00:40:02.340 Ralf Koller: I have issues 365 00:40:03.040 --> 00:40:06.400 Ralf Koller: completely understanding what with prefix even means. 366 00:40:06.450 --> 00:40:07.920 benji: Okay in that regard. 367 00:40:11.590 --> 00:40:23.279 benji: And IIII appreciate that point of view. And O, always when people say, Oh, I don't want to come to this meeting, because my English isn't so good. I say, no, no, we want the people who 368 00:40:23.320 --> 00:40:31.960 benji: whose first language is not English, because that that's a very valuable point of view and usability discussions. So you don't like 369 00:40:32.400 --> 00:40:38.100 benji: with prefix? No, I don't say I don't like it. I just wanted to point out that 370 00:40:40.360 --> 00:40:45.269 Ralf Koller: to get meaning into it is difficult to do to understand what it actually implies 371 00:40:45.540 --> 00:41:01.110 Ralf Koller: I have a problem with with a prefix for me is something is before bytes. So I mean by I see, for example, if Byte mean in that in that example, 15 Byte, for example, that something is prefixed to that 15. 372 00:41:01.560 --> 00:41:03.720 Ralf Koller: That is what I would understand. 373 00:41:05.840 --> 00:41:09.529 Simo Hellsten: Yeah, in German translation. Would it be something like. 374 00:41:09.730 --> 00:41:12.270 Simo Hellsten: Meet 4 sets of your mice heighten. 375 00:41:15.540 --> 00:41:18.839 Simo Hellsten: Maybe I have it backwards. Maybe it should be bytes with suffix. 376 00:41:20.200 --> 00:41:22.380 Simo Hellsten: No, but that prefix is for the 377 00:41:23.620 --> 00:41:29.249 Simo Hellsten: bytes kilobytes. So it's kind of up. Yeah, it's not. It's not clear. 378 00:41:29.510 --> 00:41:39.020 benji: It's a prefix on the suffix 379 00:41:39.080 --> 00:41:45.330 Simo Hellsten: a sake of record. The reason we can't just use normal suffix for this is that we need to divide that 380 00:41:45.970 --> 00:41:49.390 Simo Hellsten: integer by 8, and then by 381 00:41:49.500 --> 00:41:55.470 Simo Hellsten: kind of Q, one mega things. So normally we would have. We could just edit this 382 00:41:55.760 --> 00:42:02.280 Simo Hellsten: suffix to whatever. But then we because we change the number, so it doesn't really 383 00:42:03.430 --> 00:42:08.239 Simo Hellsten: we can't, because it's also confusing, because we have prefixes and suffixists. 384 00:42:08.530 --> 00:42:10.410 Simo Hellsten: In that 385 00:42:11.110 --> 00:42:17.789 Simo Hellsten: some other parts of the I feel have used us figure to configuration. 386 00:42:32.500 --> 00:42:34.729 Simo Hellsten: so is it install settings. 387 00:42:36.990 --> 00:42:38.260 benji: And 388 00:42:39.590 --> 00:42:45.209 benji: let's also consider the option of continuing to call it file size. 389 00:42:55.000 --> 00:43:03.109 Simo Hellsten: Yeah, if we want to create problems, then we could ask file size on disk or file size 390 00:43:04.200 --> 00:43:07.960 Simo Hellsten: mean some other calculation method. 391 00:43:11.160 --> 00:43:16.130 Simo Hellsten: So file sizes differ on where it's stored. 392 00:43:17.430 --> 00:43:18.560 Simo Hellsten: Also. 393 00:43:20.370 --> 00:43:22.320 Simo Hellsten: Now let's get getting. 394 00:43:22.380 --> 00:43:24.260 Simo Hellsten: Try and go find problems. 395 00:43:44.410 --> 00:43:46.520 Simo Hellsten: well. 396 00:43:49.670 --> 00:43:53.779 Simo Hellsten: but somehow I don't like bite size, so II would kind of it's 397 00:43:54.070 --> 00:43:55.379 Simo Hellsten: vomit would sound 398 00:43:55.880 --> 00:43:59.590 Simo Hellsten: easier if it would be size in bytes. Actually. 399 00:44:02.250 --> 00:44:03.000 Ralf Koller: Yep. 400 00:44:07.720 --> 00:44:11.019 Simo Hellsten: so it's in bytes or shorter version bytes. 401 00:44:19.270 --> 00:44:25.070 Ralf Koller: But with the shorter version the context is missing. But I agree that size in bytes 402 00:44:27.080 --> 00:44:32.099 Ralf Koller: might be a considerable compromise from my perspective, I compared to 403 00:44:32.150 --> 00:44:36.860 Ralf Koller: bytes whose prefix was more abstract and confusing from my point of view. 404 00:44:43.010 --> 00:44:52.319 benji: I put another suggestion in the chat bytes, and then in parentheses KB comma MB comma dot dot dot those paren 405 00:45:03.050 --> 00:45:05.359 Simo Hellsten: that contents also information. 406 00:45:13.220 --> 00:45:17.929 Simo Hellsten: It also shows its big K instead of small K or 407 00:45:18.020 --> 00:45:19.230 Simo Hellsten: public art. 408 00:45:20.840 --> 00:45:24.970 Simo Hellsten: lower case or upper case K, so it's kind of, but also shows that 409 00:45:36.710 --> 00:45:37.640 benji: that's 410 00:45:37.890 --> 00:45:41.310 benji: a a a little bit long. I guess. 411 00:45:42.370 --> 00:45:48.619 benji: Probably a few characters longer than unformatted. But I don't think it's so long as to be problematic. 412 00:45:49.400 --> 00:45:57.480 benji: does does that give you an idea what to expect 413 00:46:01.810 --> 00:46:05.449 Ralf Koller: definitely better from my perspective. But 1 one question 414 00:46:05.500 --> 00:46:09.849 Ralf Koller: is it possible to. or is the 415 00:46:11.180 --> 00:46:16.850 Ralf Koller: scenario even possible, to have, an image that has a size of gigabytes. 416 00:46:20.520 --> 00:46:24.580 Ralf Koller: Otherwise you could even strike the 3 dots 417 00:46:25.790 --> 00:46:28.340 Ralf Koller: and just use Kilobyte and megabyte. 418 00:46:29.180 --> 00:46:42.780 benji: So if we're applying this to an integer field, then then that comes irrelevant. right? As as long as we're applying it only to files, we can say, Well, do we actually allow gigabyte 419 00:46:42.890 --> 00:46:44.720 benji: files to be attached? 420 00:46:44.980 --> 00:46:50.680 benji: But but when now that we're applying it to an arbitrary integer field. 421 00:46:50.810 --> 00:46:51.850 benji: sure I did 422 00:46:53.430 --> 00:46:54.600 benji: the 423 00:46:57.240 --> 00:47:02.949 benji: You know what whether or not we can attach large files to our drupal site becomes irrelevant. 424 00:47:57.760 --> 00:48:03.439 Simo Hellsten: We have any other formaters that have that kind of app additional description 425 00:48:07.130 --> 00:48:07.880 left. 426 00:48:56.640 --> 00:49:01.069 Simo Hellsten: Well, image size had at least so it's it wasn't a format robot. 427 00:49:02.050 --> 00:49:08.170 Simo Hellsten: It had original, non original image size. So there is related 428 00:49:18.070 --> 00:49:19.170 Simo Hellsten: so where? 429 00:49:19.700 --> 00:49:25.130 Simo Hellsten: But image style, it has none in parentheses or 430 00:49:25.430 --> 00:49:26.499 Ralf Koller: so, thank you. 431 00:49:26.610 --> 00:49:28.169 Simo Hellsten: Yeah. So there is a 432 00:49:37.050 --> 00:49:43.540 Simo Hellsten: yeah. So there, there are, like, yeah, on on similar similar forms, there are 433 00:49:43.710 --> 00:49:46.770 Simo Hellsten: select options with a 434 00:49:47.670 --> 00:49:52.819 Simo Hellsten: more details in parentheses. So in that case, I think that 435 00:49:53.560 --> 00:49:56.569 Simo Hellsten: bytes in parentheses KB 436 00:49:57.030 --> 00:50:02.780 Simo Hellsten: comma MB comma dot dot. Dot. That that's kind of a pizza. 437 00:50:04.970 --> 00:50:07.880 Simo Hellsten: So it's not entirely new pattern. 438 00:50:33.290 --> 00:50:35.810 benji: So shall we go with this as a recommendation? 439 00:50:42.120 --> 00:50:44.289 benji: Okay, see? Now, gives the thumbs up. 440 00:50:47.700 --> 00:50:49.269 benji: Ralph gets a thumbs up. 441 00:50:50.450 --> 00:50:52.369 benji: Offer. Go ahead. 442 00:50:53.270 --> 00:50:56.079 benji: Are you raising your hand? Do you mean to do a thumbs up 443 00:50:57.060 --> 00:51:01.120 Ofer Shaal: exactly on my phone? I meant to do a 444 00:51:01.950 --> 00:51:07.580 benji: and 445 00:51:08.810 --> 00:51:10.710 benji: Shall I leave the comment on this one 446 00:51:14.040 --> 00:51:17.109 benji: or Ralph, do you want to? Since you've already looked at the issue 447 00:51:17.380 --> 00:51:20.850 Ralf Koller: of you? Can? 448 00:51:21.320 --> 00:51:26.250 Ralf Koller: Then I'll take a look at revisiting the issue with 449 00:51:26.960 --> 00:51:29.550 Ralf Koller: talk before the meeting and 450 00:51:30.330 --> 00:51:34.090 Ralf Koller: try to come up. Where? What? The conclusion was there? 451 00:51:34.870 --> 00:51:40.259 benji: Okay, for the sake of the recording. Why don't you just bring that issue up briefly 452 00:51:40.640 --> 00:51:42.629 benji: where it was 453 00:51:43.050 --> 00:51:47.120 Ralf Koller: 1 s too many. It's open 454 00:51:48.350 --> 00:51:58.679 Ralf Koller: for the sake of the recording in the meeting on the fifteenth of September. Issue number 3, 3, 3, 8, 6, 1, 3, 455 00:51:59.790 --> 00:52:01.010 Ralf Koller: 0. 456 00:52:01.470 --> 00:52:17.079 Ralf Koller: We've discussed the following issue, issue, number 2099099. If site is a maintenance mode, omit instruction to put site in maintenance mode in dB update controller or Php. 457 00:52:18.620 --> 00:52:24.919 benji: and at the time we discussed it, but we never left a comment on the issue itself. We'll we'll try to follow up on that 458 00:52:26.280 --> 00:52:29.469 benji: so we have almost 15 min left. 459 00:52:29.760 --> 00:52:35.590 benji: but I don't think any of us have particular issues that were 460 00:52:36.120 --> 00:52:38.080 benji: ready to talk about, do we? 461 00:52:41.870 --> 00:52:49.230 benji: So I'm thinking maybe we should just well, either close the meeting early or 462 00:52:49.590 --> 00:52:56.310 benji: do you want to spend a few minutes talking about what to do next week, or in the next few weeks. 463 00:53:02.290 --> 00:53:04.850 Ralf Koller: There might be one thing 464 00:53:05.960 --> 00:53:13.200 Ralf Koller: already closed my skin. the sharing. But I've noticed. There are 465 00:53:13.990 --> 00:53:22.840 Ralf Koller: 2 issues back from the 10.1 release cycle about moving around the block. 466 00:53:23.670 --> 00:53:34.059 Ralf Koller: And from that meter issue reorganizing block items in the administration items and menu items. There are 2 issues still open 467 00:53:34.470 --> 00:53:36.809 Ralf Koller: and at least one of them 468 00:53:36.940 --> 00:53:43.199 Ralf Koller: could use at least a discussion on further. Input 469 00:53:43.260 --> 00:53:45.320 Ralf Koller: I post the link in the chat 470 00:53:47.700 --> 00:53:48.580 Ralf Koller: adjust 471 00:53:50.110 --> 00:53:51.590 Ralf Koller: ran into it. 472 00:53:51.790 --> 00:54:00.380 Ralf Koller: after we've touched layout to the last week in Tripodo show Austin as well as this week. 473 00:54:01.060 --> 00:54:03.080 Ralf Koller: and that one is 474 00:54:03.200 --> 00:54:05.640 Ralf Koller: still relevant, I suppose. 475 00:54:10.770 --> 00:54:13.579 benji: Okay, so let's see, here's 476 00:54:14.570 --> 00:54:20.540 benji: issue for usability meetings. The first one you mentioned, I think, was reorganizing block items 477 00:54:21.780 --> 00:54:25.740 Ralf Koller: in the Admin menu. That's the 478 00:54:27.760 --> 00:54:29.920 benji: so. This is the net issue 479 00:54:29.990 --> 00:54:33.420 benji: 3318110, 480 00:54:34.740 --> 00:54:38.539 benji: yeah. And and we 481 00:54:40.000 --> 00:54:42.889 benji: II would love to 482 00:54:42.950 --> 00:54:48.960 benji: Get back to that issue. I guess just briefly. 483 00:54:49.650 --> 00:54:52.380 benji: has to do with 484 00:54:52.730 --> 00:54:57.239 benji: links in the Admin menu, and we currently have 485 00:54:57.910 --> 00:55:02.099 benji: block layout directly under structure and 486 00:55:03.480 --> 00:55:06.860 benji: and and this team was 487 00:55:07.960 --> 00:55:10.660 benji: I think, pretty strongly 488 00:55:11.530 --> 00:55:15.750 benji: of the opinion that that should be moved under appearance. 489 00:55:17.570 --> 00:55:20.349 Block layout has to do with themes. 490 00:55:21.180 --> 00:55:26.730 benji: And we were sort of derailed because 491 00:55:27.080 --> 00:55:30.290 benji: There was this this 492 00:55:30.630 --> 00:55:35.119 benji: issue to do, some usability testing and the card sorting exercise 493 00:55:35.450 --> 00:55:37.960 benji: and 494 00:55:38.320 --> 00:55:41.030 benji: fortunately that never looked 495 00:55:41.490 --> 00:55:48.950 benji: led to any specific recommendations, so it got stalled there. So yes, that would be a good thing to talk about. 496 00:55:49.520 --> 00:55:53.040 benji: Then the other thing just gave you this link in the chat. 497 00:55:54.950 --> 00:56:09.350 benji: issue number 3, 3, 3, 1, 8, 5, 5, 8, adjusting block terminology. So so is this 498 00:56:09.360 --> 00:56:12.540 benji: part of the same Meta issue. The apparent issue. 499 00:56:12.770 --> 00:56:13.470 Ralf Koller: Yep. 500 00:56:14.570 --> 00:56:22.370 benji: Oh, and and this is 501 00:56:25.670 --> 00:56:31.299 benji: since since we're we now talked about content blocks rather than custom blocks. 502 00:56:32.320 --> 00:56:38.800 Ofer Shaal: well, time. 503 00:56:40.090 --> 00:56:45.119 benji: we have block types, and then, I guess, under content. We have 504 00:56:46.940 --> 00:56:52.740 benji: blocks, and we refer to these as content blocks, whereas we used to call them custom blocks. 505 00:56:53.140 --> 00:56:57.880 benji: So this issue is to 506 00:56:58.170 --> 00:57:03.390 benji: make the same change in layout builder where the screenshot shows create custom block. 507 00:57:04.760 --> 00:57:14.410 Ralf Koller: yeah. But the problem here is it's in context of layout builder. And there you have also in line blocks and all those Comp 508 00:57:14.940 --> 00:57:16.970 Ralf Koller: concepts 509 00:57:18.110 --> 00:57:22.400 Ralf Koller: collide in that very form. So 510 00:57:22.840 --> 00:57:27.109 Ralf Koller: it's tricky in the in the comments in that issue. 511 00:57:27.380 --> 00:57:31.230 Ralf Koller: I've added the current state and the open questions 512 00:57:31.440 --> 00:57:33.030 Ralf Koller: a few months. It's back. 513 00:57:34.560 --> 00:57:35.310 benji: okay. 514 00:57:35.800 --> 00:57:43.159 Ralf Koller: And although the problem is in that site. But there are also the option to add fields instead of blocks. 515 00:57:44.180 --> 00:57:45.810 Ralf Koller: And yeah, it's 516 00:57:46.040 --> 00:57:46.840 Ralf Koller: tricky. 517 00:57:55.830 --> 00:57:59.900 benji: Okay, so those are definitely good things to talk about 518 00:57:59.970 --> 00:58:01.330 benji: at the next meeting. 519 00:58:01.880 --> 00:58:12.410 benji: And there! There's also ongoing work for 520 00:58:13.190 --> 00:58:15.840 benji: the field, do I? 521 00:58:16.710 --> 00:58:22.499 benji: And I think some of that is getting close to the point where it needs further review. 522 00:58:23.150 --> 00:58:26.019 benji: So those are things we could talk about. 523 00:58:26.790 --> 00:58:35.140 benji: And as as as always, 524 00:58:35.200 --> 00:58:39.250 benji: it's it's best if one of us or or someone else 525 00:58:39.540 --> 00:58:44.919 benji: has look at an issue before bringing up a meeting, because it's 526 00:58:45.120 --> 00:58:46.410 benji: deploys. 527 00:58:47.650 --> 00:58:51.460 benji: sort of sort of wasting time as we try to understand the issue. 528 00:58:51.670 --> 00:59:05.600 benji: so if if any of us has time, let's let's look at some of those issues and and be prepared to talk about the next week, or the or the week after. 529 00:59:06.680 --> 00:59:14.920 benji: anything else you'd like to bring up before closing the meeting 530 00:59:20.640 --> 00:59:21.450 Ralf Koller: from my end. 531 00:59:24.000 --> 00:59:26.629 benji: Okay? Then it's 532 00:59:26.770 --> 00:59:38.659 benji: close meeting just a few minutes early. But I I'm I'm never fan of running out the time on meeting just to follow the schedule. So thanks for coming and I'll be here next week. Hope you can make it. Then. 533 00:59:39.470 --> 00:59:41.990 Ralf Koller: Thanks. Thank you.