devsummithowto

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
devsummithowto [2022/08/01 12:53] – Accessibility of venue PauAmmadevsummithowto [2022/10/06 22:51] (current) – Add Category: Community KubilayKocak
Line 5: Line 5:
 ===== Golden Rules ===== ===== Golden Rules =====
  
-  * Choice of venue is critically important to the dynamic of a devsummit.  You need to pick a place that allows people to talk freely, this means avoiding lecture halls with immovable chairs, for example.  You also need to ensure it's fully accessible to people with disabilities. Don't trust the venue management: they often don't know, don't care, or lie.  Have one or more people who know what to watch for inspect the premises well in advance.+  * Choice of venue is critically important to the dynamic of a devsummit.  You need to pick a place that allows people to talk freely, this means avoiding lecture halls with immovable chairs, for example.  Ideally, it's fully accessible to people with disabilities as well. Most of our typical venues (universities, hotels) in the past had this, but checking with the people providing the venue up-front (or better, having someone who knows what to watch for) is a good idea.
   * Plan *really* far in advance, at least 6 months.   * Plan *really* far in advance, at least 6 months.
   * People only attend if you ask them to personally, and possibly only if you bother them repeatedly.  The developers list is a good start.   * People only attend if you ask them to personally, and possibly only if you bother them repeatedly.  The developers list is a good start.
   * Invite interesting guests.  Guests can be external to the project, basically users of major parts of the system.  Corporate guests, i.e. developers who consume %%FreeBSD%% are an excellent choice.  Warn guests that they may need to sit through hours of people arguing about obscure kernel design issues, or just find themselves in a room full of geeks tapping at notebooks and occasionally giggling due to bad jokes on IRC.  Avoid marketing types.   * Invite interesting guests.  Guests can be external to the project, basically users of major parts of the system.  Corporate guests, i.e. developers who consume %%FreeBSD%% are an excellent choice.  Warn guests that they may need to sit through hours of people arguing about obscure kernel design issues, or just find themselves in a room full of geeks tapping at notebooks and occasionally giggling due to bad jokes on IRC.  Avoid marketing types.
   * Make sure people think about topics to work on before they arrive.  Ask people to at least submit an idea or two.   * Make sure people think about topics to work on before they arrive.  Ask people to at least submit an idea or two.
-  * Feed people but remember to ask in advance about dietary requirements.  Vegetarian is a basic requirement in our community, but there are also kosher and other religious dietary restrictions to consider. +  * Feed people but remember to ask in advance about dietary requirements.  Vegetarian is a basic requirement in our community, but there are medical restrictions (gluten, dairy, cholesterol, sodium, allergies), religious dietary restrictions (Kosher, Halal, Quaker, Hinduist, Sikh, etc.), and food aversions to consider. 
   * Don't get stuck with the bill.  Find a sponsor or tell people in advance what the cost will be.  There are always cheap options.   * Don't get stuck with the bill.  Find a sponsor or tell people in advance what the cost will be.  There are always cheap options.
   * Make sure they have your mobile phone number and a map.   * Make sure they have your mobile phone number and a map.
Line 53: Line 53:
   * One of the organizers must be local to the venue.  This is really important.   * One of the organizers must be local to the venue.  This is really important.
   * Pick a venue physically close to where people are staying (<30 minutes walk).  Don't require taking a bus.   * Pick a venue physically close to where people are staying (<30 minutes walk).  Don't require taking a bus.
-  * Make sure the venue is wheelchair-accessible.+  * Make sure the venue is accessible (ramps, elevators, accessible toilets, Braille or audio signage, quiet rooms, etc.). 
 +  * If at all possible, have on-site childcare.
   * Provide food on-site to avoid people disappearing for long periods of time finding lunch.   * Provide food on-site to avoid people disappearing for long periods of time finding lunch.
-  * Try to be near a source of caffeine.  Good coffee makes happy hacking.+  * Try to be near a source of caffeine or theobromine.  Good coffee or tea makes happy hacking.
   * Dynamics of a meeting are determined by the layout of the space.   * Dynamics of a meeting are determined by the layout of the space.
   * If you want people to talk to each other, they have to be able to see each other so working around tables is better than a lecture hall.   * If you want people to talk to each other, they have to be able to see each other so working around tables is better than a lecture hall.
Line 96: Line 97:
   * Invite guests from outside the developer community -- especially people who can provide a new view on an important topic.   * Invite guests from outside the developer community -- especially people who can provide a new view on an important topic.
   * Introduce guests.   * Introduce guests.
-  * Provide name tags. If possible with more than just the name on them.+  * Provide name tags. If possible with more than just the name on them. Include a coouple empty ones for people showing up spontaneously or at the last minute.
  
 ===== Food ===== ===== Food =====
Line 127: Line 128:
 ===== The Place People Stay/Sleep ===== ===== The Place People Stay/Sleep =====
  
 +  * Must be accessible to people with disabilities. Have one or more people who know what to watch for inspect it well in advance if possible.
   * Must have networking.   * Must have networking.
   * Must allow late check-in.  24 hour access is probably required given how far many people travel.   * Must allow late check-in.  24 hour access is probably required given how far many people travel.
Line 134: Line 136:
 ===== Random stuff ===== ===== Random stuff =====
  
-  * Name tags are really useful, especially if you have guests joining the community for the first time. Names should be no less than 20 point.+  * Name tags are really useful, especially if you have guests joining the community for the first time. Names should be no less than 20 point. Leave space for people to add their pronouns or preferred pronouns if they want or need to.
   * Get to the venue before the developers to avoid wasting everyone's time setting up projectors.   * Get to the venue before the developers to avoid wasting everyone's time setting up projectors.
   * Bring extra power strips.   * Bring extra power strips.
Line 141: Line 143:
 ---- ----
  
 +{{tag>Community}}
 {{tag>HowTo}} {{tag>HowTo}}
  
  • devsummithowto.1659358408.txt.gz
  • Last modified: 2022/08/01 12:53
  • by PauAmma