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

Workshop preparation guidelines and pack #281

Open
5 tasks
jcmolloy opened this issue Sep 19, 2015 · 3 comments
Open
5 tasks

Workshop preparation guidelines and pack #281

jcmolloy opened this issue Sep 19, 2015 · 3 comments

Comments

@jcmolloy
Copy link
Member

To make it easy for workshop organisers to set things up easily by having a tick list and guidance for each step of the way (makes it easier to delegate specific tasks)

  • Instructions e.g. set up a repo,
  • Selection of template advertising blurbs
  • Documentation of Eventbrite set up and questions (maybe use WT workshop as guide e.g. areas of interest, technical abilities)
    Thus far, in terms of promoting workshops, Eventbrite is the entity that has been used.
  • Timeline for communications
  • Template message to send 2-3 days before event with installation instructions link (to be updated per workshop)

This will complement #278 template for meeting follow up

@blahah
Copy link
Member

blahah commented Sep 19, 2015

There is already such a checklist: https://github.com/ContentMine/workshops/blob/master/organisation/checklist.md

But it will probably need updating and expanding

@jcmolloy
Copy link
Member Author

Aha - I thought I had seen one before! Clearly didn't look hard enough -
thanks RSU. The template participant info email, a few notes on what
questions to include on the eventbrite and a refresh would still be good.

Jenny

On Sat, Sep 19, 2015 at 4:46 PM, Richard Smith-Unna <
notifications@github.com> wrote:

There is already such a checklist:
https://github.com/ContentMine/workshops/blob/master/organisation/checklist.md

But it will probably need updating and expanding


Reply to this email directly or view it on GitHub
#281 (comment)
.

@jcmolloy
Copy link
Member Author

jcmolloy commented Dec 9, 2015

Reassigning to @chreman who has already done some of it. Feel free to ask me to take some, we should just make sure everything can be ticked off and the current checklist has been cross-referenced to Steph's.

@jcmolloy jcmolloy assigned chreman and unassigned GrahamSteel Dec 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants