docs: add prereqs, scope and issues section

* mirror what we have on our docs webiste

CODE_OF_CONDUCT.md

@@ -1,4 +1,6 @@
-# Contributor Covenant Code of Conduct
+# Code of Conduct
+
+By contributing toward this project you agree to the following code of conduct
 
 ## Our Pledge
 
@@ -14,21 +16,21 @@ appearance, race, religion, or sexual identity and orientation.
 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
+- 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
+- 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
+- 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
+- Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Our Responsibilities
@@ -55,7 +57,7 @@ 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 [INSERT EMAIL ADDRESS]. All
+reported by contacting the project team at info@grassecon.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.
@@ -75,9 +77,8 @@ available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.ht
 For answers to common questions about this code of conduct, see
 https://www.contributor-covenant.org/faq
 
-
-
-
 ...Try to keep in mind the immortal
 words of Bill and Ted, "Be excellent to each other."
 
+These documents are licensed under Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) https://creativecommons.org/licenses/by-sa/4.0/
+And further any software Grassrotos Economics supports is under licenced under GNU GENERAL PUBLIC LICENSE Version 3 https://www.gnu.org/licenses/

CONTRIBUTING.md

@@ -1,16 +1,66 @@
-Hello and welcome to the CIC Stack repository. Targeted for use with the ethereum virtual machine and a ussd capable telecom provider. 
+# Contribution Guidelines
 
-__To request a change to the code please fork this repository and sumbit a merge request.__
+**Karibu sana!** Hello and welcome to the Grassroots Economics [project](https://gitlab.com/grassrootseconomics). This guide will help you understand the overall
+organization of the CIC project to get you started with contributing to the project. You'll be able to pick up issues, write code to fix them, and get your work reviewed and merged.
 
-__If there is a Grassroots Economics Kanban Issue please include that in our MR it will help us track contributions. Karibu sana!__
+## Table of Contents
 
-__Visit the Development Kanban board here: https://gitlab.com/grassrootseconomics/cic-internal-integration/-/boards/2419764__
+- [Prerequisites](#Prerequisites)
+- [Scope of contributions](#Scope-of-contributions)
+- [Issues](#Issues)
+  - [Bugs](#Bugs)
+  - [Good first issues](#Good-first-issues)
+- [Git guidelines](#Git-guidelines)
+- [Merge request processs](#Merge-request-processs)
+- [Environment setup](#Environment-setup)
+- [Code style](#Code-style)
+- [Building-and-testing](#Building-and-testing)
 
-__Ask a question in our dev chat:__
+## Prerequisites
 
-[Mattermost](https://chat.grassrootseconomics.net/cic/channels/dev)
+Before contributing to the CIC Stack, ensure you have:
 
-[Discord](https://discord.gg/XWunwAsX)
+- Read and accepted to abide by the Code of Conduct
+<!-- TODO: Add link to CoC -->
+- Read and accepted the Developers Certificate of Origin
+<!-- TODO: Add link to DCO -->
 
-[Matrix, IRC soon?]
+## Scope of contributions
 
+We generally welcome all sorts or contributions. No contribution is too small. We gladly accept contributions such as:
+
+- Documentation improvements including inline documentation or even minor typos
+- Answering questions in issue discussions and pull requests
+- Fixing known bugs on our issue tracker
+- Reporting unknown bugs
+<!-- TODO: Add resposible disclosure guidelines -->
+- Securty issues through responsible disclosure
+
+## Issues
+
+Use the existing issue template and issue tags to correctly catagorize and issue when creating issues. Make sure to search for duplicated before creating a new issue.
+
+### Bugs
+
+If a bug is encountered and you can reproduce it:
+
+- Define its priority with an issue tag
+- Describe the steps to reproduce it while providing the version of the bugged service/library and your environment setup
+
+### Good first issues
+
+These are pre-tagged issues which are friendly (low barrier to entry and clearly defined tasks) for new contributors to get aquinted to the project.
+
+## Git guideleines
+
+<!-- TODO: Review after finalzing branching or forking model -->
+
+## Merge request process
+
+<!-- TODO: Review after core_contrib -->
+
+## Environment setup
+
+## Code style
+
+## Building and testing

README.md

@@ -1,19 +1,24 @@
-# Community Inclusion Currency Stack (CIC Stack) 
+## Community Inclusion Currency Stack (CIC Stack)
 
-A custodial evm wallet for executing transactions via USSD
+A custodial wallet and blockchain bidirectional interface engine for community inclusion currencies. Check the [CIC Stack summary](https://docs.grassecon.org/software) page for more information.
 
-## Getting started 
+### Contributing
 
-This repo uses docker-compose and docker buildkit. Set the following environment variables to get started:
+See our [contribution guidelines](https://docs.grassecon.org/community/contrib/) for more details on:
 
-```
-export COMPOSE_DOCKER_CLI_BUILD=1
-export DOCKER_BUILDKIT=1
-```
+- Environment setup
+- Source Code Management (SCM) guidelines
+- Filing issues
 
-To get started see [./apps/contract-migration/README.md](./apps/contract-migration/README.md)
+#### Code of Conduct
 
-## Documentation 
+This project is released with a [Code of Conduct](https://docs.grassecon.org/community/conduct/). By participating in this project you agree to abide by its terms.
 
-[https://docs.grassecon.org/cic_stack/](https://docs.grassecon.org/cic_stack/)
+### Community
 
+- [Mattermost](https://chat.grassrootseconomics.net/cic/channels/dev)
+- [Discord](https://discord.gg/ud32KMgH76)
+
+### License
+
+Licensed under [GNU AGPLv3](https://gitlab.com/grassrootseconomics/cic-internal-integration/-/blob/master/LICENSE).