Difference between revisions of "Oedem/2010"

From Openembedded.org
Jump to: navigation, search
(Agenda)
(Undo revision 3396 by Yjytalamago (Talk))
 
(3 intermediate revisions by 3 users not shown)
Line 40: Line 40:
 
  9:30 - 10:30 [[GA2010]] General Assembly.
 
  9:30 - 10:30 [[GA2010]] General Assembly.
  
10:30 - 10:00 Relationship with the Yocto Project.
+
10:30 - 11:00 Relationship with the Yocto Project.
  
 
XXXXX - XXXXX Recipe status
 
XXXXX - XXXXX Recipe status
Line 61: Line 61:
 
* Khem: patchwork workflow
 
* Khem: patchwork workflow
 
* Khem: Time based releases ( one a year)
 
* Khem: Time based releases ( one a year)
 +
* PM: Commit messages. Inclusion of the error, if something had to be fixed, and the distribution and machine with what the recipe has been tested (also with new recipes).
 +
* PM: Commit messages
  
 
XX:XX - XX:XX Development Issues
 
XX:XX - XX:XX Development Issues

Latest revision as of 07:57, 24 November 2010

OpenEmbedded Developers' Meeting 2010 will be in Cambridge, UK on the 29th and 30th of October. This is after http://www.embeddedlinuxconference.com/elc_europe10/index.html and will be held in the same place, the University Arms Hotel (http://www.devere.co.uk/our-locations/university-arms).

All developers and other interested parties are welcome.

Location

Darwin Suite in the University Arms Hotel Cambridge, England.

Registration

Due to restricted space at the venue, the number of attendees is limited to 30 poeple.

