stucco / stucco.github.io Goto Github PK

We're sure you carefully considered the structure of your STUCCO GitHub repos when planning this initiative. Intent in engaging on this topic here is to seek guidance on how to best deal with some of the resultant challenges we are having with integrating the ~32 separate STUCCO repos.

We've solved some of the challenges in managing local cloning and forking of the separate STUCCO GitHub repos by developing custom git shell scripts and Vagrantfiles. This has ultimately provided much more effective automation of what were initially highly manual processes (PS - Many, many thanks for introducing us to Vagrant through this project!!! It is proving to be a transformational tool for the evaluation, development, sharing, and operational deployment of Tools and Frameworks).

We have just established a GitHub Organizational account to provide private repositories for organization specific non-public collaborative development. As part of this overall initiative we are starting initiatives to integrate STUCCO with our organization specific customizations of MITRE CRITs. We are also looking to continue/accelerate our efforts to evangelize the integration and adoption of DHS/MITRE STIX/CybOx/MAEC schema and taxonomies for STUCCO Ontologies as well as integration of DHS/MITRE TAXII gateways once STIX integration is completed.

We are leveraging our Organizational non-profit status to establish 10 initial private repos to support our development collaboration initiatives for no cost. One challenge we haven't solved is how to fork private instances/branches of the ~32 separate STUCCO repos without incurring significant cost (relatively speaking) for our Organizational Private repos. We have one private repo "seat" available to support our STUCCO related initiatives.

While we considered cloning and consolidating/restructuring STUCCO internally, we ultimately want to submit and share non-sensitive elements of our efforts with the public STUCCO community. It seems that if we stray from the central STUCCO structure internally, this community sharing and synchronization process (as well as integrating changes to central Branches, forks, etc) will become convuluted at best, if not impossible. Again, as neophytes in this specifc aspect of GitHub, we're hopeful there may be a very simple elegant solution that has eluded us thus far.

Welcome any sugggestions or references to practical approaches for similar Use Cases.

Note: We have tried to initiate a dialog with the STUCCO Team through our DHS and MITRE channels on the integration and adoption of DHS/MITRE STIX/CybOx/MAEC schema and taxonomies for STUCCO Ontologies. We are very interested in engaging directly on this topic.