Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Thilo Borgmann <thilo.borgmann@mail.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] doc/dev_community: add the addresses of the committees
Date: Wed, 1 Mar 2023 01:02:42 +0100
Message-ID: <44c714a6-9878-ed5c-d93d-ff8bf119e49e@mail.de> (raw)
In-Reply-To: <e9569e50-2076-a102-323b-8e679a608ab8@mail.de>

Am 22.02.23 um 13:34 schrieb Thilo Borgmann:
> Am 08.02.23 um 16:57 schrieb Thilo Borgmann:
>> From: Nicolas George <george@nsup.org>
>>
>> Omitting the .org from the address should be protection enough
>> against spam spiders.
>>
>> Signed-off-by: Nicolas George <george@nsup.org>
>> ---
>>   doc/dev_community/community.md | 4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/doc/dev_community/community.md b/doc/dev_community/community.md
>> index 21e08e20e3..59519393e2 100644
>> --- a/doc/dev_community/community.md
>> +++ b/doc/dev_community/community.md
>> @@ -55,6 +55,8 @@ Candidates for election can either be suggested or self-nominated.
>>   The conflict resolution process is detailed in the [resolution process](resolution_process.md) document.
>> +The TC can be contacted at <tc@ffmpeg>.
>> +
>>   ## Community committee
>>   The Community Committee (CC) is here to arbitrage and make decisions when
>> @@ -77,3 +79,5 @@ The members of the CC can be elected from outside of the GA.
>>   Candidates for election can either be suggested or self-nominated.
>>   The CC is governed by and responsible for enforcing the Code of Conduct.
>> +
>> +The CC can be contacted at <cc@ffmpeg>.
> 
> Pushing both soon.

Pushed.

Thanks,
Thilo

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2023-03-01  0:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 15:57 Thilo Borgmann
2023-02-08 15:57 ` [FFmpeg-devel] [PATCH 2/2] doc: Merge doc/dev_community/* and Code of Conduct into a seperate file Thilo Borgmann
2023-02-09 16:37 ` [FFmpeg-devel] [PATCH 1/2] doc/dev_community: add the addresses of the committees Nicolas George
2023-02-22 12:34 ` Thilo Borgmann
2023-03-01  0:02   ` Thilo Borgmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-08 15:51 Thilo Borgmann
2023-02-08 15:55 ` Thilo Borgmann

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=44c714a6-9878-ed5c-d93d-ff8bf119e49e@mail.de \
    --to=thilo.borgmann@mail.de \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git