Documentation: Add some description of our communal places

Change-Id: Iede98359c22aefbfd5725a5e7cd661ef18d7284e
Signed-off-by: Patrick Georgi <pgeorgi@google.com>
Reviewed-on: https://review.coreboot.org/c/31146
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Angel Pons <th3fanbus@gmail.com>

3 files changed, 149 insertions, 0 deletions

diff --git a/Documentation/community/code_of_conduct.md b/Documentation/community/code_of_conduct.md
new file mode 100644
index 000000000000..c40393f919eb
--- /dev/null
+++ b/Documentation/community/code_of_conduct.md
@@ -0,0 +1,112 @@
+# Code of Conduct
+
+This code of conduct outlines our rules and expectations for everybody
+participating in the coreboot community.
+
+## coreboot community etiquette
+
+We have a friendly and productive atmosphere on our mailing lists,
+development / code review tools, IRC chat rooms and when we meet in
+person.  Our principles evolve around the following:
+
+* It's not the user's fault if something goes wrong.
+* Attempt collaboration before conflict.
+* People who intentionally insult others (users, developers, corporations,
+  other projects, or the coreboot project itself) will be dealt with. See
+  policy below.
+* We are dealing with hardware with lots of undocumented pitfalls. It is quite
+  possible that you did everything right, but coreboot or its tools still
+  won't work for you.
+
+Refrain from insulting anyone or the group they belong to. Remember that
+people might be sensitive to other things than you are.
+
+Most of our community members are not native English speakers, thus
+misunderstandings can (and do) happen. Always assume that others are
+friendly and may have picked less-than-stellar wording by accident.
+
+If you have a grievance due to conduct in this community, we want to hear
+about it so we can handle the situation. Please contact our arbitration
+team directly: They will listen to you and react in a timely fashion.
+
+For transparency there is no alias or private mailing list address for
+you to reach out to, since we want to make sure that you know who will
+(and who won't) read your message.
+
+However since people might be on travel or otherwise be unavailable at
+times, consider reaching out to multiple persons.
+
+The team will treat your messages confidential as far as the law permits.
+For the purpose of knowing what law applies, the list provides the usual
+country of residence of each team member.
+
+## Unacceptable Behavior
+
+Unacceptable behaviors include: intimidating, harassing, abusive,
+discriminatory, derogatory or demeaning speech or actions by any
+participant in our community online, at all related events and in
+one-on-one communications carried out in the context of community
+business. Community event venues may be shared with members of the public;
+please be respectful to all patrons of these locations.
+
+Examples of behaviors we do not accept in our community:
+
+* harmful or prejudicial verbal or written comments related to gender,
+  sexual orientation, race, religion, disability;
+* inappropriate physical contact, and unwelcome sexual advances;
+* deliberate intimidation, stalking or following;
+* harassing photography or recording;
+* sustained disruption of talks or other events.
+
+Using this code of conduct aggressively against other people in the
+community might also be harassment. Be considerate when enforcing the code
+of conduct and always try to listen to both sides before passing judgment.
+
+## Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any community member, including sponsors and
+those with decision-making authority, will not be tolerated.
+
+Anyone asked to stop unacceptable behavior is expected to comply
+immediately.
+
+If a community member engages in unacceptable behavior, the community
+organizers may take any action they deem appropriate, up to and including
+a temporary ban or permanent expulsion from the community without warning
+(and without refund in the case of a paid event). Community organizers
+can be part of the arbitration team, or organizers of events and online
+communities.
+
+## If You Witness or Are Subject to Unacceptable Behavior
+
+If you are subject to or witness unacceptable behavior, or have any other
+concerns, please notify someone from the arbitration team immediately.
+
+
+## Addressing Grievances
+
+If you feel you have been falsely or unfairly accused of violating this
+Code of Conduct, you should notify the arbitration team with a concise
+description of your grievance.
+
+## Scope
+
+We expect all community participants (contributors, paid or otherwise;
+sponsors; and other guests) to abide by this Code of Conduct in all
+community venues, online and in-person, as well as in all one-on-one
+communications pertaining to community business.
+
+## Contact info
+
+Our arbitration team consists of the following people
+* Stefan Reinauer <stefan.reinauer@coreboot.org> (USA)
+* Patrick Georgi <patrick@coreboot.org> (Germany)
+* Ronald Minnich <rminnich@coreboot.org> (USA)
+* Marc Jones <mjones@coreboot.org> (USA)
+
+## License and attribution
+
+This Code of Conduct is distributed under
+a [Creative Commons Attribution-ShareAlike
+license](http://creativecommons.org/licenses/by-sa/3.0/).  It is based
+on the [Citizen Code of Conduct](http://citizencodeofconduct.org/)
diff --git a/Documentation/community/conferences.md b/Documentation/community/conferences.md
new file mode 100644
index 000000000000..5531d51891de
--- /dev/null
+++ b/Documentation/community/conferences.md
@@ -0,0 +1,19 @@
+# Conferences
+The coreboot community is present at a number of conferences over the year,
+usually at [FOSDEM](https://fosdem.org), [OSFC](https://osfc.io), and the
+[Chaos Communication Congress](https://events.ccc.de/congress/).
+
+The kind of presence differs, but there's usually a booth or other kind of
+gathering where everybody is welcome to say hello and to learn more about
+coreboot.
+
+Depending on the nature of the conference, coreboot developers might bring
+their development kit with them and conduct development sessions.
+
+## Upcoming events
+
+TODO: add them
+
+## Talks
+
+TODO: link to recorded talks
diff --git a/Documentation/community/forums.md b/Documentation/community/forums.md
new file mode 100644
index 000000000000..1178c5292635
--- /dev/null
+++ b/Documentation/community/forums.md
@@ -0,0 +1,18 @@
+# Our forums
+
+The coreboot community has various venues to help each other and discuss the
+direction of our project.
+
+## Mailing list
+
+The first address for coreboot related discussion is our mailing list.
+You can subscribe on its
+[information page](https://mail.coreboot.org/postorius/lists/coreboot.coreboot.org/) and
+read its
+[archives](https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/).
+
+## IRC
+
+We also have a
+[real time chat](https://webchat.freenode.net?channels=%23coreboot)
+on the Freenode IRC network's #coreboot channel.