Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Dev meeting travel cost reimbursement request
Date: Tue, 13 Dec 2022 17:04:01 +0100
Message-ID: <20221213160401.GJ3806951@pb2> (raw)
In-Reply-To: <20221213133328.GB110766@haasn.xyz>


[-- Attachment #1.1: Type: text/plain, Size: 997 bytes --]

On Tue, Dec 13, 2022 at 01:33:28PM +0100, Niklas Haas wrote:
> Hi,
> 
> As was stated in the invitation to the Dec 2nd Barcelona dev meeting, my
> travel costs would be reimbursed by FFmpeg.
> 
> My total travel budget (train+plane+hotel) comes to (slightly above) 500
> EUR. I am therefore requesting this amount from the SPI fund.
> 
> Whom do I contact?

all refund requests are posted to ffmpeg-devel generally with
"[REFUND-REQUEST]" in the subject
then all developers can discuss / agree or object to it.
after a period of 7 days stefano would forward the request to
SPI (with whatever papers needed to proof the expenses match)
then depending on how busy the SPI treassurer is it can be
very quick or take months for the request to be handled.
Iam saying that so there are no unrealistic expectations on speed

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Avoid a single point of failure, be that a person or equipment.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2022-12-13 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 12:33 Niklas Haas
2022-12-13 16:04 ` Michael Niedermayer [this message]

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=20221213160401.GJ3806951@pb2 \
    --to=michael@niedermayer.cc \
    --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