From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id C6350E0027E; Mon, 20 Aug 2012 11:45:38 -0700 (PDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 20 Aug 2012 11:45:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.77,798,1336374000"; d="scan'208";a="188880140" Received: from unknown (HELO envy.home) ([10.7.199.146]) by orsmga002.jf.intel.com with ESMTP; 20 Aug 2012 11:45:37 -0700 Message-ID: <5032855A.5050704@linux.intel.com> Date: Mon, 20 Aug 2012 11:43:38 -0700 From: Darren Hart User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: Yocto Project X-Enigmail-Version: 1.4.3 Cc: Paul Eggleton , Jason Kridner , "Wold, Saul" Subject: Documenting the mailing lists. X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 18:45:38 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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