{"thread":{"id":"52802","subject":"[RFC][GSOC] Microproject Suggestion","startedAt":"2020-02-14T00:52:14Z","lastAt":"2020-02-14T08:49:59Z","messageCount":4,"participants":["Robear Selwans","Junio C Hamano","Denton Liu"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"391715","messageId":"CALH1-Xr_pK02j6_51EnZN=ZrSz6dijt9tn0ANJ21331GzAmBdQ@mail.gmail.com","threadId":"52802","inReplyTo":null,"subject":"[RFC][GSOC] Microproject Suggestion","fromName":"Robear Selwans","fromEmail":"rwagih.rw@gmail.com","sentAt":"2020-02-14T00:52:00Z","receivedAt":"2020-02-14T00:52:14Z","isPatch":false,"sender":{"key":"rwagih.rw@gmail.com","avatar":"https://gravatar.com/avatar/196a8e523e919aa337627b4427365961719a4b821499438fa0698ccfdc8dcf1e?d=mp&s=160"},"body":"Hi, so it came to my attention that GSOC applicants will need to\nsubmit a microproject to be considered. I was thinking about\nimplementing the squash as a separate feature from rebase. I did not\ndig up enough in the mail history to know whether this was suggested\nbefore or not.\n\nIt would be something that looks like this:\n> git squash [--offset-from-head=0]\nI did not really think it through, yet, and I don't know what options\ncould be put there so I am open to suggestions.\n\nMy motivation is quite simple. I think it is more intuitive. When\nsomeone first asked me to squash multiple commits before, the first\nthing I had in mind was `git squash`. It was kind of a disappointment\nthat this was not its own command.\n\nSo does that sound like a good idea?\n"},{"id":"391717","messageId":"xmqqy2t6osht.fsf@gitster-ct.c.googlers.com","threadId":"52802","inReplyTo":"CALH1-Xr_pK02j6_51EnZN=ZrSz6dijt9tn0ANJ21331GzAmBdQ@mail.gmail.com","subject":"Re: [RFC][GSOC] Microproject Suggestion","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-02-14T01:41:18Z","receivedAt":"2020-02-14T01:41:24Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Robear Selwans writes:\n\n> Hi, so it came to my attention that GSOC applicants will need to\n> submit a microproject to be considered. I was thinking about ...\n> So does that sound like a good idea?\n\nNot really.\n\nThe purpose of a GSoC microproject is not about producing useful end\nuser product. It is to learn the end-to-end flow, starting from the\ninitial submission, interacting with the reviewers to polish the\npatch, to reach the final version. For that purpose, we'd prefer a\nbite-sized project (and that is why it is called \"micro\")---my\npersonal gut-feeling yardstick is that anything that takes more than\n30 minutes to finish by an experienced Git developer to come up with\na perfect model answer is too big.\n\nAs a real patch for you to get your toes into Git development,\noutside the scope of GSoC, I think it would be a good sized first\npatch. It is a bit too big for a microproject, and it is a bit too\nsmall for a main GSoC project.\n\nFor the feature itself, I'd just do\n\n $ git reset --soft HEAD~$n ;# rewind\n $ git commit --amend\n\nto open an editor, and then to the editor to edit the log message,\nI'd tell it to insert \"git log ..@{1}\" to the edit buffer to help me\nformulate the log message for the consolidated change, so I do not\npersonally see me using it, even if it were available.\n\nThanks.\n"},{"id":"391745","messageId":"CALH1-XruJ8UnHTN+xi=NOPtoP-p_F2OCmkLai8kjzsLObg=AvQ@mail.gmail.com","threadId":"52802","inReplyTo":"xmqqy2t6osht.fsf@gitster-ct.c.googlers.com","subject":"Re: [RFC][GSOC] Microproject Suggestion","fromName":"Robear Selwans","fromEmail":"rwagih.rw@gmail.com","sentAt":"2020-02-14T07:29:33Z","receivedAt":"2020-02-14T07:29:47Z","isPatch":false,"sender":{"key":"rwagih.rw@gmail.com","avatar":"https://gravatar.com/avatar/196a8e523e919aa337627b4427365961719a4b821499438fa0698ccfdc8dcf1e?d=mp&s=160"},"body":"On Fri, Feb 14, 2020 at 3:41 AM Junio C Hamano wrote:\n\n> For the feature itself, I'd just do\n> $ git reset --soft HEAD~$n ;# rewind\n> $ git commit --amend\n>\n> to open an editor, and then to the editor to edit the log message,\n> I'd tell it to insert \"git log ..@{1}\" to the edit buffer to help me\n> formulate the log message for the consolidated change, so I do not\n> personally see me using it, even if it were available.\n\nYeah, this makes a lot of sense.\n\nThat was actually the only idea that I could come up with till now. I\nam open to suggestions, though. I don't really mind if it is too big,\nas I am also interested in contributing to git.\n"},{"id":"391746","messageId":"20200214084954.GA5878@generichostname","threadId":"52802","inReplyTo":"CALH1-XruJ8UnHTN+xi=NOPtoP-p_F2OCmkLai8kjzsLObg=AvQ@mail.gmail.com","subject":"Re: [RFC][GSOC] Microproject Suggestion","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2020-02-14T08:49:54Z","receivedAt":"2020-02-14T08:49:59Z","isPatch":false,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"Hi Robear,\n\nOn Fri, Feb 14, 2020 at 09:29:33AM +0200, Robear Selwans wrote:\n> That was actually the only idea that I could come up with till now. I\n> am open to suggestions, though. I don't really mind if it is too big,\n> as I am also interested in contributing to git.\n\nEven though Git doesn't have an offical issue tracker, one good place to\nlook is GitGitGadget's issue[1]. It's pretty well-curated and has a lot\nof tiny cleanup issues that you could get started on.\n\nAnother thing you could do to find inspiration is to search for\n#leftoverbits on your Git mailing list archive of choice (most people\nseem to use lore.kernel.org/git).\n\nHope that helps,\n\nDenton\n\n[1]: https://github.com/gitgitgadget/git/issues\n"}]}