From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: OEDEM: Summary of 'OE and Poky', 'Hosting', 'Bugtracker'
Date: Tue, 10 Nov 2009 14:07:26 +0100 [thread overview]
Message-ID: <1257858446.3077.3.camel@opal> (raw)
===========
Poky and OE
===========
RP still works on Poky, since Poky is easier to break, RP has more
freedom to break stuff and try new ideas for improvements that will
also benefit OE.
Intel owns Poky as the brandname, however there seems to be no clear
direction right now where they want to take it.
OE is being improved gradually to support the merits of Poky, although
due to the sheer amount of recipes it will probably always lack behind
in perceived quality. OE and Poky do try to remain in sync, though.
As a product, it is important for Poky to have a short list of
people with commit access. This already adds up to the quality of the
metadata. The dictator model works for Poky, but does not work for OE.
It is noted that the current dev process does not work particularly
well,
some people think it is too easy to get commit access to OE.
(Editor's note: See also stable branch session)
=======================================
Hosting
=======================================
The prefix of the member's mailinglist has been removed, reply-to-list
has been enabled. Various people work on getting the remaining services
on amethyst to work on LTG (which is a powerful machine these days).
Phil and Phillip are improving the server configuration to get rid
of our mail/DNS problems.
We will do changes on the git layout, e.g. org.oe.dev is becoming
'master'
and user branches will live in a seperate repository.
=======================================
Bugtracker
=======================================
We will keep the bugtracker, but perform a radical cleanup, i.e.
all non-OE and non-BB versions/milestones/components will be dumped.
We will improve the description of what belongs into the bugtracker
and what not. We will also reinstatiate the bug squashing weekends.
Cheers,
:M:
next reply other threads:[~2009-11-10 13:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 13:07 Michael 'Mickey' Lauer [this message]
2009-11-10 13:27 ` OEDEM: Summary of 'OE and Poky', 'Hosting', 'Bugtracker' Stefan Schmidt
2009-11-10 14:35 ` Esben Haabendal
2009-11-10 15:09 ` Stefan Schmidt
2009-11-10 14:38 ` Otavio Salvador
2009-11-10 15:06 ` Esben Haabendal
2009-11-10 14:50 ` Michael 'Mickey' Lauer
2009-11-10 15:14 ` Stefan Schmidt
2009-11-10 15:38 ` Richard Purdie
2009-11-10 15:54 ` Stefan Schmidt
2009-11-10 15:52 ` Michael 'Mickey' Lauer
[not found] ` <be7a9f3d0911100914o45d3526fufb4338966b9cdc33@mail.gmail.com>
2009-11-10 17:19 ` Otavio Salvador
2009-11-10 18:35 ` Esben Haabendal
2009-11-11 1:07 ` Holger Hans Peter Freyther
2009-11-11 8:29 ` Phil Blundell
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=1257858446.3077.3.camel@opal \
--to=mickey@vanille-media.de \
--cc=openembedded-devel@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.