3 Mar 2004 mrcsparker   » (Journeyer)

Forking Code and Releasing Early

Reading my email this morning I see that a project that I worked on is forking for what seems the hundredth time. I left it a few months ago waiting for the 2.6 kernel to start working on it again and it seems like about 3-4 developers have decided to start their own little 2.6 forks. You see, the problem is that the original project has not released often enough and the developers who actually need the code have gotten impatient. Myself, I have given up. The code looks like spaghetti now (with all of its #defines for 2.2, 2.3, 2.4, 2.5, and 2.6 kernels) and it really needs some serious cleaning up.

There is also another project that I started working with where the maintainer released the code under the GPL but did not want any patches from any external developers. No patches? The project does 75% of what my company needs and it seems a waste to start a new project all by myself. The Unix administrator has started installing the project on a few machines and it works really well but has some apparent shortcomings. So, do I fork? I emailed the maintainer and he does not seem keen to respond back.

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!