From: Martin Jansa <martin.jansa@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: unmaintained layers
Date: Fri, 10 Jan 2014 00:35:10 +0100 [thread overview]
Message-ID: <20140109233510.GO3709@jama> (raw)
In-Reply-To: <CADkTA4M+KG9uXtb91ANThgzMgOAb0WjiVmBvf48UszmSnX62dA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4125 bytes --]
On Thu, Jan 09, 2014 at 04:45:38PM -0500, Bruce Ashfield wrote:
> On Thu, Jan 9, 2014 at 1:45 PM, Trevor Woerner
> <trevor.woerner@linaro.org> wrote:
> > Hi everyone,
> >
> > 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?
>
> Wouldn't it be easier to do an initial sort based on commit activity ? Versus an
> opt-in query ?
Some BSPs are valid for very long time without any commit in it. So I
think it will show a lot of false-possitives.
> > meta-aarch64
> > meta-acer
> > meta-ada
> > meta-android
> > meta-angstrom
> > meta-arago-distro
> > meta-arago-extras
> > meta-asus
> > meta-aurora
> > meta-baryon
> > meta-beagleboard
> > meta-beagleboard-extras
> > meta-browser
> > meta-bug
> > meta-buglabs
> > meta-chicken
> > meta-chiefriver
> > meta-clutter
> > meta-crownbay
> > meta-crystalforest
> > meta-cubox
> > meta-darwin
> > meta-eca
> > meta-efikamx
> > meta-efl
> > meta-eldk
> > meta-emenlow
> > meta-erlang
> > meta-ettus
> > meta-filesystems
> > meta-fri2
> > meta-fsl-arm
> > meta-fsl-arm-extra
> > meta-fsl-demos
> > meta-fsl-ppc
> > meta-fso
> > meta-games
> > meta-geeksphone
> > meta-gir
> > meta-gnome
> > meta-gpe
> > meta-gstreamer10
> > meta-guacamayo
> > meta-gumstix
> > meta-gumstix-community
> > meta-gumstix-extras
> > meta-hamradio
> > meta-handheld
> > meta-hipos
> > meta-htc
> > meta-igep
> > meta-initramfs
> > meta-intel
> > meta-ivi
> > meta-jasperforest
> > meta-java
> > meta-kde
> > meta-kernel-dev
>
> maintained.
>
> > meta-kirkwood
> > meta-linaro
> > meta-linaro-toolchain
> > meta-lsi
> > meta-lxcbench
> > meta-measured
> > meta-mentor
> > meta-micro
> > meta-mingw
> > meta-minnow
> > meta-mono
> > meta-multimedia
> > meta-n450
> > meta-netbookpro
> > meta-netmodule
> > meta-networking
> > meta-nokia
> > meta-nslu2
> > meta-nuc
> > meta-oe
> > meta-openmoko
> > meta-openpandora
> > meta-openstack
> > meta-openstack-compute-deploy
> > meta-openstack-controller-deploy
> > meta-openstack-qemu
>
> All openstack layers are maintained.
>
> > meta-opie
> > meta-oracle-java
> > meta-osmocombb
> > meta-ouya
> > meta-palm
> > meta-perl
> > meta-picosam9
> > meta-qt3
> > meta-qt5
> > meta-raspberrypi
> > meta-realtime
>
> mantained
>
> > meta-ro-rootfs
> > meta-romley
> > meta-ros
> > meta-ruby
> > meta-samsung
> > meta-sdr
> > meta-security
> > meta-selinux
> > meta-shr
> > meta-shr-distro
> > meta-slugos
> > meta-smalltalk
> > meta-sourcery
> > meta-sugarbay
> > meta-sunxi
> > meta-sys940x
> > meta-systemd
> > meta-telephony
> > meta-telldus
> > meta-ti
> > meta-tlk
> > meta-tracing
> > meta-virtualization
>
> maintained
>
> But I can't say if I didn't miss something I maintain in the list,
> since it is long and I scanned
> it quickly.
>
> Bruce
>
> > meta-web-kiosk
> > meta-webos
> > meta-webos-ports
> > meta-webserver
> > meta-woce
> > meta-x10
> > meta-xfce
> > meta-xilinx
> > meta-xilinx-community
> > meta-yassl
> > meta-yocto
> > meta-yocto-bsp
> > meta-zynq
> > meta-zynq-milo
> > openembedded-core
> > toolchain-layer
> >
> >
> > Thank you for your input, and best regards,
> > Trevor
> >
> >
> >
> >
> > [1] http://layers.openembedded.org/layerindex/branch/master/layers/
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-01-09 23:34 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 [this message]
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
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=20140109233510.GO3709@jama \
--to=martin.jansa@gmail.com \
--cc=bruce.ashfield@gmail.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.