Workshop Instructor Guidelines - Revision history

Catherine at 13:55, 14 February 2019

2019-02-14T13:55:35Z

← Older revision		Revision as of 09:55, 14 February 2019
Line 9:		Line 9:
	*Consider tool limitations as well - wood working tends to only be 5 people because we don't have duplicates of most wood tools.		*Consider tool limitations as well - wood working tends to only be 5 people because we don't have duplicates of most wood tools.
	*HackRVA will cover the cost of materials and experienced people can help decide a price on the class.		*HackRVA will cover the cost of materials and experienced people can help decide a price on the class.
	*A more ~~experience~~ member can help you get started on meetup.com. It's not hard, but doesn't hurt.		*A more experienced member can help you get started on meetup.com. It's not hard, but doesn't hurt.
	*Be clear and bounded on what you're going to do in your description on meetup as well as the workshop itself.		*Be clear and bounded on what you're going to do in your description on meetup as well as the workshop itself.
	*Drop some good links in your meetup.com event for people to get a little pre-workshop knowledge.		*Drop some good links in your meetup.com event for people to get a little pre-workshop knowledge.

Aaronn0130: added 70/30

2017-01-24T03:55:30Z

added 70/30

Kent.durvin at 20:32, 15 February 2016

2016-02-15T20:32:55Z

← Older revision		Revision as of 16:32, 15 February 2016
Line 8:		Line 8:
	*Limit the number of attendees to a reasonable amount. About 10 seems to be an upper limit for most things.		*Limit the number of attendees to a reasonable amount. About 10 seems to be an upper limit for most things.
	*Consider tool limitations as well - wood working tends to only be 5 people because we don't have duplicates of most wood tools.		*Consider tool limitations as well - wood working tends to only be 5 people because we don't have duplicates of most wood tools.
	*HackRVA will cover the cost of materials and experienced people at can help decide a price on the class.		*HackRVA will cover the cost of materials and experienced people can help decide a price on the class.
	*A more experience member will help you setup the ~~even~~ on meetup.com. It's not hard, but doesn't hurt.		*A more experience member will help you setup the event on meetup.com. It's not hard, but doesn't hurt.
	*Be clear and bounded on what you're going to do in your description on meetup as well as the workshop itself.		*Be clear and bounded on what you're going to do in your description on meetup as well as the workshop itself.
	*Drop some good links in your meetup.com event for people to get a little pre-workshop knowledge.		*Drop some good links in your meetup.com event for people to get a little pre-workshop knowledge.
			*Specify clearly on Meetup any software that needs to be pre-loaded on the students' computers, with links, to save time on installations (unless installing is tricky or part of the class.)
	*We don't pay people for doing workshops - its a part of being an outstanding member of our community. Free is best for our goals.		*We don't pay people for doing workshops - its a part of being an outstanding member of our community. Free is best for our goals.

	These are all just guidelines - some we pretty much always follow, but we're open to experimentation. If you have a unique idea, let someone at HackRVA know, and we can probably ~~workout~~ something.		These are all just guidelines - some we pretty much always follow, but we're open to experimentation. If you have a unique idea, let someone at HackRVA know, and we can probably work out something.

Aaronn0130: updated and added some scheduling details

2016-02-15T19:46:51Z

updated and added some scheduling details

