Fwd: GitHub repos for 2.0 development

[Gabriel Alford]

Forwarding the email that I sent to the scap-dev list just in case people are paying attention more to the workgroups mailing lists.

Please let me know thoughts.

Gabriel Alford

Member of the technical staff

office of the chief technologist

red hat Public Sector

Red Hat

ral...@redhat.com    T: 972-707-6483    M: 303-550-7234    

---------- Forwarded message ---------
From: Gabriel Alford <ral...@redhat.com>
Date: Mon, May 20, 2019 at 10:08 AM
Subject: GitHub repos for 2.0 development
To: scap...@list.nist.gov <scap...@list.nist.gov>

Hello everyone,

At the SCAP Dev 2.0 workshop, multiple groups wanted github repos. Rather than have multiple orgs and repos all over the Github-sphere, what do you think about having a centralized location for development? There are many benefits to this. Since https://github.com/scap is taken, what about https://github.com/scapcommunity ? We can mirror the OVAL community repo there as well.

We probably shouldn’t have everyone as organization admins, but can set up a couple of people from the various 2.0 working groups. Thoughts? If people like this, they can email me off list for access at ral...@redhat.com

Gabe

--

Gabriel Alford

Member of the technical staff

office of the chief technologist

red hat Public Sector

Red Hat

ral...@redhat.com    T: 972-707-6483    M: 303-550-7234    

[Stephen Banghart]

Personally I'd support coordinating all in one repo, but I'd be curious to see what David R. thinks about migrating since he did the work to setup our current repo.

[Gabriel Alford]

I think that it is important to note that there would be a single GitHub organization with multiple repos (much like https://github.com/usnistgov).

So whatever David R. setup for the current repo would still work, it would be just be https://github.com/scapcommunity/my_repo

which makes it easy for people to find, use, and contribute versus all the different locations that we have today.

Gabriel Alford

Member of the technical staff

office of the chief technologist

red hat Public Sector

Red Hat

ral...@redhat.com    T: 972-707-6483    M: 303-550-7234    

--
To unsubscribe from this group, send email to scap-dev-conte...@list.nist.gov
Visit this group at https://list.nist.gov/scap-dev-content
---
You received this message because you are subscribed to the Google Groups "scap-dev-content" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scap-dev-conte...@list.nist.gov.

[David Ries]

I’d prefer to keep it as-is.

I don’t see any benefit to centralizing under a single GitHub account. NIST has established a central listing of groups that links to mailing lists with repo info. And, I hesitate to put all this work under “SCAP”. In my experience “SCAP” is seen as a relatively narrow interest group that represents the US Fed Govt’s interests within the broader standards-based security automation community.

-David

On May 21, 2019, at 10:53 AM, 'Stephen Banghart' via scap-dev-content <scap-dev...@list.nist.gov> wrote:

Personally I'd support coordinating all in one repo, but I'd be curious to see what David R. thinks about migrating since he did the work to setup our current repo.

On Tuesday, May 21, 2019 at 11:49:05 AM UTC-4, Gabriel Alford wrote:

Forwarding the email that I sent to the scap-dev list just in case people are paying attention more to the workgroups mailing lists.

Please let me know thoughts.

Gabriel Alford

MEMBER OF THE TECHNICAL STAFF

OFFICE OF THE CHIEF TECHNOLOGIST

RED HAT PUBLIC SECTOR

Red Hat 

ral...@redhat.com    T: 972-707-6483    M: 303-550-7234    

---------- Forwarded message ---------
From: Gabriel Alford <ral...@redhat.com>
Date: Mon, May 20, 2019 at 10:08 AM
Subject: GitHub repos for 2.0 development
To: scap...@list.nist.gov <scap...@list.nist.gov>

Hello everyone,

At the SCAP Dev 2.0 workshop, multiple groups wanted github repos. Rather than have multiple orgs and repos all over the Github-sphere, what do you think about having a centralized location for development? There are many benefits to this. Since https://github.com/scap is taken, what about https://github.com/scapcommunity ? We can mirror the OVAL community repo there as well.

We probably shouldn’t have everyone as organization admins, but can set up a couple of people from the various 2.0 working groups. Thoughts? If people like this, they can email me off list for access at ral...@redhat.com

Gabe

-- 

Gabriel Alford

MEMBER OF THE TECHNICAL STAFF

OFFICE OF THE CHIEF TECHNOLOGIST

RED HAT PUBLIC SECTOR

Red Hat 

ral...@redhat.com    T: 972-707-6483    M: 303-550-7234    

-- 
To unsubscribe from this group, send email to scap-dev-conte...@list.nist.gov
Visit this group at https://list.nist.gov/scap-dev-content
--- 
You received this message because you are subscribed to the Google Groups "scap-dev-content" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scap-dev-conte...@list.nist.gov.

David E. Ries
Co-Founder, Business Development
ri...@jovalcm.com