Comment 9 for bug 1313224

When I take a look at the debian bug report page I think I know how Merry and Pippin must have felt when they first met the ents.

After a brief look at the build process it doesn't look overly complicated to do the actual work and bundle the latest released stable version of naxsi and the corresponding learning/white-list tool, I would be happy to provide a patch if requested or invited.

But some package reorganization would be required and I guess this is just like my normal life, I don't get to decide what goes into where and when.

Are there any formal policy documents that can be uses as guidelines for an issue like this? Or is there any place were such issues are discussed?

As of now I consider the state of nginx and naxsi broken for anything but simple use-cases, and it's very confusing when a naxsi proselyte tries to read up on why things don't work and all the information you can find doesn't look or behave like the installation that is done by these packages .

Is the debian upstream package the proper place to try to fix this issue or could it be done using the ubuntu package version and afterwards "push" the change-set upstream?