> Should we move these up a directory? Content such as this will be > re-used across jboss, rhel, rhev, openstack, etc and avoidance of a > situation where every project has copies of this file would be idea.
Probably. But I think we should whiteboard it or something first. It might also make sense for each sub-project to still maintain their own references folder, containing links to the common/relevant items available in a toplevel "common" or "common/references" directory. There is an analogous issue for transforms. A little thought should go into it, and hopefully address both at the same time (and updating Makefiles if necessary). We don't need to solve this until there is activity in another sub-project, however. And even then, not until we actually have a transform that is making use of the particular references doc, which may come along shortly... > Does it make sense to move the entire references directory up a level? > While some items are tagged as RHEL, they'll be reused for RH Storage > and RHEV which use RHEL as a base (and thus will likely make references > to OS SRGs and so forth). _______________________________________________ scap-security-guide mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
