Slashdot Mirror

← Back to Stories (view on slashdot.org)

Linux Foundation Paving Way for New Kernel Developers

Posted by ScuttleMonkey on from the map-and-a-stopwatch-for-flying-blind dept.

Jack Spine writes "The Linux Foundation has published a how-to document for developers who want to negotiate the hidden shoals of open source. According to both the Linux Foundation and the Open Source Consortium, developers can get frustrated with the processes in open source coding, especially for enterprise-class projects like Linux. 'A guide to the kernel development process' aims to encourage participation from new programmers by explaining what's involved. Some developers and businesses attempting to submit changes to the Linux kernel find themselves tangled up with the processes used, according to the guide, which was written by Jonathan Corbet, executive editor of lwn.net and himself a Linux developer."

5 of 46 comments (clear)

  1. How much skill? by colmore · · Score: 4, Insightful

    So I can pretty well follow a spec, an algorithm description, or pseudo-code in C. But I'm no pro. Do I have the skills to start contributing to a top-tier open source project like the kernel, gcc, apache, etc? I'm looking at this link, what others would people recommend for how to get started?

    --
    In Capitalist America, bank robs you!
    1. Re:How much skill? by larry+bagina · · Score: 4, Insightful
      1. use FREE software.
      2. Find bugs, annoyances, or missing features.
      3. submit bug report, enhancement request, or patch
      4. watch bug report get ignored or closed, watch patch get rejected for using 4 spaces per tab instead of 2
      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    2. Re:How much skill? by Thiez · · Score: 3, Insightful

      5. Write javascript webpage that can change the indent style of code (K&R, Allman, KNF, GNU, etc). (Paste code in textarea, select style, click 'Go', and the code changes to the selected style)
      6. Place some adds on your webpage
      7. ???
      8. Profit!

  2. Just submit a patch by thefear · · Score: 3, Insightful

    The worst they can do is not apply it

    --
    :(
    1. Re:Just submit a patch by greg1104 · · Score: 5, Insightful

      Actually, the worst they can do is not apply it and decide you're incompetent/don't play by the rules/etc. Then you risk your future submissions being less likely to be considered even if you improve later. The person who wastes the time of a patch reviewer is not soon forgotten by that reviewer.

      It really is better to not submit a patch at all if you don't know what's going on yet, which is exactly why guides like this one are helpful. I've worked on a similar one for PostgreSQL because it's hard for new people to pick up the unique requirement quirks of a group of developers, and lowering that barrier improves the health of the project.