Suppose that you want to provide support for a bunch of open source codebut are not the primary author or maintainer. Inevitably you will haveto patch bugs and add features on your own in some way (and perhaps fixthe code to port it to your environment or whatever). This leads to aquestion: where is the dividing line between merely supporting the codeand actually forking your own version of the code?

To me, the dividing line is whether you can get your changes acceptedupstream and applied to the

There's a lot of things that get called 'configuration files', so I wantto be specific that I mean the sort of configuration files that have three primary uses : they'rewritten by people, used by programs, and later read by people who aretrying to figure out what the programs are set up to do. These are thekind of configuration files that XML is terrible for.

(There's a whole ecology of 'configuration files' that are generated byone program and consumed by