Differences between revisions 1 and 2
Revision 1 as of 2005-05-29 02:33:23
Size: 1669
Editor: anonymous
Comment:
Revision 2 as of 2005-05-29 02:55:33
Size: 1935
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
   * DebianKernelHistory
Line 4: Line 5:
   * security for testing/unstable
 * Package architecture. What packages does our team create, and what are they for?
   * kernel-tree vs. kernel-source
   * What kernel-headers do I need?
 * What is the right way to file a bug?
   * DebianKernelSecurity for testing/unstable
 * DebianKernelPackages - What packages does our team create, and what are they for?
   * DebianKernelTree - kernel-tree vs. kernel-source
   * DebianKernelHeaders - What kernel-headers do I need?
 * DebianKernelFilingBugs - What is the right way to file a bug?
Line 13: Line 14:
 * Where can you find our source? A walk through svn.
 * Daily build testing - Simon Horman and I have both done some work in this area; hopefully we'll have some results by DebConf5 time.
 * What requirements must a patch fulfill before we will include it
 * Interacting with the debian-installer team (l-k-di)
 * ABI changes; what they're for and why the suck
 * DebianKernelSourceControl
 * DebianKernelTesting - Simon Horman and I have both done some work in this area; hopefully we'll have some results by DebConf5 time.
 * DebianKernelPatchAcceptanceGuidelines - What requirements must a patch fulfill before we will include it
 * DebianKernelAndDebianInstaller - Interacting with the debian-installer team (l-k-di)
 * ["DebianKernelABIChanges"] - ABI changes; what they're for and why the suck
Line 22: Line 23:
 * How to build additional modules for our precompiled kernel-images
 * How the architectures work together (or not) - sharing configs, build system; sharing source vs. kernel-patch-ARCH packages.
 * DebianKernelBuildingModules - How to build additional modules for our precompiled kernel-images
 * DebianKernelArchitectureSynchronization - How the architectures work together (or not) - sharing configs, build system; sharing source vs. kernel-patch-ARCH packages.
Line 26: Line 27:
 * Firmware; what is acceptable and what's not. This topic maybe one to avoid, due to its political nature. It maybe better to fork this off into a BOF.  * KernelFirmwareLicensing; what is acceptable and what's not. This topic maybe one to avoid, due to its political nature. It maybe better to fork this off into a BOF.
  • Introduction - Who are we, and what do we do?
    • DebianKernelHistory

    • Maintenance of kernel-[source,image,patch-ARCH], initrd-tools, etc
    • ?DebianKernelSecurity for testing/unstable

  • ?DebianKernelPackages - What packages does our team create, and what are they for?

    • ?DebianKernelTree - kernel-tree vs. kernel-source

    • ?DebianKernelHeaders - What kernel-headers do I need?

  • ?DebianKernelFilingBugs - What is the right way to file a bug?

    • What bugs should be filed against the 'kernel' package, vs. a real package.
    • Classes of bugs
      • Build issues
      • Runtime issues
  • ?DebianKernelSourceControl

  • ?DebianKernelTesting - Simon Horman and I have both done some work in this area; hopefully we'll have some results by DebConf5 time.

  • DebianKernelPatchAcceptanceGuidelines - What requirements must a patch fulfill before we will include it

  • ?DebianKernelAndDebianInstaller - Interacting with the debian-installer team (l-k-di)

  • ["DebianKernelABIChanges"] - ABI changes; what they're for and why the suck
    • Exist for module compatability
    • Break upgrades (anecdotal ia64/vfat issue?)
    • How ABI breaks break debian-installer
    • Testing for ABI breaks
  • ?DebianKernelBuildingModules - How to build additional modules for our precompiled kernel-images

  • ?DebianKernelArchitectureSynchronization - How the architectures work together (or not) - sharing configs, build system; sharing source vs. kernel-patch-ARCH packages.

  • All-kernels-from-one-source-package plans. Sven Luther has been looking into building most (or all) of our kernels from a single source package. What are the benefits? What are the bottlenecks? What is the status?
  • What areas can we use help?
  • KernelFirmwareLicensing; what is acceptable and what's not. This topic maybe one to avoid, due to its political nature. It maybe better to fork this off into a BOF.