{"thread":{"id":"59488","subject":"[GSOC] [PROPOSAL v1] Draft of proposal for \"Unify ref-filter formats with other pretty formats\"","startedAt":"2023-03-28T16:05:53Z","lastAt":"2023-03-29T12:23:42Z","messageCount":2,"participants":["Zhang Yi","Hariom verma"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"474321","messageId":"4cb30507.79cd.18728e9ee58.Coremail.18994118902@163.com","threadId":"59488","inReplyTo":null,"subject":"[GSOC] [PROPOSAL v1] Draft of proposal for \"Unify ref-filter formats with other pretty formats\"","fromName":"Zhang Yi","fromEmail":"18994118902@163.com","sentAt":"2023-03-28T15:50:32Z","receivedAt":"2023-03-28T16:05:53Z","isPatch":false,"sender":{"key":"18994118902@163.com","avatar":"https://avatars.githubusercontent.com/u/48300302?v=4"},"body":"Hi, there is a my first versoin of proposal for \"Unify ref-filter formats with other \npretty formats\". There may be many backwards. I'm ready for the correction.\n\nThanks for your attention.\n\n* Unify ref-filter formats with other pretty formats\n\n* Personal Information\n\nFull name: Zhang Yi\n\nE-mail: 18994118902@163.com\nTel: (+86)18994118902\n\nEducation: Wuhan University of Technology (China)\nMajor: Computer engineering \nYear: First-year postgraduate student\n\nGithub: https://github.com/zhanyi22333\n\n* Synopsis\n\nGit has at least four implements to format command output, which makes chaos and\nhinder improvement of code quality.\n\nAim to unify the different implementations to format output for different\ncommands, we want to transform pretty into ref-filter formatting logic. According\nIn the present situation, I need to add more ref-filter atoms to replace\npretty.\n\nIn my mind, there are 6 steps logically:\n1. Check and find a pretty atom which has no substitute in ref-filter.\n2. Add reasonable test scripts and maybe documents in advance.\n3. Build a ref-filter atom and its arguments to replace a pretty atom.\n4. Make a translation between pretty formats and ref-filter arguments.\n5. Modify the pretty code to ref-filter logic.\n6. Recheck documents and run test scripts.\n\n* Benefits to Community\n\nI'm willing to stay around after the project. By that time, I will be in my\nsecond year without classes. And my tutor has an open mind about my request to\ninvovle in an open source project by now. Consider the subjective and objective\nconditions, I think there is a high possibility that I will stay around.\n\nParticularly, I wish to be a co-mentor if I have the ability. There may be some\ndifficulties. But what I learn from my finite experience is that you should not\nrefuse something positive just because of the difficulties in the mind. The\nfresh new job may be difficult, but it can show me the possibilities of the\nworld, which means change my mind.\n\nWhat's more, I tried to persuade a schoolmate who I think is kind of obsessed\nwith technology to take part in an open source community for both self-growth and\ncompanion. And I failed, because he thinks it is hard.  It's always hard to\nchange Others' deep-rooted ideas by word. But I think the actions speak louder\nthan words. Maybe after the project, I can change the minds of people around me\nabout joining an open source community. There may be no visual benefits to the\ncommunity of git but should be beneficial to the whole open source community.\n\n* Microproject\n\nt9700: modernize test scripts [1]\n\nThe microproject patches have been merged. The merge info is as below:\n\ncommit 8760a2b3c63478e8766b7ff45d798bd1be47f52d\nMerge: a2d2b5229e 509d3f5103\nAuthor: Junio C Hamano <gitster@pobox.com>\nDate:   Tue Feb 28 16:38:47 2023 -0800\n\n    Merge branch 'zy/t9700-style'\n\n    Test style fixes.\n\n    * zy/t9700-style:\n      t9700: modernize test scripts\n\n* Plan\n\n** Deliverables\n\n1. Documents.\n2. Test scripts.\n3. Modified ref-filter.\n   3.1.  New atom and arguments\n   3.2. New functions like foo_atom_parser, grab_foo\n   3.3. modified functions like grab_values and static struct.\n4. Modified pretty which is plugged in by ref-filter.\n\n** Timeline and feasibility\n\nIt seems impossible for me to estimate the time consumed. The idea page [2]\nshows the expected time is between 175 hours and 350 hours. So I checked the\ntimeline of GSOC, It shows that the official code time starts from 05-29 to\n08-28 and can be extended to 11-06. After that I check my class schedule.\nThe conclusion is as below:\n\n1. now~06-05: around 2~3 classes every week. It is easy to cover the time\nproject needs.\n2. 06-05~06-30: There are many classes on workdays. Hope I can take classes with\nflexibility.\n3.  After 06-30: This semester is finished.\n\nI think it is a bit time-limited if I follow the official timeline. It seems\nnecessary to do some work in advance.\n\n* Related work\n\nThe blog by Hariom Verma shows the outline of the work.[3]\n\nThis proposal draft benefits from Nsengiyumva Wilberforce’s recent work [4]\nmuch. Thanks.\n\n* Biograhical information\n\nIt is always funny to recall that I first learned about Linux in a stimulated\nhacker game in my fresh year in college. After that, I tried to teach myself\nLinux and started to know open source projects. Overcome many difficulties and I\nfinally know something shallow about Linux. As a side effect, I am more\nenthusiastic and better at programming compared with my schoolmates. But the\nperiod of stagnation came, I began to write some meaningless projects for school\ntasks and repeated myself without progress. The best out of the worst, I touched\nexcellent open source software during the time, such as vim, emacs, visual\nstudio code, Qt, VLC and, of course, git. Near the end of my junior year, I read\nan article about learning by contributing to an open source project by a geek\nin the community of emacs. Almost at the same time, I knew the GSOC and preferred\nto take part in git. But it was near the start date of my plan for postgraduate\nqualifying examination. So I just postponed the stuff for GSOC.  Luckily, I\npassed the examination. After I got used to life as a postgraduate student, I\nfelt the motivation to progress again. Then I tried to contribute for git. Now I\njust finish a micro project, which seems trivial. But it really let me have a\ndeeper understanding of open source and free software and more motivation to\ncontribute. I hope I can stay a long time here before being involved with other\ninteresting projects since the quality is more important than the quantity.\nI know it seems a bit stubborn to believe that contributing will lead to\nprogress, which is also influenced by my learning attitude. But without action,\nI can not verify the belief.  Sooat least I will try to contribute for one year.\nAfter that, I hope I can have a better understanding.\n\nSorry, the above text may be messing. In short, I will try to contribute for\ngit for at least one year.\n\n* Closing remarks\n\nThanks for Christian Couder's help.\n\n[1] https://lore.kernel.org/git/20230222040745.1511205-1-18994118902@163.com/\n[2] https://git.github.io/SoC-2023-Ideas/\n[3] https://harry-hov.github.io/blogs/posts/the-final-report\n[4] https://lore.kernel.org/git/pull.1452.git.1672102523902.gitgitgadget@gmail.com/\n"},{"id":"474406","messageId":"CA+CkUQ_7BDmX73epbAaUsz3fXaNcHXR4H6xQ-nyGV81YAYRbcQ@mail.gmail.com","threadId":"59488","inReplyTo":"4cb30507.79cd.18728e9ee58.Coremail.18994118902@163.com","subject":"Re: [GSOC] [PROPOSAL v1] Draft of proposal for \"Unify ref-filter formats with other pretty formats\"","fromName":"Hariom verma","fromEmail":"hariom18599@gmail.com","sentAt":"2023-03-29T12:23:24Z","receivedAt":"2023-03-29T12:23:42Z","isPatch":false,"sender":{"key":"hariom18599@gmail.com","avatar":"https://avatars.githubusercontent.com/u/37576387?v=4"},"body":"Hi\n\nOn Tue, Mar 28, 2023 at 9:20 PM Zhang Yi <18994118902@163.com> wrote:\n>\n> Hi, there is a my first versoin of proposal for \"Unify ref-filter formats with other\n> pretty formats\". There may be many backwards. I'm ready for the correction.\n>\n> Thanks for your attention.\n>\n> * Unify ref-filter formats with other pretty formats\n>\n> * Personal Information\n>\n> Full name: Zhang Yi\n>\n> E-mail: 18994118902@163.com\n> Tel: (+86)18994118902\n>\n> Education: Wuhan University of Technology (China)\n> Major: Computer engineering\n> Year: First-year postgraduate student\n>\n> Github: https://github.com/zhanyi22333\n\nOkay.\n\n> * Synopsis\n>\n> Git has at least four implements to format command output, which makes chaos and\n> hinder improvement of code quality.\n>\n> Aim to unify the different implementations to format output for different\n> commands, we want to transform pretty into ref-filter formatting logic. According\n> In the present situation, I need to add more ref-filter atoms to replace\n> pretty.\n>\n> In my mind, there are 6 steps logically:\n> 1. Check and find a pretty atom which has no substitute in ref-filter.\n> 2. Add reasonable test scripts and maybe documents in advance.\n> 3. Build a ref-filter atom and its arguments to replace a pretty atom.\n> 4. Make a translation between pretty formats and ref-filter arguments.\n> 5. Modify the pretty code to ref-filter logic.\n> 6. Recheck documents and run test scripts.\n\nI would like to see more details here. Maybe you can explain every\nstep you mentioned in detail.\nYou can also include how much work has been done and what's left.\n\n> * Benefits to Community\n>\n> I'm willing to stay around after the project. By that time, I will be in my\n> second year without classes. And my tutor has an open mind about my request to\n> invovle in an open source project by now. Consider the subjective and objective\n> conditions, I think there is a high possibility that I will stay around.\n\ns/invovle/involve\ns/Consider/Considering\n\n> Particularly, I wish to be a co-mentor if I have the ability. There may be some\n> difficulties. But what I learn from my finite experience is that you should not\n> refuse something positive just because of the difficulties in the mind. The\n> fresh new job may be difficult, but it can show me the possibilities of the\n> world, which means change my mind.\n>\n> What's more, I tried to persuade a schoolmate who I think is kind of obsessed\n> with technology to take part in an open source community for both self-growth and\n> companion. And I failed, because he thinks it is hard.  It's always hard to\n> change Others' deep-rooted ideas by word. But I think the actions speak louder\n> than words. Maybe after the project, I can change the minds of people around me\n> about joining an open source community. There may be no visual benefits to the\n> community of git but should be beneficial to the whole open source community.\n\ns/community of git/Git Community\n\n> * Microproject\n>\n> t9700: modernize test scripts [1]\n>\n> The microproject patches have been merged. The merge info is as below:\n>\n> commit 8760a2b3c63478e8766b7ff45d798bd1be47f52d\n> Merge: a2d2b5229e 509d3f5103\n> Author: Junio C Hamano <gitster@pobox.com>\n> Date:   Tue Feb 28 16:38:47 2023 -0800\n>\n>     Merge branch 'zy/t9700-style'\n>\n>     Test style fixes.\n>\n>     * zy/t9700-style:\n>       t9700: modernize test scripts\n\nGreat.\n\n> * Plan\n>\n> ** Deliverables\n>\n> 1. Documents.\n> 2. Test scripts.\n> 3. Modified ref-filter.\n>    3.1.  New atom and arguments\n>    3.2. New functions like foo_atom_parser, grab_foo\n>    3.3. modified functions like grab_values and static struct.\n> 4. Modified pretty which is plugged in by ref-filter.\n>\n> ** Timeline and feasibility\n>\n> It seems impossible for me to estimate the time consumed. The idea page [2]\n> shows the expected time is between 175 hours and 350 hours. So I checked the\n> timeline of GSOC, It shows that the official code time starts from 05-29 to\n> 08-28 and can be extended to 11-06. After that I check my class schedule.\n> The conclusion is as below:\n>\n> 1. now~06-05: around 2~3 classes every week. It is easy to cover the time\n> project needs.\n> 2. 06-05~06-30: There are many classes on workdays. Hope I can take classes with\n> flexibility.\n> 3.  After 06-30: This semester is finished.\n>\n> I think it is a bit time-limited if I follow the official timeline. It seems\n> necessary to do some work in advance.\n\nCan you merge \"Deliverables\" and \"Timeline\"?\nPlease make a detailed timeline. It can be weekly or monthly depending on you.\n\n> * Related work\n>\n> The blog by Hariom Verma shows the outline of the work.[3]\n>\n> This proposal draft benefits from Nsengiyumva Wilberforce’s recent work [4]\n> much. Thanks.\n\nMaybe it's a good idea to include what you grasped from related work.\nA brief synopsis?\n\n> * Biograhical information\n>\n> It is always funny to recall that I first learned about Linux in a stimulated\n> hacker game in my fresh year in college. After that, I tried to teach myself\n> Linux and started to know open source projects. Overcome many difficulties and I\n> finally know something shallow about Linux. As a side effect, I am more\n> enthusiastic and better at programming compared with my schoolmates. But the\n> period of stagnation came, I began to write some meaningless projects for school\n> tasks and repeated myself without progress. The best out of the worst, I touched\n> excellent open source software during the time, such as vim, emacs, visual\n> studio code, Qt, VLC and, of course, git. Near the end of my junior year, I read\n> an article about learning by contributing to an open source project by a geek\n> in the community of emacs. Almost at the same time, I knew the GSOC and preferred\n> to take part in git. But it was near the start date of my plan for postgraduate\n> qualifying examination. So I just postponed the stuff for GSOC.  Luckily, I\n> passed the examination. After I got used to life as a postgraduate student, I\n> felt the motivation to progress again. Then I tried to contribute for git. Now I\n> just finish a micro project, which seems trivial. But it really let me have a\n> deeper understanding of open source and free software and more motivation to\n> contribute. I hope I can stay a long time here before being involved with other\n> interesting projects since the quality is more important than the quantity.\n> I know it seems a bit stubborn to believe that contributing will lead to\n> progress, which is also influenced by my learning attitude. But without action,\n> I can not verify the belief.  Sooat least I will try to contribute for one year.\n> After that, I hope I can have a better understanding.\n>\n> Sorry, the above text may be messing. In short, I will try to contribute for\n> git for at least one year.\n>\n> * Closing remarks\n>\n> Thanks for Christian Couder's help.\n>\n> [1] https://lore.kernel.org/git/20230222040745.1511205-1-18994118902@163.com/\n> [2] https://git.github.io/SoC-2023-Ideas/\n> [3] https://harry-hov.github.io/blogs/posts/the-final-report\n> [4] https://lore.kernel.org/git/pull.1452.git.1672102523902.gitgitgadget@gmail.com/\n\nThank you for your proposal. I left a few comments.\n\nRegards,\nHariom\n"}]}