From: "Bird, Tim" <Tim.Bird@sony.com>
To: "linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [boot-time] SIG organizing meeting
Date: Fri, 8 Nov 2024 23:47:53 +0000 [thread overview]
Message-ID: <MW5PR13MB5632D59CC8D54682BE6EA092FD5D2@MW5PR13MB5632.namprd13.prod.outlook.com> (raw)
Hello fellow embedded Linux developers,
It's about time to plan our first meeting of the Linux boot-time SIG (Special Interest Group).
Things have been very loosely organized as I've been trying to gauge interest
in the SIG, and put forth some ideas around Linux boot-time to this list.
Unfortunately, I'll be traveling the next few weeks, so the earliest I can put something
together is the week of November 25th. I appears that people who have contacted
me with interest in the SIG are primarily from the US and Europe, and maybe India.
(It's hard to tell just from e-mails). Therefore I propose some kind of video-conference
at 9:00 am Mountain Time (I'm in that time zone) on Tuesday, November 26th.
That makes it 8:00 am Pacific, 5:00 pm CET, and 9:30 pm IST. Not great, but possibly OK.
The agenda would include a number of things, including:
- governance of the SIG
- projects to pursue
- frequency of meetings
- what resources to use
- where to put things (besides (obviously) upstream)
- how to collaborate, etc.
This is not a traditional trade association or funded project startup, so there
won't be any memberships (with fees, tiers, voting rights, etc.). But I still
think there should be some designated leadership and resources that will
be available for the SIG to use.
If I had my way, I'd use one of the Plumbers hack rooms for the meeting,
but there are details for access to that, that I need to work out. If anyone
can volunteer to provide the video conference hosting for the first SIG meeting,
please contact me privately. (Otherwise, it might be Teams, which is what I have.)
Please let me know any feedback you have on these plans. If you have a strong
idea that you would like to attend the meeting, you can ping me privately to
let me know your interest. (Fair warning - I'll be looking for volunteers for some
tasks, so if you are easily talked into Open Source work, consider your
attendance carefully. That said, lurkers are welcome also.)
A few other thoughts...
I've been a little wary about how much to copy LKML on these messages.
Usually, most of the kernel mailing lists are highly focused on technical
discussions and patch reviews. This SIG management stuff is neither of
those, and I don't want to unduly burden the kernel lists with this type
of material. To that end, I will probably stop CC-ing LKML on this type
of administrative e-mail. Also, it may be appropriate to get a separate
email list or communication channel for SIG-related conversations (ie
discussions unrelated to kernel features.) Let me know what you think.
Regards,
-- Tim
next reply other threads:[~2024-11-08 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 23:47 Bird, Tim [this message]
2024-11-23 23:35 ` [boot-time] SIG organizing meeting Bird, Tim
2024-11-23 23:37 ` Bird, Tim
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=MW5PR13MB5632D59CC8D54682BE6EA092FD5D2@MW5PR13MB5632.namprd13.prod.outlook.com \
--to=tim.bird@sony.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).