All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@gefanuc.com>
To: Using OE <openembedded-users@openembedded.org>,
	 openembedded-devel@openembedded.org
Subject: Discussion regarding the future of OpenEmbedded mailing lists
Date: Wed, 25 Feb 2009 09:47:22 +0000	[thread overview]
Message-ID: <49A513AA.9080201@gefanuc.com> (raw)

Hi All,

This email is mainly targeted at those who are subscribed to the "openembedded-users" mailing list, who are not also subscribed to the "openembedded-devel" list.

There has been a proposal on the openembedded-devel mailing list to re-organise the lists provided on openembedded.org. The re-organisation has been discussed as part of a larger discussion into the procedures that are used to review patches/changes to Openembedded, that aim to make the process more efficient and transparent.

A proposal has been put forward to merge a number of the mailing lists. There are currently 7 OpenEmbeddded mailing lists with the following purposes:

Openembedded-announce - (no description available)
Openembedded-commits - Commits to the OpenEmbedded metadata repository
Openembedded-devel - Using the OpenEmbedded metadata to build Distributions
Openembedded-issues - OE Issues
Openembedded-stablebranch - Discussion and review of changes to the stable branch and its policy
Openembedded-users - Using OE
Openembedded-private - (no description available)

The role each of these lists is currently poorly defined and in some cases either a list has too few knowledgeable/key subscribers to properly answer the questions asked, have overlapping objectives or would better serve the larger Openembedded community by being merged into a more active list. The proposal is to merge the list to form 3 better defined lists:

Openembedded-devel - for humans to post patches and ask questions
Openembedded-commits - commits, bugs, logs, etc
Openembedded-private - core team

The plan (as I understand it - please correct me if I'm wrong) is to:
* Close OpenEmbedded Announce, It seems to have received no traffic since April 2007.
* Merge OpenEmbedded-issues into Openembedded-commits. This list will be for fairly verbose automated messages and as such high traffic.
* Merge Openembedded-users and Openembedded-stablebranch in to Openembedded-devel. This will form a single list for the discussion of changes and issues regarding the Openembedded platform and to ensure all users and developers are aware of up coming changes and have a chance to be involved in any discussions. It is believed this will also aid with spotting changes that should be ported from the development branch to the stable branch and visa-versa.
* Retain Openembedded-private for private core-team discussions.

Initial support on Openembedded-devel has been very positive, though the views of those subscribed on the Openembedded-users list are also important. Objections, suggestions and support for these plans are welcome.

Martyn

-- 
Martyn Welch MEng MPhil MIET (Principal Software Engineer)   T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd,        |Registered in England and Wales
Tove Valley Business Park, Towcester,      |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB  VAT:GB 729849476



             reply	other threads:[~2009-02-25  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  9:47 Martyn Welch [this message]
     [not found] ` <B6FF18F4244BAE4991D05BF4F7A7649293467E@MCHP7I5A.ww902.siemens.net>
2009-02-25 16:08   ` Discussion regarding the future of OpenEmbedded mailing lists Martyn Welch
2009-02-25 18:38     ` Michael 'Mickey' Lauer
2009-02-25 18:50       ` Philip Balister
2009-03-02 18:38         ` Michael 'Mickey' Lauer
2009-02-26 13:22     ` Marco Cavallini
2009-02-26 19:40       ` Michael 'Mickey' Lauer

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=49A513AA.9080201@gefanuc.com \
    --to=martyn.welch@gefanuc.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=openembedded-users@openembedded.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.