Differences between revisions 1 and 2
Revision 1 as of 2006-05-28 13:32:49
Size: 1752
Editor: zobel
Comment:
Revision 2 as of 2006-05-28 13:54:13
Size: 1868
Editor: ?MarcBrockschmidt
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
If you plan to host a real life BSP, there are several things you should consider, before announcing such an event: If you plan to host a real life BSP, there are several things you should consider before announcing such an event:
Line 5: Line 5:
This is the most important information you need to be aware of, because all other points from this list depend on this number. For the fun part, there should be more than one
( :) ) person attending, but too much persons attending may make this event quite unproductive, as there will be a lot of real life chatting.
This is the most important aspect when planning a BSP. To make it actually worthwhile, you need more than one person attending. On the other hand, too many developers are often quite unproductive (at least for the target of the BSP), as they tend to discuss unrelated issues.
Line 9: Line 8:
Depending on how much persons plan to attend, you have to organize both, place to work and place to sleep. In most cases, real life BSPs will last at least 2 days (or evenings). Fellow DDs or contributors usualy will bring sleeping bags or air mattress with some, so you just need a place where they can trash. For working place, you should have 2-3 rooms with enough tables and infrastructure (see below). Having a place to work and a place to talk might be helpful in some cases. After getting a rough idea how many people are planning to attend, two places need to chosen. One central place for the actual hacking, with a reasonable network connection and if possible a local server providing a Debian ftp-mirror.
You also need to find one or more locations where the attending non-locals can sleep - they'll always bring sleeping bags and air mattresses, so only a bit of free space is needed. BSPs are not about comfortable sleeping!
Line 12: Line 12:
You won't work the whole time. Most fellow also will need something to eat or drink from time to time. Make clear how this will be handled (money). Noone excepts you to pay. But if you find a sponsor (company) who is willing to pay for one lunch or dinner everyone will surely appreciate that. Remember that hackers don't run on IP connectivity and pure air - they need something to eat and drink. This means that you should plan how this can be managed without too much improvisation. Noone expects you to pay, but perhaps a local sponsor can be found for the event. Please note that some people are vegetarians or vegans.
Line 15: Line 15:
Reliable network infrastructure is a must for such events. Nothing is more boring than not being able to work because you are offline. Also keep in mind that power might be an issue if you have several dozens PCs running. You will need a reliable network infrastructure. Both a fast local network and a good connection to the internet are absolutly needed - most of the needed information for a BSP is stored in the BTS or PTS! A local mirror can speed up things a lot (and reduce the load on your internet connection).
Depending on the number of participants, power might become an issue.
Line 18: Line 19:
Choose a date carefully. Do you think it will be productive meeting, if the final games of soccer championship is at exactly that evening you are hosting the BSP? Choose the date carefully! Even hackers have non-computer interests, so the final game of the soccer world championship is probably not the best time for a BSP :-)

Planing a real life BSP

If you plan to host a real life BSP, there are several things you should consider before announcing such an event:

1. Number of Developers

This is the most important aspect when planning a BSP. To make it actually worthwhile, you need more than one person attending. On the other hand, too many developers are often quite unproductive (at least for the target of the BSP), as they tend to discuss unrelated issues.

2. Accommodation

After getting a rough idea how many people are planning to attend, two places need to chosen. One central place for the actual hacking, with a reasonable network connection and if possible a local server providing a Debian ftp-mirror. You also need to find one or more locations where the attending non-locals can sleep - they'll always bring sleeping bags and air mattresses, so only a bit of free space is needed. BSPs are not about comfortable sleeping!

3. Food

Remember that hackers don't run on IP connectivity and pure air - they need something to eat and drink. This means that you should plan how this can be managed without too much improvisation. Noone expects you to pay, but perhaps a local sponsor can be found for the event. Please note that some people are vegetarians or vegans.

4. Infrastructure

You will need a reliable network infrastructure. Both a fast local network and a good connection to the internet are absolutly needed - most of the needed information for a BSP is stored in the BTS or PTS! A local mirror can speed up things a lot (and reduce the load on your internet connection). Depending on the number of participants, power might become an issue.

5. Date

Choose the date carefully! Even hackers have non-computer interests, so the final game of the soccer world championship is probably not the best time for a BSP :-)