This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.
Last updated: 2014-05-05
A hackfest first. We'd be working on Inkscape bugs, features and delving into coding, packaging, website issues. Anything that can benefit from developers and users being physically available in the same space.
We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015). Fill in the dates of that event here when available.
A sketch of what might happen on hackfest days, 2 or 3 days of things should be planned.
a) Social meeting b) Pre-lunch presentations c) Lunch d) Pure hacking e) Dinner f) Pure drunk hacking
Technically the best location is the MIT campus in Cambridge, Massachusetts. The SIPB computing student group has been contacted in order to get something organised. Other contacts are also available should SIBP not work out.
More details as they arrive.
The Boston/Cambridge area hosts many meetings, hackfests and Free Software events. It is both the home of the Free Software Foundation in downtown Boston, many software related companies involved in Free Software such as Red Hat, Canonical and Google as well as hosting very many large Universities with competent computer science departments.
The area is packed full of sizzling restaurants and other events for social activity.
The venue can be commuted to via the backbone of the MBTA transport network, the Red Line. Any hotel /outside/ of Cambridge and Boston centers but on this Red Line should be both affordable as well as accessible. Events should consider themselves based on this line too.
House sharing should also be possible. Martin Owens is a local who is inviting a developer to stay for the event. others may be available too.
Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.
Put things here that you think could use a bit of discussion/thought.
Tasks to tackle
What can we hack on? To me (Johan) what seems nice are tasks that become more managable/fun/... and with higher chance of completion when done in a group. Before determining specific tasks, what kind of tasks should we try to tackle?
- a bug that requires knowledge of large part of codebase
- simple repetitive refactoring or code clean up that can be parallelized and may not be so much fun alone. Examples:
- make sure every file contains standardized and correct copyright notice
- eradicate all use of gboolean/TRUE/FALSE
- move towards C++11 by =delete on copy-constructors instead of making them private+undefined)
- a more complicated refactoring that requires discussion
- a feature that can be split into parallelizable tasks possibly with different skills required, for example:
- combination of UI, backline math stuff, usability/behavior stuff
- future work discussions, for example:
For the drunk hacking sessions:
- fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.