← Older revision		Revision as of 15:46, 15 February 2016
Line 1:		Line 1:
	~~---Work in Progress---~~		Guidelines For a Good Workshop at HackRVA


	*Workshops should be a ~~Hands~~-On event.		*Workshops should be a hands-on event (lecture-only style doesn't work well - if you want to give a talk, cool - that's different though.
	*Workshops should have something started (preferably completed) by the end.		*Workshops should have something started (preferably completed) by the end.
	*Workshops seem to do best around 2 hours.		*Workshops seem to do best around 2-3 hours.
	*Limit the number of attendees to a reasonable amount. About 10 seems to be an upper limit.		*Workshops tend to be on Saturday or Sunday from/between 10am-1pm (they can start earlier or alter, but can't go beyond 1pm on weekends - those are freehack times). Weeknights can also work.
	*~~Practice a couple~~ of ~~times first~~. ~~Pacing is hard to guess~~ at.		*Limit the number of attendees to a reasonable amount. About 10 seems to be an upper limit for most things.
	*~~Materials and supplies are typically paid for out of pocket~~, but ~~can be recouped through~~ workshop ~~fees~~. ~~Meetup now supports required payment through Wepay~~. ~~Remember~~ to ~~account~~ for ~~merchant fees and consider building in~~ a ~~reasonable donation~~ to ~~the space in the fee~~. ~~[[Michael]] Lane~~ can ~~help with determining a reasonable fee~~.		*Consider tool limitations as well - wood working tends to only be 5 people because we don't have duplicates of most wood tools.
			*HackRVA will cover the cost of materials and experienced people at can help decide a price on the class.
			*A more experience member will help you setup the even on meetup.com. It's not hard, but doesn't hurt.
			*Be clear and bounded on what you're going to do in your description on meetup as well as the workshop itself.
			*Drop some good links in your meetup.com event for people to get a little pre-workshop knowledge.
			*We don't pay people for doing workshops - its a part of being an outstanding member of our community. Free is best for our goals.

			These are all just guidelines - some we pretty much always follow, but we're open to experimentation. If you have a unique idea, let someone at HackRVA know, and we can probably workout something.

Ranthalion at 14:06, 23 July 2014

2014-07-23T14:06:57Z

← Older revision		Revision as of 10:06, 23 July 2014
Line 7:		Line 7:
	*Limit the number of attendees to a reasonable amount. About 10 seems to be an upper limit.		*Limit the number of attendees to a reasonable amount. About 10 seems to be an upper limit.
	*Practice a couple of times first. Pacing is hard to guess at.		*Practice a couple of times first. Pacing is hard to guess at.
	*Materials and supplies are typically paid for out of pocket, but can be recouped through workshop fees. Meetup now supports required payment through Wepay. Remember to account for ~~the 6%~~ merchant fees and consider building in a reasonable donation to the space in the fee.		*Materials and supplies are typically paid for out of pocket, but can be recouped through workshop fees. Meetup now supports required payment through Wepay. Remember to account for merchant fees and consider building in a reasonable donation to the space in the fee. [[Michael]] Lane can help with determining a reasonable fee.

Ranthalion: Workshop Instructor Guidelines - work in progress

2014-07-02T14:32:33Z

Workshop Instructor Guidelines - work in progress

New page

---Work in Progress---

*Workshops should be a Hands-On event.
*Workshops should have something started (preferably completed) by the end.
*Workshops seem to do best around 2 hours.
*Limit the number of attendees to a reasonable amount. About 10 seems to be an upper limit.
*Practice a couple of times first. Pacing is hard to guess at.
*Materials and supplies are typically paid for out of pocket, but can be recouped through workshop fees. Meetup now supports required payment through Wepay. Remember to account for the 6% merchant fees and consider building in a reasonable donation to the space in the fee.

← Older revision		Revision as of 23:55, 23 January 2017
Line 2:		Line 2:


	*Workshops should be a hands-on event (lecture-only style doesn't work well - if you want to give a talk, cool - that's different though.		*Workshops should usually be a hands-on or practical outcome driven event (lecture-only style doesn't work well - if you want to give a talk, cool - that's different thing though and should be presented as a talk).
	*Workshops should have something started (preferably completed) by the end.		*Workshops should have something started (preferably completed) by the end or at least a skill transfer.
	*Workshops seem to do best around 2-3 hours.		*Workshops seem to do best around 2-3 hours.
	*Workshops tend to be on Saturday or Sunday from/between 10am-1pm (they can start earlier or ~~alter~~, but can't go beyond 1pm on weekends - those are freehack times). Weeknights can also work.		*Workshops tend to be on Saturday or Sunday from/between 10am-1pm (they can start earlier or later, but can't go beyond 1pm on weekends - those are freehack times). Weeknights can also work.
	*Limit the number of attendees to a reasonable amount. About 10 seems to be an upper limit for most things.		*Limit the number of attendees to a reasonable amount. About 10 seems to be an upper limit for most things.
	*Consider tool limitations as well - wood working tends to only be 5 people because we don't have duplicates of most wood tools.		*Consider tool limitations as well - wood working tends to only be 5 people because we don't have duplicates of most wood tools.
	*HackRVA will cover the cost of materials and experienced people can help decide a price on the class.		*HackRVA will cover the cost of materials and experienced people can help decide a price on the class.
	*A more experience member ~~will~~ help you ~~setup the event~~ on meetup.com. It's not hard, but doesn't hurt.		*A more experience member can help you get started on meetup.com. It's not hard, but doesn't hurt.
	*Be clear and bounded on what you're going to do in your description on meetup as well as the workshop itself.		*Be clear and bounded on what you're going to do in your description on meetup as well as the workshop itself.
	*Drop some good links in your meetup.com event for people to get a little pre-workshop knowledge.		*Drop some good links in your meetup.com event for people to get a little pre-workshop knowledge.
	*Specify clearly on Meetup any software that needs to be pre-loaded on the students' computers, with links, to save time on installations (unless installing is tricky or part of the class.)		*Specify clearly on Meetup any software that needs to be pre-loaded on the students' computers, with links, to save time on installations (unless installing is tricky or part of the class.)
	*~~We don't pay people~~ for ~~doing workshops~~ - ~~its a part of being an outstanding member of our community~~. ~~Free is best for our goals~~.		*Free is a great price for a workshop at hackrva. But we also offer 70/30 split with teacher/space on a case-by-case basis. If you're interested in this teaching option, let someone at hack know and we'll talk about that.

	These are all just guidelines - some we pretty much always follow, but we're open to experimentation. If you have a unique idea, let someone at HackRVA know, and we can probably work out something.		These are all just guidelines - some we pretty much always follow, but we're open to experimentation. If you have a unique idea, let someone at HackRVA know, and we can probably work out something.