Differences between revisions 1 and 15 (spanning 14 versions)
Revision 1 as of 2006-05-28 13:32:49
Size: 1752
Editor: zobel
Comment:
Revision 15 as of 2017-03-29 21:57:49
Size: 3723
Editor: TheAnarcat
Comment: add link to DPL reimbursment process and the sprints list
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= 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:
= Planning 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:
Line 4: Line 4:
== 1. Number of Developers ==
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.
<<TableOfContents>>
Line 8: Line 6:
== 2. Accommodation ==
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.
== 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 regarding the objective of a BSP), as they tend to discuss unrelated issues.
Line 11: Line 9:
== 3. Food ==
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.
== 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!
Line 14: Line 13:
== 4. Infrastructure ==
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.
== 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.
Line 17: Line 16:
== 5. Date ==
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?
== Sponsorships ==

One of the ways to finance BSPs is to ask the [[DPL]], see the [[Teams/DPL/Reimbursement]] process for more information.

Do coordinate with the debian-sprints mailing list.

== Infrastructure ==
You will need a reliable network infrastructure. Both a fast local network and a good connection to the internet are absolutely 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.

== 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. :-)

== Attendees ==
You will want to have experienced Debian folks present so that they can help people who are not so experienced. The main places you can find Debian people from your city are the keysigning [[Keysigning/Offers|offers]] and [[Keysigning/Need|need]] pages. The [[ReleaseParty|release party]], [[DebianDay|Debian Day]] and [[LocalGroups|local groups]] pages might also be of use in finding Debian folks in your city. If all of the above fail you can contact the Debian developer community to ask them to [[http://db.debian.org/|search the developer database]].

== Publicity ==
It is important to publicise BSPs so that you get people coming to your BSP. Some ideas for publicity include: get your BSP added to the [[http://www.debian.org/events/|Debian events page]], send a mail to the [[http://lists.debian.org/misc.html|appropriate debian-events-* and debian-dug-* lists]] and [[http://lists.debian.org/debian-devel/|debian-devel]] or [[http://lists.debian.org/debian-devel-announce|debian-devel-announce]], blog about your event on [[PlanetDebian|Planet Debian]], get your event in the [[ProjectNews|Debian Project News]], [[Teams/Publicity/Identica|post the BSP to identi.ca/debian]], post about the BSP to the mailing list of your local LUG/OSUG/FSUG and add your event to the [[http://lwn.net/Calendar/|LWN Calendar]].

After the event it is a good idea to post a report about what you achieved and get that included in some of the above.

== Other Informations ==
Have a look also at [[BSPMarathon]].

----
## This page is referenced from http://www.debian.org/News/2012/20120215
CategoryPermalink

Planning 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:

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 regarding the objective of a BSP), as they tend to discuss unrelated issues.

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!

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.

Sponsorships

One of the ways to finance BSPs is to ask the DPL, see the Teams/DPL/Reimbursement process for more information.

Do coordinate with the debian-sprints mailing list.

Infrastructure

You will need a reliable network infrastructure. Both a fast local network and a good connection to the internet are absolutely 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.

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. :-)

Attendees

You will want to have experienced Debian folks present so that they can help people who are not so experienced. The main places you can find Debian people from your city are the keysigning offers and need pages. The release party, Debian Day and local groups pages might also be of use in finding Debian folks in your city. If all of the above fail you can contact the Debian developer community to ask them to search the developer database.

Publicity

It is important to publicise BSPs so that you get people coming to your BSP. Some ideas for publicity include: get your BSP added to the Debian events page, send a mail to the appropriate debian-events-* and debian-dug-* lists and debian-devel or debian-devel-announce, blog about your event on Planet Debian, get your event in the Debian Project News, post the BSP to identi.ca/debian, post about the BSP to the mailing list of your local LUG/OSUG/FSUG and add your event to the LWN Calendar.

After the event it is a good idea to post a report about what you achieved and get that included in some of the above.

Other Informations

Have a look also at BSPMarathon.


CategoryPermalink