{"thread":{"id":"50222","subject":"Students projects: looking for small and medium project ideas","startedAt":"2019-01-14T17:53:38Z","lastAt":"2019-02-26T20:14:24Z","messageCount":7,"participants":["Matthieu Moy","Ævar Arnfjörð Bjarmason","Alban Gruin","Duy Nguyen","Fabio Aiuto","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"366661","messageId":"86fttvcehs.fsf@matthieu-moy.fr","threadId":"50222","inReplyTo":null,"subject":"Students projects: looking for small and medium project ideas","fromName":"Matthieu Moy","fromEmail":"git@matthieu-moy.fr","sentAt":"2019-01-14T17:53:35Z","receivedAt":"2019-01-14T17:53:38Z","isPatch":false,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Hi,\n\nI haven't been active for a while on this list, but for those who don't\nknow me, I'm a CS teacher and I'm regularly offering my students to\ncontribute to open-source projects as part of their school projects. A\nfew nice features like \"git rebase -i --exec\" or many of the hints in\n\"git status\" were implemented as part of these projects.\n\nI'm starting another instance of such project next week.\n\nPart of the work of students is to choose which feature they want to\nwork on, but I try to prepare this for them. I'm keeping a list of ideas\nhere:\n\n  https://git.wiki.kernel.org/index.php/SmallProjectsIdeas\n\n(At some point, I should probably migrate this to git.github.io, since\nthe wiki only seems half-alive these days).\n\nI'm looking for small to medium size projects (typically, a GSoC project\nis far too big in comparison, but we may expect more than just\nmicroprojects).\n\nYou may suggest ideas by editting the wiki page, or just by replying to\nthis email (I'll point my students to the thread). Don't hesitate to\nremove entries (or ask me to do so) on the wiki page if you think they\nare not relevant anymore.\n\nThanks in advance,\n\n-- \nMatthieu Moy\nhttps://matthieu-moy.fr/\n"},{"id":"366685","messageId":"87sgxu4z9i.fsf@evledraar.gmail.com","threadId":"50222","inReplyTo":"86fttvcehs.fsf@matthieu-moy.fr","subject":"Re: Students projects: looking for small and medium project ideas","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2019-01-14T23:04:25Z","receivedAt":"2019-01-14T23:04:31Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Mon, Jan 14 2019, Matthieu Moy wrote:\n\n> I haven't been active for a while on this list, but for those who don't\n> know me, I'm a CS teacher and I'm regularly offering my students to\n> contribute to open-source projects as part of their school projects. A\n> few nice features like \"git rebase -i --exec\" or many of the hints in\n> \"git status\" were implemented as part of these projects.\n>\n> I'm starting another instance of such project next week.\n\nGood to hear!\n\n> Part of the work of students is to choose which feature they want to\n> work on, but I try to prepare this for them. I'm keeping a list of ideas\n> here:\n>\n>   https://git.wiki.kernel.org/index.php/SmallProjectsIdeas\n>\n> (At some point, I should probably migrate this to git.github.io, since\n> the wiki only seems half-alive these days).\n>\n> I'm looking for small to medium size projects (typically, a GSoC project\n> is far too big in comparison, but we may expect more than just\n> microprojects).\n>\n> You may suggest ideas by editting the wiki page, or just by replying to\n> this email (I'll point my students to the thread). Don't hesitate to\n> remove entries (or ask me to do so) on the wiki page if you think they\n> are not relevant anymore.\n\nSome #leftoverbits I've noted on-list before would qualify, some of\nthese (e.g. grep --only-matching) have been implemented, but others not:\n\nhttps://public-inbox.org/git/87in9ucsbb.fsf@evledraar.gmail.com/\nhttps://public-inbox.org/git/87bmcyfh67.fsf@evledraar.gmail.com/\n"},{"id":"366768","messageId":"38df1011-34d3-e34e-9c4c-b70a0c6576df@gmail.com","threadId":"50222","inReplyTo":"86fttvcehs.fsf@matthieu-moy.fr","subject":"Re: Students projects: looking for small and medium project ideas","fromName":"Alban Gruin","fromEmail":"alban.gruin@gmail.com","sentAt":"2019-01-15T21:32:30Z","receivedAt":"2019-01-15T21:32:43Z","isPatch":false,"sender":{"key":"alban.gruin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6310153?v=4"},"body":"Hi Matthieu,\n\nLe 14/01/2019 à 18:53, Matthieu Moy a écrit :\n> Hi,\n> \n> I haven't been active for a while on this list, but for those who don't\n> know me, I'm a CS teacher and I'm regularly offering my students to\n> contribute to open-source projects as part of their school projects. A\n> few nice features like \"git rebase -i --exec\" or many of the hints in\n> \"git status\" were implemented as part of these projects.\n> \n> I'm starting another instance of such project next week.\n> \n> Part of the work of students is to choose which feature they want to\n> work on, but I try to prepare this for them. I'm keeping a list of ideas\n> here:\n> \n>   https://git.wiki.kernel.org/index.php/SmallProjectsIdeas\n> \n> (At some point, I should probably migrate this to git.github.io, since\n> the wiki only seems half-alive these days).\n> \n> I'm looking for small to medium size projects (typically, a GSoC project\n> is far too big in comparison, but we may expect more than just\n> microprojects).\n> \n> You may suggest ideas by editting the wiki page, or just by replying to\n> this email (I'll point my students to the thread). Don't hesitate to\n> remove entries (or ask me to do so) on the wiki page if you think they\n> are not relevant anymore.\n> \n> Thanks in advance,\n> \n\nWhen rebase.missingCommitsCheck is enabled, git will warn the user if a\ncommit was dropped with `git rebase -i'.  This check only occurs after\nthe initial editing.  But the user can edit the todo list with\n`--edit-todo'.  Here, git won’t warn the user if a commit was dropped.\n\nThe goal is to have `--edit-todo' to warn the user when\nrebase.missingCommitsCheck is enabled, too.\n\nCheers,\nAlban\n\n"},{"id":"367296","messageId":"CACsJy8CiPPp0C6o_ADv_mvi2gv=PsR+W=E3OHYw8hWbsPhrpOQ@mail.gmail.com","threadId":"50222","inReplyTo":"86fttvcehs.fsf@matthieu-moy.fr","subject":"Re: Students projects: looking for small and medium project ideas","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2019-01-22T10:09:34Z","receivedAt":"2019-01-22T10:10:03Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Tue, Jan 15, 2019 at 12:55 AM Matthieu Moy <git@matthieu-moy.fr> wrote:\n>\n> Hi,\n>\n> ...\n>\n> You may suggest ideas by editting the wiki page, or just by replying to\n> this email (I'll point my students to the thread). Don't hesitate to\n> remove entries (or ask me to do so) on the wiki page if you think they\n> are not relevant anymore.\n\nI just mentioned this elsewhere [1] but let me summarize it here\nbecause I think this could be an interesting thing to do and once you\nget attr.c code it's not that hard to do. The student would need to\nunderstand about git attributes and how it's implemented in attr.c.\nBut that's about it. More background below, but the summary line is\n\"optimize attribute lookup to be proportional with the number of\nattributes queried, not the number of attributes present in\n.gitattributes files\".\n\nSo, we normally look up the same set of attributes over a long list of\npaths. We do this by building up an \"attribute stack\" containing all\nattribute info collected from all related .gitattributes files.\nWhenever we move from one path to the next, we update the stack\nslightly (e.g. if the previous path is a/b/c and the current one is\na/d/e, we need to delete attributes from a/b/.gitattributes from the\nstack, then add ones from a/d/.gitattributes). Looking up is just a\nmatter of going through this stack, find attribute lines that match\nthe given path, then get the attribute value.\n\nThis approach will not scale well. Assume that you have a giant\n.gitattrbutes file (or spreading over many files) with a zillion\nrandom attributes and two lines about \"love\" attribute. When you look\nup this \"love\" attribute you may end up going through all those\nattribute lines. [2] hints about a better approach in the comment near\ncannot_trust_maybe_real. If you know you are looking for \"love\", when\nyou build up the attribute stack, just keep \"love\" and ignore\neverything else [3]. This way, the attribute stack that we need to\nlookup will have two lines about \"love\". Lookup time is of course now\nmuch faster. In the best possible case, when you look for an attribute\nthat is not defined anywhere in .gitattributes files in your repo, you\nget an instant \"not found\" response because the attribute stack is\nempty. This edge case was implemented in [4].\n\n[1] https://public-inbox.org/git/20190118165800.GA9956@sigill.intra.peff.net/T/#m32fef6a9e8f65dffae41e44a62dd76b4a84fa0fe\n[2] 7d42ec547c (attr.c: outline the future plans by heavily commenting\n- 2017-01-27)\n[3] well, macros make it a bit more complex, but I'll leave that as an exercise.\n[4] 06a604e670 (attr: avoid heavy work when we know the specified attr\nis not defined - 2014-12-28)\n-- \nDuy\n"},{"id":"370018","messageId":"1550928497.2346.8.camel@libero.it","threadId":"50222","inReplyTo":"86fttvcehs.fsf@matthieu-moy.fr","subject":"Re: Students projects: looking for small and medium project ideas","fromName":"Fabio Aiuto","fromEmail":"polinice83@libero.it","sentAt":"2019-02-23T13:28:17Z","receivedAt":"2019-02-23T13:28:22Z","isPatch":false,"sender":{"key":"polinice83@libero.it","avatar":null},"body":"Il giorno lun, 14/01/2019 alle 18.53 +0100, Matthieu Moy ha scritto:\n> Hi,\n> \n> I haven't been active for a while on this list, but for those who\n> don't\n> know me, I'm a CS teacher and I'm regularly offering my students to\n> contribute to open-source projects as part of their school projects.\n> A\n> few nice features like \"git rebase -i --exec\" or many of the hints in\n> \"git status\" were implemented as part of these projects.\n> \n> I'm starting another instance of such project next week.\n> \n> Part of the work of students is to choose which feature they want to\n> work on, but I try to prepare this for them. I'm keeping a list of\n> ideas\n> here:\n> \n>   https://git.wiki.kernel.org/index.php/SmallProjectsIdeas\n> \n> (At some point, I should probably migrate this to git.github.io,\n> since\n> the wiki only seems half-alive these days).\n> \n> I'm looking for small to medium size projects (typically, a GSoC\n> project\n> is far too big in comparison, but we may expect more than just\n> microprojects).\n> \n> You may suggest ideas by editting the wiki page, or just by replying\n> to\n> this email (I'll point my students to the thread). Don't hesitate to\n> remove entries (or ask me to do so) on the wiki page if you think\n> they\n> are not relevant anymore.\n> \n> Thanks in advance,\n> \nHi Matthieu and to all developers,\nI'm Fabio, no more a student and I'm brand new in community\ndevelopment. I joined the git mailing-list about two weeks ago and I'm\nlooking for some first fix or tasks. I apologize myself in advance for\nmy little know of the subject.  Hope to have some useful information to\nstart workin'.\nThank you in advance\nFabio.\n"},{"id":"370258","messageId":"86r2bu30c2.fsf@matthieu-moy.fr","threadId":"50222","inReplyTo":"1550928497.2346.8.camel@libero.it","subject":"Re: Students projects: looking for small and medium project ideas","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@matthieu-moy.fr","sentAt":"2019-02-26T17:51:09Z","receivedAt":"2019-02-26T17:51:12Z","isPatch":false,"sender":{"key":"matthieu.moy@matthieu-moy.fr","avatar":"https://gravatar.com/avatar/0d82caa87c23154bfb465283a9678b89180ce8b6e07e9da84f9ee111183c7fbc?d=mp&s=160"},"body":"Fabio Aiuto <polinice83@libero.it> writes:\n\n> Hi Matthieu and to all developers,\n> I'm Fabio, no more a student and I'm brand new in community\n> development. I joined the git mailing-list about two weeks ago and I'm\n> looking for some first fix or tasks. I apologize myself in advance for\n> my little know of the subject.  Hope to have some useful information to\n> start workin'.\n\nMy advice would be to \"scratch your own itch\", i.e. find something you\ndislike about Git, and try to improve that. It's hard to find the\nmotivation (and time) to contribute in a purely un-interested way, but\nonce you start getting the benefits of your own patches in the way _you_\nuse Git, it's really rewarding !\n\nCheers,\n\n-- \nMatthieu Moy\nhttps://matthieu-moy.fr/\n"},{"id":"370270","messageId":"nycvar.QRO.7.76.6.1902262112270.41@tvgsbejvaqbjf.bet","threadId":"50222","inReplyTo":"86r2bu30c2.fsf@matthieu-moy.fr","subject":"Re: Students projects: looking for small and medium project ideas","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2019-02-26T20:14:01Z","receivedAt":"2019-02-26T20:14:24Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 26 Feb 2019, Matthieu Moy wrote:\n\n> Fabio Aiuto <polinice83@libero.it> writes:\n> \n> > Hi Matthieu and to all developers,\n> > I'm Fabio, no more a student and I'm brand new in community\n> > development. I joined the git mailing-list about two weeks ago and I'm\n> > looking for some first fix or tasks. I apologize myself in advance for\n> > my little know of the subject.  Hope to have some useful information to\n> > start workin'.\n> \n> My advice would be to \"scratch your own itch\", i.e. find something you\n> dislike about Git, and try to improve that. It's hard to find the\n> motivation (and time) to contribute in a purely un-interested way, but\n> once you start getting the benefits of your own patches in the way _you_\n> use Git, it's really rewarding !\n\nThere are also occasional bug reports on the Git mailing list, like this\none about `git grep`:\nhttps://public-inbox.org/git/CAGHpTB+fQccqR8SF2_dS3itboKd79238KCFRe4-3PZz6bpr3iQ@mail.gmail.com/T/#u\n\nYou can also search the Git mailing list archive for `#leftoverbits`:\n\nhttps://public-inbox.org/git/?q=%23leftoverbits\n\n(Of course, caveat emptor, some of those #leftoverbits might have been\naddressed in the meantime, others might not reproduce for you, yet others\nmight not be considered bugs or worth fixing...)\n\nCiao,\nJohannes\n"}]}