| 
  
   Size: 572 
  
  Comment:  
 | 
    ← Revision 11 as of 2020-02-19 11:34:18  ⇥ 
  Size: 4139 
  
  Comment: add numbers to facilitate verification during battlemesh event 
 | 
| Deletions are marked like this. | Additions are marked like this. | 
| Line 1: | Line 1: | 
| status: "" PRE-ALPHA "" This is a draft. We expect to improve it during the v5. Your contrib will be very welcome. | status: '''PRE-ALPHA''' This is a draft. We expect to improve it during the v5. Your contrib will be very welcome. | 
| Line 5: | Line 5: | 
| * This doc is intended to be a guideline for those who want to contribute to make this event happen again and make it better | This doc is intended to be a guideline for those who want to contribute to make this event happen again and make it better | 
| Line 9: | Line 9: | 
| == Local task force == | == Key == | 
| Line 11: | Line 11: | 
| Vide recording Live streaming Accommodation  | 
 * '''Task Name''' * '''Local Tasks''' - '''Must''' be done by the local team hosting the event. * '''Remote/Online''' Tasks - ''May'' be done by a remote person. * '''Priority''' - || *** || very important, and backup needed, fatal if not available || || ** || important || || * || optional ||  | 
| Line 15: | Line 19: | 
| == International == | == Task List == || '''Task Name''' || '''Local''' || '''Remote''' || '''Priority''' || '''Description''' || '''Responsible Person''' || ||1. Accomodation || L || - || *** || - || - || ||2. Transport (from/to airport)|| L || - || ** || - || - || ||3. Transport (from/to venue)|| L || - || ** || - || - || ||4. Venue Location|| L || - || *** || - || - || ||5. Venue Equipment (Speaker, Projector)|| - || R || *** || - || - || ||6. Internet Connection|| L || - || *** || - || - || ||7. Hardware for Testing|| - || R || ** || - || - || ||8. Food Supply|| L || - || * || - || - || ||9. Financial Handling (Bank Account)|| L || - || *** || - || - || ||9.1 Invoice Handling|| L || - || ** || - || - || ||9.2 Attendence Certification|| L || - || ** || - || - || ||10. Test Manager|| - || R || ** || - || - || ||11. Firmware Preparation|| - || R || ** || - || - || ||12. Press Communication|| L || R || * || - || - || ||13. Logo|| L || R || ** || - || - || ||14. Merchandise (T-Shirts, Flags)|| - || R || * || - || - || ||15. Agenda|| - || R || ** || - || - || ||16. Social Events|| L || - || * || - || - || ||17. Mentor Team -> Annnouncement, Mentoring Organizers|| L || R || *** || - || - || ||18. Recon: visit the place, find Date|| L || R || * || - || - || ||19. Webpage|| - || R || *** || - || - || ||20. Attendence List/SignUps (DEADLINE!!)|| L || R || *** || - || - || ||21. Recording and Streaming|| - || R || * || - || - || ||22. Local Community, Sponsorship|| L || - || * || - || - ||  | 
| Line 18: | Line 48: | 
| = Minimum Requirements for Local Organizers = * 3 core people + 3 helping assistance * core people should expect to be completely devoted to the organization two weeks before the event (full time) * Attending a BattleMesh and Talk about your Location = Mentor/Recon Team = * consists of at least last years organizers * Mentors don't neccesarily have to do anything themselves, but find suitable persons/delegate and be contact persons * Mentoring the other organizers who pick up tasks, monitor their success * support and advertise the event * keep the overview * find mentors for the next event (from local event) == Process == * start during the previous event: - announce at opening event, asking for new locations - talk to representatives of locations * On Recon: - explain what we want/need to the local community - find suitable local persons - get to know each other - get organization going, announce the event, find/propose exact dates * Prep-Meeting (usually in December next to CCC in Berlin): * 80% should be settled * Account Deadlines * Prices/Location finalized * Decision making * pre-payment, if required * Final Announcement: Deadline, Price, Wire information etc = Criteria for Locations = * organization should fit to idea of the battlemesh (community event) * Local organizers who meet the minimum requirement * costs for transport and accomodations (airplane tickets) * Nice place to be :) * mentor team will decide the location = Criteria for Venue Location = * avoid places with time limitations/closing hours * broadband Internet connection * availability of safe locations with sockets for node deployment * coffee and food availability  | 
|
| Line 20: | Line 96: | 
| This doc was created as part of the tasks defined during the plenary meeting that took place 2012/03/28 in Athens during the v5. Everybody is welcome to improve it.  | 
This doc was created as part of the tasks defined during the plenary meeting that took place 2012/03/28 in Athens during the v5. Everybody is welcome to improve it. = SubPages = <<Navigation(children)>>  | 
status: PRE-ALPHA This is a draft. We expect to improve it during the v5. Your contrib will be very welcome.
Objectives
- This doc is intended to be a guideline for those who want to contribute to make this event happen again and make it better
 
