commonality/architecture-decision-records

䷁ Capture important architectural and design decisions—along with their context and consequences—for the benefit of future team members, as well as and external oversight.

architecture-decision-records's Issues

ci(scm): init repo per community standards

1. User story summary of expected behavior

⌦ Describe what you want to accomplish, in what role/capacity,
⌦ and why it's important to you.

As an OSS community member,
I want clear README and CONTRIBUTING files
In order to use and contribute to this project.

2. Acceptance criteria

⌦ Replace the examples below with your own imperative, "true/false" statements`
⌦ for the behavior you expect to see, or the behavior that would be true if
⌦ there were no errors (for defects).

• 1. All recommended community standards are met.
• 2. There is support for multiple issue_template.md files.
• 3. There is support for multiple pull_request_template.md files.

🐞 3. Steps to reproduce (for defects only)

• ⌦ Provide a link to a live example, or

• ⌦ Replace the examples below with an unambiguous sequence of
  ⌦ instructions that end with proof of the defect.

• ⌦ Include source code and log files, if relevant and available.

1. Enter the words "...." into the "Search" text field.
2. Select the Search button.
3. Next...
4. Then...
5. Finally...
6. X does not work as expected.

🐞 4. Your environment (for defects only)

• ⌦ Include as many relevant details about the environment
  ⌦ in which the defect occured.

• Version of generator-community:
• Environment name and version (e.g. Chrome 39, node.js 5.4):
• Operating System and version (desktop or mobile):
• Link to your project: