Openembedded.org - User contributions [en]

OEDEM 2018

2018-09-17T11:56:06Z

Stephano: /* Planning to Attend */

== Location and Time ==

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

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 ==

# Khem Raj (khem)
# 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)
# Changhyeok Bae (chbae)
# Kyungjik Min
# Earnest Son
# Mark Hatle (fray)
# Robert Yang

Wait List (Please add yourself at the bottom):

# Bruce Ashfield (zeddii)
# David Reyna
# Alexander Kanavin (kanavin)
# George McCollister (georgem)
# Beth Flanagan (pidge)
# Josef Holzmayr (letothe2nd)
# Stephano Cetola

== Agenda Items ==

=== OE Developers Meeting ===

* Board Member ballot
* OE Infrastructure
* 2.7 Features
* Next meeting? Normally in US at ELC in spring. But in 2019 event is in August. Skip? Arrange event in Spring? Where?

== 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-02-23T05:32:45Z

Stephano: update attendee list

== Location and Time ==

Sunday, 11 March 2018 (before ELC [March 12-14])<br>
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)
* Stephano Cetola (stephano) {1 + truck bed }

== 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

2017 General Meeting

2017-04-20T15:16:33Z

Stephano: /* Planning to attend */

== Purpose ==
The new bylaws of the organization require '''at least''' one general meeting per year. This will fulfill that requirement. Also, we plan to discuss topics of interest to the community and the project.

== Date and Time ==
'''!!!Tentative!!!''' 2017-05-03 @ 8am US-CDT(UTC-06:00)/3pm CET(UTC+01:00)

Here's a link to the time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+2017+General+Meeting&iso=20170503T08&p1=24&ah=1

Countdown link:
https://www.timeanddate.com/countdown/generic?p0=24&iso=20170503T08&msg=OpenEmbedded%202017%20General%20Meeting

== Conference Information ==

Meeting will be held as a teleconference with a IRC channel to allow for background discussion and trouble shooting of audio.

IRC: #oe-meeting on freenode

'''Dial-in Conference # 8964521'''

{| class="wikitable"
!colspan="3"|Dial-in Information
|-
| Country
| Toll Free Number(s)
| Toll Number(s)
|-
|UNITED STATES(USA)
|8006375822
|6477233937
9172102607
|-
|-
|ARGENTINA(ARG)
|8008000140
|01159843238
|-
|AUSTRALIA(AUS)
|1800706813
|0390084306
|-
|AUSTRIA(AUT)
|080088665126
1800455064
|
|-
|BELGIUM(BEL)
|080039126
|027924568
|-
|BRAZIL(BRA)
|08000201594
|
|-
|BULGARIA(BGR)
|008001201150
|
|-
|CANADA(CAN)
|8006375822
|6477233937
|-
|CHILE(CHL)
|12300201190
|225994308
|-
|CHINA NORTH(CHN)
|108007140888
|
|-
|CHINA SOUTH(CHS)
|108001400863
|
|-
|CHINA UNIFIED(CHU)
|8008195002
|4006201003
|-
|CZECH REPUBLIC(CZE)
|800701563
|234147032
|-
|DENMARK(DNK)
|80703176
|36910500
|-
|EGYPT(EGY)
|08000000216
|
|-
|FINLAND(FIN)
|0800114187
0800773408
|0923194205
|-
|FRANCE(FRA)
|0800941758
|
|-
|GERMANY(DEU)
|08001014542
|069710448206
|-
|HONG KONG(HKG)
|800903520
|30508648
|-
|HUNGARY(HUN)
|0680018377
|
|-
|INDIA(IND)
|0008001006237
0008006501628

18002660806
|
|-
|IRELAND(IRL)
|1800760168
1800944117
|014360203
|-
|ISRAEL(ISR)
|1809245898
|
|-
|ITALY(ITA)
|800785295
|
|-
|JAPAN(JPN)
|00531160557
00531190046
|0345899489
|-
|MALAYSIA(MYS)
|1800814332
|
|-
|MEXICO(MEX)
|0018005148003
|5547772297
|-
|MOROCCO(MAR)
|002110011 8553458162
|
|-
|NETHERLANDS(NLD)
|08002658235
|0207940366
|-
|NEW ZEALAND(NZL)
|0800453014
|049094653
|-
|NORWAY(NOR)
|80056416
|21033210
|-
|PAKISTAN(PAK)
|
|4238108701
|-
|PHILIPPINES(PHL)
|180011100869
|
|-
|POLAND(POL)
|008001114760
800702736
|223060765
|-
|PORTUGAL(PRT)
|800780647
|
|-
|ROMANIA(ROM)
|0800400060
0800400906
|215291724
|-
|RUSSIAN FEDERATION(RUS)
|81080025401012
|4959952645
|-
|SAUDI ARABIA(SAU)
|8008149944
|
|-
|SINGAPORE(SGP)
|8001011714
8001205024
|64944153
|-
|SLOVAKIA(SVK)
|0800606530
|
|-
|SOUTH KOREA(KOR)
|00308140655
|
|-
|SPAIN(ESP)
|900947050
|
|-
|SWEDEN(SWE)
|0201400572
|0114501530
|-
|SWITZERLAND(CHE)
|0800561819
0800705314
|0434569423
|-
|TAIWAN(TWN)
|0809090682
|
|-
|UNITED ARAB EMIRATES(ARE)
|8000176692
|
|-
|UNITED KINGDOM(GBR)
|08006920143
|2070840301
|-
|}

== Tentative Agenda ==
# Meeting Schedule
## The board would like to propose a quarterly meeting schedule with alternating online and face-to-face meetings.
# Membership
## Grandfathered all existing members in good standing
## New members
# TSC
## Grandfathered from old organization
# Online voting
# Elections
# Future plans/purpose for the organization
# Technical topics

== Planning to attend ==
* Sean Hudson (irc:darknighte)
* Denys Dmytriyenko (denix)
* Bruce Ashfield (zeddii*)
* Armin Kuster (armpit)
* Mark Hatle (fray)
* Tom Rini (Tartarus)
* Trevor Woerner (tlwoerner)
* Ross Burton (rburton)
* Stephano Cetola (stephano)

OEDAM 2017

2017-01-10T03:47:58Z

Stephano: /* Attendees */

== Location and Time ==

Monday February 20 2017

Location TBA

(Before ELC [Feb 21-23] and Yocto Project Developer Day [Feb 24])

== Attendees ==

* Armin Kuster (armpit)
* Philip Balister (Crofton)
* Trevor Woerner (tlwoerner)
* Denys Dmytriyenko (denix)
* Stephano Cetola

== Agenda Items ==

* Review items from last meeting in Berlin (Please add remarks)

== Minutes ==

OEDAM 2017

2017-01-10T03:46:41Z

Stephano: /* Attendees */

== Location and Time ==

Monday February 20 2017

Location TBA

(Before ELC [Feb 21-23] and Yocto Project Developer Day [Feb 24])

== Attendees ==

* Armin Kuster (armpit)
* Philip Balister (Crofton)
* Trevor Woerner (tlwoerner)
* Denys Dmytriyenko (denix)
* Stephano Cetola (Intel)

== Agenda Items ==

* Review items from last meeting in Berlin (Please add remarks)

== Minutes ==

How to submit a patch to OpenEmbedded

2016-11-17T22:26:41Z

Stephano: Add section with useful links to guidelines and style guide

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>.

== 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.

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.

== 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]]