From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org,
openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] New OE layer index now available
Date: Mon, 1 Apr 2013 06:47:59 -0400 [thread overview]
Message-ID: <20130401104758.GB9978@windriver.com> (raw)
In-Reply-To: <3982011.Guen6pOcoq@helios>
[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]
[[OE-core] New OE layer index now available] On 13.03.29 (Fri 21:34) Paul Eggleton wrote:
> Hi folks,
>
> There is a new index for OpenEmbedded layers available here:
>
> http://layers.openembedded.org
>
> It can be used to browse and search for existing layers, as well as the
> recipes and machines contained within them. In addition to the short
> description, repository location and usage link we were collecting in the
> existing wiki, we can now store information on maintainers, layer
> dependencies, and the associated mailing list, as well as a longer
> description. New layers can be submitted easily using a simple form which does
> not require a login.
>
> I've imported all the data from the existing index on the OE wiki and filled
> in the blanks by hand - please check the entries for your layers and if I've
> missed anything or entered something incorrectly, please let me know (reply
> off-list) and I'll fix it; alternatively if you're already listed as the
> maintainer of a layer you can create an account with the same email address
> and you'll be able to edit the entry yourself at any time.
>
> The index also supports multiple branches, but for the moment there is only a
> master branch configured as I'd like to have people check the layer data before
> adding the additional stable branches (danny and denzil).
>
> Feedback on the new site is welcome. The code is also available in case you
> want to take a look / improve something - see the TODO file for possible future
> improvements:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/
>
> Once people have had a chance to give feedback I'll replace the content of the
> existing OE wiki page with a link to the new index.
I like it, though I have a couple of questions about the accounts
themselves.
- Any chance we could have them connected (or use the same
credentials as) the patchworks ones?
- If not, what options can we set on accounts? Right now I just see
"log out" and "change password". Both pretty important, but I'd
also like to add alternate email addresses, for example, since I
use two quite regularly and update meta-networking from both.
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-04-01 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 21:34 New OE layer index now available Paul Eggleton
2013-03-29 21:58 ` [OE-core] " Otavio Salvador
2013-03-29 22:07 ` Paul Eggleton
2013-04-01 10:47 ` Joe MacDonald [this message]
2013-04-01 11:57 ` Paul Eggleton
2013-04-01 13:06 ` Joe MacDonald
[not found] ` <CAOT3miKi62MtFGjiNYeykNKAsFQ+srtwqSbsSyge3ZzGHD4DOw@mail.gmail.com>
2013-04-04 15:23 ` Paul Eggleton
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=20130401104758.GB9978@windriver.com \
--to=joe.macdonald@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox