162306a36Sopenharmony_ci.. _development_process_main: 262306a36Sopenharmony_ci 362306a36Sopenharmony_ciA guide to the Kernel Development Process 462306a36Sopenharmony_ci========================================= 562306a36Sopenharmony_ci 662306a36Sopenharmony_ciContents: 762306a36Sopenharmony_ci 862306a36Sopenharmony_ci.. toctree:: 962306a36Sopenharmony_ci :numbered: 1062306a36Sopenharmony_ci :maxdepth: 2 1162306a36Sopenharmony_ci 1262306a36Sopenharmony_ci 1.Intro 1362306a36Sopenharmony_ci 2.Process 1462306a36Sopenharmony_ci 3.Early-stage 1562306a36Sopenharmony_ci 4.Coding 1662306a36Sopenharmony_ci 5.Posting 1762306a36Sopenharmony_ci 6.Followthrough 1862306a36Sopenharmony_ci 7.AdvancedTopics 1962306a36Sopenharmony_ci 8.Conclusion 2062306a36Sopenharmony_ci 2162306a36Sopenharmony_ciThe purpose of this document is to help developers (and their managers) 2262306a36Sopenharmony_ciwork with the development community with a minimum of frustration. It is 2362306a36Sopenharmony_cian attempt to document how this community works in a way which is 2462306a36Sopenharmony_ciaccessible to those who are not intimately familiar with Linux kernel 2562306a36Sopenharmony_cidevelopment (or, indeed, free software development in general). While 2662306a36Sopenharmony_cithere is some technical material here, this is very much a process-oriented 2762306a36Sopenharmony_cidiscussion which does not require a deep knowledge of kernel programming to 2862306a36Sopenharmony_ciunderstand. 29