All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <trevor.woerner@linaro.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: unmaintained layers
Date: Fri, 10 Jan 2014 10:51:51 -0500	[thread overview]
Message-ID: <52D01717.605@linaro.org> (raw)
In-Reply-To: <36564971.Qsvan2fIrZ@helios>

Hi Paul,

On 01/10/14 09:01, Paul Eggleton wrote:
> 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.

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

I was hoping I could put together a list of the layers which are no
longer maintained to see if we could find people who might be interested
in stepping up and taking on their maintenance. Or at the very least,
clarifying a given layers' maintenance status.

At the last OE TSC meeting the issue of unmaintained layers was brought
up, I asked several times if people could specify to which layers they
were referring, but nobody replied. So people are concerned about layers
that have no maintainer, but nobody can say which ones (?). In my
opinion I thought it would be easier to solve this problem if we could
at least start by defining it.

As to what can be done about it: if a layer is not maintained, and
nobody cares for the layer, we should drop it from the list or at least
mark it as such ("buyer beware"). If a layer is not maintained, and
people do care, then we'll need to try to find someone to take
responsibility for it (we should, at the very least, make the attempt).
Also I think we should identify layers that people do care about, whose
maintenance is questionable, which are not hosted in a way where the
community can apply necessary patches to easily.

Best regards,
    Trevor


  parent reply	other threads:[~2014-01-10 15:51 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
2014-01-10 15:35   ` Koen Kooi
2014-01-10 15:51   ` Trevor Woerner [this message]
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=52D01717.605@linaro.org \
    --to=trevor.woerner@linaro.org \
    --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.