@@ -4,70 +4,22 @@ weight = 5
4template = "doc.html"
4template = "doc.html"
5description = "A guide to getting involved with the Urbit project."
5description = "A guide to getting involved with the Urbit project."
7−We accept submissions for improving our [code](https://github.com/urbit/urbit/) and [documentation](https://github.com/urbit/docs/) alike.
9−If you're interested in contributing, but don't know where to start, feel free to [send us an email](mailto:support@urbit.org).
13−Our official guide to contributing can be found [here](https://github.com/urbit/urbit/blob/master/CONTRIBUTING.md), which is most useful for large and low-level changes.
15−Before contributing code, you should familiarize yourself with the [Hoon style guide](./docs/learn/hoon/style.md). For a good example of preferred Hoon coding style, see [ford.hoon](https://github.com/urbit/arvo/blob/master/sys/vane/ford.hoon).
17−## Community Guidelines
19−Urbit is both code and community. We have guidelines for the former, and we also have guidelines for the latter.
23−Urbit is a decentralized system, both technically and in spirit. This means that no one, Tlon Corp. or otherwise, has the technical ability to police the entire network. But we do admit that moderation is necessary; we just think that it’s not strictly a technical problem.
25−What we can do, and what we propose to do in this document, is define how we plan on moderating our little, but important, corner of Urbit. We define the limits of our jurisdiction as the general-purpose discussion channel `~dopzod/urbit-help`, our forum, `fora` and, adjacently, the GitHub issues on any of the [official urbit repos](https://github.com/urbit).
27−Our hope is that the system established here can serve as a model for other corners of Urbit. But it bears repeating: **Tlon is technically incapable of moderating the Urbit network in general**.
29−### Use of these guidelines
31−The goal of these guidelines is to provide clear principles which can be used by moderators for the resolution of disputes in this jurisdiction. The hope is that, by knowing the guidelines that will be cited in case of a dispute, users can have clear expectations of how to comport themselves and how a judgement will be made. The ideal is that, right before pressing "Submit" on an inflammatory Fora post, the errant Urbiter will pause and remember the following mandates.
35−#### 1. Stay on topic
8+We accept submissions for improving our [code](https://github.com/urbit/urbit/) and [documentation](https://github.com/urbit/docs/) alike.
37−Conflicts about the work, about building Urbit, are good conflicts. Conflicts about haircuts, politics or sports are not productive and are best conducted in a DM or a private circle.
39−#### 2. Treat everyone like a person
41−All of us have pre-loaded talking points against our preferred ideological and intellectual opponents. Unleashing them prematurely often impedes communication and sours otherwise productive dialogue. It is also not nice. So, instead of treating a human being as merely an avatar for an idea, treat them like a person.
43−“Treating someone like a person” means responding to what people actually say, instead of what you think such a person would say.
45−Before responding to something that seems objectionable, make sure that the other party is actually saying what you think they’re saying. Ask questions and be nice.
47−#### 3. Skin in the game
49−No one likes comments like "this sux" in a thread of otherwise serious commentary. If other people have something to lose (even if it’s just face), be respectful. And, ideally, put some skin in the game yourself.
51−In general, establish yourself in a conversation or a subject area before you start attacking anyone. Better yet: don't attack anyone.
53−#### 4. Assume good faith
55−If anyone has gone through the trouble of booting a ship, submitting an issue, learning Hoon, reading through our docs or otherwise shown themselves committed to our wild-eyed vision, they are to be assumed to be a friend.
57−If you can choose to interpret a statement as a sneaky slight or a clumsy compliment, choose the latter.
59−#### 5. Respect the mods
61−We believe that all good governance terminates in a human relationship, and that moderators fulfill that role. All moderators will be forced to make judgments not covered by this document, and that will doubtless make some unhappy; maybe even you. Please respect the fact that someone took this responsibility on for the greater good.
10+If you're looking to get involved, there are a few things you can do:
63−The flipside of this is that moderators are expected to act in accordance with the dignity of that office. Abuse of power will not be tolerated.
12+- Join the [urbit-dev](https://groups.google.com/a/urbit.org/forum/#!forum/dev) mailing list.
13+- [Ask us about Hoon School](mailto:support@urbit.org), a course we run to teach the Hoon programming language and Urbit application development.
14+- Check out the "good contributor issues" tag in the [urbit](https://github.com/urbit/urbit/labels/good%20contributor%20issue) and [arvo](https://github.com/urbit/arvo/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+contributor+issue%22) Github repositories.
15+- Reach out to [support@urbit.org](mailto:support@urbit.org) to say hi and ask any questions you might have.
65−### Adjudication
17+If you're getting set up to work on the Urbit or Arvo code base for the first time, start with our [Getting Started](./docs/getting-started/_index.md) guide, then have a look at [CONTRIBUTING.md](https://github.com/urbit/urbit/blob/master/CONTRIBUTING.md) in the Urbit repository.
67−The body responsible for the hearing of and ruling on claims is the Council, composed of moderators. Moderators are to serve for a term of one year.
19+Many contributors start by contributing to the [documentation](https://github.com/urbit/docs), [urbit.org](https://github.com/urbit/urbit.org), or [bridge](https://github.com/urbit/bridge). If you're not yet comfortable with Hoon, we recommend starting there.
69−Any planet-holder on the network dissatisfied with the behavior of another planet-holder must first send a complaint to the Council with a link to the offending message or document.
21+If smart contracts (Solidity) are more your jam, have a look at [Azimuth](https://github.com/urbit/azimuth), Urbit's identity layer.
71−The case will be assigned a moderator at random, who will decide the matter. The finding will include a punishment which can range from censure to temporary or permanent blacklisting.
23+## Code style
73−If one of the parties in the case would like to file an appeal, the case can be heard and ruled on by the entire Council. All proceedings of the Council are public and all past behavior in the jurisdiction can be considered in the Councils’ decision.
25+Before contributing Hoon code, you should familiarize yourself with the [Hoon style guide](./docs/learn/hoon/style.md). For a good example of idiomatic Hoon, see [ford.hoon](https://github.com/urbit/arvo/blob/master/sys/vane/ford.hoon).