Re: [coreboot] Changes to the coreboot Project Structure -- the non-aneurysmal way

2014-03-26 Thread Patrick Georgi
Am Mittwoch, den 26.03.2014, 09:22 -0500 schrieb mrnuke: Masters, of Gerrit, the pleasure of training gerrit to implement this change is left entirely to you. While we're specifying behaviour: what should happen to changes that affect multiple maintainer domains? (and before you say they

Re: [coreboot] Changes to the coreboot Project Structure -- the non-aneurysmal way

2014-03-26 Thread mrnuke
On Wednesday, March 26, 2014 03:32:12 PM Patrick Georgi wrote: Am Mittwoch, den 26.03.2014, 09:22 -0500 schrieb mrnuke: Masters, of Gerrit, the pleasure of training gerrit to implement this change is left entirely to you. While we're specifying behaviour: what should happen to changes that

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-25 Thread Stefan Reinauer
* ron minnich rminn...@gmail.com [140325 06:34]: On Mon, Mar 24, 2014 at 10:20 PM, Vladimir ' -coder/phcoder' Serbinenko phco...@gmail.com wrote: I don't see how this prevents any of my propositions for the bulk of the boards. The problem you describe isn't going away with

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-25 Thread mrnuke
On Tuesday, March 25, 2014 06:56:13 PM Stefan Reinauer wrote: * ron minnich rminn...@gmail.com [140325 06:34]: On Mon, Mar 24, 2014 at 10:20 PM, Vladimir ' -coder/phcoder' Serbinenko phco...@gmail.com wrote: I don't see how this prevents any of my propositions for the bulk of

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-25 Thread Stefan Reinauer
* mrnuke mr.nuke...@gmail.com [140325 19:13]: On Tuesday, March 25, 2014 06:56:13 PM Stefan Reinauer wrote: * ron minnich rminn...@gmail.com [140325 06:34]: On Mon, Mar 24, 2014 at 10:20 PM, Vladimir ' -coder/phcoder' Serbinenko phco...@gmail.com wrote: I don't see how this

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread Paul Menzel
Dear Stefan, dear coreboot folks, Am Donnerstag, den 20.03.2014, 22:55 +0100 schrieb Stefan Reinauer: Changes to the coreboot Project Structure We -- the coreboot project -- have succeeded beyond our wildest expectations, with every major laptop vendor using our code. Going forward, this

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread Stefan Reinauer
Hi folks, ok, sorry to those who thought that I was missing in action. It feels good to have a weekend to get out into the sun every now and then, and let the dust settle a little bit in a maybe too heated discussion. I will address your concerns. * mrnuke mr.nuke...@gmail.com [140320 23:42]:

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread Stefan Reinauer
Hi Carl-Daniel, thank you for your feedback! * Carl-Daniel Hailfinger c-d.hailfinger.devel.2...@gmx.net [140321 01:39]: I see a huge bottleneck in restricting the number of committers to six. - Corporate committers will be primarily obliged to get the stuff of their own employer committed,

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread Stefan Reinauer
* David Hubbard david.c.hubbard+coreb...@gmail.com [140323 10:56]: Coreboot can be relevant even if it only supports obsolete silicon. Coreboot was the first to bring sub-second boot times to laptops. There are more examples. Yes, we worked hard to get to that goal. If it were about obsolete

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread Stefan Reinauer
* David Hubbard david.c.hubbard+coreb...@gmail.com [140323 20:33]: On Sun, Mar 23, 2014 at 12:58 PM, Vladimir ' -coder/phcoder' Serbinenko phco...@gmail.com wrote: On 23.03.2014 19:24, ron minnich wrote: So I believe the problem is not the idea of gatekeepers, but the manner

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread Stefan Reinauer
* Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com [140321 04:31]: The proposition of gatekeepers would essentially kill community effort. Even in current infrastructure reviewing is a major slowdown. With small number of gatekeepers there wouldn't be any significant contributions as

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 25.03.2014 02:33, Stefan Reinauer wrote: * David Hubbard david.c.hubbard+coreb...@gmail.com [140323 20:33]: On Sun, Mar 23, 2014 at 12:58 PM, Vladimir ' -coder/phcoder' Serbinenko phco...@gmail.com wrote: On 23.03.2014 19:24, ron minnich wrote: So I believe the problem is not

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread ron minnich
On Mon, Mar 24, 2014 at 10:20 PM, Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com wrote: I don't see how this prevents any of my propositions for the bulk of the boards. The problem you describe isn't going away with your proposition. We still want to have a top which is supposed to

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 25.03.2014 06:34, ron minnich wrote: On Mon, Mar 24, 2014 at 10:20 PM, Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com mailto:phco...@gmail.com wrote: I don't see how this prevents any of my propositions for the bulk of the boards. The problem you describe isn't

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-24 Thread ron minnich
On Mon, Mar 24, 2014 at 10:37 PM, Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com wrote: That's why I added *supposed to*. I'm aware that some boards are probably broken and not much we can do about it. Except remove them, right? ron -- coreboot mailing list:

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 23.03.2014 04:10, Peter Stuge wrote: That isn't too different from creating a fork? Fork is better. With fork we don't have to deal with the same people who pushed the community out in the first place. signature.asc Description: OpenPGP digital signature -- coreboot mailing list:

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread mrnuke
On Sunday, March 23, 2014 07:34:32 AM Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 23.03.2014 04:10, Peter Stuge wrote: That isn't too different from creating a fork? Fork is better. With fork we don't have to deal with the same people who pushed the community out in the first place.

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread David Hubbard
On Sat, Mar 22, 2014 at 9:10 PM, Peter Stuge pe...@stuge.se wrote: Vladimir 'φ-coder/phcoder' Serbinenko wrote: The proposition of gatekeepers would essentially kill community effort. That might not be a bad thing. Unfortunately, considering how the hardware industry works, individual

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread Stefan Tauner
On Sun, 23 Mar 2014 03:56:35 -0600 David Hubbard david.c.hubbard+coreb...@gmail.com wrote: Stefan appears to be missing in action. No, well, he has stated that he want to wait till everybody has calmed down (on IRC). It looks to me that he may have to wait indefinitely though, and I would also

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread Peter Stuge
David Hubbard wrote: Unfortunately, considering how the hardware industry works, individual contributors in the community can't work on code for current hardware. Peter, you make good points. As a purely community contributor I'd be happy to sign any necessary NDAs to contribute on Google

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread Alex G.
David, When you go out of line with a private email, expect to find yourself on a public list. Alex On 03/23/2014 05:04 AM, David Hubbard wrote: On Sun, Mar 23, 2014 at 1:26 AM, mrnuke mr.nuke...@gmail.com mailto:mr.nuke...@gmail.com wrote: On Sunday, March 23, 2014 07:34:32 AM

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread Gregg Levine
Hello! Please don't next time. Its considered to be rather rude, especially if the sender asked you to keep it off the list. I don't pretend to know what David H, was thinking, but I surmise he was indeed thinking of that. - Gregg C Levine gregg.drw...@gmail.com This signature fought the Time

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread ron minnich
On Sat, Mar 22, 2014 at 11:34 PM, Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com wrote: On 23.03.2014 04:10, Peter Stuge wrote: That isn't too different from creating a fork? Fork is better. With fork we don't have to deal with the same people who pushed the community out in the first

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread mrnuke
On Sunday, March 23, 2014 05:37:37 PM Peter Stuge wrote: David Hubbard wrote: But Peter, what's your take on Alex's suggestion: What do we need to do to allow commercial contributors to work directly upstream? And before you discount this question for menial technical reasons, please take

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 23.03.2014 19:24, ron minnich wrote: So I believe the problem is not the idea of gatekeepers, but the manner in which they are proposed to work. Can you tell me what about this upsets you? I want to understand. The problem is that the proposal is that all commits go through gatekeepers. It's

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 23.03.2014 19:24, ron minnich wrote: I have friends who commit to grub2, and there seem to be gatekeepers there; how do you manage that process? In case of grub2 I admit we have exactly the problems I described. I'm open to having more maintainers but right now it doesn't seem to be feasible.

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-23 Thread David Hubbard
On Sun, Mar 23, 2014 at 12:58 PM, Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com wrote: On 23.03.2014 19:24, ron minnich wrote: So I believe the problem is not the idea of gatekeepers, but the manner in which they are proposed to work. Can you tell me what about this upsets you?

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-22 Thread Kevin O'Connor
On Thu, Mar 20, 2014 at 10:55:57PM +0100, Stefan Reinauer wrote: Changes to the coreboot Project Structure We -- the coreboot project -- have succeeded beyond our wildest expectations, with every major laptop vendor using our code. [...] To ensure consistency, scalability and conformity

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-22 Thread Peter Stuge
Vladimir 'φ-coder/phcoder' Serbinenko wrote: The proposition of gatekeepers would essentially kill community effort. That might not be a bad thing. Unfortunately, considering how the hardware industry works, individual contributors in the community can't work on code for current hardware.

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-21 Thread David Hubbard
On Thu, Mar 20, 2014 at 9:31 PM, Vladimir 'φ-coder/phcoder' Serbinenko phco...@gmail.com wrote: On 21.03.2014 01:39, Carl-Daniel Hailfinger wrote: Hi Stefan, streamlining development and maintenance is definitely absoutely worthwhile. Getting rid of unmaintained code is also a good

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-21 Thread Kyösti Mälkki
On 03/20/2014 11:55 PM, Stefan Reinauer wrote: Changes to the coreboot Project Structure .. * Significantly reduce number of submitters To ensure consistency, scalability and conformity with the general coreboot strategy, we need to define a clear committer structure that defines the

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-21 Thread David Hendricks
On Thu, Mar 20, 2014 at 2:55 PM, Stefan Reinauer stefan.reina...@coreboot.org wrote: * Build a MAINTAINERS file for common code, and encourage people to keep subsystem maintainers in the loop for changes Aiming for top notch code quality, the coreboot project is generally trying to

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-21 Thread David Hendricks
On Thu, Mar 20, 2014 at 5:39 PM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2...@gmx.net wrote: Hi Stefan, streamlining development and maintenance is definitely absoutely worthwhile. Getting rid of unmaintained code is also a good thing. The guidelines presented in your mail look mostly

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-21 Thread David Hendricks
On Fri, Mar 21, 2014 at 11:52 AM, David Hendricks dhend...@google.comwrote: On Thu, Mar 20, 2014 at 5:39 PM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2...@gmx.net wrote: Hi Stefan, streamlining development and maintenance is definitely absoutely worthwhile. Getting rid of

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-20 Thread mrnuke
On Thursday, March 20, 2014 10:55:57 PM Stefan Reinauer wrote: Changes to the coreboot Project Structure Measures to improve the coreboot Development Model * Require authors to acknowledge changes made in their name (Forge-Author) [...] Couldn't agree more. * Define owners for (sets

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-20 Thread ron minnich
ah, blush, somebody wants me to be dictator. However, I can't do it. First off, if you're not going to let me invade some country, it's no fun. Secondly, it's hard to find Dictator clothes that look good on me. Just won't work. Thirdly, Stefan has been doing this very well for at least 7 years,

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-20 Thread Carl-Daniel Hailfinger
Hi Stefan, streamlining development and maintenance is definitely absoutely worthwhile. Getting rid of unmaintained code is also a good thing. The guidelines presented in your mail look mostly good IMHO, but I'd like to comment on a few things. Am 20.03.2014 22:55 schrieb Stefan Reinauer: *

Re: [coreboot] Changes to the coreboot Project Structure

2014-03-20 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 21.03.2014 01:39, Carl-Daniel Hailfinger wrote: Hi Stefan, streamlining development and maintenance is definitely absoutely worthwhile. Getting rid of unmaintained code is also a good thing. The guidelines presented in your mail look mostly good IMHO, but I'd like to comment on a few