Difference between revisions of "Team:Infodesk/CCC"

From SHA2017
Jump to: navigation, search
 
(10 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
* Make sure you have phone numbers of site maintainers (e.g. NON-sha people that own the site). Sometimes (when shit hits the fan) they know how to solve it.
 
* Make sure you have phone numbers of site maintainers (e.g. NON-sha people that own the site). Sometimes (when shit hits the fan) they know how to solve it.
 
* All the team/village leaders on the public wiki  
 
* All the team/village leaders on the public wiki  
* Printed lists for InfoDesk
+
* Printed lists with main numbers + assemblies for InfoDesk
 
* Have a CMS/wiki for info desk that has frequently asked questions, it should state whether the information is still accurate/recent and ACCESS LEVEL, you will have information that is not for all eyes/public (like: angel only). Make sure people know.
 
* Have a CMS/wiki for info desk that has frequently asked questions, it should state whether the information is still accurate/recent and ACCESS LEVEL, you will have information that is not for all eyes/public (like: angel only). Make sure people know.
 
* Usually the infodesk @ CCC is run by 2 more experienced angels/supervisors and some newer guys/angels. This is not established as a strict hierarchy, but people will take the lead naturally.
 
* Usually the infodesk @ CCC is run by 2 more experienced angels/supervisors and some newer guys/angels. This is not established as a strict hierarchy, but people will take the lead naturally.
 +
* Infodesk has "Archangel" (shifts of how many hours they like), 2 hour shifts for "normal" angels
 
* Make sure InfoDesk people can handle stress, it's not very handy during busy times.
 
* Make sure InfoDesk people can handle stress, it's not very handy during busy times.
 
* Restrict access to public facing accounts (twitter) to trusted people
 
* Restrict access to public facing accounts (twitter) to trusted people
 
* CCC has an "Awareness" team for the first time (for people who feel harassed), and although some where skeptical at first, it proved to be a positive thing, just to have some people who know what to do with these cases.
 
* CCC has an "Awareness" team for the first time (for people who feel harassed), and although some where skeptical at first, it proved to be a positive thing, just to have some people who know what to do with these cases.
 
* STAMPS -> some people have a "hacker passport" (might be provided by easter hack), and these people would love a stamp in their passport of SHA. We should look at creating a stamp!
 
* STAMPS -> some people have a "hacker passport" (might be provided by easter hack), and these people would love a stamp in their passport of SHA. We should look at creating a stamp!
 +
* STICKERS -> The more the better. Also a sticker table / place to collect stickers from assemblies / other people.
 +
* A place to change childrens diapers! (not only on the womens toilet, also on the mens toilet!)
 +
* A FAST online look up where Assemblies/projects/talks/workshops are, they sometimes change location during the event, so printed is not handy. https://c3nav.de/ - https://fahrplan.events.ccc.de/congress/2016/Fahrplan/schedule/2.html - https://events.ccc.de/congress/2016/wiki/Static:Self-organized_Sessions
 +
* Twitter feeds / IRC channel per room/saal/halle
 +
* Nearby places (like ATMs) https://events.ccc.de/congress/2016/wiki/Static:Useful_Places - https://events.ccc.de/congress/2016/wiki/Static:Food_and_drinks
 +
* CCC Infodesk uses TweetDeck for answering questions on Twitter. Only certain people have access (About 6-12, with always 1-2 people online / answering questions)
 +
* (Public) transport - Information about the trains/buses that go from/to the event to Amsterdam
 +
* Contact other dutch hacker conferences / camps for experience?

Latest revision as of 15:02, 29 December 2016

Some stuff I learned at CCC:

  • Make sure you have phone numbers of site maintainers (e.g. NON-sha people that own the site). Sometimes (when shit hits the fan) they know how to solve it.
  • All the team/village leaders on the public wiki
  • Printed lists with main numbers + assemblies for InfoDesk
  • Have a CMS/wiki for info desk that has frequently asked questions, it should state whether the information is still accurate/recent and ACCESS LEVEL, you will have information that is not for all eyes/public (like: angel only). Make sure people know.
  • Usually the infodesk @ CCC is run by 2 more experienced angels/supervisors and some newer guys/angels. This is not established as a strict hierarchy, but people will take the lead naturally.
  • Infodesk has "Archangel" (shifts of how many hours they like), 2 hour shifts for "normal" angels
  • Make sure InfoDesk people can handle stress, it's not very handy during busy times.
  • Restrict access to public facing accounts (twitter) to trusted people
  • CCC has an "Awareness" team for the first time (for people who feel harassed), and although some where skeptical at first, it proved to be a positive thing, just to have some people who know what to do with these cases.
  • STAMPS -> some people have a "hacker passport" (might be provided by easter hack), and these people would love a stamp in their passport of SHA. We should look at creating a stamp!
  • STICKERS -> The more the better. Also a sticker table / place to collect stickers from assemblies / other people.
  • A place to change childrens diapers! (not only on the womens toilet, also on the mens toilet!)
  • A FAST online look up where Assemblies/projects/talks/workshops are, they sometimes change location during the event, so printed is not handy. https://c3nav.de/ - https://fahrplan.events.ccc.de/congress/2016/Fahrplan/schedule/2.html - https://events.ccc.de/congress/2016/wiki/Static:Self-organized_Sessions
  • Twitter feeds / IRC channel per room/saal/halle
  • Nearby places (like ATMs) https://events.ccc.de/congress/2016/wiki/Static:Useful_Places - https://events.ccc.de/congress/2016/wiki/Static:Food_and_drinks
  • CCC Infodesk uses TweetDeck for answering questions on Twitter. Only certain people have access (About 6-12, with always 1-2 people online / answering questions)
  • (Public) transport - Information about the trains/buses that go from/to the event to Amsterdam
  • Contact other dutch hacker conferences / camps for experience?