Submit Event Report

Before you start

Things to remember:

• This repository is public. Anyone can read both final reports and their drafts in the pull requests. Do not leak sensitive information.
• Your email can be extracted from Git commits. Read this info to understand and configure which email address is recorded when you save documents on GitHub.
• Please don't commit images, they quickly grow the size of the repository (see below).

3 ways to submit

There are multiple ways to submit an event report depending on how familiar you are with GitHub and Git:

1. Create a gist with the report and send it to admins of this repo
2. Ask admins to give you a draft you can edit
3. Submit a pull request

To submit changes to existing reports, options 2 and 3 apply.

Reports are written in a format called Markdown. It is pretty simple, but for some techniques you don't use often there is an excellent cheatsheet that should be in your bookmarks.

No images in Git

Please do not commit images (e.g. photos) or other large files into Git because it grows repository size too quickly. Instead, link to images hosted on in your signed Keybase public folder (example), Twitter, IPFS, etc.

File hosting is an open issue. Ultimately we need a robust and replicated file archive but this is not available yet.

1. The gist way

Gist is most commonly a single versioned document and it is perfect for event reports. All you need is GitHub account.

1. Visit https://gist.github.com/
2. Enter filename in this format: YYYYMMDD-title-city-country.md. Example: 20190116-tnabc-miami-usa.md.
3. Enter report contents. You can use this template.
4. Press Create secret gist or Create public gist depending on your preference. Secret gists can only be accessed knowing the correct link and are not listed in your profile.
5. Edit the gist as necessary.
6. When finished, contact admins and ask to add your report to the repository.

Other ways to share a document would work too, but gist is

• better than chat message because it can be long and you can edit it
• better than pastebin services because it has clear version history
• better than Google Docs because it can be accessed without Google account and without executing a ton of proprietary code

Learn more about gists here.

2. Ask for a draft

This way is a bit more advanced but allows others to be aware of your work on the report, and also allows multiple people to edit it. This method is easier than the next one and all steps can be done in the browser, at the cost of some admin work.

1. Contact admins and ask to create a draft for you.
2. You will be invited as a collaborator to this or intermediate repository and provided a link to the draft.
3. Edit the draft as necessary.
4. When finished, create a pull request or ask to do it for you.

3. Submit a pull request

This way is most advanced but is also most flexible and requires less admin assistance.

1. Fork the events repository.
2. Create a file with your report or change an existing file in the reports directory. The file name must follow the format YYYYMMDD-title-city-country.md, e.g. 20190116-tnabc-miami-usa.md. For content you can use this template as a starting point.
3. Create a pull request against the events repository.

• Check Allow edits from maintainers (help).
• Optionally, use Draft pull request that cannot be merged until you mark it as ready.

Tell people about your report

When your report is processed and "merged" (kind of released), let people know about it. Use the final link in the master branch and:

1. Share it to other events people in #event_planning
2. Submit it to r/decred subreddit
3. Post it on your Twitter
4. Optionally, ask in #social_media chat room to retweet

Contact admins

To get your reports merged or to propose an improvement:

• either create an issue
• or ask in #event_planning chat room (ping @bee)

To propose a tweet or retweet of your report:

• ask in #social_media room chat room.

Chat rooms are available in Matrix, Discord or Slack.