From Openscap

Contribute

Mailing List

The development of open-SCAP is done on the open-scap mailing list. You can join at open-scap-list. Feel free to introduce yourself to the list and let us know what areas of development are of most interest to you.

IRC

There is #openscap channel available on FreeNode.

Bug and Feature Tracking

We use Red Hat's bugzilla to track bugs and features. Fill out this from form please and choose openscap as a component.

Submitting Changes

Open-SCAP is licensed under the LGPL. By submitting a patch for inclusion in open-SCAP, you are agreeing to license your changes under the LGPL.

Changes to the repository are submitted via patches on the open-scap mailing list (see above for list information). The best way to prepare the patch is to commit the change locally and use

git-format-patch -1 commit-id

to export the patch (where commit-id is the commit number of the checkin you want to send, use 'git log' to see it).

Notes to Coding Style

1. Prefix - All names of structures, functions, enums, have some kind of prefix that identify SCAP specification. We have these spicifications CPE, CVE, CVSS, OVAL, XCCDF
2. Functions - We use following syntax for structure names: prefix_object_operation_{subject} . If there is only one possible subject, then subject is not mandatory. Operation might be one of these: load,export,get,add,set,cast,free,new,update Examples: oval_object_model_load (no subject!), oval_object_model_get_object.
3. Structures- We use following syntax for structure names: prefix_name_{type} . Type might be for example: model, iterator, map. Our aim is to have all structures and their functions together in sorted list! Example: oval_sysitem_iterator, oval_object_model.
4. User defined types (typedef) - syntax: prefix_name_t.
5. Indentation - $indent -linux -l120