Team:Logistics

From SHA2017
Revision as of 16:26, 25 October 2015 by Knorrie (talk | contribs) (How to join the team?)

Jump to: navigation, search

Logistics

Logistics, a.k.a. "Wij zijn niet te beroerd om jouw rommel op te ruimen."

Preliminary page...

Next up

Next team meeting: Thursday Nov 19 2015 18:30 near The Hague Central train station

Agenda:

  • Present first version of whirlbook (Juerd/Knorrie)
  • Tracking! (Juerd)
  • Add items you want to discuss here...

Team members

How to join the team?

If you like to help:

  • Set Team=Logistics in your UserInfo
  • Join the mailing list (not there yet) and introduce yourself ("Hi! I'm Foo, I'd like to help out with Logistics, I'm very good at Bar and have the same drivers licenses as Quux has.") ;-)
  • Think about how you want to participate (there will be more info to guide you doing this)
  • Show up at the next team meeting.
  • If you like, join on IRC (see below)

Communication

Within the team:

  • Mailing list setup is not ready yet. The logistics mailing list is an important channel for communication. The mailing list is the place where we report on progress, document decisions that are made (it has an archive!) and announce meetings and other upcoming stuff.
  • IRC #sha2017-logistics @ Freenode. IRC can be used for discussing ideas when not meeting IRL, preventing too much chatter on the mailing list. (You likely might want to join #sha2017 also)
  • IRL Team meetings, which will be held regularly.

To/from other teams:

  • People from other teams are free to join our mailing list and read along. They might do or don't do this, or start / stop doing it based on the amount and type of messages on the list.
  • Same holds the other way... You might want to either join a list of another team that you are working with closely, or just subscribe and set yourself to nomail and then be able to browse the archives of that list to get info. Also join the main orga list at <insert here>.
  • Mailinglist messages to a central orga list, reporting on progress regularly (sending summary of what's happening, so that members of other teams do not have to join our list and sift through all messages to find out).
  • IRL during SHA meetings
  • Informal contacts, anything else.