public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Cancel December's Call?
Date: Mon, 1 Dec 2025 11:01:51 +0000	[thread overview]
Message-ID: <CCABB1A9-4677-4212-99F2-5AB78F99EF9A@ipfire.org> (raw)
In-Reply-To: <461d21dd-6337-4a2a-ae02-f383283c7f91@ipfire.org>

Hello everyone,

So since there have been so many replies with people being available, I suppose we are going to cancel today’s call.

I would still like to highlight that the intention is only to skip the call, but we are still going to have the conversation on this list, so that we won’t loose too much time pushing the project forward in December.

All the best,
-Michael

> On 28 Nov 2025, at 13:03, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> Hi All,
> 
> 
> On 27/11/2025 18:48, Michael Tremer wrote:
>> Hello everyone,
>> I just wanted to check with you whether we want to have the December call in a couple of days?
>> As far as I can remember, there were a couple of maybe-s and it is probably better to have anything discussed on the list so that people can potentially catch up instead of missing out on the conversation.
> 
> Someone was not going to be available on 1st Dec. I was not going to be available on the 8th but that has now changed so I could make the call now.
> 
>> Are we happy to just skip the call and come back together on Jan 5th?
> 
> It is a busy time for many people so I don't have any problems with leaving it for December and having the next call on January 5th.
> 
> Regards,
> 
> Adolf.
> 
>> -Michael
> 
> 



      reply	other threads:[~2025-12-01 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 17:48 Michael Tremer
2025-11-28 13:03 ` Adolf Belka
2025-12-01 11:01   ` Michael Tremer [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=CCABB1A9-4677-4212-99F2-5AB78F99EF9A@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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