From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 2B6D31F4D7 for ; Tue, 31 May 2022 16:25:08 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="YTZJ3Iln"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346135AbiEaQZG (ORCPT ); Tue, 31 May 2022 12:25:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46982 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346133AbiEaQZE (ORCPT ); Tue, 31 May 2022 12:25:04 -0400 Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5805395DC9 for ; Tue, 31 May 2022 09:25:02 -0700 (PDT) Received: by mail-ej1-x62f.google.com with SMTP id gh17so27704699ejc.6 for ; Tue, 31 May 2022 09:25:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+WID8AmPWhtM27N9DNnfDiSDsUmirgqUtrYvRJFz9Sk=; b=YTZJ3IlnPay9NLE6iyHrsLoxLMsCGFN62RboRWr8CNRP4Bbl/tUtsYiZxbw8qB4bjZ uKasw4I6cW1tA0yJkT0U6OREjVL6jB/dFa4cyGaeTirnhyBJCz6zyDVMZf7Pdm/H8wCw jBuJ+AA4t6PvgxPtlwqTw74/4aerAzUR/HtApp8savjnVVXSBkWp2a9bqDpncyUSTF6a 0mvjKBTKYqwgWhFoZ9dGjchwJEx3gK8GyYtbkOv7M9TrT2j5hy1QxzTWS51/Iq2tkSSa 3NnnPNE2Iupdmku8sLlt1x8Vgf7bi256DNHuu2M7DAY8QY2dUAbnQKTYCCt9EtU8so1u /l2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+WID8AmPWhtM27N9DNnfDiSDsUmirgqUtrYvRJFz9Sk=; b=XD4qCTk64gGm3suA3zQQvI6cter1L8mg/Vp58M5E+K5vpTczUJUAhYMwmO++PTOkAB kC7KipecumXDCKjLDWzHD6pI8JpfJr3hDpkG9b1vZnS+Xb4rXXtGFZV8ejf0kGTr97EJ QUnTqTQFRbwj1AKtmynxkEIKqINxBMMENknfomtXWeMN5LiqgDXueDQb8/7Mdbhrzmkz k0L8/kD0Qea34NJHo31tF4iIDoNhSoDAvQX60u9x/vAJ1W93POti8T9Ox0w+xMdXzE38 ph1b9cIVjSlReVoR7kQr3JMe87+euvurhH48wT2KLFwfMFmarPo8zTabNRH/dUt7wnJZ qmlQ== X-Gm-Message-State: AOAM531MwBUC6/R1RdCn+AjxXoRSiplPMhNlgnEQl8G/U6zzyp6kv9EG YovbrX/W5tHoRVYMKoqZk4G3m78EJ+Z0jcqiUQ== X-Google-Smtp-Source: ABdhPJyBV6+SQ4C7us1YF/CopKrAEky0MKKEgDgrj1SwrUxkqx0IVMS6UJlEpavifVnww343cztWDnCUucr/Inb9c9w= X-Received: by 2002:a17:907:7e88:b0:6fa:55f:881a with SMTP id qb8-20020a1709077e8800b006fa055f881amr53684062ejc.476.1654014300750; Tue, 31 May 2022 09:25:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tapasweni Pathak Date: Tue, 31 May 2022 21:54:24 +0530 Message-ID: Subject: Re: Unify ref-filter formats with other pretty formats: GSoC'22 To: Christian Couder Cc: Junio C Hamano , Hariom verma , Taylor Blau , git Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Hi Christian, On Tue, Apr 26, 2022 at 3:25 PM Christian Couder wrote: > > Hi Tapasweni, > > On Fri, Apr 22, 2022 at 12:29 PM Tapasweni Pathak > wrote: > > On Fri, Apr 22, 2022 at 2:44 PM Christian Couder > > wrote: > > > On Wed, Apr 20, 2022 at 1:49 PM Tapasweni Pathak > > > wrote: > > > > > I would like to work on this with a planner, separately, we can see > > > > what should be adapted in mine to have everything go smooth and > > > > GSoC'22 project especially. > > > > > > As you seem interested in other things too, I think it's better to > > > avoid this one for now. It could be a bad experience as it's a really > > > difficult subject, and I think it would be much better for you to > > > start with something easier and smaller. > > > > I must insist; would be interested in a planner and document prep for > > the project, I can see some details > > - https://git.github.io/SoC-2021-Ideas/ > > - https://lore.kernel.org/git/pull.989.git.1625155693.gitgitgadget@gmail.com/ > > - https://docs.google.com/document/d/119k-Xa4CKOt5rC1gg1cqPr6H3MvdgTUizndJGAo1Erk/edit > > - https://github.blog/2021-11-15-highlights-from-git-2-34/ > > - https://lore.kernel.org/git/CAOLTT8S8TxuTmddGp2WGoPtTc3gwGXzizBfVzKd87otRw7Dpiw@mail.gmail.com/ > > > > to set things for the next steps, let me know if you strongly feel to > > not take up the problem right away. > > I am not sure what "planner" and "document prep" mean exactly to you, > and what "the problem" is. I replied to your other email and I hope it > helps, but maybe in my replies here and to your other email I am > missing something. In this case please let me know. GSoC Timeline. :) > > We are ok to describe projects in a few sentences or paragraphs, like > in https://git.github.io/SoC-2021-Ideas/ where we describe the > projects we propose, but for GSoC and Outreachy, applicants interested > in a project are those who actually write the proposals which usually > include a timeline. > > I am sure not, but it looks to me like you would like us (not you) to > write a full proposal including a timeline. No, no. not. at. all. > > For example the proposal in > https://docs.google.com/document/d/119k-Xa4CKOt5rC1gg1cqPr6H3MvdgTUizndJGAo1Erk/edit > which includes a timeline was fully writen by ZheNing Hu, and was then > accepted by us, so that ZheNing Hu could then participate in the GSoC > 2021 and start the actual work. > > https://lore.kernel.org/git/pull.989.git.1625155693.gitgitgadget@gmail.com/ > shows some of the work he did and sent to the mailing list as part of > the GSoC. > > https://github.blog/2021-11-15-highlights-from-git-2-34/ is not > especially related to any GSoC. > > https://lore.kernel.org/git/CAOLTT8S8TxuTmddGp2WGoPtTc3gwGXzizBfVzKd87otRw7Dpiw@mail.gmail.com/ > is a discussion about the Outreachy Winter 2021-2022 round (not GSoC) > where ZheNing Hu accepted to co-mentor with me someone who would work > on continuing Hariom's GSoC 2020 "Unify ref-filter formats with other > \-\-pretty formats" project. As there were no Outreachy applicants > interested in working on this, we proposed this same project to the > upcoming GSoC. > > So I don't see any problem that we should take up with the links you > listed. If someone would have it write a full proposal and a detailed > timeline it would be you, not us. Of course, as you propose to work > outside GSoC and Outreachy, we don't require that from you, because > you would not be part of any such official program and wouldn't get > paid. > > I hope I don't misunderstand what you said. I will update will a timeline in the next few weeks (June). Thank you for the information.