Richard/Saul, I've been running with these changes since before ELC, so they've had some good soak time. The first two changes lay the ground for for some 1.1 functionality and are used by recipes in

Hi Beth, M1, Yes there's definitely quite an overlap here and we should coordinate efforts. Will catch you later on IRC to organise some time. Cheers, Paul -- Paul Eggleton Intel Open Source

Most of the issues surrounding the license field is currently on my plate for M1.D License tracking Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes

The TSC was asked by the board to figure out the details of the election which we did in the first meeting as requested and provided our feedback back to the board. The board naturally has the

2011/5/3 Richard Purdie <richard.purdie@...> I don't think it is up to the TSC to decide on the re-election timeframe. As it stands the TSC got a 2 month mandate. See the quote above (from Philip's

The current situation was making the best of a bad set of circumstances, the plan is to hold elections and nothing has changed in that regard. This was discussed at the last TSC meeting and we

Speaking as a member of the TSC, our understanding is an election would be called for the first position at the beginning of May. (More or less this week.) The TSC members up for election was

2011/5/3 Philip Balister <philip@...> [...] Sorry but the current TSC is NOT elected by the eV members. Actually the board even fails to meet its own "rules" stipulated when they installed this

As most of you know, there is an OpenEmbedded eV to provide an umbrella organization for handling various aspects of managing the project. There is a description here:

Here are the notes from the Tuesday, May 3rd Yocto Technical Team meeting. Thanks. - Julie Attendees: Dave, Darren, Richard, Mark, Julie, Joshua, Saul, Tom, Beth, Jessica, Jeff Polk, Alex de Vries,

Hi all, As part of the 1.1 feature list I suggested a review of the INCOMPATIBLE_LICENSE and COMMERCIAL* package exclusion mechanisms we have within Poky. Below I've outlined my ideas and would

Thanks Liping, this looks good to me. I've merged it into an image-creator branch on contrib I will be collecting image-creator related BitBake patches there for now with the goal of porting them to

Yocto Technical Team, We will be having our regular Technical Team meeting on Tuesday at 8am. If you'd like to join, dial in and agenda are below. Thanks. - Julie Dial in: Tuesday, May 03, 2011,

I just realized another major issue I have with this approach. It doesn't just mean that I _can_ use git fetch to get a specific branch to avoid pulling in a massive pile of objects I don't need, it

Hi, Josh Thanks for your very careful review indeed! I will correct them and resend the patch! Regards, criping

From: Liping Ke <liping.ke@...> Add -t options in bitbake for configuring server type. Signed-off-by: Liping Ke <liping.ke@...> --- bitbake/bin/bitbake | 22 +++++++++++++++++----- 1

From: Liping Ke <liping.ke@...> Add -t options in bitbake for configuring server type. Signed-off-by: Liping Ke <liping.ke@...> Pull URL: git://git.pokylinux.org/poky-contrib.git

Hi Liping, This looks good to me. Two minor typo nits below, once they're fixed I will create a branch on poky-contrib to collect image-creator related patches until we're ready to switch to

Agreed. I don't know what gitolite is capable of. I would really like to be able to create and destroy my own repositories in a central location with other Yocto developers. However, this doesn't

Agreed with the points above. git really is just wrangling a bunch of objects into commit chains and a branch points to a starting point. So I completely agree that all chains don't have to lead