Zen-Sources is a collaborative effort of kernel hackers and enthusiasts to provide the best Linux kernel possible. We include code that is not yet found in the mainline kernel in an attempt to support the latest hardware, new features, security fixes, optimizations, etc. We are generally more up to date than your distribution's default kernel. If there is something you would like included in a future Zen kernel just ask and we will try to include it. Zen-Sources is NOT a "patchset" like many of you are used to. Zen-Sources is a Linux kernel. We do all of our development in a git repository, and most of the code we include gets pulled from other git repositories. Since we rarely interact with patches these days, we are not going to go out of our way to provide "broken-out patches". The only patch you will get from us is a monolithic patch applied on top of some vanilla kernel base; we prefer you to use git and "git checkout" the latest stable tag. If you need a "broken-out patch" use gitweb or 'git diff'.
Dec 18 17:30

Use KLive to help us track Zen kernel usage stats!

The KLive system (http://klive.cpushare.com/) is used by any volunteer Linux users that wish to contribute and provide statistical information about kernel versions usage. Ultimately, this information helps in the kernel development process. More about KLive can be found on the KLive wiki (https://www.cpushare.com/wiki/klive/).

On Gentoo it's as easy as "emerge klive; rc-udpate add klive default"

Apr 05 04:24

Tuxonice gone

Tuxonce is gone starting with [b]2.6.29-zen3[/b], tuxonice will never be in another zen release as a third party feature.

This is due to its [b]tendency to break other things, tendency to not compile unless you are compiling tuxonice too, and it's overally general flake/unstableness[/b]

If you need tuxonice in a future zen release, you are responsible to incorporate it yourself. You will NOT be supported. Any threads in the forum relating to an unofficially patched tuxonice problem will be ignored, any bugs in the bug tracker will be closed and marked as "won't fix"

Mar 27 20:27

Branch master-rt!

- New branch popped up, master-rt. It's some branches merged on top of the rt patch
- Some stuff from zen is missing for various reasons
- If you tell me you are using for anything other than audio/dj related things then I will probably make fun of you (a lot)

[b]This is 100% unsupported, if anything comes up in bug tracker or forums it will be closed/deleted accordingly

If I see a ubuntu wiki or forum or something with instructions on how to get a zenrt kernel, master-rt will disappear.

If you have any questions, direct it to irc (#zen-sources - freenode) or email.

Mar 14 23:02

What is included in a zen kernel?

[color=indigo]*[/color] A general list of kernel code included in zen kernels can be found at: http://zen-sources.org/content/kernel-code-included-zen-kernels
[color=indigo]*[/color] The list isn't true for every zen release, but you can view [url=http://git.zen-sources.org/]gitweb[/url] for a truly accurate idea.

Mar 14 01:04

Help! I get all these merge conflicts!

[color=indigo]*[/color] This happens rarely now since we merge -s ours on every rebase now, but in some situations we may have to reset the tree if something breaks which will cause something like this:

Code:
Auto-merged .gitignore
Auto-merged MAINTAINERS
Auto-merged Makefile
CONFLICT (content): Merge conflict in Makefile
Removed arch/mips/lasat/sysctl.h
Auto-merged drivers/ata/libata-scsi.c
Auto-merged drivers/char/Kconfig
Auto-merged drivers/char/drm/ati_pcigart.c
Auto-merged drivers/char/drm/drm.h
Auto-merged drivers/char/drm/drm_drv.c

Mar 14 00:56

User input/relations/etc?

[color=indigo]*[/color] Users requests are always considered if they are practical and aren't asking for any broken/ugly/hacked code.
[color=indigo]*[/color] Users often help in the community answering questions, responding to issues, etc. No one questions this :P
[color=indigo]*[/color] If someone comes into irc with a problem it is usually solved instantly because someone in there is always ready to help out, if it's a bug in the git tree a solution is usually determined on the spot and pushed to git immediately afterward.

Mar 14 00:52

I want to become a developer, how can I?

[color=indigo]*[/color] I don't know, there are no applications or anything.
[color=indigo]*[/color] The only way you could possibly get git push access is if you are active in irc often, and contribute extreme amounts of things (enough where we're not around all the time for you to inquire about it), and then you would be invited.
[color=indigo]*[/color] Pretty much the only way you can become one is if we ask you to, and that doesn't happen very often.

Mar 14 00:42

I want to incorporate zen-sources into my project! How can I?

[color=indigo]*[/color] If you are running a linux distribution, linux CD, or other project and are determining what to base your kernel off on in your distribution, you may want to consider using zen-sources instead of creating one for scratch.
[color=indigo]*[/color] Reasons for this may be: It's fully featured (loaded with features that some or ALL of users may find useful), It's updated practically every day through git, it's documented nearly completely, proven stability, etc.

Mar 14 00:26

Why should I use this kernel?

[color=indigo]*[/color] Basically, this kernel includes everything you could possible want and need. Even if you don't need anything you will find something useful in a zen kernel that you won't find in linus' kernel or another patchset.
[color=indigo]*[/color] This kernel has a solid community for support. If you log on to irc and want a feature there is a strong chance that if a dev is vailable that that feature will be added right then and there (except for sloppy/hacked/broken code, for example: squashfs-lzma)

Mar 14 00:25

Who develops it?

[color=indigo]*[/color] The developer list for the zen-sources kernel can be found at: http://zen-sources.org/content/developer-list