First Draft of the README.md (#2)

Reason for Change
=================
* Get er going

Changes
=======
* Add a first draft of a `README.md` file.
* Copy over the Code of Conduct and Mission/Vision/Values document.

Author: adarsh

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 [email protected]. 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/

README.md

@@ -1,2 +1,74 @@
-# board
+# Ruby Together Board of Directors
 Proceedings, Documents, and Processes for the Ruby Together Board of Directors
+
+## Overview
+
+This repository contains the documents and other materials related to the operations of the Ruby Together board.
+
+Our goals in creating this repo are:
+
+1. Centralize all board governance documents and artifacts
+2. Increase transparency for the members and public
+3. Provide a conduit for member and public feedback
+
+Like all things, this is an experiment and first draft. We will be improving our processes and sharing additional information as needs arise and context changes.
+
+## Board Members
+
+* Coraline Ehmke
+* Adarsh Pandit
+* Courteney Ervin
+* Allison McMillan
+* André Arko
+* Valerie Woolard Srinivasan
+* (one open board seat)
+
+## Documents
+
+* [Mission, Vision, and Values](VISION_MISSON_VALUES.md)
+* [Code of Conduct](CODE_OF_CONDUCT.md)
+
+## Communication
+
+### How to Share Feedback with Ruby Together (Inbound)
+
+#### Public
+
+To share public feedback, open an issue in this repository. It can be about anything, it's just a central place to collect input from outside of the board.
+
+As we discuss then resolve those issues, we will close the issue.
+
+#### Private
+
+Our private feedback method for is email, [email protected]. That address will forward to all of the directors on the board.
+
+### How to Keep Up to Date with Ruby Together (Outbound)
+
+To our best ability, we will set up channels to share out information as it happens in order to keep our membership informed and build trust with the broader community.
+
+#### Twitter
+
+[@rubytogether](https://twitter.com/rubytogether)
+
+#### Email
+
+Members of Ruby Together receive a monthly update email. To view past updates on the web, go to the [news page of the website](https://rubytogether.org/news).
+
+#### Website
+
+[rubytogether.org](rubytogether.org)
+
+#### Member's Slack
+
+Members of Ruby Together are automatically added to a private Slack organization. Updates will be posted in #general as they occur.
+
+#### This Repository
+
+[rubytogether/board](https://github.com/rubytogether/board)
+
+## TODO
+
+- Board Meetings (How they are conducted, summary of meetings, agendas prior to meetings)
+- Budget and Finances
+- Roles and Responsiblities of everyone in RT
+

VISION_MISSON_VALUES.md

@@ -0,0 +1,63 @@
+# Vision, Mission, and Values
+
+A Draft Document from the Ruby Together Board of Directors
+
+## Goals
+
+We are writing these down to help align us on where we are going and how we will
+get there. We will use these guidelines to help us make lots of small decisions,
+so that the big ones will be easier.
+
+## Vision
+_The world as we’d like to see it—Ruby open source made better for everyone._
+
+* Popular Ruby projects are actively maintained, and Ruby's critical infrastructure is secure and stable.
+* Project users and maintainers are empowered to decide what’s best for their projects.
+* Ruby open source projects have a diverse group of maintainers, who feel recognized for their work.
+* Ruby open source projects provide a well-managed and welcoming community, and make it easy for devs of any skill level to contribute.
+* Ruby open source developers are paid for their work, reducing maintainer burnout.
+* Companies support maintenance work for tools which they use, even if they can't afford to hire devs for open source work.
+
+## Mission
+_How we intend to make our vision real—by representing the Ruby community and paying developers to maintain Ruby open source._
+
+### Work For And With The Ruby Community
+* Give control to the community
+  * Developer members and companies who fund Ruby Together each get one vote in board elections; board members choose which projects to fund. Votes are per-entity, not based on amount paid..
+  * Companies aren’t allowed to hold more than one seat on the board. Companies have giving limits in order to maintain balance and guard against single-entity pressure.
+* Be accountable and transparent
+  * Publish more. This includes status updates and progress summaries, as well as income, expenditures, and budget summaries every month. Every month, we tell you what we did with the money, and our upcoming plans.
+* Collaborate with other community organizations
+  * Work together with other Ruby community organizations because a rising tide raises all ships.
+
+### Cultivate Healthy Open-Source Projects
+
+* Increase the number of open-source project maintainers
+  * Support more developers for fewer hours per week. More devs reduces solo-maintainer risk.
+  * Encourage contributions of ~5 hours/week which helps those with full-time jobs participate.
+* Welcome and encourage contributors
+  * Make projects easy for anyone to contribute to, regardless of experience level.
+  * Establish a collaborative, positive space for projects, with a clear enforcement policy.
+* Involve developers across the full range of experience
+  * We need the expertise and caution of experience, but we also need enthusiasm and fresh perspectives to make breakthroughs and revolutions possible.
+  * It’s more important to listen to and empower new developers than to keep existing experts comfortable, so Ruby open source can exist and thrive into the future.
+* Have a clear and transparent funding process
+  * We have a place to see current and past funded projects online
+  * We have an open process to propose, evaluate, and fund new projects.
+
+## Values
+_What we want to be like as an organization and a community_
+
+* Treat everyone as a valuable human being, worthy of respect and empathy. No exceptions.
+* When raising issues, propose a solution if you can.
+* Acknowledge and appreciate work others have done, especially communication and emotional labor.
+* Strive to empower Ruby developers first, then open source contributors, and finally open source maintainers.
+* Sustainable action is critical for long-term results in non-profit and open source work.
+* Like open source, we thrive on the input of our members and our community.
+
+### Feedback
+
+Please open a Pull Request to provide feedback and suggest changes. We value
+everyone's contribution, regardless of their membership in Ruby Together.
+
+In the interest of ensuring that all feedback is public and transparent, please create a new account in order to provide anonymous feedback, if you would prefer to do so.