From: Junio C Hamano <gitster@pobox.com>
To: Amir Montazery <amir@ostif.org>
Cc: git@vger.kernel.org
Subject: Re: Coordinated Security Audit for git. Contacts needed
Date: Thu, 21 Jul 2022 10:47:14 -0700 [thread overview]
Message-ID: <xmqq8romicil.fsf@gitster.g> (raw)
In-Reply-To: <CADKuG0uzh3syzgfiPLepiTLXNzkoYhLFX1h-DE3C7c8j6HXALQ@mail.gmail.com> (Amir Montazery's message of "Thu, 21 Jul 2022 11:49:51 -0500")
Amir Montazery <amir@ostif.org> writes:
> We would love to collaborate to establish communication channels with
> key maintainers. Would it be possible for one of us to join one of
We do not call people "maintainers", but "developers" and/or
"contributors".
> your community meetings for 5 minutes? Or is there a key person we
> should be engaging?
There is no "community meetings" other than the informal "stand-up"
irc discussion that is biweekly. The log of the latest is at
https://colabti.org/irclogger/irclogger_log/git-devel?date=2022-07-18
but generally speaking we are not into "synchronous" communication.
You come to this mailing list and start talking, and that is how you
are heard by community members, which you're already doing fine ;-).
In case you are not familiar with Git, you can see output from
git shortlog --no-merges -s -n --since=2.years | head
to see who have been the active contributors.
Thanks.
next prev parent reply other threads:[~2022-07-21 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 16:49 Coordinated Security Audit for git. Contacts needed Amir Montazery
2022-07-21 17:47 ` Junio C Hamano [this message]
2022-07-21 18:06 ` Amir Montazery
2022-07-21 18:47 ` Junio C Hamano
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=xmqq8romicil.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=amir@ostif.org \
--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).