git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Patrick Steinhardt <ps@pks.im>
Cc: Christian Couder <christian.couder@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Git in GSoC 2025
Date: Wed, 5 Feb 2025 00:06:32 +0530	[thread overview]
Message-ID: <cde4132d-fd6f-4f83-adb4-7ea124b6f09f@gmail.com> (raw)
In-Reply-To: <xmqqtt9byxia.fsf@gitster.g>

On 03/02/25 18:51, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> 
>> I was wondering whether it might make sense to also move the list of
>> microprojects into the Git project itself, e.g. as something like
>> "Documentation/Projects.txt". This would make it easier for us to update
>> the list of long-running projects whenever a new project is added and
>> makes it easier for people to discover it.
> 
> I wonder if this is better managed as either a separate tree (like
> the 'todo' branch that houses "What's cooking" reports among other
> things) with history disjoint from the main project, or even a
> separate Wiki?
>

Just to cross-check this, isn't the current home for this file,
http://git.github.io, already a separate wiki of sorts? The site's
description literally says something along the same lines:

 > These pages are intended to be edited collaboratively (i.e., it is an
 > alternative to us having a wiki, but one that is edited entirely via
 > Git pushes. The repository could be found on GitHub.

So, do you think if it would be fine to leave it where it currently is?


[[ References ]]

[1]: https://git.github.io/

--
Sivaraam


  reply	other threads:[~2025-02-04 18:36 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-19 10:13 Git in GSoC 2025 Kaartic Sivaraam
2025-01-20  7:07 ` Patrick Steinhardt
2025-01-20 13:38   ` shejialuo
2025-01-21 11:47   ` Oswald Buddenhagen
     [not found]   ` <CA+ARAtqfXo75PzzB3cQjDbvLxwytUK=xJiGG=VHZ1sNCcfyktQ@mail.gmail.com>
2025-01-27  8:06     ` Patrick Steinhardt
2025-01-27 12:43       ` shejialuo
2025-01-28 18:20       ` Kaartic Sivaraam
2025-01-28 17:30   ` Kaartic Sivaraam
2025-02-02 11:52     ` Kaartic Sivaraam
2025-02-03  8:45       ` Patrick Steinhardt
2025-02-03 11:53       ` Karthik Nayak
2025-02-04  2:29       ` shejialuo
2025-02-04 18:33       ` Kaartic Sivaraam
2025-02-05 13:20         ` Christian Couder
2025-02-07  7:32           ` Kaartic Sivaraam
2025-02-07  8:07             ` Christian Couder
2025-02-07 10:55             ` Patrick Steinhardt
2025-02-11  5:18               ` Kaartic Sivaraam
2025-02-16 12:56                 ` Ghanshyam Thakkar
2025-02-16 13:53                   ` Kaartic Sivaraam
2025-02-16 17:48                     ` Junio C Hamano
2025-02-17 15:21                     ` Ghanshyam Thakkar
2025-03-07 10:01                     ` Karthik Nayak
2025-03-20 17:50                       ` Kaartic Sivaraam
2025-03-21 21:02                         ` Karthik Nayak
2025-02-08 15:34             ` shejialuo
2025-02-10 17:00             ` Karthik Nayak
2025-01-20  8:19 ` Christian Couder
2025-01-20 11:09   ` Patrick Steinhardt
2025-01-21 20:35     ` Junio C Hamano
2025-01-30  5:44       ` Kaartic Sivaraam
2025-01-30  7:32         ` Patrick Steinhardt
2025-01-30  8:37           ` Christian Couder
2025-01-30 10:56             ` Patrick Steinhardt
2025-01-30 19:18           ` Junio C Hamano
2025-01-30 21:00             ` Junio C Hamano
2025-01-31  4:51               ` Patrick Steinhardt
2025-01-31 16:09                 ` Junio C Hamano
2025-02-03  8:49                   ` Patrick Steinhardt
2025-01-31  4:48             ` Patrick Steinhardt
2025-02-03 13:21     ` Junio C Hamano
2025-02-04 18:36       ` Kaartic Sivaraam [this message]
2025-01-30  5:39   ` Kaartic Sivaraam
2025-01-20 10:12 ` Karthik Nayak
2025-01-20 13:27 ` shejialuo
2025-02-28  3:03 ` Kaartic Sivaraam
2025-02-28  5:06   ` shejialuo
2025-02-28  6:16   ` Patrick Steinhardt
2025-02-28  7:56   ` Christian Couder
2025-02-28 10:12   ` Ghanshyam Thakkar
2025-03-01  0:47   ` Kaartic Sivaraam
2025-03-03 10:00   ` Karthik Nayak

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cde4132d-fd6f-4f83-adb4-7ea124b6f09f@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ps@pks.im \
    /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.
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 NNTP newsgroup(s).