Events/2014/US Summer Hackfest

The US Community had a Summer Hackfest, which took place in Boston 26th / 27th of July.

Participants

 * T-shirt design

Venue
Xamarin's Boston office has kindly offered to host our event! Here's their street address:

Xamarin, Inc. 2 Park Plaza Boston, MA

Xamarin is on the 7th floor.

Directions to the Venue
The venue appears to be just off of Boston Common, SE of the intersection of Charles St. and Boylston St.
 * The door is between P.F.Chang and Boloco restaurants.

On a map

 * Google Maps
 * Open Street Map - The corner building to the left of the sign for Troquet restaurant

From the T

 * The venue was roughly equidistant from the Arlington and Boylston stations

Venue Contact
Who's were our contacts on the ground (i.e. who can unlock doors for us, etc..?)


 * Alessandra Araujo
 * Jayme Singleton

(Ask Robinson/Mmeeks for relevant contact info)

Travel Bursaries
The Document Foundation may be able to refund tickets to and from the US Summer Hackfest, after prior approval by the organizers, under the following conditions:
 * Transportation and accommodation in a shared hotel room with single beds as available on location (2 hackers sharing one room)
 * Volunteer-first - people affiliated with a company involved in LibreOffice work will come last
 * First-come-first-served - participants will get reimbursed in order of their sign-up on the wiki attendance list, until budget runs out.
 * Ask the organizers as soon as possible (ideally right before booking) if budget is still available. Be aware of the fact that tax law requires us to collect original receipts, so please keep them (or hand them in at the Hackfest)

Please be economic and pick cheap travel.

For those who attended: If you'd like to request a travel reimbursement, please follow the HowTo at TDF/Policies/Refunding for the SPI refunding, and mail [mailto:treasurer@documentfoundation.org treasurer@documentfoundation.org] with your documents.

The deadline for the initial batch of travel bursaries is July 10th, 2014 23:59UTC. After that deadline there might still be funding served, if available, but it won't take precedence over existing promises.

Schedule

 * Friday
 * Early arrivals met for dinner/drinks


 * Saturday
 * 9am - Breakfast  (Bagels, OJ, Coffee, ..)
 * 9:30am - Event starts
 * 12ish - Lunch (Boloco is in the same building (?) -- might be a good option)
 * 6ish - Dinner (Pizza?)
 * Later - Go to bed  (left around midnight; bed by 3 or so)


 * Sunday
 * 10am - Breakfast  (Bagels, OJ, Coffee, ..)
 * 10:30am - Event starts
 * 12ish - Lunch (Sandwiches? pizza?)
 * 3pm - Wrap-up for those who have to fly home for work on Monday
 * (We may continue along until 5ish, depending upon how many people are left)

Activities
TBA -- the hackfest will include some combination of

Programming/Coding/Hacking:
 * Hacking on LibreOffice Code
 * Hacking on QA and other support code including the BSA, Bugzilla, MediaWiki (events?), etc..

QA:
 * Introduction to triaging
 * Learning about the Bibisect tool

Outreach/Marketing:
 * Introduction to the activities of the Marketing Team
 * How to become more active w/LibreOffice outreach
 * Steps towards running a successful LibreOffice event locally

Design:
 * We'd love to grow our Design Team and involve artists
 * We need: People familiar with Inkscape, GIMP, and/or non-free alternatives
 * TO PREPARE: Easy Hacks/projects for newcomers
 * Sticker design/redesign (DLP, I heart LibreOffice, others?? -- maybe a hackfest sticker?)
 * Hackfest Button (general idea: Give to someone during a conference, encourage them to attend hackfest starting the next day)
 * Re-work DFD 'open formats' pamphlet for TDF/LibreOffice
 * Re-work/update LibreOffice stock pamphlets ("Community" and "Intro to LO")

Introduction to other teams:
 * Documentation
 * Localization
 * Design

Achievements

 * Various calc performance related cleanups (Jeff Stedfast)
 * Editeng search / replace field expansion bug fix + unit tests (Michael Meeks)
 * Testing the new AWS pre-built VM's - awesome (thanks to Christian Lohmaier)
 * Introduced community members to QA bug triage process (Algot, Immanuel, etc.)