Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub Open Source Community Standards #39

Closed
arcticicestudio opened this issue Jun 22, 2019 · 1 comment
Closed

GitHub Open Source Community Standards #39

arcticicestudio opened this issue Jun 22, 2019 · 1 comment

Comments

@arcticicestudio
Copy link
Owner

arcticicestudio commented Jun 22, 2019

Epic: #33
Depends on #49

GitHub introduced a feature for recommended community standards. snowsaw tries to adhere to the great Open Source Guides and will adapt to the recommendations to complete the projects community profile.

Code of Conduct

To facilitate a healthy and constructive community behavior, snowsaw will adhere and enforce a code of conduct.

It will include sections about

  • what we believe in and how we act
  • unacceptable behavior
  • the responsibilities of the maintainer
  • the enforcement of the Code of Conduct
  • consequences for violations
  • the scope of the Code of Conduct

See the GitHub Help for more details about the provided integrations.

Contributing Guidelines

The contribution guidelines help to build a community that encourages people to use, contribute to, and evangelize a project.

It will include sections about

See the GitHub introduction blog post and GitHub Help for more details about the provided integrations.

@arcticicestudio arcticicestudio added this to the 0.4.0 milestone Jun 22, 2019
@arcticicestudio arcticicestudio self-assigned this Jun 22, 2019
arcticicestudio added a commit that referenced this issue Jun 22, 2019
In order to start the Go project rewrite (1) from scratch the current
repository structure and files have been reset to a clean state to
remove all references to the previous implementations, documentations
and project structure/layout.

Starting from a "fresh" state allows to build the project up with the
correct structure and design pattern as if there were leftovers from
the previous repository data resulting in mixed files and folders.

This commit must be pushed first before all other blocked tickets can be
resolved that are also bound to the epic GH-33!
See the corresponding milestone (2) for more details about the
implementation/resolve order.

>>>> Tasks

- `.idea/` (3) - Deleted the whole folder, the files were scoped for
  "Pycharm Community Edition" and will be replaced with the correct
  files for "IntelliJ Ultimate Edition" with the official Go plugin (4)
  (Goland (5)) later on.
- `assets/` (6) - Deleted the whole folder, all assets will be
  redesigned and added again later on.
- `bin/` (7) - Deleted the whole folder, the script was part of the
  Python implementation and represented the entry point of the app.
- `snowsaw/` (8) - Deleted the whole folder, included the main Python
  app and API implementations.
- `.editorconfig` (9) - Deleted the file, it will be recreated in GH-38
  to match the new project layout and latest "Arctic Ice Studio" project
  design standards/guidelines.
- `.gitignore` (10) - Deleted the file, it will be recreated in GH-35 to
  match the new project layout and latest "Arctic Ice Studio" project
  design standards/guidelines.
- `CHANGELOG.md` (11) - Deleted the file, it will be recreated later on to
  match the new project layout and latest "Arctic Ice Studio" project
  design standards/guidelines.
- `README.md` (12) - Deleted the file, it will be recreated later on to
  match the new project layout and latest "Arctic Ice Studio" project
  design standards/guidelines including the new project assets
  (logo, repository hero etc.).

References:
  (1) #33
  (2) https://github.com/arcticicestudio/snowsaw/milestone/5
  (3) https://github.com/arcticicestudio/snowsaw/tree/bc54e5136be27f8037de5bbc2f046f37eb036274/.idea
  (4) https://plugins.jetbrains.com/plugin/9568-go
  (5) https://www.jetbrains.com/go
  (6) https://github.com/arcticicestudio/snowsaw/tree/bc54e5136be27f8037de5bbc2f046f37eb036274/assets
  (7) https://github.com/arcticicestudio/snowsaw/tree/bc54e5136be27f8037de5bbc2f046f37eb036274/bin
  (8) https://github.com/arcticicestudio/snowsaw/tree/bc54e5136be27f8037de5bbc2f046f37eb036274/snowsaw
  (9) https://github.com/arcticicestudio/snowsaw/blob/bc54e5136be27f8037de5bbc2f046f37eb036274/.editorconfig
  (10) https://github.com/arcticicestudio/snowsaw/blob/bc54e5136be27f8037de5bbc2f046f37eb036274/.gitignore
  (11) https://github.com/arcticicestudio/snowsaw/blob/bc54e5136be27f8037de5bbc2f046f37eb036274/CHANGELOG.md
  (12) https://github.com/arcticicestudio/snowsaw/blob/bc54e5136be27f8037de5bbc2f046f37eb036274/README.md

