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

Recommendations for a practical conference timeline #22

Merged
merged 2 commits into from Jun 24, 2018

Conversation

Projects
None yet
3 participants
@skade
Contributor

skade commented Mar 30, 2018

#17

@badboy badboy self-requested a review Apr 1, 2018

@spastorino

This comment has been minimized.

spastorino commented May 30, 2018

First of all, this is great!!!

As we are running Rust Latam, I think it could be nice to add a define a rough estimate of conference costs bullet to the immediate stuff. Which would involve having a couple of venue prices, food, recording, translations if needed, etc, etc.
With that info you may know more or less if the thing is viable and/or how much would you need to set the sponsor and tickets prices.

Another thing is that ...

## 5 days before

* Communicate diatary restrictions to the caterer

## 4 days before

* Badges go to printer

May be too short. It's definitely too short here, small country, third world so it's not that you get this kind of stuff in one day. I'd move to at least 1 month in advance to be 100% sure that you will get the stuff.

@badboy

This comment has been minimized.

Member

badboy commented Jun 1, 2018

@spastorino: Especially dates are definitely a thing that varies from location to location. However these are things you can plan for (you just need to clarify it early when the deadline would be).

During impl Days @skade gave a workshop for event planning and we're collecting results here: https://github.com/rust-community/foss-events-planner

We plan to extend the issues into a document with a proper timeline and a task list one can work from.

@spastorino

This comment has been minimized.

spastorino commented Jun 1, 2018

So are those dates seen as deadline? or start of work?, I guess deadlines, in that case it's ok :).

@badboy

This comment has been minimized.

Member

badboy commented Jun 1, 2018

Deadlines. That's when it needs to happen.

@skade

This comment has been minimized.

Contributor

skade commented Jun 1, 2018

Hi @spastorino, thanks for noticing that. Especially the "dietary restrictions" should be "final dietary restrictions".

You can always communicate earlier, but people will fill out their forms until the very last minute, which means you want to find the latest possible date for that. Your supplier will help you in finding that date.

@spastorino

This comment has been minimized.

spastorino commented Jun 1, 2018

You can always communicate earlier, but people will fill out their forms until the very last minute, which means you want to find the latest possible date for that. Your supplier will help you in finding that date.

Yes, that's true. I was trying to give some advice about how things may work in the third world. In particular in Uruguay things are probably going to be ok, but doing that here is taking a huge risk ;). Probably better to do an "estimate" of the food and restrictions.

@skade

This comment has been minimized.

Contributor

skade commented Jun 6, 2018

@spastorino Yeah, we should communicate better that "this deadline should be planned with your supplier".

BTW, we have rust-community/foss-events-planner now, which might help with that in the future.

@badboy

This comment has been minimized.

Member

badboy commented Jun 24, 2018

I'm fine with merging this here now, maybe adding a small note that it's a rough overview and that we will revise it with the foss-event-planer

@badboy

badboy approved these changes Jun 24, 2018

@skade

This comment has been minimized.

Contributor

skade commented Jun 24, 2018

@badboy cool, could you open an issue over there then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment