Openembedded.org - User contributions [en]

OEDEM2025

2025-08-24T08:12:14Z

Halstead: Not sure why Philip removed me. Trying again.

==Sponsors==

Thanks to our sponsors for helping out with the food for the meeting.

Morning coffee and snacks - [https://redwiretechnologies.us/ Redwire Technologies]

Lunch - [https://www.konsulko.com/ Konsulko]

Afternoon snacks and coffee - [https://pengutronix.de/en/index.html Pengutronix]

Dinner - Qualcomm (food only, you pay for drinks)

==Location and time==

The venue is [https://hotelarena.nl/en/ Hotel Arena] at

Gravesandestraat 55
1092 AA Amsterdam
The Netherlands

The meeting starts at 1000 on August 24, 2025 and runs until we are done, or until 1800 when we have to leave.

==Registration==

Registration is handled at https://pretix.eu/OpenEmbedded/oedem25/

Currently the ticket shop shows the room as full. You can join the waiting list if you are interested and we will try and get people to free up tickets if they can not make it.

==Agenda==

* config file handling on R/O systems, hermetic /usr, https://uapi-group.org/specifications/specs/configuration_files_specification/ (Jan Lübbe)
* handling of static users across distros, https://www.freedesktop.org/software/systemd/man/latest/sysusers.d.html (Jan Lübbe)
* boot phase variable naming (Jon Mason)
* What comes after Sato (Ross Burton)
* Megan leads a game to find out how we feel about various parts of the ecosystem, with discussion (Megan)
* Future developer meetings. What do people want, what does the project need, how do we make these happen? Should we do at 20'th anniversary developer meeting in Berlin next year? (Philip)
* Email is becoming less reliable. Emails from pretix are going to spam, making it hard to organize this meeting. Patches end up tagged as spam by groups.io. Moving forward, what steps can we take to improve communication. Add tools you think might be useful below.(Philip)
** https://community.tmpdir.org/ (Discourse)
* meta-security future plans: user's feedback (Marta & Scott)
* Addressing CRA requirements (secure by default) (Marta)
* bitbake-setup: How do we make progress? What will encourage users to give it a try? (Tim)
* Application cross-development challenging (and therefore prefer Debian). Update and discussion about latest improvements related to SDKs and IDE's (Adrian)

==Dinner==

Add your name here if you are interested in dinner after the meeting. Koen has a reservation at Shiva at 1900.

# Jon Mason
# Koen Kooi
# Jose Quaresma
# Peter Kjellerstedt
# Jan Lübbe
# Michael Olbrich
# Marta Rybczynska
# Michael Opdenacker (arriving around 20:15)
# Joshua Watt
# Chuck Wolber
# Karey Wolber
# Scott Murray
# Vyacheslav Yurkov (Slava)
# Iben Ahlström
# Piotr Buliński
# Philip Balister
# Alexander Sverdlin
# Alessandro Zini
# Stefan Gloor
# Adrian Freihofer
# Nynke Zandstra
# Tim Orling
# Patrick Wicki
# Megan Knight
# Cory Hisey
# Peter Johennecken
# Kaiwan Billimoria
# Michael Halstead

===Recommended Restaurants===
* [https://www.shivarestaurant.nl/ Shiva] (Indian Food)

===Recommended bars/pubs===
* https://wynand-fockink.nl/

==Minutes==

==A Photo from the first OEDEM==
[[File:OEDEM2006.jpeg]]

[[Category:OEDEM]]

OEDEM2025

2025-08-24T08:08:12Z

Halstead: add category

==Sponsors==

Thanks to our sponsors for helping out with the food for the meeting.

Morning coffee and snacks - [https://redwiretechnologies.us/ Redwire Technologies]

Lunch - [https://www.konsulko.com/ Konsulko]

Afternoon snacks and coffee - [https://pengutronix.de/en/index.html Pengutronix]

Dinner - Qualcomm (food only, you pay for drinks)

==Location and time==

The venue is [https://hotelarena.nl/en/ Hotel Arena] at

Gravesandestraat 55
1092 AA Amsterdam
The Netherlands

The meeting starts at 1000 on August 24, 2025 and runs until we are done, or until 1800 when we have to leave.

==Registration==

Registration is handled at https://pretix.eu/OpenEmbedded/oedem25/

Currently the ticket shop shows the room as full. You can join the waiting list if you are interested and we will try and get people to free up tickets if they can not make it.

==Agenda==

* config file handling on R/O systems, hermetic /usr, https://uapi-group.org/specifications/specs/configuration_files_specification/ (Jan Lübbe)
* handling of static users across distros, https://www.freedesktop.org/software/systemd/man/latest/sysusers.d.html (Jan Lübbe)
* boot phase variable naming (Jon Mason)
* What comes after Sato (Ross Burton)
* Megan leads a game to find out how we feel about various parts of the ecosystem, with discussion (Megan)
* Future developer meetings. What do people want, what does the project need, how do we make these happen? Should we do at 20'th anniversary developer meeting in Berlin next year? (Philip)
* Email is becoming less reliable. Emails from pretix are going to spam, making it hard to organize this meeting. Patches end up tagged as spam by groups.io. Moving forward, what steps can we take to improve communication. Add tools you think might be useful below.(Philip)
** https://community.tmpdir.org/ (Discourse)
* meta-security future plans: user's feedback (Marta & Scott)
* Addressing CRA requirements (secure by default) (Marta)
* bitbake-setup: How do we make progress? What will encourage users to give it a try? (Tim)
* Application cross-development challenging (and therefore prefer Debian). Update and discussion about latest improvements related to SDKs and IDE's (Adrian)

==Dinner==

Add your name here if you are interested in dinner after the meeting. Koen has a reservation at Shiva at 1900.

# Jon Mason
# Koen Kooi
# Jose Quaresma
# Peter Kjellerstedt
# Jan Lübbe
# Michael Olbrich
# Marta Rybczynska
# Michael Opdenacker (arriving around 20:15)
# Joshua Watt
# Chuck Wolber
# Karey Wolber
# Scott Murray
# Vyacheslav Yurkov (Slava)
# Iben Ahlström
# Piotr Buliński
# Philip Balister
# Alexander Sverdlin
# Alessandro Zini
# Stefan Gloor
# Adrian Freihofer
# Nynke Zandstra
# Tim Orling
# Patrick Wicki
# Megan Knight
# Cory Hisey
# Peter Johennecken
# Kaiwan Billimoria

===Recommended Restaurants===
* [https://www.shivarestaurant.nl/ Shiva] (Indian Food)

===Recommended bars/pubs===
* https://wynand-fockink.nl/

==Minutes==

==A Photo from the first OEDEM==
[[File:OEDEM2006.jpeg]]

[[Category:OEDEM]]

OEDEM2025

2025-08-23T16:54:44Z

Halstead: /* Dinner */

Patchwork

2023-10-03T20:17:06Z

Halstead:

[http://ozlabs.org/~jk/projects/patchwork/ Patchwork] is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project.

The OpenEmbedded Patchwork installation has been superseded by https://patchwork.yoctoproject.org/. The installation is accessible by the link in the navigation bar under ''oe services''.

== Apply patches ==

To apply a patch from the [https://patchwork.yoctoproject.org/ patchwork queue] using [[Git]], download the mbox file and apply it using
git am < file

If the submitter of the patch has not written the ''Subject'' of the email according to the OpenEmbedded policy for commit messages, then use
git commit --amend
to edit the commit message before you push.

== Outdated ==
Information past this point is outdated and will be removed or updated soon
----

You could also use the script in [https://git.openembedded.org/openembedded/tree/contrib/patchwork/pw-am.sh contrib/patchwork/pw-am.sh] this script will fetch an 'mbox' patch from patchwork and git am it
usage: pw-am.sh <number1> <number2> ...
example: 'pw-am.sh 12 13' will get the patch from http://patchwork.openembedded.org/patch/12/
and http://patchwork.openembedded.org/patch/13/

It is desirable to update the state of the patch in the patch queue. This could also be added to the script.

== Multiple layers sharing the same oe project on patchwork ==

http://patchwork.openembedded.org/project/oe/list/
is populated from openembedded-devel ML and shared by multiple projects, each project usually defines prefix which should be used when sending patches to ML ([meta-layer-name] tag should be used).

In order to keep main page clean, patches are split to multiple bundles, current list is:
* [http://patchwork.openembedded.org/bundle/jama/2011.03-maintenance/?archive=both 2011.03-maintenance]
* [http://patchwork.openembedded.org/bundle/jama/daisy/?archive=both daisy]
* [http://patchwork.openembedded.org/bundle/jama/danny/?archive=both danny]
* [http://patchwork.openembedded.org/bundle/jama/denzil/?archive=both denzil]
* [http://patchwork.openembedded.org/bundle/jama/dizzy/?archive=both dizzy]
* [http://patchwork.openembedded.org/bundle/jama/dora/?archive=both dora]
* [http://patchwork.openembedded.org/bundle/jama/dylan/?archive=both dylan]
* [http://patchwork.openembedded.org/bundle/jama/fido/?archive=both fido]
* [http://patchwork.openembedded.org/bundle/jama/jethro/?archive=both jethro]
* [http://patchwork.openembedded.org/bundle/jama/krogoth/?archive=both krogoth]
* [http://patchwork.openembedded.org/bundle/jama/master-next/?archive=both master-next]
* [http://patchwork.openembedded.org/bundle/jama/meta-browser/?archive=both meta-browser]
* [http://patchwork.openembedded.org/bundle/jama/meta-efl/?archive=both meta-efl]
* [http://patchwork.openembedded.org/bundle/jama/meta-erlang/?archive=both meta-erlang]
* [http://patchwork.openembedded.org/bundle/jama/meta-filesystems/?archive=both meta-filesystems]
* [http://patchwork.openembedded.org/bundle/jama/meta-foss-openswitch/?archive=both meta-foss-openswitch]
* [http://patchwork.openembedded.org/bundle/jama/meta-fsl-arm/?archive=both meta-fsl-arm]
* [http://patchwork.openembedded.org/bundle/jama/meta-games/?archive=both meta-games]
* [http://patchwork.openembedded.org/bundle/jama/meta-gumstix/?archive=both meta-gumstix]
* [http://patchwork.openembedded.org/bundle/jama/meta-handheld/?archive=both meta-handheld]
* [http://patchwork.openembedded.org/bundle/jama/meta-initramfs/?archive=both meta-initramfs]
* [http://patchwork.openembedded.org/bundle/jama/meta-intel-iot-middleware/?archive=both meta-intel-iot-middleware]
* [http://patchwork.openembedded.org/bundle/jama/meta-java/?archive=both meta-java]
* [http://patchwork.openembedded.org/bundle/jama/meta-kde/?archive=both meta-kde]
* [http://patchwork.openembedded.org/bundle/jama/meta-networking/?archive=both meta-networking]
* [http://patchwork.openembedded.org/bundle/jama/meta-opie/?archive=both meta-opie]
* [http://patchwork.openembedded.org/bundle/jama/meta-perl/?archive=both meta-perl]
* [http://patchwork.openembedded.org/bundle/jama/meta-qt3/?archive=both meta-qt3]
* [http://patchwork.openembedded.org/bundle/jama/meta-qt4/?archive=both meta-qt4]
* [http://patchwork.openembedded.org/bundle/jama/meta-qt5/?archive=both meta-qt5]
* [http://patchwork.openembedded.org/bundle/jama/meta-raspberrypi/?archive=both meta-raspberrypi]
* [http://patchwork.openembedded.org/bundle/jama/meta-security/?archive=both meta-security]
* [http://patchwork.openembedded.org/bundle/jama/meta-systemd/?archive=both meta-systemd]
* [http://patchwork.openembedded.org/bundle/jama/meta-webserver/?archive=both meta-webserver]
* [http://patchwork.openembedded.org/bundle/jama/morty/?archive=both morty]
* [http://patchwork.openembedded.org/bundle/jama/oe-classic/?archive=both oe-classic]
* [http://patchwork.openembedded.org/bundle/jama/oe-classic-lic/?archive=both oe-classic-lic]
* [http://patchwork.openembedded.org/bundle/jama/toolchain-layer/?archive=both toolchain-layer]

master-next bundle is used for meta-efl meta-gnome meta-gpe meta-multimedia meta-oe meta-ruby meta-systemd meta-xfce changes when they are moved to jenkins build for verification build (meta-oe-contrib/jansa/master branch).

When some patch is moved to bundle it's archive status is set to archived, but state is still "New". That's why you need to change default filter to see archived patches in bundles.

== Update the state of patches ==

You have to register to be able to update the state of patches. You can use the Web interface, through an email message containing an appropriately formatted string for this purpose, or `pwclient`.

=== Edit patch state through a string in email message ===

Series submitter and project maintainers can change a patch state by including a string at the end of an email message sent as reply to either the original email message or to any message in the thread. The string must be in the following format (including square brackets):

[Patchwork-Status: <new-state>]

where <new-state> can be any of the existing states (excepting Accepted).

== pwclient ==

`pwclient` can be used for example to retrieve patches, search the queue or update the state.

All necessary information for `pwclient` is linked from the bottom of http://patchwork.openembedded.org/project/oe/. Use

./pwclient --help

for an overview on how to use it.

[[Category:Dev]]
[[Category:Community]]

Patchwork

2023-10-03T20:16:31Z

Halstead: Prepare to remove patchwork info

[http://ozlabs.org/~jk/projects/patchwork/ Patchwork] is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project.

The OpenEmbedded Patchwork installation has been superseded by https://patchwork.yoctoproject.org/. The installation is accessible by the link in the navigation bar under ''oe services''.

== Apply patches ==

To apply a patch from the [https://patchwork.yoctoproject.org/ patchwork queue] using [[Git]], download the mbox file and apply it using
git am < file

If the submitter of the patch has not written the ''Subject'' of the email according to the OpenEmbedded policy for commit messages, then use
git commit --amend
to edit the commit message before you push.

Information past this point is outdated and will be removed or updated soon
----

You could also use the script in [https://git.openembedded.org/openembedded/tree/contrib/patchwork/pw-am.sh contrib/patchwork/pw-am.sh] this script will fetch an 'mbox' patch from patchwork and git am it
usage: pw-am.sh <number1> <number2> ...
example: 'pw-am.sh 12 13' will get the patch from http://patchwork.openembedded.org/patch/12/
and http://patchwork.openembedded.org/patch/13/

It is desirable to update the state of the patch in the patch queue. This could also be added to the script.

== Multiple layers sharing the same oe project on patchwork ==

http://patchwork.openembedded.org/project/oe/list/
is populated from openembedded-devel ML and shared by multiple projects, each project usually defines prefix which should be used when sending patches to ML ([meta-layer-name] tag should be used).

In order to keep main page clean, patches are split to multiple bundles, current list is:
* [http://patchwork.openembedded.org/bundle/jama/2011.03-maintenance/?archive=both 2011.03-maintenance]
* [http://patchwork.openembedded.org/bundle/jama/daisy/?archive=both daisy]
* [http://patchwork.openembedded.org/bundle/jama/danny/?archive=both danny]
* [http://patchwork.openembedded.org/bundle/jama/denzil/?archive=both denzil]
* [http://patchwork.openembedded.org/bundle/jama/dizzy/?archive=both dizzy]
* [http://patchwork.openembedded.org/bundle/jama/dora/?archive=both dora]
* [http://patchwork.openembedded.org/bundle/jama/dylan/?archive=both dylan]
* [http://patchwork.openembedded.org/bundle/jama/fido/?archive=both fido]
* [http://patchwork.openembedded.org/bundle/jama/jethro/?archive=both jethro]
* [http://patchwork.openembedded.org/bundle/jama/krogoth/?archive=both krogoth]
* [http://patchwork.openembedded.org/bundle/jama/master-next/?archive=both master-next]
* [http://patchwork.openembedded.org/bundle/jama/meta-browser/?archive=both meta-browser]
* [http://patchwork.openembedded.org/bundle/jama/meta-efl/?archive=both meta-efl]
* [http://patchwork.openembedded.org/bundle/jama/meta-erlang/?archive=both meta-erlang]
* [http://patchwork.openembedded.org/bundle/jama/meta-filesystems/?archive=both meta-filesystems]
* [http://patchwork.openembedded.org/bundle/jama/meta-foss-openswitch/?archive=both meta-foss-openswitch]
* [http://patchwork.openembedded.org/bundle/jama/meta-fsl-arm/?archive=both meta-fsl-arm]
* [http://patchwork.openembedded.org/bundle/jama/meta-games/?archive=both meta-games]
* [http://patchwork.openembedded.org/bundle/jama/meta-gumstix/?archive=both meta-gumstix]
* [http://patchwork.openembedded.org/bundle/jama/meta-handheld/?archive=both meta-handheld]
* [http://patchwork.openembedded.org/bundle/jama/meta-initramfs/?archive=both meta-initramfs]
* [http://patchwork.openembedded.org/bundle/jama/meta-intel-iot-middleware/?archive=both meta-intel-iot-middleware]
* [http://patchwork.openembedded.org/bundle/jama/meta-java/?archive=both meta-java]
* [http://patchwork.openembedded.org/bundle/jama/meta-kde/?archive=both meta-kde]
* [http://patchwork.openembedded.org/bundle/jama/meta-networking/?archive=both meta-networking]
* [http://patchwork.openembedded.org/bundle/jama/meta-opie/?archive=both meta-opie]
* [http://patchwork.openembedded.org/bundle/jama/meta-perl/?archive=both meta-perl]
* [http://patchwork.openembedded.org/bundle/jama/meta-qt3/?archive=both meta-qt3]
* [http://patchwork.openembedded.org/bundle/jama/meta-qt4/?archive=both meta-qt4]
* [http://patchwork.openembedded.org/bundle/jama/meta-qt5/?archive=both meta-qt5]
* [http://patchwork.openembedded.org/bundle/jama/meta-raspberrypi/?archive=both meta-raspberrypi]
* [http://patchwork.openembedded.org/bundle/jama/meta-security/?archive=both meta-security]
* [http://patchwork.openembedded.org/bundle/jama/meta-systemd/?archive=both meta-systemd]
* [http://patchwork.openembedded.org/bundle/jama/meta-webserver/?archive=both meta-webserver]
* [http://patchwork.openembedded.org/bundle/jama/morty/?archive=both morty]
* [http://patchwork.openembedded.org/bundle/jama/oe-classic/?archive=both oe-classic]
* [http://patchwork.openembedded.org/bundle/jama/oe-classic-lic/?archive=both oe-classic-lic]
* [http://patchwork.openembedded.org/bundle/jama/toolchain-layer/?archive=both toolchain-layer]

master-next bundle is used for meta-efl meta-gnome meta-gpe meta-multimedia meta-oe meta-ruby meta-systemd meta-xfce changes when they are moved to jenkins build for verification build (meta-oe-contrib/jansa/master branch).

When some patch is moved to bundle it's archive status is set to archived, but state is still "New". That's why you need to change default filter to see archived patches in bundles.

== Update the state of patches ==

You have to register to be able to update the state of patches. You can use the Web interface, through an email message containing an appropriately formatted string for this purpose, or `pwclient`.

=== Edit patch state through a string in email message ===

Series submitter and project maintainers can change a patch state by including a string at the end of an email message sent as reply to either the original email message or to any message in the thread. The string must be in the following format (including square brackets):

[Patchwork-Status: <new-state>]

where <new-state> can be any of the existing states (excepting Accepted).

== pwclient ==

`pwclient` can be used for example to retrieve patches, search the queue or update the state.

All necessary information for `pwclient` is linked from the bottom of http://patchwork.openembedded.org/project/oe/. Use

./pwclient --help

for an overview on how to use it.

[[Category:Dev]]
[[Category:Community]]

How to submit a patch to OpenEmbedded

2021-10-28T23:23:23Z

Halstead:

OpenEmbedded welcomes contributions. Before submitting a patch however there are a few things to keep in mind.

== Finding the right place for your patch ==

OpenEmbedded is now split up into separate layers: OpenEmbedded-Core (OE-Core) which is a small set of core recipes, and other layers for recipes beyond that. For most layers, patches are sent to a mailing list for review before being merged. For further information specific to the layer you're working on, please see the README file in the layer.

New recipes in particular should be added to the appropriate layer. See the [http://layers.openembedded.org layer index] for the list of public layers. If your new recipe doesn't seem to fit anywhere it can be added to the meta-oe layer in the meta-openembedded repository, although if it is likely to be followed by numbers of similar recipes then you may wish to consider [[Creating a new Layer|creating a new layer]].

== A task-oriented guide to creating a patch ==

Let's say you have made a fix to a recipe, you've tested that it works and you'd like to submit it for merging.

=== Set up git ===

Properly configuring git (using tekkub@gmail.com as an example user)

On Debian / Ubuntu (Note: Fedora uses `yum` OpenSuse uses zypper or yast)

sudo aptitude install git-core git-email

These are important to the commit meta-data

git config --global user.name "Tekkub"
git config --global user.email "tekkub@gmail.com"

Any Google Apps account

git config --global sendemail.smtpserver smtp.gmail.com
git config --global sendemail.smtpserverport 587
git config --global sendemail.smtpencryption tls
git config --global sendemail.smtpuser tekkupl@gmail.com

You can use the --envelope-sender option to have the email appear from the address you are subscribed to the list with. You will need to use the Accounts and import tab under the gmail settings tab. Use the Send mail as selection to address you want to send email from.

=== Subscribe to the mailing list ===

You need to subscribe to the appropriate mailing-list in order to be able to send your patch(es) there; for patches against OE-Core the mailing list is '''openembedded-core@lists.openembedded.org''' and for patches against meta-oe and many other layers the list is '''openembedded-devel@lists.openembedded.org'''. See [[Mailing lists]] for subscription and further details.

=== Committing your patch ===

Commit with a concise and descriptive message - one that explains your changes in a way others get a short overview without looking at the code.

cd oe-core/ # or whereever you keep your clone of the repo
git add meta/recipes-devtools/flex
git commit -s # don't use the -m option but include my signature

flex: backport Debian patches to fix generated code warnings

The generated parser had warnings regarding signess and return check
which makes Linux Kernel's perf tool from 3.4 release to fail without
those patches.

All commit messages must include Signed-off-by (-s option to commit as above). For more guidelines on messages please see [[Commit Patch Message Guidelines]].

Note that when adding multiple new recipes, each recipe should be added in a separate commit. For upgrades of existing recipes, the previous version should usually be deleted as part of the same commit to add the upgraded version.

=== Sending patches ===

There are two possible methods for submitting patches. Either one is acceptable; for a series containing a number of patches the pull request method is preferred although not mandatory.

==== Sending using git-send-email ====

To send just the top commit on your current branch (substitute mailing list address as appropriate):

git send-email --to=openembedded-core@lists.openembedded.org --confirm=always -M -1

For multiple commits you can substitute -1 above with -N (where N is the number of commits) or instead specify a revision before which to start e.g. HEAD~3, master etc.

Note: in either case if you are submitting a patch for meta-oe or any layer other than OE-Core, please add the appropriate prefix so that it is clear which layer the patch is intended to be applied to:
--subject-prefix="meta-oe][PATCH"

Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)

==== Sending via a pull request ====

Alternatively, for larger patch series it is preferable to send a pull request which not only includes the patch but also a pointer to a branch that can be pulled from. This involves making a local branch for your changes, pushing this branch to an accessible repository and then using the <code>create-pull-request</code> and <code>send-pull-request</code> scripts (supplied with OE-Core) to create and send a patch series with a link to the branch for review. Step-by-step instructions:

# Find a repository to push your changes to, and add this as a remote to your git working tree. If you're going to be submitting a lot of changes, some of the repositories have a corresponding <code>-contrib</code> repository which you can use for this purpose - access to these for OE-related work is open to anyone who requests it. Otherwise github or some other public git hosting service can suffice.
# Create a branch for your changes if you haven't already. Other than backports from master or fixing bugs that only occur in an older branch, this should be on top of the master branch.
# Push the branch to the remote.
# Run <code>scripts/create-pull-request -u remote-name</code> (where <code>remote-name</code> is the name of the remote where you'll be pushing the branch). For meta-oe and other layers where a single mailing list covers more than one layer you'll need to add <code>-p "layername][PATCH"</code> replacing layername with the name of the layer so that it is clear which layer the patches are intended for.
# The script will report that it has created a <code>pull-XXXXX</code> directory has been created. Edit the <code>pull-XXXXX/0000-cover-letter.patch</code> with your favourite text editor and change the title and top of the body as appropriate.
# Run <code>scripts/send-pull-request -p pull-XXXXX -t openembedded-core@lists.openembedded.org</code> (replacing openembedded-core@lists.openembedded.org with the appropriate mailing list address for layers other than OE-Core). Where there is a clear maintainer for the area you're changing it may also help to add <code>-C maintainer@example.com</code>.

===== Request OE contrib Write Access =====

please send an email to [mailto:mhalstead@linuxfoundation.org Michael Halstead] and:
# Attach your ssh '''public''' key which usually named id_rsa.pub. If you don't have one generate it by running <tt>ssh-keygen -t rsa -b 4096 -C "your_email@example.com"</tt>.
# List the repositories you're planning to contribute to.
# Include your preferred branch prefix for *-contrib repositories.

=== Backporting fixes to stable releases ===

When a bug is present on a stable branch of OE yet has been fixed in master one can request that the stable branch's maintainer accept the fix into the stable branch.
The best way to do this is generate a patch with the backport and submit it to the openembedded-core@lists.openembedded.org mailing list (CC'ing the maintainer may help the patch be reviewed for inclusion more quickly).

Patches for stable branches should be prefixed with the branch name (which is the same as the release series name), for example morty, pyro, etc.
Once you've identified the commit hash of the patch you'd like to see accepted as a backport you can generate the patch with:

git format-patch <COMMIT_HASH> -1 --subject-prefix="<BRANCH_NAME>][PATCH"

The generated patch can then be sent using the procedure described above.

== Community review ==

Your patch will be sent to the mailing list and for some layers should be immediately visible on http://patches.openembedded.org/

If you get feedback in reply to your patch, you should make changes according to the feedback and submit the next version. Please remember to use <code>--subject-prefix="PATCH v2"</code>, v3, v4 etc. to mark the patch iteration. Please also '''test your revised changes''' - in particular don't just edit the patch file written out by git-format-patch and resend it.

If your patch has not had any feedback after a few days it may have been missed or the appropriate reviewers may not currently be around; it is perfectly fine to reply to it yourself with a "ping" / reminder request for feedback. NOTE: patch review for feature / recipe upgrade patches will likely be delayed during a feature freeze because these types of patches aren't merged during this time - you may have to wait until after the freeze is lifted.

== Appendix ==

=== Steps for people which don't have SMTP access for git ===

Patches should not be sent as attachment but inline.

If you do not have SMTP access to your email account you have two options:

1. Use a different account (e.g. gmail). you can make one especially for this. Note that the account may differ from the one in signed-off (although that is inconvenient)

2. Just include the patch in the body of your email. Make sure you use an email client that does not touch the message (turn spaces in tabs,
wrap lines etc etc).

A good mail client to do so is '''pine''' (or '''alpine''') or '''mutt'''. For more information refer to [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/email-clients.txt Documentation/email-clients.txt] in linux kernel sources.

=== Streamlining git-send-email with configuration ===

Don't want to have to remember to specify the right options when using git-send-email (or the pull request script)? You can actually set these in git's configuration and save yourself a lot of hassle.

<ul>
<li>Always confirm sending (for all repositories):
<pre>git config --global sendemail.confirm always</pre></li>
<li>Set send-to email address for the repository (don't forget to specify the right address!):
<pre>git config --local sendemail.to openembedded-devel@lists.openembedded.org</pre>
</li>
<li>If the mailing list requires a subject prefix for the layer (only works when the repository only contains one layer; set layer name as appropriate):
<pre>git config --local format.subjectprefix "meta-something][PATCH"</pre>
</li>
</ul>

==See also==
* [[Commit Patch Message Guidelines]]
* [[Styleguide]]

[[Category:FAQ]]
[[Category:User]]

User talk:Alejandro

2021-06-02T17:04:33Z

Halstead: Welcome!

'''Welcome to ''Openembedded.org''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:Halstead|Halstead]] ([[User talk:Halstead|talk]]) 17:04, 2 June 2021 (UTC)

User:Alejandro

2021-06-02T17:04:33Z

Halstead: Creating user page for new user.

OE Developer at MS

User talk:Michael Opdenacker

2021-06-02T17:03:56Z

Halstead: Welcome!

User:Michael Opdenacker

2021-06-02T17:03:56Z

Halstead: Creating user page for new user.

Michael Opdenacker is the founder of Bootlin, a service company specializing in Free and Open Source Software for embedded systems, and a heavy user of the Yocto Project. Michael is contributing to the Yocto Project documentation.

Mailing lists

2020-04-21T16:05:58Z

Halstead: Update info for groups.io

{| class="wikitable" border="2"
|| '''Email address of list''' || '''Purpose''' || '''Subscribe and view archives'''
|-
||openembedded-core@lists.openembedded.org || General discussion & [[How_to_submit_a_patch_to_OpenEmbedded|patch submission]] for [[OpenEmbedded-Core|OE-Core]] || [https://lists.openembedded.org/g/openembedded-core join+archives]
|-
||openembedded-devel@lists.openembedded.org || General discussion & patch submission for other meta layers || [https://lists.openembedded.org/g/openembedded-devel join+archives]
|-
|-
||openembedded-architecture@lists.openembedded.org || Discussions about overall OpenEmbedded Architecture and Status || [https://lists.openembedded.org/g/openembedded-architecture join+archives]
|-
||openembedded-commits@lists.openembedded.org || Git commits || [https://lists.openembedded.org/g/openembedded-commits join+archives]
|-
||bitbake-devel@lists.openembedded.org || Bitbake developers mailing list || [https://lists.openembedded.org/g/bitbake-devel join+archives]
|-
||<strike>openembedded-users@lists.openembedded.org</strike>|| User discussion (defunct - use openembedded-devel) || [http://lists.openembedded.org/pipermail/openembedded-users/ archives]
|-
||<strike>openembedded-issues@lists.openembedded.org</strike>|| Bug tracker status updates (defunct) || [http://lists.openembedded.org/pipermail/openembedded-issues/ archives]
|-
||<strike>openembedded-stablebranch@lists.openembedded.org</strike> || Discussion about the stable branch (defunct) ||
|}

<nowiki>
* denotes a searchable archive including an interactive tree view for threads (might not work with all types of browsers)
</nowiki>

[[Category:Community]]

GroupsMigration

2020-03-21T00:52:15Z

Halstead: Post migration edit

On March 20th 2020 OE moved from self-managed Mailman to the Groups.io platform, which provides mailing list services in a simple but modern interface. Groups.io offers all of the capabilities of our existing Mailman mailing service plus additional community tools that make it an exceptional service solution.

====What are the key differences between Mailman and Groups.io?====

* Groups.io has a modern interface, robust user security model, and interactive, searchable archives

* Groups.io provides advanced features including muting threads and integrations with modern tools like GitHub, Slack, and Trello

* Groups.io also has optional extras like a shared calendar, polling, chat, a wiki, and more

* Groups.io uses a concept of subgroups, where members first join the project “group” (a master list, normally called "main"), then they choose the specific “subgroup” lists they want to subscribe to

====How is the experience different for me as a list moderator or participant?====

In many ways, it is very much the same. Moderation is much more streamlined. If you interaction primarily via your e-mail client you won't notice a change at all. Some From headers will be re-written to pass DMARC. This will require maintainers to alter author information before applying patches. We've added hooks to the git server to prevent bad author info from making it into the repositories.

====Where do I find the settings and owner/moderator tools?====

To change settings while in a group or subgroup, left click “Admin” from the side menu.

Then from “Admin” you can select:

“Settings” to change overall settings for a group, including privacy and message policy settings.

“Members” to manage people within a group, including adjusting their role and privileges

“Pending” to view messages pending moderation

If you’d like to learn more about using Groups.io , please [https://groups.io/static/help reference their help documentation].

====What about outstanding messages and subscriptions in the moderation queue?====

Pending memberships or posts (and similar pending moderation actions) in Mailman were not preserved in this migration. Most list owners cleaned up their queues shortly before the migration so very little was discarded.

==== I sent a message during the migration. Will is arrive?====

Messages sent to the mailing lists during the migration window will take one to several hours to arrive depending on your mail server configuration. No messages were accepted by the mail server that did not make it into the migration.

====What about outstanding links to the pipermail archives?====

The current archives available as they are at a new URL. For example:

https://lists.openembedded.org/pipermail/openembedded-devel/2020-March/date.html -> https://www.openembedded.org/pipermail/openembedded-devel/2020-March/date.html

Existing archives have been imported into groups.io and are available to browse there.

====Reply-to header changes====

Currently openembedded-commits@lists.openembedded.org reply-to is set to openembedded-devel@lists.openembedded.org. After the migration replies will go to sender.

====Automated e-mail sent from non-receiving addresses====

Any e-mail needs to come from an address that can receive e-mail. If you have a long-standing automated process it might be possible to whitelist certain non-receiving addresses. Reach out directly about this.

====Who can help in case of issue? / My question isn't answered here. What should I do?====

If you are facing any issue related to the Groups.io migration or have an unaddressed question, please e-mail pointofcontact@lists.yoctoproject.org. Yocto Project admins manage the current Mailman lists and are helping with the migration.

GroupsMigration

2020-03-13T20:01:18Z

Halstead:

On March 20th 2020 OE will move from self-managed Mailman to Groups.io, which provides mailing list services in a simple but modern interface. Groups.io offers all of the capabilities of our existing Mailman mailing service plus additional community tools that make it an exceptional service solution.

====What are the key differences between Mailman and Groups.io?====

* Groups.io has a modern interface, robust user security model, and interactive, searchable archives

* Groups.io provides advanced features including muting threads and integrations with modern tools like GitHub, Slack, and Trello

* Groups.io also has optional extras like a shared calendar, polling, chat, a wiki, and more

* Groups.io uses a concept of subgroups, where members first join the project “group” (a master list, normally called "main"), then they choose the specific “subgroup” lists they want to subscribe to

====How is the experience different for me as a list moderator or participant?====

In many ways, it is very much the same. Moderation is much more streamlined. If you interaction primarily via your e-mail client you won't notice a change at all. Some From headers will be re-written to pass DMARC. This will require maintainers to alter author information before applying patches. We've added hooks to the git server to prevent bad author info from making it into the repositories.

====Where do I find the settings and owner/moderator tools?====

To change settings while in a group or subgroup, left click “Admin” from the side menu.

Then from “Admin” you can select:

“Settings” to change overall settings for a group, including privacy and message policy settings.

“Members” to manage people within a group, including adjusting their role and privileges

“Pending” to view messages pending moderation

If you’d like to learn more about using Groups.io , please [https://groups.io/static/help reference their help documentation].

====What about outstanding messages and subscriptions in the moderation queue?====

Pending memberships or posts (and similar pending moderation actions) in Mailman were not preserved in this migration. Most list owners cleaned up their queues shortly before the migration so very little was discarded.

==== I sent a message during the migration. Will is arrive?====

Messages sent to the mailing lists during the migration window will take one to several hours to arrive depending on your mail server configuration. No messages were accepted by the mail server that did not make it into the migration.

====What about outstanding links to the pipermail archives?====

We will make an effort to make the current archives available as they are at a new URL. Existing archives will be imported into groups.io.

====Reply-to header changes====

Currently openembedded-commits@lists.openembedded.org reply-to is set to openembedded-devel@lists.openembedded.org. After the migration replies will go to sender.

====Who can help in case of issue? / My question isn't answered here. What should I do?====

If you are facing any issue related to the Groups.io migration or have an unaddressed question, please e-mail pointofcontact@lists.yoctoproject.org. Yocto Project admins manage the current Mailman lists and are helping with the migration.

GroupsMigration

2020-03-12T17:37:56Z

Halstead: Adding Groups Migration information.

On March 20th 2020 OE will move from self-managed Mailman to Groups.io, which provides mailing list services in a simple but modern interface. Groups.io offers all of the capabilities of our existing Mailman mailing service plus additional community tools that make it an exceptional service solution.

====What are the key differences between Mailman and Groups.io?====

* Groups.io has a modern interface, robust user security model, and interactive, searchable archives

* Groups.io provides advanced features including muting threads and integrations with modern tools like GitHub, Slack, and Trello

* Groups.io also has optional extras like a shared calendar, polling, chat, a wiki, and more

* Groups.io uses a concept of subgroups, where members first join the project “group” (a master list, normally called "main"), then they choose the specific “subgroup” lists they want to subscribe to

====How is the experience different for me as a list moderator or participant?====

In many ways, it is very much the same. Moderation is much more streamlined. If you interaction primarily via your e-mail client you won't notice a change at all. Some From headers will be re-written to pass DMARC. This will require maintainers to alter author information before applying patches. We've added hooks to the git server to prevent bad author info from making it into the repositories.

====Where do I find the settings and owner/moderator tools?====

To change settings while in a group or subgroup, left click “Admin” from the side menu.

Then from “Admin” you can select:

“Settings” to change overall settings for a group, including privacy and message policy settings.

“Members” to manage people within a group, including adjusting their role and privileges

“Pending” to view messages pending moderation

If you’d like to learn more about using Groups.io , please [https://groups.io/static/help reference their help documentation].

====What about outstanding messages and subscriptions in the moderation queue?====

Pending memberships or posts (and similar pending moderation actions) in Mailman were not preserved in this migration. Most list owners cleaned up their queues shortly before the migration so very little was discarded.

==== I sent a message during the migration. Will is arrive?====

Messages sent to the mailing lists during the migration window will take one to several hours to arrive depending on your mail server configuration. No messages were accepted by the mail server that did not make it into the migration.

====What about outstanding links to the pipermail archives?====

We will make an effort to make the current archives available as they are at a new URL. Existing archives will be imported into groups.io.

====Who can help in case of issue? / My question isn't answered here. What should I do?====

If you are facing any issue related to the Groups.io migration or have an unaddressed question, please e-mail pointofcontact@lists.yoctoproject.org. Yocto Project admins manage the current Mailman lists and are helping with the migration.

OEDEM 2019

2019-10-02T17:55:32Z

Halstead: /* Planning to Attend */

== Location and Time ==

Friday, 1 November 2019 (Part of Yocto Project Summit after ELCE [October 31 - November 1]) 
OEDEM is on Day 2 of the Summit, November 1.

Details on the Yocto Project Summit are here https://wiki.yoctoproject.org/wiki/Yocto_Project_Summit_2019.
And the registration link https://www.cvent.com/events/yocto-project-summit-2019/registration-f185462e4bb240fea6364d2db7a270f4.aspx?fqp=true

== Logistics ==

== Remote conference link ==

== Planning to Attend ==

# Philip Balister (Crofton) [XL]
# Peter Kjellerstedt (Saur) [3XL]
# Ola Nilsson (olani) [M]
# Marco Cavallini (mckoan) [M]
# Jon Mason (jonmason) [L]
# Josef Holzmayr (LetoThe2nd) [XL]
# Mark Hatle (fray) [XL]
# Khem Raj (khem) [M]
# Scott Murray (smurray) [2XL]
# Matt Porter (mdp) [L]
# Michael Halstead (halstead) [L]
# Andrea Galbusera (gizero) [M]
# Paul Barker (paulbarker) [M]
# Jan-Simon Möller [2XL]
# Richard Purdie (RP) [L]
# Alexander Kanavin (kanavin) [S]
# Mauro Salvini [M]
# Manjukumar [S]
# Alejandro Hernandez [M]
# Jan Lübbe (shoragan) [XL]
# Behan Webster (behanw) [3XL]
# Ruslan Bilovol (rbilovol) [XL]
# Grygorii Tertychnyi (gtertych) [L]
# Bruce Ashfield (zeddii) [XL]
# Daniel Gomez (dagmcr) [L]
# Nicolas Dechesne (ndec) [XL]
# Mark Asselstine (marka) [L]

== Agenda Items ==

=== OE Developers Meeting ===

# Review and discuss talks from the Yocto Project Summit the day before.
# Clean-up of wiki and meta layer index
# Ways to recognize corporate sponsors and those who donate hardware (and/or money)
# T-shirts?
# How do we communicate with users better? Not everyone is on mailing lists. Social Media?
# Results of the Yocto/Openembedded new features survey (http://bit.ly/2kXvdsd)

=== Meeting minutes for OEDeM ===

== Minutes ==

SHARED MINUTES AT

ACTIONS identified in meeting:

=== Prior minutes ===

Minutes from Edinburgh, Oct 2018:
https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk/

Minutes from Portland, Mar 2018:
https://docs.google.com/document/d/1h_otwcH-6ej4URB5vER-7FpaPthrji3TpJWf5jAKRIk/edit?usp=sharing

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

OEDEM 2019

2019-09-11T14:40:53Z

Halstead:

== Location and Time ==

Friday, 1 November 2019 (Part of Yocto Project Summit after ELCE [October 31 - November 1]) 
OEDEM is on Day 2 of the Summit, November 1.

== Logistics ==

== Remote conference link ==

== Planning to Attend ==

# Philip Balister (Crofton)
# Peter Kjellerstedt (Saur)
# Ola Nilsson (olani)
# Marco Cavallini (mckoan)
# Jon Mason (jonmason)
# Josef Holzmayr (LetoThe2nd)
# Mark Hatle (fray)
# Scott Murray (smurray)
# Matt Porter (mdp)
# Michael Halstead (halstead)

== Agenda Items ==

=== OE Developers Meeting ===

# Review and discuss talks from the Yocto Project Summit the day before.

=== Meeting minutes for OEDeM ===

== Minutes ==

SHARED MINUTES AT

ACTIONS identified in meeting:

=== Prior minutes ===

Minutes from Edinburgh, Oct 2018:
https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk/

Minutes from Portland, Mar 2018:
https://docs.google.com/document/d/1h_otwcH-6ej4URB5vER-7FpaPthrji3TpJWf5jAKRIk/edit?usp=sharing

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

OEDEM 2018

2018-08-22T18:11:34Z

Halstead: /* Planning to Attend */ I'm going!

== Location and Time ==

Sunday, 21 October 2018 (before ELCE [October 22-24]) 

Expectation is to finish by 1800

Hilton Edinburgh Grosvenor
5-21 Grosvenor Street
EH12 5EF Edinburgh

SAT-NAV: EH12 5EF

5 minute walk to Haymarket Train Station

No onsite car park. Ask Crofton if you need local parking information.

== Logistics ==

Yes, we know it is Sunday. Best we could do this year.

Attendance is capped at 40. Armin is the bouncer.

== Remote conference link ==

== Planning to Attend ==

# Armpit (Akuster)
# Philip Balister (Crofton)
# Denys Dmytriyenko (denix)
# Marco Cavallini (mckoan)
# Jan Lübbe (shoragan)
# Peter Kjellerstedt (Saur)
# Jeff Osier-Mixon (Jefro)
# Scott Murray (smurray)
# Ruslan Bilovol
# Phil Blundell
# Ross Burton (rburton)
# Richard Purdie (RP)
# Richard Leitner
# Jan-Simon Möller (dl9pf)
# Koen Kooi
# Robert Berger (will join in afternoon approx. 14:00?)
# Ulrich Ölmann (OnkelUlla)
# Trevor Woerner (tlwoerner)
# Matt Porter (mdp)
# Nicolas Dechesne (ndec)
# Grygorii Tertychnyi
# Behan Webster (behanw)
# Phil Wise (cajun-rat)
# Martin Hundebøll (hundeboll)
# Tim Orling (moto-timo)
# Bill Mills
# Kate Stewart
# Jeff Morrison
# Alan Wang
# Andrea Galbusera (gizero)
# Ricardo Salveti (rsalveti)
# Christopher Clark (xtopher)
# Rich Persaud
# Michael Halstead (halstead)

== Agenda Items ==

=== OE Developers Meeting ===

== Minutes ==

SHARED MINUTES AT

ACTIONS identified in meeting:

=== Prior minutes ===

Minutes from Portland, Mar 2018:
https://docs.google.com/document/d/1h_otwcH-6ej4URB5vER-7FpaPthrji3TpJWf5jAKRIk/edit?usp=sharing

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

OEDAM 2018

2018-03-12T18:45:00Z

Halstead:

== Location and Time ==

Sunday, 11 March 2018 (before ELC [March 12-14]) 
Board meeting to happen before the event
Doors open at 10am
Developer's meeting to start at 10:30
Expectation is to finish by 1800

For those who want to commute with Armin, Please meet in the Lobby in the Hilton
where ELC is hosted at 9:30 am. I can only take 15.

Lunch and coffee are provided by the Yocto Project.

Location: Mentor Graphics Headquarters
8105 Boeckman Road, Wilsonville, OR
Evergreen Building, E2411 Training room

Lunch location is McMenamins Old Church & Pub, 30340 SW Boones Ferry Rd, Wilsonville.
Lunch will be at about 12:45.

Carpooling is encouraged, see below

== Logistics ==

Yes, we know it is Sunday. Best we could do this year.

'''Daylight Savings Time starts tomorrow''', so be sure to roll your clocks FORWARD by an hour - so 10am is actually logical 9am.

The planned start is 10:30. I am planning to arrive at 10am with coffee. It is roughly 1/2 hour drive from downtown, so please plan accordingly.

Carpooling is highly encouraged. Armin has a van rented that can take up to 15. Jefro is already picking up 2 and has room for 1-2 more. If anyone else has a vehicle and can take people, please pipe up on the email thread or send email to jefro@jefro.net. Note that an uber or lyft will be a $35 trip from downtown.

The day will need to end by 6pm. Jefro will be going back up to the Hilton at top speed to set up the Yocto booth.

== Remote conference link ==

If you are not able to be there in person, you can join this conference remotely over zoom.us:

Join URL: https://zoom.us/j/347593211

== Planning to Attend ==

Carpool note: Please add a {#} after your name if you plan to drive and can take # of people in your car other than yourself

* Jeff Osier-Mixon "Jefro" {4}
* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Sean Hudson (darknighte)
* Manjukumar Matha (manju)
* Joshua Watt (JPEWhacker)
* Zachary Booth
* Jim Lodes
* Armin Kuster (Armpit){15}
* Scott Murray (smurray)
* Tim Orling (moto-timo)
* Alejandro Hernandez (aehs29)
* Christopher Clark
* Behan Webster (behanw)
* Marek Vasut (Marex)
* Taras Kondratiuk
* Bill Mills
* Ricardo Salveti (rsalveti)
* Khem Raj (khem)
* Tom King (ka6sox)
* Rich Persaud
* Michael Halstead (halstead)
* Stephano Cetola (stephano) {1 + truck bed }
* Richard Purdie (RP)
* Marco Cavallini (mckoan)
* Mark Hatle (fray) {1}

== Agenda Items ==

=== OE Board ===
E.v status

=== OE Developers Meeting ===
# State of the Union
## Discuss meta-oe release process
## World build monitoring and automatic notifications
# Topics from GA
## Introduction
### Quick agenda overview (Sean)
### Refer to https://www.openembedded.org/wiki/2018_02_General_Meeting
## Call for Topics at OEDAM in 2018-03 in Portland
####Refer to https://www.openembedded.org/wiki/OEDAM_2018
###Layer Quality (hatle)
###Splitting meta-oe if not resolved prior to meeting (armpit)
####Patch submissions (all OE components)
###REQUEST: Identify areas where we need maintainers to help
####ptest additions to meta-oe (timo)
###REQUEST: Could someone run through a simple example to help others learn to do this correctly
####OEQA testing
###Clear need for a quickstart guide (one-page recipe to get folks started quickly)
###Running tests (individual, groups, all)
###Connecting to a Machine ( h/w)(armpit)
###FOSDEM feedback (paulbarker)
###Auto Updater ( AUH)(armpit)???
# Logistics for OEDAM in 2018-03 in Portland
## Board will facilitate putting folks needing rides and folks with spots in their cars together. (see OEDAM wiki)
## Moped balance in question… Carpooling recommended...

== Minutes ==

SHARED MINUTES AT
https://docs.google.com/document/d/1h_otwcH-6ej4URB5vER-7FpaPthrji3TpJWf5jAKRIk/edit?usp=sharing

=== Prior minutes ===

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

OEDAM 2018

2018-03-11T17:50:11Z

Halstead:

== Location and Time ==

Sunday, 11 March 2018 (before ELC [March 12-14]) 
Board meeting to happen before the event
Doors open at 10am
Developer's meeting to start at 10:30
Expectation is to finish by 1800

For those who want to commute with Armin, Please meet in the Lobby in the Hilton
where ELC is hosted at 9:30 am. I can only take 15.

Lunch and coffee are provided by the Yocto Project.

Location: Mentor Graphics Headquarters
8105 Boeckman Road, Wilsonville, OR
Evergreen Building, E2411 Training room
(E-mail mhalstead@linuxfoundation.org if you are stuck at the entrance. )

Lunch location is McMenamins Old Church & Pub, 30340 SW Boones Ferry Rd, Wilsonville.
Lunch will be at about 12:45.

Carpooling is encouraged, see below

== Logistics ==

Yes, we know it is Sunday. Best we could do this year.

'''Daylight Savings Time starts tomorrow''', so be sure to roll your clocks FORWARD by an hour - so 10am is actually logical 9am.

The planned start is 10:30. I am planning to arrive at 10am with coffee. It is roughly 1/2 hour drive from downtown, so please plan accordingly.

Carpooling is highly encouraged. Armin has a van rented that can take up to 15. Jefro is already picking up 2 and has room for 1-2 more. If anyone else has a vehicle and can take people, please pipe up on the email thread or send email to jefro@jefro.net. Note that an uber or lyft will be a $35 trip from downtown.

The day will need to end by 6pm. Jefro will be going back up to the Hilton at top speed to set up the Yocto booth.

== Remote conference link ==

If you are not able to be there in person, you can join this conference remotely over zoom.us:

Join URL: https://zoom.us/j/347593211

== Planning to Attend ==

Carpool note: Please add a {#} after your name if you plan to drive and can take # of people in your car other than yourself

* Jeff Osier-Mixon "Jefro" {4}
* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Sean Hudson (darknighte)
* Manjukumar Matha (manju)
* Joshua Watt (JPEWhacker)
* Zachary Booth
* Jim Lodes
* Armin Kuster (Armpit){15}
* Scott Murray (smurray)
* Tim Orling (moto-timo)
* Alejandro Hernandez (aehs29)
* Christopher Clark
* Behan Webster (behanw)
* Marek Vasut (Marex)
* Taras Kondratiuk
* Bill Mills
* Ricardo Salveti (rsalveti)
* Khem Raj (khem)
* Tom King (ka6sox)
* Rich Persaud
* Michael Halstead (halstead)
* Stephano Cetola (stephano) {1 + truck bed }
* Richard Purdie (RP)
* Marco Cavallini (mckoan)
* Mark Hatle (fray) {1}

== Agenda Items ==

=== OE Board ===
E.v status

=== OE Developers Meeting ===
# State of the Union
## Discuss meta-oe release process
## World build monitoring and automatic notifications
# Topics from GA
## Introduction
### Quick agenda overview (Sean)
### Refer to https://www.openembedded.org/wiki/2018_02_General_Meeting
## Call for Topics at OEDAM in 2018-03 in Portland
####Refer to https://www.openembedded.org/wiki/OEDAM_2018
###Layer Quality (hatle)
###Splitting meta-oe if not resolved prior to meeting (armpit)
####Patch submissions (all OE components)
###REQUEST: Identify areas where we need maintainers to help
####ptest additions to meta-oe (timo)
###REQUEST: Could someone run through a simple example to help others learn to do this correctly
####OEQA testing
###Clear need for a quickstart guide (one-page recipe to get folks started quickly)
###Running tests (individual, groups, all)
###Connecting to a Machine ( h/w)(armpit)
###FOSDEM feedback (paulbarker)
###Auto Updater ( AUH)(armpit)???
# Logistics for OEDAM in 2018-03 in Portland
## Board will facilitate putting folks needing rides and folks with spots in their cars together. (see OEDAM wiki)
## Moped balance in question… Carpooling recommended...

== Minutes ==

SHARED MINUTES AT
https://docs.google.com/document/d/1h_otwcH-6ej4URB5vER-7FpaPthrji3TpJWf5jAKRIk/edit?usp=sharing

=== Prior minutes ===

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

OEDAM 2018

2018-03-11T17:42:07Z

Halstead: Fix building address

== Location and Time ==

Sunday, 11 March 2018 (before ELC [March 12-14]) 
Board meeting to happen before the event
Doors open at 10am
Developer's meeting to start at 10:30
Expectation is to finish by 1800

For those who want to commute with Armin, Please meet in the Lobby in the Hilton
where ELC is hosted at 9:30 am. I can only take 15.

Lunch and coffee are provided by the Yocto Project.

Location: Mentor Graphics Headquarters
8105 Boeckman Road, Wilsonville, OR
Evergreen Building, E2411 Training room

Lunch location is McMenamins Old Church & Pub, 30340 SW Boones Ferry Rd, Wilsonville.
Lunch will be at about 12:45.

Carpooling is encouraged, see below

== Logistics ==

Yes, we know it is Sunday. Best we could do this year.

'''Daylight Savings Time starts tomorrow''', so be sure to roll your clocks FORWARD by an hour - so 10am is actually logical 9am.

The planned start is 10:30. I am planning to arrive at 10am with coffee. It is roughly 1/2 hour drive from downtown, so please plan accordingly.

Carpooling is highly encouraged. Armin has a van rented that can take up to 15. Jefro is already picking up 2 and has room for 1-2 more. If anyone else has a vehicle and can take people, please pipe up on the email thread or send email to jefro@jefro.net. Note that an uber or lyft will be a $35 trip from downtown.

The day will need to end by 6pm. Jefro will be going back up to the Hilton at top speed to set up the Yocto booth.

== Remote conference link ==

If you are not able to be there in person, you can join this conference remotely over zoom.us:

Join URL: https://zoom.us/j/347593211

== Planning to Attend ==

Carpool note: Please add a {#} after your name if you plan to drive and can take # of people in your car other than yourself

* Jeff Osier-Mixon "Jefro" {4}
* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Sean Hudson (darknighte)
* Manjukumar Matha (manju)
* Joshua Watt (JPEWhacker)
* Zachary Booth
* Jim Lodes
* Armin Kuster (Armpit){15}
* Scott Murray (smurray)
* Tim Orling (moto-timo)
* Alejandro Hernandez (aehs29)
* Christopher Clark
* Behan Webster (behanw)
* Marek Vasut (Marex)
* Taras Kondratiuk
* Bill Mills
* Ricardo Salveti (rsalveti)
* Khem Raj (khem)
* Tom King (ka6sox)
* Rich Persaud
* Michael Halstead (halstead)
* Stephano Cetola (stephano) {1 + truck bed }
* Richard Purdie (RP)
* Marco Cavallini (mckoan)

== Agenda Items ==

=== OE Board ===
E.v status

=== OE Developers Meeting ===
# State of the Union
## Discuss meta-oe release process
## World build monitoring and automatic notifications
# Topics from GA
## Introduction
### Quick agenda overview (Sean)
### Refer to https://www.openembedded.org/wiki/2018_02_General_Meeting
## Call for Topics at OEDAM in 2018-03 in Portland
####Refer to https://www.openembedded.org/wiki/OEDAM_2018
###Layer Quality (hatle)
###Splitting meta-oe if not resolved prior to meeting (armpit)
####Patch submissions (all OE components)
###REQUEST: Identify areas where we need maintainers to help
####ptest additions to meta-oe (timo)
###REQUEST: Could someone run through a simple example to help others learn to do this correctly
####OEQA testing
###Clear need for a quickstart guide (one-page recipe to get folks started quickly)
###Running tests (individual, groups, all)
###Connecting to a Machine ( h/w)(armpit)
###FOSDEM feedback (paulbarker)
###Auto Updater ( AUH)(armpit)???
# Logistics for OEDAM in 2018-03 in Portland
## Board will facilitate putting folks needing rides and folks with spots in their cars together. (see OEDAM wiki)
## Moped balance in question… Carpooling recommended...

== Minutes ==

=== Prior minutes ===

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

OEDAM 2018

2018-02-23T01:40:16Z

Halstead: /* Planning to Attend */

== Location and Time ==

Sunday, 11 March 2018 (before ELC [March 12-14]) 
Board meeting to start at 09:30
Developer's meeting to start at 10:30
Expectation is to finish by 1800

Lunch is provided

Location: Mentor Graphics Headquarters, Wilsonville, OR
Carpooling is encouraged, see below

Yes, we know it is Sunday. Best we could do this year.

== Planning to Attend ==

Carpool note: Please add a {#} after your name if you plan to drive and can take # of people in your car other than yourself

* Jeff Osier-Mixon "Jefro" {4}
* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Sean Hudson (darknighte)
* Manjukumar Matha (manju)
* Joshua Watt (JPEWhacker)
* Zachary Booth
* Jim Lodes
* Armin Kuster (Armpit){15}
* Scott Murray (smurray)
* Tim Orling (moto-timo)
* Alejandro Hernandez (aehs29)
* Christopher Clark
* Behan Webster (behanw)
* Marek Vasut (Marex)
* Taras Kondratiuk
* Bill Mills
* Ricardo Salveti (rsalveti)
* Khem Raj (khem)
* Tom King (ka6sox)
* Rich Persaud
* Michael Halstead (halstead)

== Agenda Items ==

=== OE Board ===
E.v status

=== OE Developers Meeting ===
# Discuss meta-oe release process
# World build monitoring and automatic notifications

== Minutes ==

=== Prior minutes ===

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

User talk:Workingdan

2017-10-16T19:47:02Z

Halstead: Welcome!

User:Workingdan

2017-10-16T19:47:02Z

Halstead: Creating user page for new user.

multi-talented developer who works in various technologies and languages to solve real-world problems for real-world clients

User talk:Rgrigar

2017-10-16T19:46:35Z

Halstead: Welcome!

User:Rgrigar

2017-10-16T19:46:35Z

Halstead: Creating user page for new user.

Lead, IT Infrastructure for the Linux Foundation (and helping the Yocto Project).

OEDAM 2016

2016-04-07T23:25:10Z

Halstead: /* Attendees */

== Location and Time ==

Friday April 8 2016

Catamaran Resort & Hotel 
3999 Mission Boulevard 
San Diego, CA 92109 
858-539-8727

transportation will be provided, TBA
(after ELC [Apr 4-6] and Yocto Project Developer Day [Apr 7])

NOTE: this event is NOT going to be at the Marriott Marquis as previously announced

== Attendees ==
Armin Kuster (Armpit) 
Behan Webster (behanw) 
Denys Dmytriyenko (denix) 
Jan-Simon Möller (dl9pf) 
Philip Balister (Crofton|work) 
Sean Hudson (darknighte) 
Tim Orling (Moto-timo) 
Trevor Woerner 
Tom King (ka6sox) 
Mark Hatle (fray) 
Jeff Osier-Mixon (jefro) 
Frederick Ollinger (Follinge) 
Marc Villanueva (Tentative) 
Rudolf Streif (rstreif) 
Gratian Crisan 
Alejandro Hernandez (aehs29) 
Belén Barros Pena (belen) 
Scott Murray (smurray) 
Koen Kooi (koen) 
George McCollister (georgem) 
Fred Ollinger 
Michael Halstead (halstead) morning only 

== Agenda Items ==

* Is there a better name for this meeting that would make it easier for people to get funding to attend?
* Review items from last meeting in Dublin (Please add remarks)

===BSPs & Layer Index===
* oe driving toward machine readable files, can also drive from layer
test (yp compat) side - KK
* publicize defs of each list? discuss on members list - where to
overall architecture discussions belong
* TSC to add new mailing list specifically about project
architecture, no patches, and determine list name [Done]
* KK bring discussion to new mailing list

===BSP standards - standards exist,coming soon are methods for comparing===
a given layer with the standard
* need wiki documentation for TSC to ratify
* document distro vs. machine policies, other best practices

===BSP layer availability===
* encourage board vendors to provide a BSP, make it easier to do so
* ask yp ab to talk to linux.com [PB] - community issue
* look at digi manual[http://www.digi.com/resources/documentation/digidocs/90001945-13/default.htm#task/yocto/t_customize_root_file_system_yocto.htm%3FTocPath%3DDigi%2520Embedded%2520Yocto%7CSystem%2520development%7CFirst%2520steps%7C_____3] (i.e. "just add bsp changes in local.conf"):

===meta-yocto to meta-poky===
* RP to take action on the YP side, possibly not for 2.0 [Done, rename happened]
* formalize lowercase as mandatory requirement for overrides, look for other options in the future [Done]

===Layer Index feature requests discussed with layer index build feedback>>===
* ask for cycles from employers to work on these issues
* make people aware, help with triage, provide resources

===Security===
* need a method for tracking CVs

===Systemd===
complaints: more package config, comments; look at packaging to have
minimal systemd even with options available
* need someone with time available to work on it
* need to get systemd feedback, people using systemd talk to package maintainer
* file systemctl wrapper bug

===Advocacy===
* board to discuss advocacy/community, invite jefro to meetings
Potential OE Day at ELCE next year
* board: do a proper cfp

== Minutes ==

OEDAM 2016

2016-04-07T23:24:32Z

Halstead: /* Attendees */

== Location and Time ==

Friday April 8 2016

Catamaran Resort & Hotel 
3999 Mission Boulevard 
San Diego, CA 92109 
858-539-8727

transportation will be provided, TBA
(after ELC [Apr 4-6] and Yocto Project Developer Day [Apr 7])

NOTE: this event is NOT going to be at the Marriott Marquis as previously announced

== Attendees ==
Armin Kuster (Armpit) 
Behan Webster (behanw) 
Denys Dmytriyenko (denix) 
Jan-Simon Möller (dl9pf) 
Philip Balister (Crofton|work) 
Sean Hudson (darknighte) 
Tim Orling (Moto-timo) 
Trevor Woerner 
Tom King (ka6sox) 
Mark Hatle (fray) 
Jeff Osier-Mixon (jefro) 
Frederick Ollinger (Follinge) 
Marc Villanueva (Tentative) 
Rudolf Streif (rstreif) 
Gratian Crisan 
Alejandro Hernandez (aehs29) 
Belén Barros Pena (belen) 
Scott Murray (smurray) 
Koen Kooi (koen) 
George McCollister (georgem) 
Fred Ollinger
Michael Halstead (halstead) morning only 

== Agenda Items ==

* Is there a better name for this meeting that would make it easier for people to get funding to attend?
* Review items from last meeting in Dublin (Please add remarks)

===BSPs & Layer Index===
* oe driving toward machine readable files, can also drive from layer
test (yp compat) side - KK
* publicize defs of each list? discuss on members list - where to
overall architecture discussions belong
* TSC to add new mailing list specifically about project
architecture, no patches, and determine list name [Done]
* KK bring discussion to new mailing list

===BSP standards - standards exist,coming soon are methods for comparing===
a given layer with the standard
* need wiki documentation for TSC to ratify
* document distro vs. machine policies, other best practices

===BSP layer availability===
* encourage board vendors to provide a BSP, make it easier to do so
* ask yp ab to talk to linux.com [PB] - community issue
* look at digi manual[http://www.digi.com/resources/documentation/digidocs/90001945-13/default.htm#task/yocto/t_customize_root_file_system_yocto.htm%3FTocPath%3DDigi%2520Embedded%2520Yocto%7CSystem%2520development%7CFirst%2520steps%7C_____3] (i.e. "just add bsp changes in local.conf"):

===meta-yocto to meta-poky===
* RP to take action on the YP side, possibly not for 2.0 [Done, rename happened]
* formalize lowercase as mandatory requirement for overrides, look for other options in the future [Done]

===Layer Index feature requests discussed with layer index build feedback>>===
* ask for cycles from employers to work on these issues
* make people aware, help with triage, provide resources

===Security===
* need a method for tracking CVs

===Systemd===
complaints: more package config, comments; look at packaging to have
minimal systemd even with options available
* need someone with time available to work on it
* need to get systemd feedback, people using systemd talk to package maintainer
* file systemctl wrapper bug

===Advocacy===
* board to discuss advocacy/community, invite jefro to meetings
Potential OE Day at ELCE next year
* board: do a proper cfp

== Minutes ==

OEDEM 2015

2015-10-09T10:15:52Z

Halstead:

The 2015 OpenEmbedded Developer's European Meeting will take place Friday, Oct 9, 2015 in Dublin, Ireland. Part of this meeting will also constitute the annual OE General Assembly, and some corporation/eV matters will be discussed.

== Location and Time ==

[http://www.thegibsonhotel.ie/ The Gibson Hotel] 
Point Village 
Dublin 1, Ireland 
+353 1 681 5000

9am - 5pm (note: times may change)

Gibson Hotel is at the end of the red LUAS line, adjacent to the stadium. Come up to the 3rd floor and follow the signs for the Cordoba room. (the sign says "Mtg", that's us) There is coffee here. See you all soon

== OpenEmbedded eV General Assembly ==

We have a short administrative meeting before starting the Developer meeting. All are welcome for this.

* Proposal to dissolve the current e.V. and re-constituting it in the U.S. to reduce the administrative burden for the project.
* Define a method for identifying lapsed memberships.
* Proxy form [[File:Proxy_instructions-oe.pdf]]
* [http://www.openembedded.org/wiki/Dublin,_2015 Meeting Minutes]

== Agenda ==

* Metadata
** OVERRIDE syntax: is it time to reconsider _?
** meta-yocto -> meta-poky. People are still spending too much time explaining reality. (Crofton)

* BSPs (tlwoerner)
** Standards for BSP behavior. (Crofton)
** feedback on layerindex to indicate BSP:
*** last successful compile (feedback from outside builders?)
*** last successful boot
*** master branch parsability (perhaps ties into bugzilla 7792?)
** several BSP layers to choose from for some boards, none for others (linux.com SBC survey)
** guidelines/requirements for setting up a new BSP on layerindex
*** bugzilla
*** mailing list (use general mailing list(s) for patches?)
*** git.yoctoproject.org/<yourbsplayer>
** making sure BSP layers only touch the variables/settings they should touch
*** should a BSP layer ever use = ?
** does/should a BSP produce artifacts that are easy to install to SD cards? (Crofton)

*Processes
** LayerIndex feature requests (tlwoerner)
** build feedback (autobuilders and off-site)
** Build and test failures on the public Autobuilder (Bluelightening)

*Systemd
** Systemd packaging. As new things appear, they are lumped into one package. Update split? (Crofton relaying info)
** Can we get systemd's first-boot support to work? It is currently disabled in the systemd recipe by touching /etc/machine-id. (Saur)
** How to make it easy to setup a system "the systemd way"? New DISTRO_FEATURE or IMAGE_FEATURE? (Saur)
*** Link /bin -> /usr/bin, /lib -> /usr/lib, etc.
*** Change ${systemd_unitdir} to /usr/lib.
*** Make the systemctl wrapper install in ${systemd_unitdir} rather than ${systemconf}/systemd.
**** This should also happen when installing a package in runtime.

*Advocacy
** There are still a lot of projects (too many?) not using OE (tlwoerner)
** why aren't more projects using OE?
** how can we get more people using OE?
** who should we be targeting? (build people (obviously), kernel devs? user-space devs?)

== Attendees ==

If you plan to attend, please list your name below.

# Jeff Osier-Mixon (jefro)
# Philip Balister (Crofton)
# Trevor Woerner (tlwoerner)
# Anders Darander (andersd)
# Marco Cavallini (mckoan)
# Koen Kooi (koen)
# Alexandre Belloni (abelloni)
# Armin Kuster (armpit)
# Belén Barros Pena (belen)
# Peter Kjellerstedt (Saur)
# Alejandro del Castillo (adelcast)
# Denys Dmytriyenko (denix)
# Sean Hudson (darknighte)
# Nathan Rossi (nrossi)
# Mark Hatle (fray)
# Nicolas Dechesne (ndec)
# Paul Eggleton (bluelightning)
# Andrei Gherzan (agherzan)
# Felipe F. Tonello (ftonello)
# Changhyeok Bae (chbae)
# Saul Wold (sgw)
# Ashish Shrivastava
# Pascal Bach (bachp)
# Richard Purdie (RP)
# Michael Halstead (halstead)

OEDEM 2015

2015-10-09T08:21:34Z

Halstead:

The 2015 OpenEmbedded Developer's European Meeting will take place Friday, Oct 9, 2015 in Dublin, Ireland. Part of this meeting will also constitute the annual OE General Assembly, and some corporation/eV matters will be discussed.

== Location and Time ==

[http://www.thegibsonhotel.ie/ The Gibson Hotel] 
Point Village 
Dublin 1, Ireland 
+353 1 681 5000

9am - 5pm (note: times may change)

Gibson Hotel is at the end of the red LUAS line, adjacent to the stadium. Come up to the 3rd floor and follow the signs for the Cordoba room. (the sign says "Mtg", that's us) There is coffee here. See you all soon

== OpenEmbedded eV General Assembly ==

We have a short administrative meeting before starting the Developer meeting. All are welcome for this.

* Proposal to dissolve the current e.V. and re-constituting it in the U.S. to reduce the administrative burden for the project.
* Define a method for identifying lapsed memberships.
* Proxy form [[File:Proxy_instructions-oe.pdf]]

== Agenda ==

* Metadata
** OVERRIDE syntax: is it time to reconsider _?
** meta-yocto -> meta-poky. People are still spending too much time explaining reality. (Crofton)

* BSPs (tlwoerner)
** Standards for BSP behavior. (Crofton)
** feedback on layerindex to indicate BSP:
*** last successful compile (feedback from outside builders?)
*** last successful boot
*** master branch parsability (perhaps ties into bugzilla 7792?)
** several BSP layers to choose from for some boards, none for others (linux.com SBC survey)
** guidelines/requirements for setting up a new BSP on layerindex
*** bugzilla
*** mailing list (use general mailing list(s) for patches?)
*** git.yoctoproject.org/<yourbsplayer>
** making sure BSP layers only touch the variables/settings they should touch
*** should a BSP layer ever use = ?
** does/should a BSP produce artifacts that are easy to install to SD cards? (Crofton)

*Processes
** LayerIndex feature requests (tlwoerner)
** build feedback (autobuilders and off-site)
** Autobuilder failures (Bluelightening)

*Systemd
** Systemd packaging. As new things appear, they are lumped into one package. Update split? (Crofton relaying info)
** Can we get systemd's first-boot support to work? It is currently disabled in the systemd recipe by touching /etc/machine-id. (Saur)
** How to make it easy to setup a system "the systemd way"? New DISTRO_FEATURE or IMAGE_FEATURE? (Saur)
*** Link /bin -> /usr/bin, /lib -> /usr/lib, etc.
*** Change ${systemd_unitdir} to /usr/lib.
*** Make the systemctl wrapper install in ${systemd_unitdir} rather than ${systemconf}/systemd.
**** This should also happen when installing a package in runtime.

*Advocacy
** There are still a lot of projects (too many?) not using OE (tlwoerner)
** why aren't more projects using OE?
** how can we get more people using OE?
** who should we be targeting? (build people (obviously), kernel devs? user-space devs?)

== Attendees ==

If you plan to attend, please list your name below.

# Jeff Osier-Mixon (jefro)
# Philip Balister (Crofton)
# Trevor Woerner (tlwoerner)
# Anders Darander (andersd)
# Marco Cavallini (mckoan)
# Koen Kooi (koen)
# Alexandre Belloni (abelloni)
# Armin Kuster (armpit)
# Belén Barros Pena (belen)
# Peter Kjellerstedt (Saur)
# Alejandro del Castillo (adelcast)
# Denys Dmytriyenko (denix)
# Sean Hudson (darknighte)
# Nathan Rossi (nrossi)
# Mark Hatle (fray)
# Nicolas Dechesne (ndec)
# Paul Eggleton (bluelightning)
# Andrei Gherzan (agherzan)
# Felipe F. Tonello (ftonello)
# Changhyeok Bae (chbae)
# Saul Wold (sgw)
# Ashish Shrivastava
# Pascal Bach (bachp)
# Richard Purdie (RP)
# Michael Halstead (halstead)

OEDAM 2015

2015-02-12T21:01:10Z

Halstead:

== Location and Time ==

March 27-28 (after ELC and Yocto Project Developer Day)

2315 North 1st Street, San Jose, CA 95131

https://goo.gl/maps/1pRGR

== Attendees ==

* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Armin Kuster (Armpit)
* Martin Jansa (JaMa) - 50%
* Michael Halstead (halstead) - Friday only

== Agenda Items ==

OEDAM 2015

2015-02-12T21:00:37Z

Halstead:

== Location and Time ==

March 27-28 (after ELC and Yocto Project Developer Day)

2315 North 1st Street, San Jose, CA 95131

https://goo.gl/maps/1pRGR

== Attendees ==

* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Armin Kuster (Armpit)
* Martin Jansa (JaMa) 50%
* Michael Halstead (Friday only)

== Agenda Items ==

OEDAM 2015

2015-02-12T18:08:42Z

Halstead:

== Location and Time ==

March 27-28 (after ELC and Yocto Project Developer Day)

2315 North 1st Street, San Jose, CA 95131

https://goo.gl/maps/1pRGR

== Attendees ==

* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Armin Kuster (Armpit)
* Martin Jansa (JaMa) 50%
* Michael Halstead (Saturday only)

== Agenda Items ==

OEDAM 2014

2014-05-02T16:03:57Z

Halstead: /* Attendees */

= OpenEmbedded Developers America Meeting =

The OpenEmbedded Project is holding a developers meeting May 2-3, 2014, in Santa Clara, CA. This meeting is co-located with the Embedded Linux Conference North America. All active OpenEmbedded developers are invited to attend.

Contact [mailto:jefro@jefro.net Jefro] with any questions.

== Location & Time ==

May 2-3, 2014 
9am - 5pm

[https://www.google.com/maps/preview#!q=4600+Patrick+Henry+Dr+Santa+Clara%2C+CA+95054+&data=!1m4!1m3!1d9724!2d-121.985724!3d37.3978139!4m15!2m14!1m13!1s0x808fc9d0bdf38417%3A0x8ca7d9c558968760!3m8!1m3!1d2439!2d-80.4013806!3d37.1440125!3m2!1i1366!2i589!4f13.1!4m2!3d37.3978139!4d-121.985724 Ettus Research / National Instruments] 
4600 Patrick Henry Drive 
Santa Clara, CA 95054 USA

I am looking into providing coffee and tidbits in the mornings. I may wait until the day of the event to see how many people actually show up, so don't plan on a caffeine injection before 10am each day.

Lunches will be catered, restaurant TBD and I'm open to suggestions. Food trucks did not work out. The current plan is for catering by Old Ironsides Cafe on Friday, and possibly pizza on Saturday.

A fully hosted dinner party will be held at the Tied House Brewing Company in Mountain View, Friday May 2, 6pm-8pm. This venue is accessible by light rail or by car with free parking. If you can not make it to this event, please let [mailto:jefro@jefro.net Jefro] know.

All meals provided by the [http://yoctoproject.org Yocto Project Community Office]

Carpools for the Tied House:

* Jefro (room for 3 more)
* JaMa (room for 3 more)

== Goals ==

* Have fun.
* Get useful work done that benefits from high bandwidth interactions.
* Get more people involved with the project at a higher level.

== Working Agenda ==

This agenda is flexible, and meant to reflect the important issues in the OE community. Please feel free to contribute agenda items. We will finalize the agenda after introduction to maximize use of people's time.

* Introductions. Be prepared to tell us who you are and how you use OpenEmbedded (and the Yocto Project)
* The Yocto Project is supposed to make Embedded easy. What is still hard?
* bug scrub (also bug collecting/wrangling)
* ongoing role of the OE TSC
* wiki/website organization
* online voting
* increasing the amount of hardware that works out of the box with oe-core + layers
* next + 1 release
* quality of meta-oe and what to do with it: http://lists.openembedded.org/pipermail/openembedded-devel/2014-March/094893.html
* lune to replace sato?
* developer community - outreach/recruiting/mentoring, new developer documentation, process and QA tools
* image deployment/update best practices (shared yocto issue)
* feedback on Toaster, the web interface for BitBake (some background in this thread https://lists.yoctoproject.org/pipermail/yocto/2014-April/018956.html)
* infrastructure sync

== Attendees ==

* Philip Balister (Crofton)
* <strike>Richard Purdie (RP)</strike>
* Mark Hatle (fray)
* Khem Raj (khem)
* Martin Jansa (jama)
* Armin Kuster (akuster)
* Jeff Osier-Mixon (jefro)
* Alejandro del Castillo
* Tom King (ka6sox)
* Steve Arnold (mr_science/nerdboy)
* Herb Kuta
* Trevor Woerner (tlwoerner)
* Sean Hudson (darknighte)
* Denys Dmytriyenko (denix)
* Toby Flynn
* Adam Bell
* Belen Barros Pena (belen)
* Brian Hutchinson
* Tim Orling (moto-timo)
* Michael Halstead (halstead)
* <your name here>

OEDAM 2014

2014-04-14T16:53:39Z

Halstead: typo

= OpenEmbedded Developers America Meeting =

The OpenEmbedded Project is holding a developers meeting May 2-3, 2014, in Santa Clara, CA. This meeting is co-located with the Embedded Linux Conference North America. All active OpenEmbedded developers are invited to attend.

Contact [mailto:jefro@jefro.net Jefro] with any questions.

== Location & Time ==

May 2-3, 2014 
time TBD

[https://www.google.com/maps/preview#!q=4600+Patrick+Henry+Dr+Santa+Clara%2C+CA+95054+&data=!1m4!1m3!1d9724!2d-121.985724!3d37.3978139!4m15!2m14!1m13!1s0x808fc9d0bdf38417%3A0x8ca7d9c558968760!3m8!1m3!1d2439!2d-80.4013806!3d37.1440125!3m2!1i1366!2i589!4f13.1!4m2!3d37.3978139!4d-121.985724 Ettus Research / National Instruments] 
4600 Patrick Henry Drive 
Santa Clara, CA 95054 USA

Lunches will be provided by the [http://yoctoproject.org Yocto Project Community Office]

The area is a bit of a wasteland without good food choices close (walking) by. If you have lunch ideas let Jefro or Philip know. We can look into asking a food truck to come by: http://roaminghunger.com/sjc.

== Goals ==

* Have fun.
* Get useful work done that benefits from high bandwidth interactions.
* Get more people involved with the project at a higher level.

== Working Agenda ==

This agenda is flexible, and meant to reflect the important issues in the OE community. Please feel free to contribute agenda items. We will finalize the agenda after introduction to maximize use of people's time.

* Introductions. Be prepared to tell us who you are and how you use OpenEmbedded (and the Yocto Project)
* The Yocto Project is supposed to make Embedded easy. What is still hard?
* bug scrub (also bug collecting/wrangling)
* ongoing role of the OE TSC
* wiki/website organization
* online voting
* increasing the amount of hardware that works out of the box with oe-core + layers
* next + 1 release
* developer community - outreach/recruiting/mentoring, new developer documentation, process and QA tools
* image deployment/update best practices (shared yocto issue)
* feedback on Toaster, the web interface for BitBake (some background in this thread https://lists.yoctoproject.org/pipermail/yocto/2014-April/018956.html)

== Attendees ==

* Philip Balister (Crofton)
* Richard Purdie (RP)
* Mark Hatle (fray)
* Khem Raj (khem)
* Martin Jansa (jama)
* Armin Kuster (akuster)
* Jeff Osier-Mixon (jefro)
* Alejandro del Castillo
* Tom King (ka6sox)
* Steve Arnold (mr_science/nerdboy)
* Herb Kuta
* Trevor Woerner (tlwoerner)
* Sean Hudson (darknighte)
* Denys Dmytriyenko (denix)
* Toby Flynn
* Adam Bell
* Belen Barros Pena (belen)
* Brian Hutchinson
* Tim Orling (moto-timo)
* Michael Halstead (halstead) day 1 only
* <your name here>

OEDAM 2014

2014-04-14T16:47:19Z

Halstead:

= OpenEmbedded Developers America Meeting =

The OpenEmbedded Project is holding a developers meeting May 2-3, 2014, in Santa Clara, CA. This meeting is co-located with the Embedded Linux Conference North America. All active OpenEmbedded developers are invited to attend.

Contact [mailto:jefro@jefro.net Jefro] with any questions.

== Location & Time ==

May 2-3, 2014 
time TBD

[https://www.google.com/maps/preview#!q=4600+Patrick+Henry+Dr+Santa+Clara%2C+CA+95054+&data=!1m4!1m3!1d9724!2d-121.985724!3d37.3978139!4m15!2m14!1m13!1s0x808fc9d0bdf38417%3A0x8ca7d9c558968760!3m8!1m3!1d2439!2d-80.4013806!3d37.1440125!3m2!1i1366!2i589!4f13.1!4m2!3d37.3978139!4d-121.985724 Ettus Research / National Instruments] 
4600 Patrick Henry Drive 
Santa Clara, CA 95054 USA

Lunches will be provided by the [http://yoctoproject.org Yocto Project Community Office]

The area is a bit of a wasteland without good food choices close (walking) by. If you have lunch ideas let Jefro or Philip know. We can look into asking a food truck to come by: http://roaminghunger.com/sjc.

== Goals ==

* Have fun.
* Get useful work done that benefits from high bandwidth interactions.
* Get more people involved wit the project at a higher level.

== Working Agenda ==

This agenda is flexible, and meant to reflect the important issues in the OE community. Please feel free to contribute agenda items. We will finalize the agenda after introduction to maximize use of people's time.

* Introductions. Be prepared to tell us who you are and how you use OpenEmbedded (and the Yocto Project)
* The Yocto Project is supposed to make Embedded easy. What is still hard?
* bug scrub (also bug collecting/wrangling)
* ongoing role of the OE TSC
* wiki/website organization
* online voting
* increasing the amount of hardware that works out of the box with oe-core + layers
* next + 1 release
* developer community - outreach/recruiting/mentoring, new developer documentation, process and QA tools
* image deployment/update best practices (shared yocto issue)
* feedback on Toaster, the web interface for BitBake (some background in this thread https://lists.yoctoproject.org/pipermail/yocto/2014-April/018956.html)

== Attendees ==

* Philip Balister (Crofton)
* Richard Purdie (RP)
* Mark Hatle (fray)
* Khem Raj (khem)
* Martin Jansa (jama)
* Armin Kuster (akuster)
* Jeff Osier-Mixon (jefro)
* Alejandro del Castillo
* Tom King (ka6sox)
* Steve Arnold (mr_science/nerdboy)
* Herb Kuta
* Trevor Woerner (tlwoerner)
* Sean Hudson (darknighte)
* Denys Dmytriyenko (denix)
* Toby Flynn
* Adam Bell
* Belen Barros Pena (belen)
* Brian Hutchinson
* Tim Orling (moto-timo)
* Michael Halstead (halstead) day 1 only
* <your name here>