Merging human-connection to master

human-connection/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,35 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

human-connection/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

human-connection/.gitignore

@@ -0,0 +1 @@
+/.github

human-connection/.gitmodules

@@ -0,0 +1,12 @@
+[submodule "Nitro-Web"]
+	path = Nitro-Web
+	url = https://github.com/Human-Connection/Nitro-Web.git
+[submodule "Nitro-Backend"]
+	path = Nitro-Backend
+	url = https://github.com/Human-Connection/Nitro-Backend.git
+[submodule "Nitro-Embed"]
+	path = Nitro-Embed
+	url = https://github.com/Human-Connection/Nitro-Embed.git
+[submodule "Nitro-Styleguide"]
+	path = Nitro-Styleguide
+	url = https://github.com/Human-Connection/Nitro-Styleguide.git

human-connection/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# 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, gender identity and expression, level of experience, 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 developer@human-connection.org. The project team will review and investigate all complaints, and will respond in a way that it deems 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 [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

human-connection/CONTRIBUTING.md

@@ -0,0 +1,72 @@
+Thanks so much for thinking of contributing to the Human Connection project, we really appreciate it! :-)
+
+### Getting Set Up
+
+Instructions for how to install all the necessary software can be found in our [documentation](https://docs.human-connection.org/nitro/)
+
+We recommend that new folks should ideally work together with an existing developer.  Please join our discord instance to chat with developers or just ask them in tickets in [Zenhub](https://app.zenhub.com/workspaces/human-connection-nitro-5c0154ecc699f60fc92cf11f/boards?repos=152252353):
+
+![](https://dl.dropbox.com/s/vbmcihkduy9dhko/Screenshot%202019-01-03%2015.50.11.png?dl=0)
+
+Here are some general notes on our development flow:
+
+### Development 
+
+* Currently operating in two week sprints
+* We are using ZenHub to coordinate
+  - estimating time per issue is the crucial feature of [Zenhub](https://app.zenhub.com/workspaces/human-connection-nitro-5c0154ecc699f60fc92cf11f) that Github does not have
+  - "up-for-grabs" links to [Github project](https://github.com/orgs/Human-Connection/projects/10?card_filter_query=label%3A%22good+first+issue)
+  - ordering on ZenHub not necessarily reflected on github projects
+
+* AgileVentures run open pairing sessions at 10:30am UTC each week on Tuesdays and Thursdays
+
+* Core team
+  - all the people who are hired by HC non-profit corporation
+  - you can Meet-the-team [every two weeks in German](https://human-connection.org/veranstaltungen/) and [every month in English](https://human-connection.org/en/events/).
+  - 9 people
+    - 2 core developers (Robert [@roschaefer](https://github.com/roschaefer) and Greg [@appinteractive](https://github.com/appinteractive))
+    - 3 marketeers Jasi, Dennis and Sensi
+    - Hardy doing business development
+    - Martin head of IT and previously data protection officer
+    - Victor doing accounting and controlling
+    - Nicolas is the community manager (reviews content in the network) reflects community opinion back to the core team
+    
+* when can folks pair with Robert
+  - 10am UTC until 5pm UTC every working day
+  
+### Philosophy
+
+We practise [collective code ownership](http://www.extremeprogramming.org/rules/collective.html) rather than strong code ownership, which means that:
+
+* anyone can start working on anyone elses code
+* we avoid blocking because someone else isn't working on something
+* however it's sometimes good to leave something in order to create successful education experience
+* everyone should always push their code to branches so others can see it
+
+Everyone feel free to request merges or answers to issues from the project managers
+
+But what do we do when waiting for merge into master (wanting to keep PRs small)
+  --> Robert recommends creating a pull request for each step
+ - programming is also about thinking about other people - empathy for your co-workers
+  - but what about when you are waiting for merge?
+  - solutions
+    - 1) put 2nd PR into branch that the first PR is hitting - but requires update after merging
+    - 2) prefer to leave exiting PR until it can be reviewed, and instead go and work on some other part of the codebase that is not impacted by the first PR
+    
+### Notes
+
+question: when you want to pick a task - (find out priority) - is it in discord? is it in AV slack? --> Robert says you can always ask in discord - group channels are the best
+
+Robert shares: [Zenhub board](https://app.zenhub.com/workspaces/nitro-embed-5c0154ecc699f60fc92cf11f/boards?repos=112590397,152252353,152252578,157710732,163305928)
+Robert says the order of tickets are preserved in ZenHub and reflect their priority (most important at the top) and so check out the current milestones
+
+Matt - question about who can work on [ticket 100](https://app.zenhub.com/workspaces/nitro-embed-5c0154ecc699f60fc92cf11f/issues/human-connection/human-connection/100) --> Robert - in rare occasions it might be exclusive to someone with admin permissions
+Robert: notes greg just pushed this today: https://github.com/Human-Connection/Nitro-Deployment
+
+Matt makes point that new stories will have to be taken off the "New Issues" and Robert says that's fine, if you don't like the first one, then you can take the next one. Volunteeers have no commitment except their own self development and their awesomeness by contributing to free and open-source software projects.
+
+Robert notes that everyone is invited to join the kickoff meetings
+
+Robert - difference between "important" (creates a lot of value) and "beginner friendly" (easy to implement)
+
+

human-connection/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2018 Human-Connection
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

human-connection/Nitro-Backend

@@ -0,0 +1 @@
+Subproject commit fd8cc3f7e60f4be10994ea934575fe38a60345f8

human-connection/Nitro-Embed

@@ -0,0 +1 @@
+Subproject commit 296fc5a0399425c698be0e8875b8dbd6a4455994

human-connection/Nitro-Styleguide

@@ -0,0 +1 @@
+Subproject commit 3f7a00b8b94c4bfd2a029d6a50c847f3ab027692

human-connection/Nitro-Web

@@ -0,0 +1 @@
+Subproject commit 0c2a228b47647de5bfe873ade42fb1bf110c8bc0

human-connection/README.md

@@ -0,0 +1,47 @@
+<p align="center">
+  <a href="https://human-connection.org"><img align="center" src="https://github.com/Human-Connection/Human-Connection/blob/master/lets_get_together_2.png" alt="Human-Connection" /></a>
+</p>
+
+# Human-Connection
+
+An Open Source Social Network for the positive change that we need in the World.
+Human-Connection is being built to provide better Communication Tools for everyone.
+We want to do more than comments and sharing!
+
+**Features**
+- Post Builder/Editor
+- Voting
+- Best of Lists
+- Pro & Contra Discussions
+- Projects
+- Event Management
+- Organizations
+- Chats & Group Chats
+- Knowledge Sharing
+- Let's Talk
+- Versus Challenging
+- Modular UI
+
+**Repositories**
+
+| Repo | Status |
+|---|---|
+| [Nitro Web](https://github.com/Human-Connection/Nitro-Web) | [![Build Status](https://travis-ci.com/Human-Connection/Nitro-Web.svg?branch=master)](https://travis-ci.com/Human-Connection/Nitro-Web) | [Nitro Web](https://github.com/Human-Connection/Nitro-Web) |
+| [Nitro Backend](https://github.com/Human-Connection/Nitro-Backend) | [![Build Status](https://travis-ci.com/Human-Connection/Nitro-Backend.svg?branch=master)](https://travis-ci.com/Human-Connection/Nitro-Styleguide) | [Nitro Backend](https://github.com/Human-Connection/Nitro-Backend) |
+| [Nitro Styleguide](https://github.com/Human-Connection/Nitro-Styleguide) | [![Build Status](https://travis-ci.com/Human-Connection/Nitro-Styleguide.svg?branch=master)](https://travis-ci.com/Human-Connection/Nitro-Styleguide) | [Nitro Styleguide](https://github.com/Human-Connection/Nitro-Styleguide) |
+| [Nitro Embed](https://github.com/Human-Connection/Nitro-Embed) | ![Todo: add build pipeline](https://img.shields.io/badge/TODO-add%20build%20pipeline-red.svg) |
+  
+**Technology Stack**
+- vuejs
+- nuxtjs
+- neo4j
+- graphql
+
+## Documentation
+[Docs](https://docs.human-connection.org/nitro)
+
+## Translations
+You can help translating the interface by joining us on [lokalise.co](https://lokalise.co/public/556252725c18dd752dd546.13222042/).
+
+## Developer Chat
+[Discord](https://discord.gg/6ub73U3)