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

Review procedure for supporting/attending external events #352

Closed
amcewen opened this issue Oct 4, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@amcewen
Copy link
Member

commented Oct 4, 2016

Given we only just managed a presence at Manchester MakeFest, we should see what we need to do to make it less stressful.

Might be helped if we get an events team as part of #244...

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Nov 10, 2016

Suggestions:

  • Prepare a stock checklist
  • Create a new issue for any new event, assign to people involved, copy and paste checklist in.

@DefProc DefProc referenced this issue Feb 19, 2017

Closed

Go to Maker Faire UK 2017 #448

1 of 13 tasks complete
@DefProc

This comment has been minimized.

Copy link

commented Nov 20, 2017

Here's how I see it:

  • Create an issue for applying to the event.
  • Apply the Meetup: Events Label.
  • Create a Milestone if many tasks are required.
  • Assign/choose/volunteer a champion to co-ordinate the event for DoES (it helps if they commit to going) — assign that person(s) to the event issue.

Using the main event issue as a progress tracker, the coördinator should:

  • Apply for the event as applicable (ideally from a DoES email, but from the event champion if suitable).
  • Recruit attendees.
  • Collate the exhibition.
  • Recruit/organise transport (as appropriate).
  • Help attendees find hotels (if appropriate).
  • Create a packlist.
  • Reply to any H&S and risk assessment requirements.
  • Liaise with the event organisers regarding any drop-off and pick-up requirements.
  • Go to the event.
  • Come back
  • Unpack
  • Report any necessary information and close any issues for the event.

@DefProc DefProc removed their assignment Nov 20, 2017

@DoESsean DoESsean closed this Jul 4, 2019

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Jul 4, 2019

@DoESsean

This comment has been minimized.

Copy link
Contributor

commented Jul 4, 2019

I have not. My assumption was that, since we've attended quite a few events since this issue was raised, the people that were running DoES' presence had them internalised.

Probably should do that, to be fair.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.