max-mapper / max-mapper/messages

hebocon pdx

Open
#41 33 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
29
Forks
1
PR merge metrics
No merged PRs in 30d

Description

cc @nvcexploder @BenSJones

We are organizing a hebocon for Portland.

TODO list for now:

  • pick date for first organizers meetup
  • find + invite organizers
  • squat twitter account (@heboconpdx)

TODO for first meeting (or after):

  • pick date for sumo day
  • pick venue for sumo day
  • pick venue for robot building parties
  • decide on exact format + logistics (in person at first meeting)
  • create outreach team to do personal outreach to potential attendees
  • add to calagator
  • schedule robot building parties leading up to the sumo day
  • create facebook event + add admins
  • logo
  • static site

also the hebocon organizers facebook requests we do this when ready:

At the time like this, please post to here.
* When you join this group.
- Write clearly where you would like to host Hebocon in. If there already are organizers in the same area, they can find you.
* When you decide the place and the date of your Hebocon.
- Please notice whether I can annouce it on our Facebook page or not. If I can, please add a short message from you to Hebocon fans around world.
* When your Hebocon is finished.
- If you can post the photos and videos here, we will introduce on our Facebook page! If you have too much datas to post, please send to me via email or something.

additionally, here is a rulebook: http://portal.nifty.com/hebocon/files/HEBOCON_simple_rule_book_v1.zip

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points. Start by reviewing the TODO list and linked rulebook; the work would need an agreed event plan and separately scoped tasks for the listed organizational and site work, none of which is currently defined as a newcomer-sized change.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.