All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: unmaintained layers
Date: Fri, 10 Jan 2014 14:01:21 +0000	[thread overview]
Message-ID: <36564971.Qsvan2fIrZ@helios> (raw)
In-Reply-To: <52CEEE43.1090209@linaro.org>

On Thursday 09 January 2014 13:45:23 Trevor Woerner wrote:
> At the last TSC meeting the topic of unmaintained layers came up. Here
> is the sorted list of master layers from the layer index [1], would it
> be possible for those in the know to indicate which layers are, or are
> suspected of being, unmaintained?

This is all very interesting with people piping up that their layers are 
maintained, but I'm not sure it helps solve the overall problem.

We have some immediate issues with patches to particular layers going 
unmerged. That's in the process of being resolved.

However, looking to the future it was suggested at the TSC meeting it would be 
nice to have some kind of measure or indication for the layer (ideally in the 
layer index) as to how well-maintained it is. Is there a practical and 
objective measurement we can have about the layer's maintenance status? I 
don't have a good idea of what this would actually mean - how many outstanding 
patches it has? How recently it has been built/tested?

Also, if it does appear that a layer has gone "unmaintained" by popular 
consensus, what should actually be done about it?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  parent reply	other threads:[~2014-01-10 14:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 18:45 unmaintained layers Trevor Woerner
2014-01-09 21:45 ` Bruce Ashfield
2014-01-09 22:43   ` Mark Hatle
2014-01-09 23:20     ` Trevor Woerner
2014-01-10  1:14       ` Philip Balister
2014-01-10  4:54       ` Bruce Ashfield
2014-01-10  5:47         ` Marko Lindqvist
2014-01-09 23:35   ` Martin Jansa
2014-01-10  1:23     ` Chris Larson
2014-01-10  4:50     ` Bruce Ashfield
2014-01-10  5:54 ` Andreas Müller
2014-01-10  6:29 ` Nathan Rossi
2014-01-10  7:03 ` Fathi Boudra
2014-01-10  7:08 ` Lukas Bulwahn
2014-01-10  7:21 ` Hongxu Jia
2014-01-10 13:20 ` Mario Schuknecht
2014-01-10 14:01 ` Paul Eggleton [this message]
2014-01-10 15:35   ` Koen Kooi
2014-01-10 15:51   ` Trevor Woerner
2014-01-10 16:02     ` Philip Balister
2014-01-10 16:24       ` Trevor Woerner
2014-01-10 16:28 ` Saul Wold
2014-01-10 17:27 ` Andrei Gherzan
2014-01-10 18:54 ` João Henrique Freitas
2014-01-12 20:28 ` Mike Looijmans
2014-01-12 20:42   ` Trevor Woerner

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=36564971.Qsvan2fIrZ@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.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.