From: <Tim.Bird@sony.com>
To: tech-board-discuss@lists.linuxfoundation.org
Subject: [Tech-board-discuss] Minutes summary from March 7, 2019 TAB conference call
Date: Tue, 6 Aug 2019 16:14:03 +0000 [thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF97793469@USCULXMSG01.am.sony.com> (raw)
Minutes from the TAB conference call on March 7, 2019
= Public Summary =
Attendees: Chris, Greg, Jon, Tim, Ted, Steve, Dan, Laura, Kees
Apologies: Olof
== Executive Summary ==
* Minutes approval
Unanimous approval for last two meetings' notes.
* Code of conduct committee docs and action items
Olof continuing to make edits. Should be done within the next week or so. CoC committee member selection continued to be discussed. Committee will be 5 members including Greg KH and Mishi Choudhary. It is expected that the TAB will reach out to specific individuals to fill the remaining 3 slots with the goal of finding responsible people in the kernel community who do not overlap with TAB.
* Picking up the electronic voting discussion
Sample electronic voting (condorcet) finished, and looks promising. However, switching tally method AND casting method at the same time may not be the best idea. Research will continue to try to find a non-ranked electronic voting system so we can reach the more important goal of allowing "absentee voting" for TAB elections. Criteria for absentee voting is still under discussion.
* Scheduling elections for chair/vice chair
Vote will happen at April meeting. Possibly with new electronic voting system.
* Plumbers news
No major news. Progress continues, announcement is expected before the next TAB meeting.
* Maintenance project funding
With other project funding mechanisms aimed mostly at novel projects or entry-level contributors, there needs to be a place to fund specific ongoing kernel projects that do not have another home. Discussion with LF is expected to help resolve this.
reply other threads:[~2019-08-06 16:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ECADFF3FD767C149AD96A924E7EA6EAF97793469@USCULXMSG01.am.sony.com \
--to=tim.bird@sony.com \
--cc=tech-board-discuss@lists.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).