12:57:34 RRSAgent has joined #wot-td 12:57:38 logging to https://www.w3.org/2024/04/04-wot-td-irc 12:57:44 meeting: WoT-WG - TD-TF Slot 2 13:00:17 JKRhb has joined #wot-td 13:01:10 Tomo has joined #wot-td 13:01:34 Ege has joined #wot-td 13:01:55 ktoumura has joined #wot-td 13:02:15 present+ Kaz_Ashimura, Ege_Korkan, Luca_Barbato, Kunihiko_Toumura, Michael_Koster 13:02:16 chair: Ege, Koster 13:02:18 mahda has joined #wot-td 13:02:59 JKRhb has joined #wot-td 13:03:26 present+ Mahda_Noura 13:03:40 present+ Daniel_Peintner 13:05:05 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#April_3_and_4%2C_2024 13:05:18 present+ Tomoaki_Mizushima, Cristiano_Aguzzi 13:05:25 rrsagent, make log public 13:05:31 rrsagent, draft minutes 13:05:33 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:05:58 dape has joined #wot-td 13:06:24 scribe: dape 13:06:43 TOPIC: Minutes 13:06:58 mjk has joined #wot-td 13:06:59 https://www.w3.org/2024/03/28-wot-td-minutes.html 13:07:05 -> March 28 -> https://www.w3.org/2024/03/28-wot-td-minutes.html 13:07:37 EK: No objections -> minutes approved 13:07:53 TOPIC: Organizational 13:08:03 SUBTOPIC: TTWG registry analysis 13:08:12 EK: see https://github.com/w3c/wot/issues/1188 13:08:28 mm has joined #wot-td 13:08:28 ... ask for volunteer 13:08:59 ... M.Koster and I can deal with it 13:09:03 present+ Michael_McCool 13:09:04 rrsagent, draft minutes 13:09:05 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:09:14 TOPIC: Resource Management 13:09:53 q+ 13:09:55 EK: see https://github.com/w3c/wot-thing-description/pull/1969 13:10:07 q- 13:10:10 https://github.com/w3c/wot-thing-description/blob/egekorkan-patch-1/VERSIONING.md 13:10:29 (ntd in 30m hopefully we can get through the versioning by then) 13:10:40 EK: we want to agree on part "until REC release" 13:10:40 JKRhb has joined #wot-td 13:10:42 q+ 13:10:44 ... 2 open points 13:10:52 s/TOPIC: Organizational// 13:10:57 ... moreover, we should look at "changelog" section 13:11:07 q? 13:11:33 i/TOPIC: Minutes/topic: Organizational/ 13:11:42 MMC: proposal for date vs sequence number 13:11:47 s/TOPIC: Minutes/subtopic: Minutes/ 13:11:52 ... propose to do both 13:11:53 rrsagent, draft minutes 13:11:54 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:12:16 ... normally we just have 1 number.. but helps in case of PlugFests 13:12:52 MMC: number starts every day ... but normally it is just one 13:13:14 +1 for . separator 13:13:55 EK: Number for flexibility reason 13:14:00 q+ 13:14:19 ... other reason is communication with other human 13:14:21 JKRhb has joined #wot-td 13:14:26 q? 13:14:28 ack m 13:14:30 ack mm 13:14:40 q+ 13:15:03 Kaz: The content is fine and reasonable.. anyhow.. description seems complicated 13:15:16 ... we might want to fix the prose 13:15:57 EK: I see 13:16:17 q- 13:16:21 CA: I am ok with current format 13:16:50 ... should the "-1" always be there.. even if there is just one release 13:16:54 rrsagent, draft minutes 13:16:55 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:17:01 MMC: Yes 13:17:26 EK: Cristiano, what do you prefer? 13:17:46 q+ 13:17:51 q+ 13:17:53 CA: using "date" might be better.. even though it is longer 13:18:16 ... just number is okay also 13:18:30 ack cr 13:18:31 LB: fine with approach 13:18:45 ... propose to have many releases 13:19:24 ... as separator I prefer dot over dash 13:19:52 ... btw, date can be tuned by adding hour etc 13:19:56 q+ 13:20:22 q+ 13:20:47 LB: time reference in version is nice to reason 13:21:09 ... adding sequence number is similar to adding hour 13:21:42 (kaz, can I jump the q?) 13:22:17 date, "-", i/proposal for/[[ number, e.g., "2.0.0-pre20240301-1+td-2.0.0-pre20240301-1" (posibly use "." instead of "-") ]]/ 13:22:18 q? 13:22:24 ack l 13:22:26 ... alternative to use portions only if needed 13:22:26 qq+ mm 13:22:37 q- mm 13:22:41 q- mm 13:22:42 MMC: I prefer day granularity 13:23:02 ... sequence number is better than hour ... during TestFests etc 13:23:22 i/proposal for/[[ date, "-", number, e.g., "2.0.0-pre20240301-1+td-2.0.0-pre20240301-1" (posibly use "." instead of "-") ]]/ 13:23:28 rrsagent, draft minutes 13:23:29 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:23:35 ... i still prefer dayDate + secuenceNr 13:23:36 q? 13:23:40 ack mm 13:23:47 s/secuenceNr/sequenceNr 13:23:56 +1 for `.` 13:24:00 Kaz: Discussion is important and delicate 13:24:18 ... should minute the proposal 13:24:26 (again, I have to leave soon also...) 13:24:43 date,.,number, i.e. 2.0.0-pre20240301.1+td-2.0.0-pre20240301.1 13:24:59 (really three main propsals: date (day granuaritly), sequence number, or both) 13:25:08 q? 13:25:13 q+ 13:25:25 q- 13:25:28 ack d 13:25:44 i|proposal for date|@@@ first example notation here!| 13:25:55 DP: prefer well defined format.. not adding portions when needed only 13:26:05 q? 13:26:08 q+ 13:26:13 ack m 13:26:16 MMC: prefer mixed format 13:26:54 EK: Is everybody fine with the following format? 13:27:17 +1 for not changing granularity - fixed day granularity to keep things simple. 13:27:22 simplish 13:27:27 q+ 13:27:44 ack k 13:27:59 q? 13:28:05 ack luca_barbato 13:28:08 kaz: I'm OK with the updated notation, but we should document @@ 13:28:17 LB: fine with current proposal.. seems simpler.. 13:28:25 ... there is enough agreement 13:28:58 ... w.r.t. changelog ... we can generate it from commits 13:29:06 q+ +1 for conventional commit 13:29:18 s/@@/what "-" and "." mean here, e.g., "-" to show the separation of module and "." to show the separation within each module./ 13:29:20 ack l 13:29:37 q+ cris1 13:29:40 q- +1 13:29:59 ack cris1 13:30:09 q+ dape 13:30:21 q- dape 13:30:41 present+ Jan_Romann 13:30:46 dape has joined #wot-td 13:31:24 s/of module/of modules/ 13:31:25 proposal: using the following in pre REC release for the version number of all resources(semver for resource)-pre(date with day).(sequence number)+(spec version)-pre(date with day).(sequence number) 13:31:51 RESOLUTION: using the following in pre REC release for the version number of all resources: (semver for resource)-pre(date with day).(sequence number)+(spec version)-pre(date with day).(sequence number) 13:32:42 EK: Perfect, will update PR accordingly 13:32:45 q+ 13:33:18 Kaz: Minor: does the bottom section say discussion.. or should we rather delete that part 13:33:26 ... at least for the final version 13:33:32 EK: Yes, will remove it later on 13:33:54 q- 13:33:59 q? 13:34:35 EK: What about the regular releases? 13:34:42 ... monthly or when needed? 13:34:53 MMC: Whenever needed? 13:35:01 rrsagent, draft minutes 13:35:02 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:35:08 s/Whenever needed?/Whenever needed 13:35:53 MMC: micro PRs should not create releases 13:36:00 q+ 13:36:05 q+ 13:36:10 i|proposal for dat vs|subtopic: Open point 1: Decide whether we want a simple integer or a date after the pre| 13:36:26 q+ 13:36:29 DP: Agree, whenever needed makes sense 13:36:29 ack d 13:36:42 q+ 13:37:07 LB: As long we have the machinery ready ... it is fine to create artifacts when needed 13:37:22 i|What about the|subtopic: Open point 2: Whenever needed or monthly| 13:37:46 rrsagent, draft minutes 13:37:47 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:37:53 ... anyhow, does not provide regularity 13:38:17 q? 13:38:18 q? 13:38:21 ack l 13:38:50 Kaz: Minor comment: "title open point 2" should not be changed today 13:39:28 Kaz: General: we should record all changes 13:39:43 q? 13:39:57 q- 13:40:01 dape has joined #wot-td 13:40:15 Kaz: ... need mechanism to track all the changes 13:40:29 (ntd, for real now - but I trust you guys to decide something reasonable, will follow your lead) 13:40:57 Kaz: Small PRs are fine 13:41:11 EK: Any objection to work with commits and PRs? 13:42:28 LB: branches is working area.. merge commit is the actual change (log) 13:42:43 q? 13:43:08 .. for changelog we need merge or squash commits 13:43:41 s/is working area/are working areas/ 13:45:08 i|proposal for date vs|subtopic: Open point 1: Decide whether we want a simple integer or a date after the pre| 13:45:09 dape8 has joined #wot-td 13:45:13 EK: agree to use conv. commit messages 13:45:17 rrsagent, draft minutes 13:45:18 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:45:24 q? 13:45:24 ack c 13:46:12 CA: +1 for current proposal to release as often as possible 13:46:46 proposal: We should consider a release after a resource-targeting PR but we can skip some if see the need 13:47:17 +1 13:47:18 proposal: We should consider a release after a resource-targeting PR but we can skip some if we see the need 13:47:28 mjk has joined #wot-td 13:47:46 q+ 13:47:59 q? 13:48:08 ack k 13:48:26 resolution: We should consider a release after a resource-targeting PR but we can skip some if we see the need 13:48:38 i/agree to/scribenick: dape8/ 13:48:41 rrsagent, draft minutes 13:48:42 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:49:17 q+ 13:49:24 EK: 13:49:40 Kaz: Need to clarify the expectations 13:49:45 ... not today 13:49:48 EK: Agree 13:49:48 q- 13:49:58 s/expectations/exceptions 13:50:02 s/not today/not today, though/ 13:50:19 EK: I would go to "changelog" dicussion 13:50:29 ... we talked about it already a bit 13:50:34 q? 13:50:58 ... in discovery TF changelog is used already 13:51:26 EK: First question: Where is the changelog? 13:51:49 .. outside html or Markdown 13:51:49 q+ 13:52:02 ... not sure about tooling 13:52:05 q? 13:52:36 EK: other point. Should it be relative difference ? 13:52:49 ... diff to previous release ? 13:53:11 ... w.r.t. automation ... we should give it a try 13:54:01 ktoumura has joined #wot-td 13:54:01 CA: scope in conventional comment might help 13:54:22 JKRhb has joined #wot-td 13:54:22 ... I used that in the past and it worked 13:55:14 ... about auto-changes ... tool can be instructed to do the diff/changelog based on last official release 13:55:44 CA: conventional commit is useful .. but sometimes the "type" of change is not easy... 13:55:51 q+ 13:56:16 ack cris1 13:56:17 rrsagent, draft minutes 13:56:18 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:56:24 ack cris 13:56:48 i|I would go to "|subtopic: Changelog| 13:56:50 rrsagent, draft minutes 13:56:51 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 13:57:21 EK: one commit message for a multiple set of changes in different resources 13:57:37 q+ 13:57:44 CA: doing separate commits does not make sense 13:57:47 q? 13:58:20 ack lu 13:58:44 LB: If we generate different changelog for each artifact ... 13:59:16 ... we do not work on software commits 13:59:23 ... we do not work on software commits 13:59:25 dsadas 13:59:44 mjk has joined #wot-td 13:59:46 s/... we do not work on software commits// 14:00:03 dape has joined #wot-td 14:00:07 s/dsadas// 14:00:43 q? 14:02:49 Kaz: We should continue the discussion since we are out of time 14:03:03 ... we also need to think why we need changelog 14:03:11 ... for external developers? 14:03:48 s/discussion since/discussion next time since/ 14:05:06 s/for external developers?/basically, we'd like to provide information to external developers so that they can tell what was changed when./ 14:05:41 s/out of time/out of time. However, let's record important point as "Open points" on the VERSIONING.md./ 14:06:01 s/when./when. We need to consider that when we continue the discussion./ 14:06:28 [[ 14:06:34 Open points on Changelogs: 14:06:36 Guideline for commit messages 14:06:37 Should there be one changelog file or per resource? 14:06:37 Clarify the goal of the changelog. For now, it is 14:06:45 s/Guide/* Guide/ 14:06:54 s/Should/* Should/ 14:07:02 s/Clari/* Clari/ 14:07:05 [adjourned] 14:07:14 i/adj/]]/ 14:07:19 rrsagent, draft miutes 14:07:19 I'm logging. I don't understand 'draft miutes', kaz. Try /msg RRSAgent help 14:07:31 s/rrsagent, draft miutes// 14:07:35 rrsagent, draft minutes 14:07:36 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 14:07:56 i/We should/scribenick: dape/ 14:07:58 rrsagent, draft minutes 14:07:59 I have made the request to generate https://www.w3.org/2024/04/04-wot-td-minutes.html kaz 14:19:29 JKRhb has joined #wot-td 14:30:01 JKRhb has joined #wot-td 15:22:49 JKRhb has joined #wot-td 15:57:07 JKRhb has joined #wot-td 16:06:23 JKRhb has joined #wot-td 16:21:44 JKRhb has joined #wot-td 16:22:35 Zakim has left #wot-td 17:22:46 JKRhb has joined #wot-td 17:23:34 JKRhb has joined #wot-td 17:30:58 JKRhb has joined #wot-td