Tasks
Key
Task Name
Local Tasks - Must be done by the local team hosting the event.
Remote/Online Tasks - May be done by a remote person.
Priority -
***  | 
  very important, and backup needed, fatal if not available  | 
**  | 
  important  | 
*  | 
  optional  | 
Task List
Task Name  | 
  Local  | 
  Remote  | 
  Priority  | 
  Description  | 
  Responsible Person  | 
1. Accomodation  | 
  L  | 
  -  | 
  ***  | 
  -  | 
  -  | 
2. Transport (from/to airport)  | 
  L  | 
  -  | 
  **  | 
  -  | 
  -  | 
3. Transport (from/to venue)  | 
  L  | 
  -  | 
  **  | 
  -  | 
  -  | 
4. Venue Location  | 
  L  | 
  -  | 
  ***  | 
  -  | 
  -  | 
5. Venue Equipment (Speaker, Projector)  | 
  -  | 
  R  | 
  ***  | 
  -  | 
  -  | 
6. Internet Connection  | 
  L  | 
  -  | 
  ***  | 
  -  | 
  -  | 
7. Hardware for Testing  | 
  -  | 
  R  | 
  **  | 
  -  | 
  -  | 
8. Food Supply  | 
  L  | 
  -  | 
  *  | 
  -  | 
  -  | 
9. Financial Handling (Bank Account)  | 
  L  | 
  -  | 
  ***  | 
  -  | 
  -  | 
9.1 Invoice Handling  | 
  L  | 
  -  | 
  **  | 
  -  | 
  -  | 
9.2 Attendence Certification  | 
  L  | 
  -  | 
  **  | 
  -  | 
  -  | 
10. Test Manager  | 
  -  | 
  R  | 
  **  | 
  -  | 
  -  | 
11. Firmware Preparation  | 
  -  | 
  R  | 
  **  | 
  -  | 
  -  | 
12. Press Communication  | 
  L  | 
  R  | 
  *  | 
  -  | 
  -  | 
13. Logo  | 
  L  | 
  R  | 
  **  | 
  -  | 
  -  | 
14. Merchandise (T-Shirts, Flags)  | 
  -  | 
  R  | 
  *  | 
  -  | 
  -  | 
15. Agenda  | 
  -  | 
  R  | 
  **  | 
  -  | 
  -  | 
16. Social Events  | 
  L  | 
  -  | 
  *  | 
  -  | 
  -  | 
17. Mentor Team -> Annnouncement, Mentoring Organizers  | 
  L  | 
  R  | 
  ***  | 
  -  | 
  -  | 
18. Recon: visit the place, find Date  | 
  L  | 
  R  | 
  *  | 
  -  | 
  -  | 
19. Webpage  | 
  -  | 
  R  | 
  ***  | 
  -  | 
  -  | 
20. Attendence List/SignUps (DEADLINE!!)  | 
  L  | 
  R  | 
  ***  | 
  -  | 
  -  | 
21. Recording and Streaming  | 
  -  | 
  R  | 
  *  | 
  -  | 
  -  | 
22. Local Community, Sponsorship  | 
  L  | 
  -  | 
  *  | 
  -  | 
  -  | 
Minimum Requirements for Local Organizers
- 3 core people + 3 helping assistance
 - core people should expect to be completely devoted to the organization two weeks before the event (full time)
 Attending a BattleMesh and Talk about your Location
Mentor/Recon Team
- consists of at least last years organizers
 - Mentors don't neccesarily have to do anything themselves, but find suitable persons/delegate and be contact persons
 - Mentoring the other organizers who pick up tasks, monitor their success
 - support and advertise the event
 - keep the overview
 - find mentors for the next event (from local event)
 
Process
- start during the previous event: 
- - announce at opening event, asking for new locations - talk to representatives of locations
 
 - On Recon: 
- - explain what we want/need to the local community - find suitable local persons - get to know each other - get organization going, announce the event, find/propose exact dates
 
 - Prep-Meeting (usually in December next to CCC in Berlin): 
- 80% should be settled
 - Account Deadlines
 - Prices/Location finalized
 - Decision making
 - pre-payment, if required
 
 - Final Announcement: Deadline, Price, Wire information etc
 
Criteria for Locations
- organization should fit to idea of the battlemesh (community event)
 - Local organizers who meet the minimum requirement
 - costs for transport and accomodations (airplane tickets)
 Nice place to be
 - mentor team will decide the location
 
Criteria for Venue Location
- avoid places with time limitations/closing hours
 - broadband Internet connection
 - availability of safe locations with sockets for node deployment
 - coffee and food availability
 
History of this doc
This doc was created as part of the tasks defined during the plenary meeting that took place 2012/03/28 in Athens during the v5. Everybody is welcome to improve it.
SubPages
| /Tests | 
