pburkholder / decksets Goto Github PK

Regular text:

Console:

✔ ~/Projects/18f/cg-dashboard [master ↓·12|✔]
12:59 $ ls
CONTRIBUTING.md		circle.yml		env.sample		package.json		templates/
Gopkg.lock		codecheck.sh*		helpers/		profile.cov		wdio.conf.js
Gopkg.toml		context/		karma.conf.js		redirects/		webpack.config.js
LICENSE.md		controllers/		mailer/			screenshots/
Procfile		deploy/			manifests/		server.go
README.md		devtools/		node_modules/		static/
RELEASE.md		docker-compose.yml	npm-shrinkwrap.json	static_src/

Shell:

✔ ~/Projects/18f/cg-dashboard [master ↓·12|✔]
12:59 $ ls
CONTRIBUTING.md		circle.yml		env.sample		package.json		templates/
Gopkg.lock		codecheck.sh*		helpers/		profile.cov		wdio.conf.js
Gopkg.toml		context/		karma.conf.js		redirects/		webpack.config.js
LICENSE.md		controllers/		mailer/			screenshots/
Procfile		deploy/			manifests/		server.go
README.md		devtools/		node_modules/		static/
RELEASE.md		docker-compose.yml	npm-shrinkwrap.json	static_src/

This issue was automatically created by Allstar.

Security Policy Violation
Security policy not enabled.
A SECURITY.md file can give users information about what constitutes a vulnerability and how to report one securely so that information about a bug is not publicly visible. Examples of secure reporting methods include using an issue tracker with private issue support, or encrypted email with a published key.

To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/pburkholder/decksets/security/policy to enable.

For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository.

Created by pburkholder/.allstar and GSA-TTS/.allstar

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

This issue was automatically created by Allstar.

Security Policy Violation
No protection found for branch master

Created by pburkholder/.allstar and GSA-TTS/.allstar

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

2001

• Space odyssey photo
• DLESE photo
• We were a 1 pizza team
• We released on demand
• John Weatherly introduced my to TDD w/ JUnit
• Tim ... introduced me to cfengine
• I learned about CVS
• I was the Ops guy, but I worked every day with the Devs
• Attended all engineering planning meetings
• We launched and kept launch & won awards....

2007

• NIH - Engineers were in a different f'ing building
• We did a lot of things right technically, but...
• I tried to build technical liaisons between ops groups and engineers, but the culture wasn't ready.

In 2009 - It all started clicking w/ Hammond and Alllspaw

2011 started supported DevOpsDC meetup.

Where to now?

• DEI - If DevOps is Aha! to Kaching!, we need the best ideas, and the best perspectives on them. We just have the white guys getting funding and we'll just have more Juiceros, WeWorks and Ubers.
• Shift security left on the value chaing
• Shif technology right on the Wardley maps
• Platfform, platform, platforms