Agenda Suggestions

  • FM: I would like to suggest a discussion on recipe quality and how to improve it. I must say that I am somewhat disappointed by the number of recipes that do not fetch or do not patch. How are we going to handle this
  • FM: related to the previous: how to deal with orphaned recipes, distros and machines
  • FM: suggest to re-institute the MAINTAINERS field, at least for distro and machine conf files but preferably also in recipes. Currently it is often not clear who maintains what
  • FM: review/commit/revert policy (e.g. formalize the suggestion that NAKs need to be motivated and that submitted patches can be pushed if there is no neg feedback within say 2 weeks (even if there is no feedback at all).
  • FM: maybe discuss the testing branch/procedures
  • FM: usage of DEFAULT_PREFERENCE = "-1" (and more concrete: the creation of new recipes with DP = -1, that never seem to loose its DP)
  • Khem: Libtool 2.4 upgrade.
  • Khem: bitbake world. What do we do ?
  • Khem: patchwork workflow
  • Khem: Security updates how to handle
  • Khem: Make LICENSE field mandatory in recipes
  • Khem: Time based releases ( one a year)
  • Hrw: recipes/ subdirectories (all "inherit opie" or "inherit palmtop" -> recipes/opie/ dir etc)
  • RP: srctree, srcrev mess, pain with linux-wrs - time to rework the scm fetchers?
  • RP: Proposal - merge fetch and unpack tasks
  • LW: the recipe owner needs to well understand class implementation details, no consistency, no documentation, and subject to change.
  • LW: BB2 and OE2 from scratch?

Agenda

Friday

OpenEmbedded eV General Assembly

9:00 -  9:30 Meeting Organization, Review Agenda, Setup Gobby for minutes.
9:30 - 10:30 GA2010 General Assembly.

10:30 - 11:00 Relationship with the Yocto Project.

XXXXX - XXXXX Recipe status

  • FM: I would like to suggest a discussion on recipe quality and how to improve it. I must say tha I am somewhat disappointed by the number of recipes that do not fetch or do not patch. How are we going to handle this
  • FM: usage of DEFAULT_PREFERENCE = "-1" (and more concrete: the creation of new recipes with DP = -1, that never seem to loose its DP)
  • Khem: Make LICENSE field mandatory in recipes
  • Hrw: recipes/ subdirectories (all "inherit opie" or "inherit palmtop" -> recipes/opie/ dir etc)
  • LW: the recipe owner needs to well understand class implementation details, no consistency, no documentation, and subject to
  • FM: suggest to re-institute the MAINTAINERS field, at least for distro and machine conf files but preferably also in recipes. Currently it is often not clear who maintains what

XX:XX - XX:XX Quality

  • PB What is quality?
  • Khem: bitbake world. What do we do ?
  • Khem: Security updates how to handle

XX:XX - XX:XX Project workflow and policies

  • FM: related to the previous: how to deal with orphaned recipes, distros and machines
  • FM: review/commit/revert policy (e.g. formalize the suggestion that NAKs need to be motivated and that submitted patches can be pushed if there is no neg feedback within say 2 weeks (even if there is no feedback at all).
  • FM: maybe discuss the testing branch/procedures
  • Khem: patchwork workflow
  • Khem: Time based releases ( one a year)
  • PM: Commit messages. Inclusion of the error, if something had to be fixed, and the distribution and machine with what the recipe has been tested (also with new recipes).
  • PM: Commit messages

XX:XX - XX:XX Development Issues

  • Khem: Libtool 2.4 upgrade.
  • RP: srctree, srcrev mess, pain with linux-wrs - time to rework the scm fetchers?
  • RP: Proposal - merge fetch and unpack tasks
  • LW: BB2 and OE2 from scratch?

Saturday

XX:XX - XX:XX Patchfest with remaining time

Travel

London Stansted airport is the nearest to Cambridge with regular service. (There is a small airport in Cambridge itself but I don't think any scheduled airlines operate from there anymore.)

For those travelling from Europe, Stansted is about a 30-minute train ride from Cambridge city centre and is served by Air Berlin, Ryanair and Germanwings among others. Luton airport is about 1 hour away by bus and is served by Easyjet.

For those travelling from further away, most long-haul flights arrive at Heathrow or Gatwick airports (although there is some transatlantic service into Stansted). Both Heathrow and Gatwick are about 2 hours from Cambridge by train or bus: the train is quicker but involves several changes in London, whereas the bus is slow but cheaper and less complicated.

If arriving at LHR airport, take the Piccadilly line from the Underground station and ride it all the way to Kings Cross St Pancras. Ascend to street level, follow signs to Kings Cross mainline station (not St Pancras: the two stations are different although they share a subway stop) and then look for trains to Cambridge or Kings Lynn on the departure board. There are usually two fast services and two slow services to Cambridge per hour: the slow trains are often overtaken by the fast ones en route so it may be best to wait for a fast service even if this is not the next to depart.

If arriving at LCY, take the DLR to Bank, then change to the Northern Line northbound. From Kings Cross St Pancras, proceed as for LHR, above.

http://nationalrail.co.uk

http://nationalexpress.co.uk/

Alternatively you can take the Eurostar to London St Pancras, which is 50 minutes from Cambridge by train.

See also the ELCE10 website for some travel informations: http://www.embeddedlinuxconference.com/elc_europe10/hotel.html

Accommodation

The nearest full-service hotel is ...

Cheapest accomodation is ...

Food and drink

...

Attending for sure

  1. Philip Balister
  2. Florian Boor
  3. Denys Dmytriyenko
  4. Mark Hatle
  5. Koen Kooi
  6. Fabio Mauri (friday until 15:00)
  7. Frans Meulenbroeks
  8. Jeff Polk
  9. Richard Purdie
  10. Raffaele Recalcati (friday until 15:00)
  11. Stefan Schmidt
  12. Leon Woestenberg
  13. Saul Wold
  14. Davide Bonfanti (only friday until 15:00)

Attending not yet sure

...

Won't be able to attend

  1. Michael Lauer -- really sorry :/
  2. Robert Schuster