From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: [RFH] Issues and Contributions to friendly third-party projects
Date: Fri, 14 Mar 2025 10:56:39 -0700 [thread overview]
Message-ID: <xmqqldt7fqco.fsf@gitster.g> (raw)
In-Reply-To: <xmqqwmd91zc2.fsf@gitster.g> (Junio C. Hamano's message of "Fri, 28 Feb 2025 14:25:33 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> After seeing a issue report on git-scm.com (and remembering number
>> of issues reported on friendly third-party projects on this list
>> and getting redirected to elsewhere), it may probably make sense to
>> document who they are, what they do, and how to contact them, in the
>> same document that drove these contributors to this list in the
>> first place.
>>
>> I am still not sure which of our document is the best place to do
>> so, but no matter where it eventually goes, it would be better to
>> first agree on
>>
>> - if doing so is a good idea to begin with (such a list in a
>> document will incur maintenance cost)
>>
>> - who to include on such a list (the list will become useless if it
>> includes everything on earth that claims to be related to Git;
>> where do we draw the line?)
>>
>> - how the list will be maintained (are we responsible to ping them?
>> will they update us to keep their entry from going stale?)
>>
>> As a discussion starter, here is what I added to the source to "A
>> note from the maintainer" message I send out every once in a while
>> (https://lore.kernel.org/git/xmqqr05a5wjv.fsf@gitster.g/ is the last
>> one I sent out).
>>
>> Comments? Corrections? Opinions?
>>
>> Thanks.
>
>
> Around here, no news is a bad news. I'll rescind this update and
> the next edition of maintainer's notes (planned to be sent out in
> the middle of next month) will not list these updates.
I changed my mind and the latest edition of MaintNotes does have
these. Corrections are welcome to the contact info listed there, so
are additions and removals.
next prev parent reply other threads:[~2025-03-14 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 16:34 [RFH] Issues and Contributions to friendly third-party projects Junio C Hamano
2025-02-28 22:25 ` Junio C Hamano
2025-03-14 17:56 ` Junio C Hamano [this message]
2025-03-14 18:44 ` Jeff King
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=xmqqldt7fqco.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.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
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).