Initial public version v0.0.1.

Author: AlekSi

.github/CODEOWNERS

@@ -0,0 +1 @@
+*   @AlekSi

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,16 @@
+*Please use this template for reporting suspected bugs or requests for help.*
+
+# Issue description
+
+# Environment
+
+* Gosh version (commit hash if unreleased):
+* `go env` output:
+
+# Minimal test code / Steps to reproduce the issue
+
+1.
+
+# What's the actual result? (include panic message & call stack if applicable)
+
+# What's the expected result?

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+# Pull Request Notice
+
+Before sending a pull request make sure each commit solves one clear, minimal,
+plausible problem. Further each commit should have the following format:
+
+```
+Problem: X is broken
+
+Solution: do Y and Z to fix X
+```
+
+Please try to have the code changes conform to the style of the surrounding code.
+
+Please avoid sending a pull request with recursive merge nodes, as they
+are impossible to fix once merged. Please rebase your branch on
+top of `master` instead of merging it.
+
+```
+git remote add upstream git@github.com:gosh-lang/gosh.git
+git fetch upstream
+git rebase upstream/master
+git push -f
+```
+
+In case you already merged instead of rebasing you can drop the merge commit.
+
+```
+git rebase -i HEAD~10
+```
+
+Now, find your merge commit and mark it as drop and save. Finally rebase!
+
+If you are a new contributor please have a look at our contributing guidelines:
+[CONTRIBUTING.md](../CONTRIBUTING.md)

.gitignore

@@ -0,0 +1,9 @@
+/.idea/
+/.vscode/
+
+/vendor/
+
+/internal/gofuzz/workdir/
+
+*.out
+*.test

.golangci.yml

@@ -0,0 +1,37 @@
+---
+linters-settings:
+  govet:
+    use-installed-packages: true
+
+  gocyclo:
+    min-complexity: 30
+
+  maligned:
+    suggest-new: true
+
+  # prevent import of go/ast, go/parser, etc.
+  depguard:
+    list-type: blacklist
+    include-go-root: true
+    packages:
+      - go/
+
+  lll:
+    line-length: 140
+    tab-width: 4
+
+  unused:
+    check-exported: true
+
+  unparam:
+    algo: rta
+    check-exported: true
+
+linters:
+  enable-all: true
+
+issues:
+  exclude-use-default: false
+  exclude:
+    # gas: Duplicates errcheck, but with more false positives like strings.Builder.WriteString
+    - "G104: Errors unhandled"

CHANGELOG.md

@@ -0,0 +1,5 @@
+## v0.0.1 "Smile" (2016-09-28)
+
+* First public version.
+* You can write FizzBuzz in it!
+* But not much else.

CODE_OF_CONDUCT.md

@@ -0,0 +1,73 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at conduct@gosh-lang.org. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -0,0 +1,11 @@
+# Contributing Guidelines
+
+Gosh, as an experiment, uses the [C4 process](https://rfc.zeromq.org/spec:42/C4/).
+Please do take the time to read it.
+
+If you feel like it is too heavyweight and you rather not contribute at all than use it,
+please at least follow those 2 basic rules:
+
+1. Always create an issue first. Always communicate before writing code.
+2. Please use the suggested commit message format and pull request body format.
+   That allows us to use them in the CHANGELOG.md without changes.