All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: ksummit-discuss@lists.linuxfoundation.org,
	tech-board-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] TAB Nomination - Wolfram Sang
Date: Mon, 9 Sep 2019 01:48:36 +0100	[thread overview]
Message-ID: <20190909004836.GA2015@kunai> (raw)

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]


I am hacking on the Linux Kernel since 2008 mostly in the embedded space
and maintain the I2C subsystem since 2012. I have spoken at various
conferences around the globe about technical and workflow topics ever
since. I care for a vibrant and healthy community.

I have not been on the TAB before. I'd like to figure out for myself
which possibilities it offers to keep the Linux community going strong.
I am currently most concerned about the lack of maintainers and
reviewers. I'd like to see if this is a place which can spark
initiatives here and there.

Also, while I see the TAB has become more transparent and visible in the
last two years, I think there is more potential there. I want to
contribute to that, too.

I work as a consultant, so views of an individual developer are known to
me as well as views of larger companies. I'd call myself an experienced
Kernel developer, but I haven't been around since the beginning. I'd
like to bring this mix to the table of the TAB.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: ksummit-discuss@lists.linuxfoundation.org,
	tech-board-discuss@lists.linuxfoundation.org
Subject: [Tech-board-discuss] TAB Nomination - Wolfram Sang
Date: Mon, 9 Sep 2019 01:48:36 +0100	[thread overview]
Message-ID: <20190909004836.GA2015@kunai> (raw)

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]


I am hacking on the Linux Kernel since 2008 mostly in the embedded space
and maintain the I2C subsystem since 2012. I have spoken at various
conferences around the globe about technical and workflow topics ever
since. I care for a vibrant and healthy community.

I have not been on the TAB before. I'd like to figure out for myself
which possibilities it offers to keep the Linux community going strong.
I am currently most concerned about the lack of maintainers and
reviewers. I'd like to see if this is a place which can spark
initiatives here and there.

Also, while I see the TAB has become more transparent and visible in the
last two years, I think there is more potential there. I want to
contribute to that, too.

I work as a consultant, so views of an individual developer are known to
me as well as views of larger companies. I'd call myself an experienced
Kernel developer, but I haven't been around since the beginning. I'd
like to bring this mix to the table of the TAB.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-09-09  0:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  0:48 Wolfram Sang [this message]
2019-09-09  0:48 ` [Tech-board-discuss] TAB Nomination - Wolfram Sang Wolfram Sang

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=20190909004836.GA2015@kunai \
    --to=wsa@the-dreams.de \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.