Epic: GH-33
Blocked GH-34 GH-35 GH-36 GH-37 GH-38 GH-39 GH-42 GH-43 GH-44 GH-45
        GH-46 GH-47 GH-48
Resolves GH-49
arcticicestudio added a commit that referenced this issue Jun 22, 2019
To facilitate a healthy and constructive community behavior, snowsaw
adheres and enforce a code of conduct (1).

This commit includes the sections about

- what we believe in and how we act
- unacceptable behavior
- the responsibilities of the maintainer
- the enforcement of the Code of Conduct
- consequences for violations
- the scope of the Code of Conduct

See the GitHub Help (2) for more details about the provided
integrations.

References:
  (1) opensource.guide/code-of-conduct
  (2) help.github.com/articles/adding-a-code-of-conduct-to-your-project

Epic: GH-33
Depends on GH-49
GH-39
arcticicestudio added a commit that referenced this issue Jun 22, 2019
The contribution guidelines (1) help to build a community that
encourages people to use, contribute to (2), and evangelize a project.

It includes sections about

- how to get started
- bug reports
- enhancement suggestions
- pull requests
- style guides
  -  Markdown Style Guide (3)
  - Git Style Guide (4)
- credits

See the GitHub introduction blog post (5) and GitHub Help (6) for more
details about the provided integrations.

References:
  (1) github.com/blog/1184-contributing-guidelines
  (2) opensource.guide/how-to-contribute
  (3) arcticicestudio/styleguide-markdown
  (4) arcticicestudio/styleguide-git
  (5) https://github.blog/2012-09-17-contributing-guidelines
  (5) help.github.com/articles/setting-guidelines-for-repository-contributors

Epic: GH-33
Depends on GH-49
Resolves GH-39
arcticicestudio added a commit that referenced this issue Jun 22, 2019
* Open Source community standards: Code of Conduct

To facilitate a healthy and constructive community behavior, snowsaw
adheres and enforce a code of conduct (1).

This commit includes the sections about

- what we believe in and how we act
- unacceptable behavior
- the responsibilities of the maintainer
- the enforcement of the Code of Conduct
- consequences for violations
- the scope of the Code of Conduct

See the GitHub Help (2) for more details about the provided
integrations.

References:
  (1) opensource.guide/code-of-conduct
  (2) help.github.com/articles/adding-a-code-of-conduct-to-your-project

Epic: GH-33
Depends on GH-49
GH-39

+---------------------------------------------------------------------+

* Open Source community standards: Contributing Guidelines

The contribution guidelines (1) help to build a community that
encourages people to use, contribute to (2), and evangelize a project.

It includes sections about

- how to get started
- bug reports
- enhancement suggestions
- pull requests
- style guides
  -  Markdown Style Guide (3)
  - Git Style Guide (4)
- credits

See the GitHub introduction blog post (5) and GitHub Help (6) for more
details about the provided integrations.

References:
  (1) github.com/blog/1184-contributing-guidelines
  (2) opensource.guide/how-to-contribute
  (3) arcticicestudio/styleguide-markdown
  (4) arcticicestudio/styleguide-git
  (5) https://github.blog/2012-09-17-contributing-guidelines
  (5) help.github.com/articles/setting-guidelines-for-repository-contributors

Epic: GH-33
Depends on GH-49
Resolves GH-39
@arcticicestudio
Copy link
Owner Author

Resolved in 30df86d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant