Alexander Leidinger wrote: > Quoting Sofian Brabez <[EMAIL PROTECTED]> (from Fri, 4 Apr 2008 05:11:41 > +0200): > >> About syscl(3) OID description lack, i send my Google Summer Code >> application to complete it this summer ;). > > Unfortunately this is not suitable for the SoC. Google wants code > contributions, not pure documentation work. Maybe you can find something > else you would be willing to do during the SoC. In case you haven't send > multiple applications, feel free to send more than one.
I feel that in this case it's only the case of proper wording. Strictly speaking, adding descriptions to sysctls is a matter of coding kernel code in C. Though it may not be 100% within the spirit of the rules, it's certainly within the legalese. In any case it's not exactly trivial since some semantics used by sysctls are convoluted and require either understanding the code or nagging the author of the code. I also feel that it's a practically very useful project (augmented with writing "real" documentation as an integral, but officially out of focus, part of the project).
signature.asc
Description: OpenPGP digital signature