-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #14 from lrug/responding-to-feedback
Responding to feedback
- Loading branch information
Showing
1 changed file
with
29 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,7 +5,7 @@ title: README.lrug | |
|
||
# README.lrug | ||
|
||
LRUG is a London-based community for anyone who is interested in the Ruby programming language. | ||
LRUG is a London-based community for anyone who is interested in the Ruby programming language, especially beginners. | ||
|
||
LRUG provides [online](http://lrug.org/mailing-list) and [offline](http://lanyrd.com/series/lrug/) opportunities to: | ||
|
||
|
@@ -18,9 +18,11 @@ We want LRUG to be a diverse and inclusive community, united by an interest in R | |
* [Code of Conduct](#code-of-conduct) | ||
* [Incident Handling](#incident-handling) | ||
* [Meetings](#meetings) | ||
* [Scheduling](#scheduling) | ||
* [Content](#content) | ||
* [Timing](#timing) | ||
* [Talks](#talks) | ||
* [Scheduling](#scheduling) | ||
* [Content](#content) | ||
* [Timing](#timing) | ||
* [After The Talks](#after-the-talks) | ||
* [Sponsorship](#sponsorship) | ||
|
||
## Code of Conduct | ||
|
@@ -31,7 +33,7 @@ It’s of primary importance that everyone who wants to participate feels safe a | |
* be considerate of people’s time and attention | ||
* contribute positively and constructively to discussions (online or in-person) | ||
|
||
On the mailing list, we want to maintain a high signal-to-noise ratio, so please: | ||
On the mailing list, we want to maintain a high signal-to-noise ratio and while the organisers will step in as soon as they see poor behaviour, we encourage you to say something if you see it first. So please: | ||
|
||
* lead by example — if a discussion is devolving into snark and name-calling, either let it die or raise the tone | ||
* keep standards high — if someone acts disrespectfully, make that crystal clear to them | ||
|
@@ -52,34 +54,52 @@ If you experience or witness any harassing behaviour, please report it to: | |
|
||
## Meetings | ||
|
||
We meet once a month at Skills Matter, usually on the second Monday. There are typically two talks and then we go to the pub. There’s always tea and coffee at Skills Matter, and sometimes there’ll be pizza; beer is limited to the pub afterwards. | ||
We meet once a month at [Skills Matter](http://skillsmatter.com/location-details/design-architecture/484/96), usually on the second Monday. There are typically [two talks](#talks) and then we go to [the pub](#after-the-talks). There’s always tea and coffee at Skills Matter, and sometimes there’ll be pizza; beer is limited to the pub afterwards. | ||
|
||
To stay informed about our upcoming meetings you can: | ||
|
||
* subscribe to [our calendar](http://lrug.org/meeting-calendar) | ||
* follow the [LRUG series on lanyrd](http://lanyrd.com/series/lrug/) | ||
* follow [@lrug](http://twitter.com/lrug) | ||
* subscribe to [the mailing list](http://lrug.org/mailing-list) | ||
* subscribe to [the lrug.org meetings RSS](http://lrug.org/rss/meetings) | ||
|
||
### Talks | ||
|
||
Most of our meetings have talks from community members and we're always looking for people to give a talk. If you'd like to give a talk you should get in touch with [Murray Steele](http://h-lame.com/) ([@hlame](http://twitter.com/hlame), [[email protected]](mailto:[email protected])) and suggest it. | ||
|
||
Our goal is to accept any offered talk. If the talk is obviously about Ruby it's a no-brainer; you can give your talk. If it's not obviously about Ruby we'll have a discussion first to see what the hook is for Rubyists. We're quite an open-minded group, so the hook doesn't have to be that obvious. In the unlikely event that it turns out that LRUG isn't a good home for your talk, we'll do our best to come up with some alternative ideas for places you could give it. | ||
|
||
### Scheduling | ||
#### Scheduling | ||
|
||
Slots for talks are first-come, first-served. Once you've decided to give your talk we'll let you know when the next likely meeting is that there would be a free slot. For example, we usually have two talks per meeting, so if there are 4 people on our list of volunteers when you offer your talk it would be likely that the third meeting is the one you'd be scheduled for. Of course, people drop out or aren't available for a specific meeting so you might get a slot sooner. | ||
|
||
If there is a specific future meeting that would be most convenient for you, let us know and we'll do our best to accommodate that. | ||
|
||
### Content | ||
#### Content | ||
|
||
LRUG is a mixed-ability crowd; we have talks from first-timers just learning Ruby all the way up to people that have been using it for years. This means you can pitch your talk at any level and someone will get something out of it. It's a mostly technical crowd, so don't shy away from getting into the nitty gritty of your topic. We'd prefer an in-depth discussion of a single aspect to a shallow overview of the whole thing. | ||
|
||
Your talk should observe the code of conduct. Any talks that don't will be stopped and the speaker asked to leave. | ||
|
||
If you are using the projector you should favour large fonts and a high contrast colour scheme with dark text on a light background in anything you show. The default settings for most presentation applications are a safe bet, but you might have to pre-configure your terminal or editor if you are using those. | ||
|
||
### Timing | ||
#### Timing | ||
|
||
Our normal pattern for a meeting is two speakers with 40 minute time slots, although one-off meetings might be different. For example, our February meetings are for lightning talks, run using the "20 slides, 20 seconds each" format. | ||
|
||
A slot isn’t how long your talk should be, but how much time you will get in front of the group. You can fill that time slot as you see fit (talk + questions, talk only, &c). | ||
|
||
For a 40-minute slot, we recommend a 30-minute talk. This leaves plenty of time for you to over-run, answer questions, and faff about with a laptop at the start. | ||
|
||
### After The Talks | ||
|
||
When the talks are finished, usually around 8pm, most of the group head over to [The Slaughtered Lamb](http://www.theslaughteredlambpub.com/). This part of the meeting is your opportunity to socialise with other LRUG members and speak with the presenters about their talks. | ||
|
||
Just because we're in a pub doesn't mean you have to drink alcohol. If you do choose to drink alcohol we encourage you to explore the food menu and drink responsibly. | ||
|
||
Although the venue for this part of the meeting is a pub and therefore feels more informal, be aware that the code of conduct still applies. | ||
|
||
## Sponsorship | ||
|
||
LRUG is hosted by [Skills Matter](http://skillsmatter.com/) who provide the venue; make tea, coffee, & water available during the talks; film the talks; and handle registration. We don't currently need venue sponsorship or an alternate venue. | ||
|