Merge pull request blueprint-freespeech#2 from blueprint-freespeech/b…

…lueprint-master

Updated build script

.gitmodules

@@ -1,18 +1,3 @@
-[submodule "buildscripts/src/openssl"]
-	path = buildscripts/src/openssl
-	url = https://github.com/openssl/openssl.git
-[submodule "buildscripts/src/tor"]
-	path = buildscripts/src/tor
-	url = https://git.torproject.org/tor.git
-[submodule "buildscripts/src/protobuf"]
-	path = buildscripts/src/protobuf
-	url = https://github.com/google/protobuf.git
-[submodule "buildscripts/src/qt5"]
-	path = buildscripts/src/qt5
-	url = https://github.com/qtproject/qt5.git
-[submodule "buildscripts/src/libevent"]
-	path = buildscripts/src/libevent
-	url = https://github.com/libevent/libevent
 [submodule "src/extern/fmt"]
 	path = src/extern/fmt
 	url = https://github.com/fmtlib/fmt.git

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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  [[email protected]]( mailto:[email protected]). 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
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTE.md

@@ -0,0 +1,63 @@
+# Contribution Guidelines
+
+We welcome contributions towards code, documentation, testing, and translation.
+This guide should help explain the ways you can contribute and how to go about
+it.
+
+## About the project
+
+If you are looking to contribute code, our project uses C++ with QT5. If you
+aren't comfortable making a code contribution there are lots of other ways to
+contribute, for example, improving documentation and testing across different
+platforms. The best approach is to either comment on an issue you are interested
+in contributing to, or create a new issue that describes the contribution you
+wish to make.
+
+## How do I make a contribution?
+
+Never made an open source contribution before? Wondering how contributions work
+in the in our project? Here's a quick rundown!
+
+- Find an issue that you are interested in addressing or a feature that you
+  would like to add. Create a new issue if necessary.
+- Fork the repository associated with the issue to your local GitHub
+  organization. This means that you will have a copy of the repository under
+  your-GitHub-username/tego-core.
+- Clone the repository to your local machine using `git clone
+  https://github.com/github-username/tego-core.git`.
+- Create a new branch for your fix using `git checkout -b branch-name-here`.
+- Make the appropriate changes for the issue you are trying to address or the
+  feature that you want to add.
+- If you are new to Git or GitHub see
+  [https://guides.github.com/](https://guides.github.com/) for tutorials and
+  guides.
+- Push your changes to your remote repository
+- Submit a pull request to the upstream tego-core repository
+- Provide a short description of the changes in the title of the pull request,
+  reference the issue or bug number as well.
+- Provide more details of the changes in the pull description, in particular
+  highlight any current weaknesses or outstanding problems. If your code has
+  made changes to Crypto or protocol classes a detailed description of the
+  changes and justification will be required. Please try to make pull requests
+  for features separately - avoid bundling multiple issues or features into a
+  single pull request. This makes code review easier and more manageable.
+- A maintainer will review the pull request and provide feedback where
+  appropriate. Please be patient, our maintainers are volunteers and only have a
+  limited amount of time to work on the project.
+- Make changes to the pull request if the reviewing maintainer recommends them.
+
+## Where can I go for help?
+
+If you need help, you can ask questions via the issue that covers your
+contribution. In future we will provide some additional communication channels
+as we get them setup.
+
+## What does the Code of Conduct mean for me?
+
+Our Code of Conduct
+[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-v2.0%20adopted-ff69b4.svg)](CODE_OF_CONDUCT.md)
+means that you are responsible for treating everyone on the project with respect
+and courtesy regardless of their identity. If you are the victim of any
+inappropriate behavior or comments as described in our Code of Conduct, we are
+here for you and will do the best to ensure that the person responsible is reprimanded
+appropriately, per our code.