Venue info template

[caffodian]

This issue will probably be moved and live in the nonexistent private space, but what do we want to capture about venues? Here are a few things I've privately noted for myself and other organizers in the past:

• capacity
• AV setup (projector? recording? audio available?)
• food/alcohol allowed?
• location
• contact info
• how we know them (do we know someone that works there, was it a prior meetup, etc. This is also useful for cases where the venue requires an employee to be present - if someone in-network works there, a way of giving back would be to be present. On the other hand you don't want to overload people with meetup obligations just for working at a space, so there has to be expectations and encouragement to say no )
• what do they want out of it? (exposure within the community, hiring for specific languages, interest in supporting certain missions, etc.)
• cost (when not free)
• accessibility

[Mariatta]

This is the form we started using for pyladies vancouver https://goo.gl/forms/fEWpR1axuhNNs7Dd2

[keywordnew]

We could use a markdown file to hold Venues and all the important info proposed above in the private repo (once it's set up).

Like these:

• https://github.com/nodeschool/vancouver/blob/master/SCHEDULING.md
• https://github.com/Code-and-Coffee-YVR/Code-and-Coffee-YVR.github.io/blob/master/SCHEDULING.md

This is quick and easy, but def open to other ideas.

[keywordnew]

@Qard Would it be better to already have the name updated before asking for the upgrade to the org Github plan?

[keywordnew]

Action item from last Pasta Dinner resolved: All collective members should have access on request to the venue repo https://github.com/keywordnew/vancouver-spaces/

It's private as it holds personal information of 3rd parties, ie venue contacts.

[keywordnew]

If there are no objections, this issue can be closed :-)