helpfulengineering / devops Goto Github PK

I would like to...

• [] Import an existing repository
• Create a new repository

The current address of my repository is...

The Slack channel of the project is...

project-deelgo

I want to license the data under...

• [] Hardware and/or firmware: CERN-OHL-P
• Software: Apache License, Version 2.0
• Guides, instructional videos, and other materials: Creative Commons Attribution 4.0

Source: official licensing guide

Create new stackset in sandbox account to create dev SAML2 identity provider and assumable SAML2 Roles

I would like to...

• Import an existing repository
• Create a new repository

The current address of my repository is...

https://github.com/fpdotmonkey/SplitterStaging

The Slack channel of the project is...

#project-tetra

I want to license the data under...

• Hardware and/or firmware: CERN-OHL-P
• Software: Apache License, Version 2.0
• Guides, instructional videos, and other materials: Creative Commons Attribution 4.0

Source: official licensing guide

About

One of the items that was brought up in our last conversation was the term SRE being more fitting for the team/efforts. This was not addressed since and when I wanted to start writing some into documentation, I was confronted with this question first.

Call to action

Not being a DevOps eng or SRE, I don't think I can make the call here.
It would be great if there was a 1-3 day conversation here to document the decision on this here:
Should this remain as "DevOps" or should we change the name to SRE as suggested once?

I know this is not an important issue, but this is good practice for us to document decisions in github and create a culture based on conversations and collaboration.

Gsuite set up documentation

Specify that the org member setting up a shared inbox is required to get in touch with a DevOps member before starting the process as the verification code needs to be shared in coordination.

I would like to...

• [] Import an existing repository
• [ x] Create a new repository

The current address of my repository is...

The Slack channel of the project is...

I want to license the data under...

• Hardware and/or firmware: CERN-OHL-P
• Software: Apache License, Version 2.0
• Guides, instructional videos, and other materials: Creative Commons Attribution 4.0
• [x ] outstanding question

Source: official licensing guide