All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:06:00 -0400	[thread overview]
Message-ID: <20130401130600.GE10672@windriver.com> (raw)
In-Reply-To: <1410613.FPl62IiBfB@helios>

[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]

[Re: [OE-core] New OE layer index now available] On 13.04.01 (Mon 12:57) Paul Eggleton wrote:

> On Monday 01 April 2013 06:47:59 Joe MacDonald wrote:
> > 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?
> 
> Seems like they are both based on Django so I guess it would be possible; the 
> only impediment (assuming there was no Django version mismatch) would be that 
> patchwork is currently on different infrastructure.

Okay, that's sort of what I figured, but I thought I'd ask anyway.  I
would love it as a layer maintainer to have a single dashboard I could
log into and get the whole view.  It may be that this is something I
rarely use anyway, though, in comparison to patchworks, so the effort of
connecting these two pieces isn't worth it.

> >    - 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.
> 
> There's no alternate email address field; one could be added I suppose but the 
> question is, how would you like this to be used within the index?

I don't know?  :-)  Honestly, not really all that sure what I'm looking
at here, but I'm thinking that if making updates in the interface to
layer information is tied to an email address, it'd be convenient for me
to log in as one username and have both my common email addresses
associated with it (with one being the primary, I guess).  Or to have
the ability to change the email address as necessary.

-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-04-01 13:23 UTC|newest]

Thread overview: 14+ 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 ` Otavio Salvador
2013-03-29 21:58   ` [OE-core] " Otavio Salvador
2013-03-29 22:07   ` Paul Eggleton
2013-03-29 22:07     ` [OE-core] " Paul Eggleton
2013-04-01 10:47 ` Joe MacDonald
2013-04-01 11:57   ` Paul Eggleton
2013-04-01 11:57     ` [OE-core] " Paul Eggleton
2013-04-01 13:06     ` Joe MacDonald [this message]
2013-04-04 15:01 ` Nicolas Dechesne
2013-04-04 15:01   ` [OE-core] " Nicolas Dechesne
2013-04-04 15:23   ` Paul Eggleton
2013-04-04 15:23     ` [OE-core] " Paul Eggleton
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=20130401130600.GE10672@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 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.