public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: Dan Rue <dan.rue@linaro.org>, kernelci@groups.io
Subject: Re: [kernelci] Some suggestions and questions
Date: Fri, 14 Dec 2018 10:00:38 -0800	[thread overview]
Message-ID: <7ha7l8ng3d.fsf@baylibre.com> (raw)
In-Reply-To: <20181212213831.xnw3ugwvpw4o365o@xps.therub.org>

"Dan Rue" <dan.rue@linaro.org> writes:

> I've received some (internal from Linaro) questions and suggestions
> recently, and I wanted to relay them here for consideration.
>
> Can we have a changelog, that would show changes to software, hardware,
> and infrastructure.

Sure, just needs an owner. :)

> Can the kernelCI FAQ provide a link to the mailing list archive?

Needs a front-end change.

> Can we make the meeting minutes doc public?

As already discussed, I think the minues sent to the list are better,
and facilitates discussion more than the doc.

> In the interest of transparency, can we disclose how emails sent to
> info@kernelci.org are handled?

This predates the list, so any new mails (of which there are almost
none) are redirected to the mailing list. 

I think to fix this, we need to fix the /contact page to point to the
groups.io list instead of the info alias.

Kevin

  parent reply	other threads:[~2018-12-14 18:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 21:38 Some suggestions and questions Dan Rue
2018-12-13 11:49 ` [kernelci] " Mark Brown
2018-12-13 12:14   ` Mike Holmes
2018-12-13 12:34     ` Mark Brown
2018-12-13 15:29       ` Dan Rue
2018-12-13 16:19         ` Mark Brown
2018-12-13 16:33           ` Dan Rue
2018-12-13 16:38             ` Mark Brown
     [not found] ` <156FE20DF2374CC6.18828@groups.io>
2018-12-13 12:15   ` [kernelci] " Mark Brown
2018-12-14 18:00 ` Kevin Hilman [this message]
2018-12-14 18:06   ` Mark Brown
2018-12-14 21:51     ` Kevin Hilman

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=7ha7l8ng3d.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=dan.rue@linaro.org \
    --cc=kernelci@groups.io \
    /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