Darwin Suite in the [http://www.devere.co.uk/our-locations/university-arms.html University Arms Hotel] Cambridge, England.

−

Call ... if you get hopelessly lost.

+

== Registration ==

== Registration ==

−

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

+

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

== Agenda Suggestions ==

== Agenda Suggestions ==

Line 18:

Line 17:

* 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: 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: 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)

* 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)

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

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)

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)

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

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.