adidas / adidas-devops-maturity-framework Goto Github PK

• I'm submitting a ...

  • [X ] bug report
  • feature request
  • support request

• What is the current behavior?
  Spelling mistake under Development Capability, Releases row under RUN section. It says

"Gradual releases to subset of users in specific sites / geographies thereby limiting the blash raduis for potential issues"

• What is the expected behavior?
  Change to

"Gradual releases to subset of users in specific sites / geographies thereby limiting the blast radius for potential issues"

• What is the motivation / use case for changing the behavior?

Correcting the spelling error

• Other information (e.g. detailed explanation, related issues, links for us to have context, etc)

• I'm submitting a ...

  • [X ] bug report
  • feature request
  • support request

• What is the current behavior?
  Possible typo in the devops_maturity_framework.md
  "Tight" vs. "Tied"?
  See Architecture Capability, "Use a loosely coupled architecture"

"System have no or very few direct dependencies to other systems. And those dependencies are tight to open standards and not tight to technologies and frameworks (e.g. Java RPC)"

• What is the expected behavior?
  I assume "Tied" was intended?

• What is the motivation / use case for changing the behavior?
  Help improve the quality of the documentation

• Other information (e.g. detailed explanation, related issues, links for us to have context, etc)
  https://github.com/adidas/adidas-devops-maturity-framework/blob/master/framework/devops_maturity_framework.md

• I'm submitting a ...

  • support request

• What is the current behavior?
  You recommend that All production artifacts under version control. Does that mean you recommend to put binaries and docker containers into version control systems too?

• What is the expected behavior?
  No binaries in git.

• I'm submitting a ...

  • support request

• What is the current behavior?
  What is Platform Engineering? Please clarify. If it is not the DevOps team then how are they different?

• I'm submitting a ...

  • bug report

• What is the current behavior?

• The crawl in "SRE role and activities" says 'responsibilty`
• The walk in "Resiliency / Chaos Engineering" says 'resilency'
• The run in "Foster and enable team experimentation linked to business value" says 'experimentation'

• What is the expected behavior?

• The crawl in "SRE role and activities" should say 'responsibility`
• The walk in "Resiliency / Chaos Engineering" should say 'resiliency'
• The run in "Foster and enable team experimentation linked to business value" should say 'experimentations' like crawl and walk do

• What is the motivation / use case for changing the behavior?

• Not a deal breaker, but spelling mistakes don't look professional

• Other information (e.g. detailed explanation, related issues, links for us to have context, etc)
  The spelling mistakes are in adidas-devops-maturity-framework/framework/devops_maturity_framework

Fix in my PR #11

• I'm submitting a ...

  • bug report
  • feature request
  • support request

• What is the current behavior?
  The MIT license must be updated with the correct aim and designed purposes.
  Fixes:

  • MIT license with the aim of helping the community with our tools and libraries which we think can be also useful for other people.
  • NOTICE: The software has been designed solely for the purpose of analyzing the code quality by checking the coding guidelines.

• What is the expected behavior?
  Replace those two sentences with the correct purpose.

• What is the motivation / use case for changing the behavior?
  License must fit the rules.

• I'm submitting a ...

  • support request

• What is the current behavior?
  All team members are able to access private customer data in PROD.

• What is the expected behavior?
  Access to PROD is limited to the secure team.

• What is the motivation / use case for changing the behavior?
  Reduce attack vector. Comply with GDPR. Get clarity regarding who specifically can access customer data in in which cases.

• Other information (e.g. detailed explanation, related issues, links for us to have context, etc)