WEBVTT 00:00.000 --> 00:12.400 Hi everyone, and welcome to HKML, a tool for working on made-in list-driven project without 00:12.400 --> 00:21.000 subscribing from Sing Some Yai, okay SJ, please welcome. 00:21.000 --> 00:27.680 Thanks for the introduction, and thanks for coming to my talk. 00:27.680 --> 00:33.880 So today I want to talk about a tool for working with made-in-list-based development project 00:33.880 --> 00:39.200 without subscribing to the mailing list and get support by explosive amount of mates. 00:39.200 --> 00:44.800 So first start of the mailing history development, so the mailing list development is a 00:44.800 --> 00:50.440 development model that many of the open source projects are using instead of GitHub, 00:50.440 --> 00:58.460 by communicating everything here, playing text mates, using the CCM, some public mailing 00:58.460 --> 01:04.460 list, so that anyone that imbered in and having interest can also be participate to the 01:04.460 --> 01:05.460 development. 01:05.460 --> 01:10.040 So we do patches of missions and patch reviews and reporting issues and discussions, 01:10.040 --> 01:13.200 whatever, or on the mailing list. 01:13.200 --> 01:18.160 The links corner which is one of the biggest open source projects of the world is also 01:18.160 --> 01:24.720 using this approach, and there are some arguments about this model that is some people 01:24.720 --> 01:29.760 really like that because it is very flexible and also decentralized. 01:29.760 --> 01:38.240 Meanwhile some people really hate that because it is not having a good UI and also by using 01:38.240 --> 01:43.480 that people usually get explosive amount of mates from the mailing list, of course it 01:43.480 --> 01:49.920 will depend on the popularity of the project but in case of links corner, this is some big 01:49.920 --> 01:50.920 problem. 01:50.920 --> 01:58.720 And also nowadays young generations like me, more familiar with Gmail, like Cloud E-Mex, 01:58.720 --> 02:04.560 and those are not very optimized for this kind of usage mainly because they don't have 02:04.560 --> 02:12.080 to fix with font side and for reading the patch if not that good. 02:12.080 --> 02:20.240 And also usually people use some self-email setup for this model model, but self-email setup 02:20.240 --> 02:25.560 is some kind of loss technology to young generations and also anyway the email clients 02:25.560 --> 02:28.560 work that developed for this purpose. 02:28.560 --> 02:33.840 And then there was an invention of a great tool called public inbox. 02:33.840 --> 02:40.720 It is an implementation of sharing of emails, inbox that not privately but in publicly 02:40.720 --> 02:42.440 and using it. 02:42.440 --> 02:48.720 It used to save and share all the emails of the mailing list and it provides a modern 02:48.720 --> 02:54.700 web UI and a tool for searching specific emails that are important to the mail to specific 02:54.700 --> 02:56.760 mailing list, called name. 02:56.760 --> 03:01.760 And the list corner is also using the public inbox you can see every mail to pet links 03:01.760 --> 03:08.280 corner community from Lorda.org and for it has multiple email developers to unsubscribe 03:08.280 --> 03:13.800 the mailing list and get no loss of by the explosive amount of mail. 03:13.800 --> 03:22.760 And most common usage is using web UI for reading the mail or using layout to search and import 03:22.760 --> 03:29.520 emails of the interest into the email client that supports the inbox and then reading 03:29.520 --> 03:35.600 it from the email clients or sending it to the email clients like Mod. 03:35.600 --> 03:43.560 And also because the mail client is not very optimized for this kind of workflow, there 03:43.560 --> 03:49.160 is another tool called before which is also integrated with public inbox and providing 03:49.160 --> 03:54.600 very convenient ways to collect batch batch batches and sending batches. 03:54.600 --> 04:00.000 Nevertheless, still some people feel not that comfy with the combination of the tools and 04:00.000 --> 04:06.400 I thought that a wider capital single tool that using public inbox and just was because 04:06.400 --> 04:12.120 I thought that not just one tool is better than running more than one tool because in case 04:12.120 --> 04:21.120 of lay plus mod plus before case people the new commercial run of three tools together 04:21.120 --> 04:26.120 but if we can be just that to one it would be good I believe. 04:26.120 --> 04:30.240 And therefore I have started hacking of HKVM. 04:30.240 --> 04:35.480 This is a tool that developed for public mailing is best development which aims to just 04:35.480 --> 04:42.040 work with very, very minimum preparations, specifically it requires you to set it first. 04:42.040 --> 04:43.640 That's all. 04:43.640 --> 04:49.000 And it is optimized for public inbox usage and also especially for Linux corner because 04:49.000 --> 04:53.480 I'm working for Linux corner, maintaining Daemon subsystem. 04:53.480 --> 04:59.440 And also it is officially committed to support the Daemon and Linux corner developer. 04:59.440 --> 05:04.600 It is committed to support at least Daemon developers, because I'm maintaining Daemon and 05:04.600 --> 05:10.560 I want to help Daemon contributors that is my self support of this project. 05:10.560 --> 05:16.240 So how to install this, installing is very simple, you can just clone it and that's all. 05:16.240 --> 05:35.240 If you want to do this for only Linux corner, let me show you. 05:35.240 --> 06:04.920 You can clone, oh, why are you asking, oh, yeah, okay, okay, okay, I have prepared 06:04.920 --> 06:15.480 so much, oh, yeah, this is all that needed to install that for if you want to use that for 06:15.480 --> 06:20.120 only Linux corner and if you want to use that for different projects, you need some setup but 06:20.120 --> 06:22.800 you can get it from it me. 06:22.800 --> 06:30.640 And to write a new mail, it is very simple, just hkmail right, then it will, if, if people 06:30.680 --> 06:36.320 this is the first time, it also asked me some questions but you can just say yes if you want 06:36.320 --> 06:43.320 to do this only for Linux and then it asked me what text editor I want to use to write 06:43.320 --> 07:02.720 the mail and then it gives me the editor and I can edit the tool to say my personal email 07:02.720 --> 07:23.880 right, whatever, whatever, okay, and then just write it and if it is then it will ask some 07:23.880 --> 07:28.640 basic questions and will I want to send this mail. 07:28.640 --> 07:36.240 Then it also asked me if I want to tag this mail as a sent, of course I will, then that's 07:36.240 --> 07:37.240 all. 07:37.240 --> 07:44.080 So this is how to write mail on hkmail, I can also show you if the mail was successfully 07:44.080 --> 07:50.080 sent or not on my private inbox but I don't want to show that so please just try 07:50.080 --> 07:52.800 that on your own and then check that. 07:52.800 --> 08:03.840 And how we can read mail, it is again very easy, hkmail list for example, if we want to 08:03.840 --> 08:10.240 get mail for demo mail list, you can just put very nice next here. 08:10.240 --> 08:17.880 Then it will fetch the mail from the gate of the public inbox and then show you the list 08:17.880 --> 08:21.120 of the mail on the mailing list in this way. 08:21.120 --> 08:27.800 And here almost everything should be available here for every general mail works. 08:27.800 --> 08:33.800 You can press catch a mark to get some help about key bindings that's supporting here, 08:33.800 --> 08:39.800 some kind of beam-like key binding for scrolling is supported and also searching and most 08:39.800 --> 08:47.320 important keys are Q which creates the product screen and M for open value. 08:47.320 --> 08:53.640 From here, you can focus on specific mail and then press M to get context menu about what 08:53.640 --> 08:55.200 we can do about this mail. 08:55.200 --> 09:07.000 You can open the mail and read the context or list the complete thread of the mail at this. 09:07.000 --> 09:16.520 Or you can also reply or forward, for example, if you can reply the mail like using the 09:16.520 --> 09:23.520 interface that very similar to what we have used for writing the mail. 09:23.520 --> 09:26.920 Of course, I'll send this mail. 09:26.920 --> 09:33.760 So yeah, that's what you can do with the basically with the mail and also one of the 09:33.760 --> 09:41.640 important menu on the list is supporting the list, most of the list as on MB files. 09:41.640 --> 09:45.800 If you have some other MB files supporting email clients and if you want to use that, 09:45.800 --> 09:47.200 you can also use that. 09:47.200 --> 09:53.040 Or if you have some problems at getting the mail from the public inbox, you can export 09:53.040 --> 10:01.840 the mail that sends to maybe your private inbox to MB files and then import that on HTML. 10:01.840 --> 10:06.320 You can do the important OK. 10:06.320 --> 10:14.160 You can do the important by HTML list with MB files. 10:14.160 --> 10:21.320 And also, so basic email work can be done in that way and also how to organize the 10:21.320 --> 10:22.320 mail. 10:22.320 --> 10:32.000 If you can add arbitrary text to your specific mail, this is a timer, then I can show it 10:32.000 --> 10:33.480 from my site. 10:33.480 --> 10:39.280 So you can add any arbitrary text as we have shown that the tool is automatically adding 10:39.280 --> 10:41.760 a sent tag on there. 10:41.760 --> 10:52.800 And you can also list, you can also list, you can also list, you can also list, you can also 10:52.800 --> 11:02.680 list your current setup and also list names of specific tag using HTML list. 11:02.680 --> 11:07.760 So these are some best that I have tagged as interesting because I want to list those 11:07.760 --> 11:08.760 later. 11:08.760 --> 11:16.640 And also, you can backup and restore the personal information, including the tag information 11:16.640 --> 11:19.160 as to your personal gift report. 11:19.160 --> 11:24.320 You can set up your personal gift report anywhere on GitHub or GitHub or your personal system 11:24.320 --> 11:27.440 and then do think like this. 11:27.440 --> 11:34.520 For example, you can just, if you could HTML think to think any information that you 11:34.520 --> 11:36.680 have made. 11:36.680 --> 11:43.960 And also, this tool is very optimized for patches based mailing list based workflow, 11:43.960 --> 11:48.960 which means that it helps you formatting and sending patches. 11:48.960 --> 11:59.760 For example, if you are working on Linux and if you have some this kind of changes made 11:59.760 --> 12:12.960 on your own, then you can use HTML patch format, like very similar to that of git form 12:12.960 --> 12:20.760 patch to generate patch files, then this tool will generate the patch files of the 12:20.760 --> 12:26.920 comment, like git form a patch dodge, but it further to check the git maintainer that 12:26.920 --> 12:27.920 here file. 12:27.920 --> 12:34.960 If it exists, it runs it and find the recipient for each of the patch files using the script 12:34.960 --> 12:40.960 and then add the recipient for each of the patch that is suggested by the git maintainer 12:40.960 --> 12:45.200 pf script on cc list. 12:45.200 --> 12:52.400 This is actually useful mainly because in some case, we need to write patch files patch 12:52.400 --> 12:58.520 series that end to be merged in different subsystems, for example, for three wide clean-up 12:58.520 --> 13:03.480 I need to touch some files for memory management subsystem, but also touch some files for 13:03.480 --> 13:06.600 documentation or arch directory. 13:06.600 --> 13:11.880 And for that, each of the patch files, different disciplines are recommended. 13:11.880 --> 13:14.920 And in such a case, we have two options. 13:14.920 --> 13:20.760 One option is to ccabulate people on every patch files. 13:20.760 --> 13:28.200 The other option is cc only require these options to each patch files, but cc everyone 13:28.200 --> 13:34.920 on the covaluctor may, so that people can have minimum amount of maps on their inbox 13:34.920 --> 13:41.200 and get less annoyed to patch some later and get some more kind review. 13:41.200 --> 13:49.000 And in these two further halves, filling of the covaluctor using some text file, we'll 13:49.080 --> 13:59.000 specify the format here, covaluctor proposed commit, which can also be made using HTML touch command. 13:59.800 --> 14:05.960 And then if it all looks good, it further finds if there is check patch.pl file and then 14:05.960 --> 14:13.800 run it to find any problems that I have made in the patch files that I can quite quickly. 14:13.800 --> 14:27.160 And then if it all looks good, then it further, it further helps the sender reviews the 14:27.160 --> 14:33.480 least few points of each of the patch files, so that there is no more mistakes. 14:33.640 --> 14:47.000 And then, finally, it gives us the last chance to modify and further it as if I want to 14:47.000 --> 14:52.600 just send the patch if as of may or whatnot. Yeah, we have only 26 seconds. 14:53.320 --> 14:57.720 And finally, you can also use this tool to collect the patch files. 14:58.680 --> 15:08.920 Let's see the demo list. And for example, for this patch from the menu, we have handled 15:08.920 --> 15:16.200 edge patches. From here, we can check patch to run check patch.pl file for each of the patches 15:16.200 --> 15:24.520 or apply the patch and save edge patch files so that you can read it. So in summary, the 15:24.520 --> 15:29.960 very distributed development was an HTML is a tool for helping this mother. And it is 15:29.960 --> 15:36.840 probably committed to support the demo while you have cornered at least. That's it. Thank you.