From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Git in GSoC 2025
Date: Fri, 31 Jan 2025 05:51:51 +0100 [thread overview]
Message-ID: <Z5xW57fsOCNcGViY@pks.im> (raw)
In-Reply-To: <xmqqr04kaufo.fsf@gitster.g>
On Thu, Jan 30, 2025 at 01:00:27PM -0800, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > I do not mind either word, either, but I have two small issues to
> > raise:
> >
> > - Is each topic "owned" by some specific person? Would an owner
> > retires from the project, would the leftover bits go away with
> > the owner?
>
> I obviously meant "When an owner retires", but more importantly, I
> should have offered an alternative here, instead of just raising it
> as an issue.
>
> How about making the rule a lot simpler?
>
> The expiration date kicks in _mechanically_, i.e. stale entries
> are unconditionally dropped at the date, based solely on the
> comparison between the timestamp and the wall clock.
>
> People are free to advocate for its continued existence, and when
> such an effort achieves a concensus among then-active members of the
> community by the stated expiration date, a patch to update the
> entry's expiration date may be accepted, thereby prolonging its
> shelf life. Unless such a thing happens before the expiration date
> comes, we will mechanically drop the entry.
>
> Of course people _can_ resurrect an expired entry later as a new
> one when it seems appropriate.
>
> That makes the decision to expire things from the list easy to make.
Works for me. Ideally, as any other topic, the retirement should be sent
to the mailing list as a normal patch series so that people may chime in
on the retirement and state reasons why they don't think that is a good
idea.
Patrick
next prev parent reply other threads:[~2025-01-31 4:51 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 [this message]
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
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=Z5xW57fsOCNcGViY@pks.im \
--to=ps@pks.im \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@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.
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).