| 1 |
On Mon, Oct 21, 2013 at 5:55 PM, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
| 2 |
> On 2013-10-20 9:14 PM, Mark David Dumlao <madumlao@×××××.com> wrote: |
| 3 |
>> |
| 4 |
>> Linus isnt actually actively developing the kernel nowadays. Mostly he |
| 5 |
>> just merges commits from his "trusted lieutenants" in charge of various |
| 6 |
>> subsystems. The notion of Linus as being at the helm is mostly just a |
| 7 |
>> convenient fiction that corporate culture (and by extension, the media) |
| 8 |
>> - which is used to "strong leadership" - uses to make sense of open |
| 9 |
>> source development. |
| 10 |
> |
| 11 |
> |
| 12 |
> I know all that, but he does have the final word on merges still, right? |
| 13 |
> Which is the most important aspect of the point at hand... |
| 14 |
> |
| 15 |
|
| 16 |
I doubt he actually has the time to read every line of code submitted |
| 17 |
to the kernel, being that in 2008, it was running at 6000+ lines / |
| 18 |
changes per day and it's only gotten faster. |
| 19 |
|
| 20 |
Again, most of kernel development is very largely self-organizing. |
| 21 |
There are of course, rally points around some personalities, but it's |
| 22 |
an exaggeration of trust to rely on Linus to be the gatekeeper for |
| 23 |
political decisions. Especially since he famously dislikes getting |
| 24 |
involved in politics. |
| 25 |
|
| 26 |
http://www.youtube.com/watch?v=L2SED6sewRw |
| 27 |
|
| 28 |
tldr: if the maintainer of some subsystem agrees, it's probably in. It |
| 29 |
takes a lot of trust to get to become a maintainer. |
| 30 |
|
| 31 |
-- |
| 32 |
This email is: [ ] actionable [x] fyi [ ] social |
| 33 |
Response needed: [ ] yes [ ] up to you [x] no |
| 34 |
Time-sensitive: [ ] immediate [ ] soon [x] none |
Archives