From: Carlos O'Donell <carlos@redhat.com>
To: cti-tac@lists.linuxfoundation.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Status of glibc-related service cost review for CTI?
Date: Thu, 1 Jun 2023 08:18:20 -0400 [thread overview]
Message-ID: <2b961760-b1c5-0bf3-1da4-b76d06cb925f@redhat.com> (raw)
Konstantin,
This issue came up in today's CTI TAC meeting and I took the AI to email you here.
Do we have an update on the status of the cost of CTI supporting glibc's service requirements?
Is glibc too small to even count?
Does it make it hard to estimate?
Would you rather budget this or estimate a price based on load or resources used?
We have a similar outstanding question to ensure the LF's BBB instance stays funded for glibc
community patch review meetings, CTI TAC meetings, and possibly Office Hours for the projects.
--
Cheers,
Carlos.
next reply other threads:[~2023-06-01 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 12:18 Carlos O'Donell [this message]
2023-06-07 19:37 ` Status of glibc-related service cost review for CTI? Konstantin Ryabitsev
2023-06-07 23:04 ` David Edelsohn
2023-06-08 11:56 ` Carlos O'Donell
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=2b961760-b1c5-0bf3-1da4-b76d06cb925f@redhat.com \
--to=carlos@redhat.com \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=konstantin@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).