5.3 KiB
How To Participate
Bitcoin.org needs volunteers like you! Here are some ways you can help:
-
"Watch" this repository to be notified of issues and Pull Requests (PRs) that could use your attention. Scroll to the top of this page and click the Watch button to get notifications by email and on your GitHub home page.
Alternatively, email volunteer coordinators Will Binns will@bitcoin.org or Dave Harding dave@dtrt.org with a short list of your interests and skills, and they will email you when there's an issue or PR that could use your attention.
-
Help write new documentation for the developer documentation pages or full node page, or review PRs adding new documentation. You don't need to be a Bitcoin expert to review a PR---these docs are written for non-experts, so we need to know if non-experts find them confusing or incomplete. If you review a PR and don't find any problems worth commenting about, leave a "Looks Good To Me (LGTM)" comment.
-
Submit new wallets for the Choose Your Wallet page, or help us review wallet submissions.
-
Translate Bitcoin.org into another language using Transifex or help review new and updated translations.
-
Add Bitcoin events to the events page either by editing
_events.ymlaccording to the event instructions or by filling in a pre-made events issue. -
Help improve Bitcoin.org using your unique skills. We can always use the help of writers, editors, graphic artists, web designers, and anyone else to enhance Bitcoin.org's current content or to add new content. See the list of recommended starter projects or email volunteer coordinators Will Binns will@bitcoin.org or Dave Harding dave@dtrt.org to start a conversation about how you can help Bitcoin.org.
You can always report problems or help improve bitcoin.org by opening a new issue or pull request on GitHub.
Blog Posts
Posts for the [Bitcoin.org Site Blog][] should be added to the _posts
directory with the naming convention:
YEAR-MONTH-DAY-ARBITRARY_FILE_NAME (with year, month, and day as
two-digit numbers). The YAML front matter should be similar to this:
---
type: posts
layout: post
lang: en
category: blog
title: "Quarterly Report March 2015"
permalink: /en/posts/quarterly-report-march-2015.html
date: 2015-03-05
author: >
David A. Harding (<a href="mailto:dave@dtrt.org">email</a>, <a
href="https://github.com/harding">GitHub</a>,
<a href="http://www.reddit.com/user/harda/">Reddit</a>)
---
The type, layout, and category should always be as specified above. The other parameters should be set to values specific to that post, but the permalink must end in '.html'.
Below the YAML front matter, enter the content of the post in Markdown
format. Images should be placed in img/blog/free if they are
MIT-licensed or img/blog/nonfree if they have a more restrictive
copyright license.
Developer PGP keys
The site hosts the PGP keys for several Bitcoin Core contributors. Here are some notes about updating those keys based on previous experience:
- If a key is revoked, update the key with the revocation immediately. Anyone with commit access to the site repository may do this without prior review, but they should post the commit ID to an open issue or PR so other people can review it. After the revoked key is uploaded, discussion about verifying/adding a replacement key may continue at a slower pace.
Code of Conduct
Contributors to Bitcoin.org are expected to adhere to the project's Code of Conduct.