Aging Linux Kernel Community Is Looking For Younger Participants

Lemeowski writes "Time has been good to Linux and the kernel community, with the level of participation and volume of activity reaching unprecedented levels. But as core Linux kernel developers grow older, there's a very real concern about ensuring younger generations are getting involved. In this post, Open Access supporter Luis Ibanez shares some exciting stats about recent releases of the Linux kernel, but also warns that 'Maintaining the vitality of this large community does not happen spontaneously. On the contrary, it requires dedication and attention by community members on how to bring new contributors on board, and how to train them and integrate them alongside the well-established developers.'"

Comments

Well, I'll tell you why I'm not interested..

[Anonymous Coward]

I'm part of one of these younger generations, and I'm honestly not interested in getting involved because I've seen how much of a raging asshole Linuz can be. He's a great maintainer, but he could be honest and give constructive criticism in less condescending ways. I'm not as experienced as he is, but that doesn't give him the right to be a complete dick in public theater.

Re:Well, I'll tell you why I'm not interested..

[Joining Yet Again]

This. I've tinkered with the kernel, written device drivers, blah, but there's no way in hell I'd ever try to contribute upstream, because I know I'm not an experienced kernel hacker, and frankly I'm not sewn for the sort of macho abuse that dorks like to give each other.

There are other things I do as a hobby where I'm surrounded by people who are highly experienced, well-respected, but also excellent teachers - e.g. ham radio. There, I'm happy to do as much as I can for the community.

N.B. I'm not saying that I'd necessarily be good enough to contribute to the official kernel, merely that I wouldn't even try in that sort of environment.

Re:Well, I'll tell you why I'm not interested..

[Anonymous Coward]

in that sort of environment.

Well clearly you have never once 'been to' the LKML but instead built your opinion on the basis of stories-posted-on-slashdot.
Otherwise you would know that the LKML receives around 400 mails per day, the vast majority of which are polite, friendly and helpful.
Compare that with the number of posts offensive enough to make a story on /.

Re:Well, I'll tell you why I'm not interested..

[ifiwereasculptor]

It's funny how different perspectives can be. If I wanted to contribute to the kernel and someone ended up being severely impolite, I'd find it weird and either reply or don't. On the other hand, if my boss was being abusive, I'd switch jobs ASAP. I guess what I'm trying to say is that I find random interpersonal abuse way less disturbing than workplace abuse, since in the latter case you're at a clear hierarchical disadvantage and actually depend on your boss to get your paycheck.

And, by the way, it's interesting that you say "some prick who expects me to VOLUNTEER for the honor of having him dress me down like a bitch? Not so much." while posting on /., where that kind of free verbal aggression seems to be mandatory.

As someone who is taking OS course

[Anonymous Coward]

This semester, I am taking OS course at UMBC.
Course is easy, material is easy. Hard part - figuring out how the fuck you should write Linux Kernel code.
Why there are no good tutorials that on how to write basic kernel code, good guides on its structure (many book sold on Amazon are outdated) ......there should be one, centralized place with all the useful materials for the beginners + it should be constantly updated.

Re:Consider the possibility it might be done

[fisted]

I know I've mentioned this before, but you need to consider the possibility that your software might be done.

Considered and considered stupid, because suggested in the context of operating systems. Operating systems are only done when hardware is 'done', which is unlikely to happen any time soon IMO.

Propose projects on which newbies can start

[lorinc]

I'm actually managing an OS course for graduate students, and it's heavily based on linux (userspace and kernelspace). We do a few exercices (like writing a kernel module that computes averages), but nothing fancy. I've always been looking to propose them some projects related to kernel dev, but as I'm not a kernel hacker myself, I have clearly no idea of what seems reasonable.

So here's the deal: If you are involved on some subsystem of the linux kernel and you have something you want to get coded that can be a first experience with kernel dev, and that can be done under about 100 hours (the length of a typical project), you contact me. I'll do as much as possible as a first step filtering so that you won't get spamed. It's a win-win situation: I have great projects for my students, you get free work. For this year, it's a bit short, because projects are from September until January, but next year is ok.

The real problem is in not hiring junior anybody

[undeadbill]

When Linux was first released, it was relatively easy to break into the IT field and get directly into programming with limited experience and resources. The fact that the Linux kernel was initially created by a 15 year old kid on a home computer says much about that. My saying so doesn't lessen Linus Torvald's genius in any way, but it does underscore how those opportunities to create haven't been extended to future 15 year olds in the same manner.

Or anyone of working age. When was the last time a company hired junior admins and other flunkies specifically for the purpose of training them up to a competent level of expertise? That was common in the 90s, and is almost non-existent 20 years later. The last two companies I've worked for flat out refuse to hire junior staff and train them. Many companies refuse to future proof their IT (ops and dev) staffing in any way. This has led to a huge gap in expertise.

The final issue that was birthed out of refusing to hire inexperienced staff is all of the certification programs that arose as a result of such parsimony. Am I the only one who thinks that being able to turn on a few services *doesn't* make someone a systems administrator? I'd be more concerned about their ability to write and update their own changes to services, and to the man pages, and submitting complete work back to the relevant project- but THAT isn't (generally) taught in the cert programs, even though that will make someone a better administrator and/or developer. This just weakens expectations in the field, and severely limits a self-selected candidate pool of future kernel programmers.

"environment"

[SuperBanana]

Well clearly you do not understand what the word "environment" means.

If someone makes a sexist, derogatory joke in the weekly programming meeting and someone is offended and complains, it's not a defense to say "well it was only one joke, in one meeting, from one person."

The problem is not the one joke. The problem is that the environment was conducive, accepting, and tolerant of the joke. Linus's abusive treatment of others is not only tolerated, but accepted, excused, and justified, both there and on other communities (like Slashdot, right now...) Because he's in a leadership position, it sets the example and tone for how others are treated...

The response to people saying "I'm not comfortable contributing" is not "stop being a baby." If it is, you don't actually care about getting people to contribute.