{"thread":{"id":"60312","subject":"How To Pick And Work On A Microproject","startedAt":"2023-10-05T22:18:35Z","lastAt":"2023-10-06T19:03:33Z","messageCount":4,"participants":["Naomi Ibe","Junio C Hamano","Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"482727","messageId":"CACS=G2z84_-WkWa-BnK8bNNqb9z_o37BC3-kb_NkrjzAL=r4Sg@mail.gmail.com","threadId":"60312","inReplyTo":null,"subject":"How To Pick And Work On A Microproject","fromName":"Naomi Ibe","fromEmail":"naomi.ibeh69@gmail.com","sentAt":"2023-10-05T22:14:50Z","receivedAt":"2023-10-05T22:18:35Z","isPatch":false,"sender":{"key":"naomi.ibeh69@gmail.com","avatar":"https://avatars.githubusercontent.com/u/104323769?v=4"},"body":"I have gone through this link\nhttps://git.github.io/General-Microproject-Information/ and I am not\nreally clear with it especially this line\n\"Select a microproject and check that it has not yet been taken or\ndiscussed by searching the mailing list. Public Inbox is your friend.\"\n On the mailing list I see messages with the [PATCH] keyword in front\nof them, am I expected to pick one and reply to it? How do I reply\ndirectly under the thread which contains the issue? Please, how do I\nfind the issue on the Git repository? I checked the repo and could not\nfind the \"issues\" section also .\nPlease HELP!!! Any explanations would be very much appreciated, as I\nwould prefer to start working on it as early as possible.\nThank you.\n"},{"id":"482729","messageId":"xmqq7co0elnt.fsf@gitster.g","threadId":"60312","inReplyTo":"CACS=G2z84_-WkWa-BnK8bNNqb9z_o37BC3-kb_NkrjzAL=r4Sg@mail.gmail.com","subject":"Re: How To Pick And Work On A Microproject","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-10-05T22:42:30Z","receivedAt":"2023-10-05T22:42:37Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Naomi Ibe writes:\n\n> \"Select a microproject and check that it has not yet been taken or\n> discussed by searching the mailing list. Public Inbox is your friend.\"\n\nYeah, that is VERY unfriendly. There is no mention on the pool of\nmicroproject ideas from which you can \"select\" here. I wonder if\nsome HTML link is missing in the sentence (i.e., clicking a word\nleading to a page that lists what you can select from), or it has\nalways been like this.\n\nLater in the same document, I see\n\n How to find other ideas for microprojects\n\n First check the specific page(s) or information about Git\n microprojects related to your program that should have been\n published on this site or on the GSoC or Outreachy site. But then\n still read on everything below!\n\nwhich is much more realistic, as long as the \"specific page(s)\" are\nwell curated (which I have no idea myself, as I have never been in\nthe mentoring pool). Naomi, have you checked and found such a page\non Outreachy site?\n\nThen it goes on to suggest finding a bug report, but I tend to think\nthat fixing them is way oversized to be a good microproject.\n\n\nAnd finally it gives a casual mention of good+first+issue, which is\nprobably the closest to what _should_ be listed as the first place\nto try (sorry, I however do not know how well the list is curated,\neither, but from a cursory look it looks legit).\n\nhttps://github.com/gitgitgadget/git/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22\n\nThere also is a mention of #leftoverbits in the document, but by its\nnature, they can easily become stale or irrelevant, and they tend to\nbe more real issues, and I would expect them to be unnecessarily\nharder than what dip-your-toe-in-the-water-and-say-hello\nmicroprojects need to be.\n"},{"id":"482737","messageId":"CAP8UFD1cd5YZqAxYbYUMNkAYJLLGjBpNe_NK5nVq3eLxxSDzEQ@mail.gmail.com","threadId":"60312","inReplyTo":"xmqq7co0elnt.fsf@gitster.g","subject":"Re: How To Pick And Work On A Microproject","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2023-10-06T09:02:01Z","receivedAt":"2023-10-06T09:02:19Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Fri, Oct 6, 2023 at 12:42 AM Junio C Hamano wrote:\n>\n> Naomi Ibe writes:\n>\n> > \"Select a microproject and check that it has not yet been taken or\n> > discussed by searching the mailing list. Public Inbox is your friend.\"\n>\n> Yeah, that is VERY unfriendly. There is no mention on the pool of\n> microproject ideas from which you can \"select\" here. I wonder if\n> some HTML link is missing in the sentence (i.e., clicking a word\n> leading to a page that lists what you can select from), or it has\n> always been like this.\n\nThis sentence has been like that for a long time. I have just improved\nit to the following:\n\n\"* Select a microproject and check that it has not yet been taken or\n discussed by searching the mailing list. Please read all the\n sections below related to finding or selecting a microproject.\"\n\nI have also made it clearer that the list these sentences are in is a\n\"Summary of the steps needed to complete a microproject\" by adding a\nsection with that title.\n\n> Later in the same document, I see\n>\n> How to find other ideas for microprojects\n>\n> First check the specific page(s) or information about Git\n> microprojects related to your program that should have been\n> published on this site or on the GSoC or Outreachy site. But then\n> still read on everything below!\n>\n> which is much more realistic, as long as the \"specific page(s)\" are\n> well curated (which I have no idea myself, as I have never been in\n> the mentoring pool). Naomi, have you checked and found such a page\n> on Outreachy site?\n\nThere is no such page as I haven't taken the time to write one. But I\nhave added the following paragraph just below the above one:\n\n\"It’s also possible that we haven’t taken the time to put up a page\nlisting microprojects ideas for your program. The pages we used to\ncreate for that were named “XXXX Applicant Microprojects” where XXXX\nis the program name and a date, for example “SoC 2016 Applicant\nMicroprojects” for the GSoC in 2016, or “Outreachy Winter 2021-2022\nApplicant Microprojects” for Outreachy in 2021-2022. See the following\ndirectory to find these old pages that might still be useful:\n\nhttps://git.github.io/Historical-SoC-Outreachy/\"\n\nI am not sure how others feel about this, but I think it would be\nbetter in the future to not have to prepare such pages, and to just\nhave a section with a number of examples of good microprojects on this\nhttps://git.github.io/General-Microproject-Information/ page. It will\nbe easier to update this section when we know about other good ideas\nor better ideas, or when we want to remove an idea that we don't\nconsider good anymore, or just update an idea.\n\n> Then it goes on to suggest finding a bug report, but I tend to think\n> that fixing them is way oversized to be a good microproject.\n\nI agree that it's oversized for most bugs. I have just added the\nfollowing paragraph at the end of this \"Searching for bug reports\"\nsubsection:\n\n\"Also some bugs are difficult to understand and require too much or\ntoo difficult work for a microproject, so don’t spend too much time on\nthem if it appears that they might not be simple to fix, and don’t\nhesitate to ask on the mailing list if they are a good microproject.\"\n\n> And finally it gives a casual mention of good+first+issue, which is\n> probably the closest to what _should_ be listed as the first place\n> to try (sorry, I however do not know how well the list is curated,\n> either, but from a cursory look it looks legit).\n>\n> https://github.com/gitgitgadget/git/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22\n>\n> There also is a mention of #leftoverbits in the document, but by its\n> nature, they can easily become stale or irrelevant, and they tend to\n> be more real issues, and I would expect them to be unnecessarily\n> harder than what dip-your-toe-in-the-water-and-say-hello\n> microprojects need to be.\n\nI have just added the following at the end of the subsection about\n#leftoverbits:\n\n\"As for bugs, and many things really, you can also ask if you are not\nsure it's simple enough to fix.\"\n\nThanks for reviewing the doc!\n"},{"id":"482759","messageId":"xmqq1qe7a806.fsf@gitster.g","threadId":"60312","inReplyTo":"CAP8UFD1cd5YZqAxYbYUMNkAYJLLGjBpNe_NK5nVq3eLxxSDzEQ@mail.gmail.com","subject":"Re: How To Pick And Work On A Microproject","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-10-06T19:03:21Z","receivedAt":"2023-10-06T19:03:33Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Christian Couder writes:\n\n> I am not sure how others feel about this, but I think it would be\n> better in the future to not have to prepare such pages, and to just\n> have a section with a number of examples of good microprojects on this\n> https://git.github.io/General-Microproject-Information/ page. It will\n> be easier to update this section when we know about other good ideas\n> or better ideas, or when we want to remove an idea that we don't\n> consider good anymore, or just update an idea.\n\nIf we have curated one-stop shop for microproject candidates to make\nit easy to find them, it would be a vast improvement over the status\nquo. The easier for us to update the contents of the list, the\nbetter for participants. Having only one place that we need to look\nat is one way to do so, and the general microproject information\npage would be the best place to host it. I like it.\n\n>> Then it goes on to suggest finding a bug report, but I tend to think\n>> that fixing them is way oversized to be a good microproject.\n>\n> I agree that it's oversized for most bugs. I have just added the\n> following paragraph at the end of this \"Searching for bug reports\"\n> subsection:\n>\n> \"Also some bugs are difficult to understand and require too much or\n> too difficult work for a microproject, so don’t spend too much time on\n> them if it appears that they might not be simple to fix, and don’t\n> hesitate to ask on the mailing list if they are a good microproject.\"\n\nWould that be better, or would it be simpler to gut the whole\nparagraph about bug reports? This is \"how to pick a microproject\",\nnot \"how to pick your main project to work on during your mentoring\nprogram\".\n\nUnlike #leftoverbits that sometimes cover trivial but boring style\nnormalization and easy refactoring of code into helper functions, I\nhave never seen a bug report on the list that may make a good\nmicroproject. If we were to add a curated list of microproject idea\non the general microproject information page, it probably is better\nto remove these mentions of bugreports and #leftoverbits, so that\nreaders will not get distracted. \"Don't hesitate to ask\" so that\nthey may try to tackle more challenging one, if they wish, is a good\nthing to say nevertheless.\n\nThanks.\n"}]}