From: Matthew Khouzam via lttng-dev <lttng-dev@lists.lttng.org>
To: tracecompass developer discussions <tracecompass-dev@eclipse.org>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Invitation: Trace Compass Monthly Project Meetings
Date: Mon, 26 Jan 2026 16:42:16 +0000 [thread overview]
Message-ID: <DS4PPFB691D9211B0432FC71D96571491B79E93A@DS4PPFB691D9211.namprd15.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Hello everyone,
The Trace Compass project holds monthly online meetings to discuss the current state of the project, ongoing development work, and upcoming plans.
These meetings are primarily intended for committers and contributors, but anyone interested in Trace Compass development is welcome to attend.
Schedule:
The meetings take place every second Wednesday of the month at 10:00 AM Eastern Time.
Location:
The meetings are held online using Google Meet.
https://meet.google.com/rsq-gzem-tkv
Calendar:
All meetings are published in a shared Google Calendar.
View the calendar:
https://calendar.google.com/calendar/u/0?cid=dHJhY2Vjb21wYXNzQGdtYWlsLmNvbQ
Subscribe via iCal:
https://calendar.google.com/calendar/ical/dHJhY2Vjb21wYXNzQGdtYWlsLmNvbQ/public/basic.ics
Subscribing to the calendar is the best way to stay informed about upcoming meetings and any schedule changes.
Agendas and minutes:
Agendas and minutes are maintained on the Trace Compass GitHub Wiki (https://github.com/eclipse-tracecompass/org.eclipse.tracecompass/wiki/Project_Meetings) . Participants are encouraged to propose agenda items ahead of time by editing the relevant meeting page.
We look forward to seeing you at an upcoming meeting.
Best regards,
The Trace Compass Project
[-- Attachment #2: Type: text/html, Size: 4529 bytes --]
next reply other threads:[~2026-01-26 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 16:42 Matthew Khouzam via lttng-dev [this message]
2026-04-05 0:45 ` [tracecompass-dev] " Jonah Graham via lttng-dev
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=DS4PPFB691D9211B0432FC71D96571491B79E93A@DS4PPFB691D9211.namprd15.prod.outlook.com \
--to=lttng-dev@lists.lttng.org \
--cc=matthew.khouzam@ericsson.com \
--cc=tracecompass-dev@eclipse.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