Diego Biurrun <[email protected]> writes: > > Not hard, but pointless, because it defeats the purpose of this endeavor, > which is making emacs behave correctly out-of-the-box. The operative > word here is "out-of-the-box". > > We do have a coding style, but far too often during reviews we have to > point that style out to people, especially newcomers. This is because > > a) the style is underdocumented and > b) it is too easy to mess up. > > I will address a) once I'm done with the spring cleanup. Luckily > Andrea has stepped up and contributed towards fixing b). Let's not > make getting contributions accepted harder than it already is, this > is going in the right direction. > > If the emacs defaults have to be set manually, then we will have to > keep telling people "Oh, you should have put that file from tools/ > in the top-level directory, now please redo your patch.", but we > don't want that, we want them to get it right from the start. > > Diego
+1. Moreover there is one other thing which I think is to note. The impression I get from some comments is that the libav community should be closed to the few aficionados, which know all the bureaucratic things that have to be done to participate in the project. There are outside many developers that would contribute with a couple of patches a year, and maybe they do the same on 15 different projects. These 15 different projects all use (of course) different coding styles and policies. It would be nice if instead of trying to figure out in some hidden documentation what is the desired style for this and that at least for the emacs/vi users would work automatically. These default settings would also not break anything as far as I know (or I would be glad to see a counterexample), and would avoid annoying things like: - fix the indentation - remove the trailing whitespaces over and over again. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
