Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How-to checklist #4

Closed
2 of 39 tasks
amandaharlin opened this issue Sep 2, 2014 · 5 comments
Closed
2 of 39 tasks

How-to checklist #4

amandaharlin opened this issue Sep 2, 2014 · 5 comments

Comments

@amandaharlin
Copy link
Member

this isn't finished, but i'll post the checklist. i'd like to make this into a form that people interact with (because the 'or' option doesn't translate well without the radio buttons).

  • Find a need for a user group to fill
  • Find interest in the community
  • Join Techlahoma
  • Have a Code of Conduct
    • Use the Techlahoma CoC, modify an existing CoC, or create your own
  • Use a 'super user' account for everything
    • Create a 'super user' group email account
    • Use that email for everything: twitter, meetup, g+, etc
  • Decide on your meeting place
    • Techlahoma provides user groups with a free meeting space at Prototek
    • Find a meeting space, agree to their insurance forms for meeting at the space, and pay to reserve it it
      • Small groups (12 people) can meet at the 404. Small, Med, Large groups can meet at the Library, the Paramount, or inside a business.
  • Decide when you'll meet
    • Use the Techlahoma Date/Time Availability Page to see what's open
  • Recruit Organizers and Volunteers
    • Have at least three volunteers to help out the group
    • Decide on primary focuses for individual volunteers
  • Have a group website
    • Host it in a maintainable space
    • Train your volunteers on how to update the website
    • Use Hexo (Techlahoma provides groups with training on an easy to setup and maintainable blogging platform, Hexo)
      • Pick a theme that Techlahoma created, create your own, or use an existing theme
    • Add your group's info to the site
      • About
      • Date & Time
      • Location
      • Social Media
      • Contact
  • Pick an email provider
    • Use MailChimp
      • View Techlahoma's MailChimp training if needed
    • Use Meetup as a mailing option
  • Ask your community what they want to learn about
    • Ask potential speakers if they'd talk at your group
    • Consider preparing talks to give in case of necessity
    • Agree to never skip your regularly scheduled meeting. Have a 'town tall' meeting at your group if a speaker is unavailable. Just don't lose that momentum.
  • Decide if you'll record the event or live stream
    • Use Techlahoma's recording gear by meeting at Prototek. (Techlahoma provides user groups with a dedicated computer, software, and video cameras for recording speakers and events)
    • Buy a computer, computer screen, software, video cameras
@the-simian
Copy link
Member

This is a good checklist. Its a markdown hoedown jamboree. 🐷 🐐 🐮 🐄 🐔 🐴

@amandaharlin
Copy link
Member Author

lol

@amandaharlin
Copy link
Member Author

i want to make this into a decision tree for people to click through.

  • we are an existing group or
  • want to start a new group
  • our group meets/will meet about {TECH}
  • we meet/will meet in {CITY}
  • we need/will need support for {mentoring, location, food, streaming, etc}
  • our group meets on {DAY/TIME} or
  • potential days & times our group will meet on are {DAY/TIME}

since i've got that meeting date data (or a portion of it now) just thought i'd store it in this comment until the decision tree gets made.


okc tech user group schedules:

1st week
Lunch - T?, W, Th, F
Dinner - M
Not available:
1st M - okcsharp (Lunch)
1st T - cocoaheadsokc (Night) & oklahomaphp (Varies day & city)
1st W - Irregulars (Night)
1st Th - okcdata (Night)
1st F - okc2600 (Night)

2nd week
Lunch - M, F
Dinner - T, W, Th, F
Not available:
2nd M - okcsql (Night)
2nd T - okcjug (Lunch)
2nd W - okcpy (Lunch)
2nd T - okcrb (Lunch)

3rd week
Lunch - M, F
Dinner - M, T
Not available:
3rd T - okcjs (Lunch)
3rd W - issa (Lunch) & irregulars (Night)
3rd Th - tableau (lunch), nerd beers (Night), Drupal (Night)
3rd F - dc405 (Night)

4th week
Lunch - M, T, W, Th, F
Dinner - M, T, F
Not available:
4th W - okcmysql (Night)
Last Th - okgd (Night) (Typically falls on the 4th week, but varies)


tulsa tech user group schedules:

1st week
Lunch -
Dinner -
Not available:

2nd week
Lunch -
Dinner -
Not available:

3rd week
Lunch -
Dinner -
Not available:

4th week
Lunch -
Dinner -
Not available:

@amandaharlin
Copy link
Member Author

Update

Tech Community Schedule

1st week 

M - okcsharp (Lunch)

T - cocoaheadsokc (Night) & oklahomaphp (Varies day & city, typically T though)

W - Irregulars (Night)

T - OKData (night)

F - okc2600 (Night)

2nd week 

M - okcsql (Night)

T - okcjug (Lunch)

W - okcpy (Lunch) 

T - okcrb (Lunch)

F - okclugnuts (Dinner) 

3rd week 

T - okcjs (Lunch)

W - issa (Lunch) & Irregulars (Night)

Th - nerd beers (Night), Drupal (Night)

4th week 

M - codeforokc (Night)
W - okcmysql (Night)

Last week

Last Th - okgd (Night) (falls on the last thurs of the month)

Dates not set: OKCSS (ux/ui/design), Open Hardware, Nerdy Girls Code Club (different Saturdays), Tulsa JS

@amandaharlin
Copy link
Member Author

This checklist can be in the usergroup generator (and also in an online format for non-yeoman users).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants