From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Jason Kridner <jdk@ti.com>, "Wold, Saul" <saul.wold@intel.com>
Subject: Documenting the mailing lists.
Date: Mon, 20 Aug 2012 11:43:38 -0700 [thread overview]
Message-ID: <5032855A.5050704@linux.intel.com> (raw)
Scott,
We've come across some more confusion about mailing lists recently. I've
sent a patch against poky to try and clear it up a bit in the source,
but we should also see about cleaning up the web descriptions of the lists.
We have two pages that describe the lists:
http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/
My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to
it with links to https://lists.yoctoproject.org. This eliminates the
need to keep the CMS version in sync with the mailman page. The mailman
page should be considered the master anyway as the Description field is
taken directly from the list administrative settings.
We should then work to create meaningful Descriptions of all the lists.
These should still fit on a single line, but I think we can improve on
what we have. For example:
meta-ti Mailing list for the meta-ti layer
is not particularly enlightening. Perhaps something like:
meta-ti Usage and development of the meta-ti layer
If we do this all at once, we can also ensure a consistent language,
tone, etc. I'll propose something for each list here and ask that
interested parties comment and correct in reply. Once agreed upon, the
admins of the respective lists can make the changes (all CC'd)
Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch
submission for meta-yocto
shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure
Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system
(see README for patch submission)
shoeleather Neutral Board Lab Mailing List
I'm not sure what "neutral" is meant to convey. How about:
Discussion list for the Shoeleather embedded board lab
yocto General discussion list for the Yocto Project and
development for projects without dedicated lists
I think the yocto list is a bit problematic in that it mixes project
conceptual discussion, user help desk, and development all on the same
list. However, I'm trying to clarify what these actually are here - not
change anything.
yocto-ab Yocto Project Advisory Board ???
This should imply the intended audience. Is it just meant for members?
Is it meant as a way for non-AB members to observe what is going on?
yocto-advocacy Yocto Project advocacy & outreach AB subgroup
Same as above.
yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???
There is no detailed description for this list, so I'm not sure what
this is really about.
Yocto-builds Build failures and discussion about the autobuilder
(includes typo fix, "build system" removed to avoid confusion with the
"poky build system")
yocto-infrastructure Infrastructure ???
Jefro or Michael, can you come up with something appropriate here?
For lists where certain guidelines should be used in communications and
patch submission, we should document that in the detailed description of
the list, such as [project] tags for example.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next reply other threads:[~2012-08-20 18:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 18:43 Darren Hart [this message]
2012-08-20 19:15 ` Documenting the mailing lists Denys Dmytriyenko
2012-08-20 20:55 ` Rifenbark, Scott M
2012-08-20 21:19 ` Darren Hart
2012-08-20 21:23 ` Rifenbark, Scott M
2012-08-20 21:19 ` Denys Dmytriyenko
2012-08-20 21:26 ` Paul Eggleton
2012-08-20 21:27 ` Darren Hart
2012-08-20 21:33 ` Paul Eggleton
2012-08-20 21:34 ` Rifenbark, Scott M
2012-08-20 21:53 ` Hudson, Sean
2012-08-20 22:04 ` Darren Hart
2012-08-20 22:22 ` Rifenbark, Scott M
2012-08-20 21:40 ` Hudson, Sean
2012-08-20 21:56 ` Michael Halstead
2012-08-20 22:06 ` Darren Hart
2012-08-20 22:18 ` Jeff Osier-Mixon
2012-08-20 22:37 ` Darren Hart
2012-08-20 22:43 ` Jeff Osier-Mixon
2012-08-20 22:50 ` Darren Hart
2012-08-20 23:19 ` Paul Eggleton
2012-08-21 16:28 ` Darren Hart
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=5032855A.5050704@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=jdk@ti.com \
--cc=paul.eggleton@linux.intel.com \
--cc=saul.wold@intel.com \
--cc=yocto@yoctoproject.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.