From: Оля Тележная <email@example.com> To: Christian Couder <firstname.lastname@example.org> Cc: Thomas Gummerer <email@example.com>, Johannes Schindelin <Johannes.Schindelin@gmx.de>, git <firstname.lastname@example.org>, Jeff King <email@example.com>, SZEDER Gábor <firstname.lastname@example.org>, Matthieu Moy <Matthieu.Moy@gmail.com> Subject: Re: GSoC 2019: Git's application submitted Date: Mon, 11 Feb 2019 11:31:35 +0300 Message-ID: <CAL21Bm=n0pe5M0G5eB9svQcmM9dC023J46HFo-jYuDQeyKcwFw@mail.gmail.com> (raw) In-Reply-To: <CAP8UFD24Jgetmb9_ANm07Emwr90obVpiRPyX+HtmaHcL1fYq5g@mail.gmail.com> пн, 11 февр. 2019 г. в 10:46, Christian Couder <email@example.com>: > > On Mon, Feb 11, 2019 at 6:48 AM Оля Тележная <firstname.lastname@example.org> wrote: > > > > > It would be nice to have a few more project ideas. > > > > I am not sure I have additional ideas for 3-month project for the intern, but > > > > > https://git.github.io/SoC-2019-Ideas/ currently lists only 2 possible > > > projects: > > > > > > - Unify ref-filter formats with other --pretty formats (which is new) > > > > I am ready to act as a mentor in this task, I know that part of > > project good enough. > > Great! I thought that it would be a good project for you to mentor and > that's why I added it. > > By the way if you would prefer not to mentor the other project I can > remove you from its possible mentor list. I am ready to try mentoring on both projects, but it would be much easier for me to work only for this one. I removed my name from the other one and made pull request: https://github.com/git/git.github.io/pull/355 If project about pretty will not be selected by any of the students, I am happy to help other mentors with other projects. > > > I have additional related task: We have a function called > > oid_object_info, it allows to download meta-info of the file. It was > > used in cat-file, and inspired by that example, I improved ref-filter, > > so now ref-filter works faster with it. Moreover, I have found that > > oid_object_info allows to get the contents of the file. It was useful > > in ref-filter, and actually it could be also useful in cat-file, but > > we still download the file differently in cat-file, and it looks > > awkward. I need to make just one last move to finish my patch: it will > > close the task about migrating cat-file formatting logic to > > ref-filter. But cat-file still will not use general way to download > > the file. So, the task is to get rid of additional file-reading logic. > > I guess this task is much smaller than original one, but at least the > > student will have chance to finish it in 3 months. > > My patch is here: https://github.com/git/git/pull/568 > > But I hope you will also see it this week in the mailing list. > > Proposed task is in TODO in the end of ref-filter file. > > Do you mean the following comment from > https://github.com/git/git/blob/c17ed82b8983ea7e172181d869966db546c6a528/ref-filter.c#L2393-L2399: > > /* > * TODO: add support of %(*raw). Need to switch between oi and oi_deref for that. > * TODO: split logic and printing (as it is done in format_ref_array_item and > * show_ref_array_item). After that we could use %(raw) in all > ref-filter commands. > * TODO: rewrite print_object_or_die so that it will reuse result of general > * oid_object_info_extended call. > */ > > ? > > It doesn't look like that's it. Could you just copy the task into an > email? Or if you think it could be an idea for a GSoC project, could > you send a pull request to add it to: > > https://github.com/git/git.github.io/blob/master/SoC-2019-Ideas.md > > ? Yes, that's it. Particularly, the last TODO. But other TODOs will be also solved as a result. I can add it to the list of the projects if you find this task suitable. > > > By the way, we had a letter from Google, it is said that our tasks are > > sparsed. I am not sure I understand it correctly. Should I help the > > project somehow to solve our issues? > > Yeah, we got en email from Stephanie Taylor saying that our idea list > is quite sparse this year with a link to: > > https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list > > which contains: > > "Even if you are a new organization and only want one or two students > showing that you have multiple ideas (a bare minimum of 4 solid ideas) > is vital." > > They also want "more detailed description of [each] project (2-5 > sentences)", so I think we should work on that too. I added description for one of projects, it is also in my pull request. > > So yeah, any help to fix the idea list is very welcome! > > Thanks, > Christian.
next prev parent reply index Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-04 9:16 Christian Couder [not found] ` <CAL21Bm=K6zZ=APkiP3A_X7xVoOfx-MY2435YMp5y1ztE-xyYtg@mail.gmail.com> 2019-02-04 12:54 ` Christian Couder 2019-02-04 21:52 ` Thomas Gummerer 2019-02-05 21:17 ` Thomas Gummerer 2019-02-05 22:00 ` Christian Couder 2019-02-06 22:09 ` Thomas Gummerer 2019-02-07 19:39 ` Johannes Schindelin 2019-02-07 21:33 ` Thomas Gummerer 2019-02-11 5:41 ` Оля Тележная 2019-02-11 7:45 ` Christian Couder 2019-02-11 8:31 ` Оля Тележная [this message] 2019-02-11 10:52 ` Christian Couder 2019-02-13 22:36 ` Elijah Newren 2019-02-14 9:48 ` Christian Couder 2019-02-11 8:35 ` Christian Couder 2019-02-11 22:18 ` Thomas Gummerer 2019-02-11 23:58 ` Christian Couder 2019-02-12 20:25 ` Thomas Gummerer 2019-02-12 20:49 ` Christian Couder 2019-02-12 22:13 ` Thomas Gummerer 2019-02-06 12:27 ` Johannes Schindelin 2019-03-05 12:04 ` Duy Nguyen 2019-03-05 12:23 ` Duy Nguyen 2019-03-06 4:49 ` Jeff King 2019-03-06 9:36 ` Duy Nguyen 2019-03-06 19:08 ` Jeff King 2019-03-06 14:16 ` Johannes Schindelin 2019-03-18 12:51 ` Duy Nguyen 2019-03-18 16:37 ` Christian Couder
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAL21Bm=n0pe5M0G5eB9svQcmM9dC023J46HFo-jYuDQeyKcwFw@mail.gmail.com' \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --cc=Matthieu.Moy@gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
email@example.com list mirror (unofficial, one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox