git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	Git Community <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
	Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
	Emily Shaffer <emilyshaffer@google.com>,
	Atharva Raykar <raykar.ath@gmail.com>,
	ZheNing Hu <adlternative@gmail.com>
Subject: Re: Git in GSoC 2022?
Date: Thu, 3 Feb 2022 14:12:13 +0000	[thread overview]
Message-ID: <730fb307-3bc7-b52f-49c1-d83b5ab55c95@iee.email> (raw)
In-Reply-To: <439ebfba-d493-2cff-434a-b1073e755688@gmail.com>

On 26/01/2022 18:29, Kaartic Sivaraam wrote:
> If we are interested in participating we need:
>
>   - Volunteers who are wiling to act as mentors. I would be
>     willing to be volunteer myself as a mentor for one student.
>  
>   - Microprojects: I believe we could repurpose the Outreachy
>     microproject ideas[2] for GSoC too. If others have suggestions
>     for microproject ideas, please share them.
>
>   - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
>     but both were picked by GSoC students the previous year. So,
>     we would need new ones this year.
Git Demonstration Repositories
=============================

One idea/concept that I've had that might be suitable for a project
either here or within the Google Season of Docs is to generate
demonstration repositories that match the examples used in the
documentation and parts of the test suite to help users explore and
understand the concepts that are being documented in the man pages.

It's more than a classic coding problem because it impinges on a lot of
subjective and admin areas but should be fairly beneficial for users.

The two examples that come to mind are the --show-pulls repo [1], and
the 'history simplification' repo [2].

Using the test suite as the repo generator ensures the Demo Repos are
reproducible/deterministic.

My latest thinking is that the repos would be held in-tree under
/Documentation/RepoBundles and have been exported as bundles by an
explicit test_export_function. Of key importance in the project is to
minimise/eliminate any extra maintainer actions, so once a patch with a
repo export is accepted, the flow through the delivery process to user
installs is essentially the same as the man pages.

Not sure if that's fleshed out enough, or if it's at the wrong level for
GSoC, or If I'm right as a Mentor, but I'd be happy to co-mentor.

>
>     Taylor showed interest in a bitmap-related project during
>     the Outreachy application period [4]. Taylor, are you still
>     interested in mentoring a bitmap-related project? Would it
>     be possible for you to do so for the upcoming GSoC?
--
Philip
[1] Git log --show-pulls
{the sha1
https://github.com/git/git/commit/8d049e182e2e213a012e2d6839becfe0e2de79db,
 get the t/tnnnn t/t6012-rev-list-simplify.sh,
 get the docs rev-list #L582-707}

[2] git rev list History simplification
{get the man page #Lnn
https://github.com/git/git/blob/master/Documentation/rev-list-options.txt#L386-L425,
 get the Chuck Li https://github.com/ChuckTest/git-history-test.git,
 get the gfw
https://groups.google.com/d/msgid/git-users/11286f4a-c961-4d12-91a0-f49e34d8691bn%40googlegroups.com}

  parent reply	other threads:[~2022-02-03 14:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 18:29 Git in GSoC 2022? Kaartic Sivaraam
2022-01-26 20:05 ` Taylor Blau
2022-01-27  9:32   ` Christian Couder
2022-01-29 18:09     ` Kaartic Sivaraam
2022-02-13 13:35     ` Christian Couder
2022-02-15 20:34       ` Kaartic Sivaraam
2022-02-15 23:18       ` Hariom verma
2022-02-16 15:40         ` Christian Couder
2022-02-17 15:07           ` Hariom verma
2022-02-17 17:18           ` Kaartic Sivaraam
2022-02-18  2:14             ` Hariom verma
2022-02-26 20:29   ` Kaartic Sivaraam
2022-02-28 11:03     ` Christian Couder
2022-02-28 18:02       ` Kaartic Sivaraam
2022-03-01 13:51         ` Christian Couder
2022-03-04 18:34           ` Kaartic Sivaraam
2022-01-27  3:55 ` Bagas Sanjaya
2022-01-27  9:44   ` Christian Couder
     [not found]     ` <nycvar.QRO.7.76.6.2201281114440.347@tvgsbejvaqbjf.bet>
2022-01-29 18:36       ` Kaartic Sivaraam
2022-03-09 11:49         ` Johannes Schindelin
2022-03-09 19:57           ` Kaartic Sivaraam
2022-01-27 14:39 ` Derrick Stolee
2022-01-29 18:19   ` Kaartic Sivaraam
2022-02-02 17:42     ` Derrick Stolee
2022-01-27 15:00 ` ZheNing Hu
2022-01-29 17:43   ` Kaartic Sivaraam
2022-02-03 14:12 ` Philip Oakley [this message]
2022-02-12 18:12   ` Kaartic Sivaraam
2022-02-13  9:33     ` Christian Couder
2022-02-15 15:05       ` Philip Oakley
2022-02-15 20:32       ` Kaartic Sivaraam
2022-02-16 15:55         ` Christian Couder
2022-02-17 17:28           ` Kaartic Sivaraam
2022-03-07 19:38 ` Kaartic Sivaraam
2022-03-07 19:50   ` Derrick Stolee
2022-03-07 22:25   ` Hariom verma

Reply instructions:

You may reply publicly 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=730fb307-3bc7-b52f-49c1-d83b5ab55c95@iee.email \
    --to=philipoakley@iee.email \
    --cc=adlternative@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=raykar.ath@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).