Inkscape Wiki - User contributions [en]

Jenkins server setup

2015-09-11T20:26:25Z

Johanengelen: /* Several packages for our Jenkins jobs */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-x.x (choose whatever version is most recent)
You may need to create symlinks if "clang" and "scan-build" do not work on the cmdline:
sudo ln -s /usr/bin/clang-x.x /usr/bin/clang
sudo ln -s /usr/bin/clang++-x.x /usr/bin/clang++
sudo ln -s /usr/bin/scan-build-x.x /usr/bin/scan-build

For unit tests of the python extensions:
apt-get install python-lxml python-numpy

For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin
* thinBackup
* Role Strategy Plugin

=====Role-based security setup=====

* Manage Jenkins -> Configure Global Security -> Set security management to Role-based strategy.
* Manage Jenkins -> Manage and Assign roles
** Manage roles: set up the roles!
** Assign roles : assign roles to the users (also assign Anonymous to a (of course restricted) role)

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Jenkins server setup

2015-09-11T20:16:37Z

Johanengelen: /* Several packages for our Jenkins jobs */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-x.x (choose whatever version is most recent)

For unit tests of the python extensions:
apt-get install python-lxml python-numpy

For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin
* thinBackup
* Role Strategy Plugin

=====Role-based security setup=====

* Manage Jenkins -> Configure Global Security -> Set security management to Role-based strategy.
* Manage Jenkins -> Manage and Assign roles
** Manage roles: set up the roles!
** Assign roles : assign roles to the users (also assign Anonymous to a (of course restricted) role)

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Hackfest2015 Topics

2015-04-19T19:51:00Z

Johanengelen: remove my name from 'testing' header

Please add topics you would like to discuss or work you would like to see done at the hackfest.

Other pages: [[Hackfest2015|Hackfest 2015]], [[Hackfest2015 Attendees]].

== Discussions ==

=== SVG 2 strategy (Tav) ===

* Overview/rundown of relevant new SVG2 features. What are they, what will need done to implement them?
* How do we handle fallbacks?
* When do we add things to the GUI? (When three browsers offers support?)

=== Program flow (Tav) ===

* Diagram how Inkscape behaves/should behave on:
** Opening a file.
** Changing a style item (e.g. 'fill').
** Moving a node.
** Deleting an item.
*** Comment: Deleting an item causes Inkscape to create a new SVG document with containing the deleted item to allow pasting.

==== Motivation ====

Add a few random print statements in Inkscape and you'll see that Inkscape visits certain functions more often than one would think it should. Having well defined diagrams will allow developers to clean up existing code and to better understand what needs to be done to add new features. I've noticed that we suffer from "cargo cult programming" where people add functions without fully understanding if they are truly needed.

* Ideas
** Better, easily referenced API documentation
** Code reviews
** `linux perf` can be used to identify performance critical functions

==== Comments from Krzysztof ====

This is a pretty big problem right now. The flow looks like this:

Something is updated in the SP tree
# updateRepr() is called
# new XML is written
# XML modification listeners fire
# SP tree is re-read from the XML
# A recursive call to update() is made
# Each of those update calls updates the rendering tree in turn.

As a result, changing the document height triggers a full update of
the rendering tree, even though almost nothing changes.

The current approach makes it impossible to introduce errors that
cause the XML and the SP tree to go out of sync, at the cost of
performance. We could discuss what to do about this.

=== Refactoring ===

Can we decide on a roadmap to work with new APIs and compilers? How do we minimize breakages for downstream users? Can we balance risk with reward? How does each migration benefit the developers, package maintainers and end users?

Some possible changes to discuss:

* Moving to C++11 (AV)
** code cleanup/maintainability
** improved data structures/templating
* Adding a hard Cairo 1.14 dependency (AV)
** Fix bitmap downscaling issue
* Gtk+ 3 migration (AV)
** Get rid of lots of conditional code
** Get rid of embedded GDK library fork
** Some "cleaner" API available
** How do we handle canvas flickering/rendering issues?
* C++ification (AV)
** Migrate widgets/dialogs to Gtkmm
** Get rid of popt
** Get rid of GObject usage
* Removing 3rd party Library dependencies from version control (AV)
* Change how we're utilizing 3rd party libraries (Josh)
** Stop using Poppler internals, use the proper API via poppler-glib (https://bugs.launchpad.net/inkscape/+bug/239544)
** Use newer Pango-Cairo text/glyph APIs (https://bugs.launchpad.net/inkscape/+bug/420822)
* Unnecessary profileration of namespaces (Krzysztof)Things like Inkscape::UI::View::View are excessive. I cannot imagine a scenario where we would need more than 2 levels of namespaces. Everything UI-related should sit in Inkscape::UI, without separate namespaces for widgets and dialogs which only serve to increase typing.
* Directory structure. Let's make a directory for the SP tree, and namespace it as Inkscape::SVG (or maybe Inkscape::DOM). (Krzysztof)
* Identify clever geometry code which can be cleaned up and moved to 2Geom. (Krzysztof)

=== Testing ===

* Discuss Jenkins/unittesting/rendertesting.

=== Website (DoctorMO) ===

* How do people feel about it's current functions
* How should we move it forwards?
* Plans for mailing list migrations.
* Getting developers set up with local copies for hacking.

=== Roadmap Planning (Bryce) ===

Prioritize feature and infrastructure development work for next several releases.

=== Fundraisers (Bryce) ===

Brainstorm future fundraising ideas.

=== Community Development (Bryce) ===

* Championing FOSS ideals generally
* Expanding userbase
* Building up a strong evangelist user community
* Recruiting newbie developers, encouraging involvement, and mentoring
* Re-connecting with old timers
* Promoting existing developers into leadership roles

=== Design new plugin/extension system ===

== Hacking ==

=== Invert coordinate system (Tav) ===

If there was ever a good moment to do the coordinate system flip, this is it. (should coordinates be configurable in relation to the canvas?)

==== Comment from Krzysztof ====

We need to decide whether we want to keep the 3D Box at all costs, or is the coordinate system inversion a more important goal than having 3D Box. Being unable to fix 3D Box was the main reason I didn't commit this change when I initially made it. FWIW, I think the 3D Box tool is nearly unusable and needs to be rewritten from scratch. It also pollutes the entire codebase with special handling for its perspective elements, indicating faulty
design.

=== Harfbuzz: Better CSS support and User Fonts (WOFF) ===

There will be a Harfbuzz documenting session taking place at the same time as the Inkscape Hackfest. Maybe we can get some expertise on how to improve our font handling. CSS now has much more sophisticated ways of selecting alternative glyphs that Harfbuzz may support. Also, it would be nice to be able to use user fonts, in particular WOFF fonts, into Inkscape. At the moment we rely on Pango for all our font related stuff and Pango's support for new CSS stuff and for user fonts is negligible if completely non-existent.

=== Make Systems ===

==== CMake (Bryce) ====

A while back someone made a valiant attempt to get Inkscape built with cmake, but if this ever worked it's bitrotted to where it doesn't work presently. Hack it back into working shape on Linux, Mac, and Windows. Write up evaluation.

==== WAF (Krzysztof) ====

I would rather use Waf. CMake has its own, sloppy scripting language; writing anything moderately complex in it is an exercise in frustration. By contrast, Waf scripts can leverage all the mighty power of Python.

Killer feature: since Waf stores a database of what was compiled, it support wildcards correctly. As in, when the set of files matched by a wildcard in the build script changes, it will automatically recompiles the correct files, without the need to modify build scripts. CMake cannot do this, because it just generates makefiles, and Make cannot support wildcards in this manner because it does not have any persistence beyond what is stored in the file system.

Other things we could easily do with Waf are:
* render test integration
* automatically updating the AUTHORS file and the authors tab in the About dialog from Bazaar logs
* creating a completely standalone executable (using e.g. GResource to store data files in the executable itself)

=== Hardware Acceleration Experimentation (Bryce) ===

Create experimental branch using Cairo-GLX as the rendering backend. Evaluate rendering performance. Brainstorm follow up work.

Jenkins server setup

2015-02-01T15:36:26Z

Johanengelen: /* Role-based security setup */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5

For unit tests of the python extensions:
apt-get install python-lxml python-numpy

For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin
* thinBackup
* Role Strategy Plugin

=====Role-based security setup=====

* Manage Jenkins -> Configure Global Security -> Set security management to Role-based strategy.
* Manage Jenkins -> Manage and Assign roles
** Manage roles: set up the roles!
** Assign roles : assign roles to the users (also assign Anonymous to a (of course restricted) role)

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Jenkins server setup

2015-02-01T15:35:25Z

Johanengelen: /* Role-based security setup */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5

For unit tests of the python extensions:
apt-get install python-lxml python-numpy

For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin
* thinBackup
* Role Strategy Plugin

=====Role-based security setup=====

* Manage Jenkins -> Configure Global Security -> Set security management to Role-based strategy.
* Manage Jenkins -> Manage and Assign roles
** Manage roles: set up the roles!
** Assign roles : assign roles to the users

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Jenkins server setup

2015-02-01T15:30:18Z

Johanengelen: security setup, part 1

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5

For unit tests of the python extensions:
apt-get install python-lxml python-numpy

For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin
* thinBackup
* Role Strategy Plugin

=====Role-based security setup=====

* Manage Jenkins -> Configure Global Security -> Set security management to Role-based strategy.
* Manage Jenkins -> Manage and Assign roles
**

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Jenkins server setup

2015-02-01T15:18:47Z

Johanengelen: /* Installed Jenkins plugins */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5

For unit tests of the python extensions:
apt-get install python-lxml python-numpy

For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin
* thinBackup
* Role Strategy Plugin

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Jenkins server setup

2015-01-25T00:32:44Z

Johanengelen: /* Several packages for our Jenkins jobs */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5

For unit tests of the python extensions:
apt-get install python-lxml python-numpy

For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin
* thinBackup

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Jenkins server setup

2015-01-25T00:31:36Z

Johanengelen: /* Several packages for our Jenkins jobs */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5

For unit tests:
apt-get install python-lxml

For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin
* thinBackup

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Jenkins server setup

2015-01-24T12:43:33Z

Johanengelen: /* Installed Jenkins plugins */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5
For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin
* thinBackup

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Jenkins server setup

2015-01-22T00:13:17Z

Johanengelen: /* TO DO */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5
For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape
* get email working: should send mails to maillist when something breaks

Jenkins server setup

2015-01-22T00:12:41Z

Johanengelen: /* TO DO */

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5
For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to report the unit test results for inkscape

Inkscape

2015-01-22T00:10:23Z

Johanengelen: /* Continuous Integration (Automated testing) */

This is a freeform area for Inkscape development and discussion.
Curious about [[WikiSyntax]]?

Other languages: [[Inkscape en español|Wiki en español]], [[L'Inkscape en Català|Wiki en Català]], [[Inkscape em Português|Wiki em Português]], [[Startseite|Wiki auf deutsch]]...

{| cellspacing="11" style="width:100%;"
|-style="vertical-align:top;"
| style="width:33%;background-color: #E6E6E6; padding:.5em;"|
=== Project Info ===
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[Features of Inkscape|Features]]
* [[FAQ]] - Frequently Asked Questions
* [[Supported operating systems]]
* [[Tools]] - Supporting Tools and Applications
* [[Galleries]]
* [[Inkscape coverage|Coverage]] - Awards, articles, presentations, books about Inkscape
* [[Inkscape popularity|Popularity]]
* [[Contact information]] - the developers' e-mails and SVN nicknames
* [[InkscapeInvariants|Inkscape's Mission]]
* [[CommunicationChannels|Communication Channels]]: how to reach us
* [[AnnouncementToSodipodi|Announcement To Sodipodi]]: this started it all
* [[Branding]]
* [[ContactInfo|Contact Information]]: who's behind Inkscape
* [[Travel Reimbursement Policy]]

|style="width:33%;;background-color: white; padding:.5em;"|

=== User Documentation ===
* [[Installing Inkscape|Installation]]
* [[International and Local Communities]]
* [[Inkscape glossary]]
* [[User manual information]] - where to find the free Inkscape manual and how to contribute to it
* [http://inkscape.org/en/learn/tutorials/ Tutorials]
* [[Inkscape SVG vs. plain SVG]]
* [[Output format requirements]] - what's needed to save in some formats
* [[Effect requirements]] - what's needed to use some effects
* [[Effect reference]] - what each effect does
* [[Connector tool tutorial]]
* [[Installing fonts]]
* [[Emergency save]] - recovery in case Inkscape crashed
* [[Release notes]]
** for version [[Release notes/0.91|0.91]] (active development)
** '''for version [[Release notes/0.48.5|0.48.5]] (current release)'''
** older versions: [[Release notes/0.48.4|0.48.4]] [[Release notes/0.48.3|0.48.3]], [[Release notes/0.48.2|0.48.2]], [[Release notes/0.48.1|0.48.1]], [[Release notes/0.48|0.48]], [[Release notes/0.47|0.47]]
* [[Announcing Releases]]
* [[Tricks and tips]] - miscellaneous advice, may be slightly outdated

|style="width:33%;background-color: #E6E6E6; padding:.5em;"|

=== Help Inkscape Without Coding ===
* [[Bug management]]
* [[Testing]]
* [[Translation information]]
* [[Editing Inkscape's website|Website]]
* [[Inkscape Classes]]
* [[Conferences]]
* [[Marketing Scratchpad]]

* [[HelpWanted]]
* [[BugTriageProjects]]
* [[CreatingDists]]: how to build packages
* [[StableBranchUpdates]]
* [[UpdatingTrackerItems]]
* [[TutorialsAndHelp]]
* [[How_To_Start_A_Page]] how to use the wiki
* [[CreatingScreencasts]]
* [[AboutScreenContest]]
|}

{| cellspacing="0" style="width: 100%; background-color: white; border-width:1px; border-style:solid; border-color:#62C012; align:left; padding:11px 0em 0em 11px;"
|- style="vertical-align:top;"
| colspan="2"|

=== Developer Documentation ===
|- style="vertical-align:top;"
| style="width:50%;|
==== First Steps ====
* [[Working with Bazaar]] - How to obtain the source code. A quick start on how to use our version control system
* [[Compiling Inkscape|Compilation]]
* [[Using Eclipse]]
* [[Developer manual]] - various important information, be sure to read this before coding
* [[Debugging Inkscape|Debugging]] - random tips to help debug problems
* [[Project organization]] - procedures, hierarchy, developer roles and the likes
* [[Janitorial tasks]] - small tasks that need doing
* [[Doxygen documentation]]
* [[Working with SVN]] - besides the code in Bazaar, we still have some things in SVN.

==== Developer tutorials ====
* [[Architectural overview]] - a high-level look at Inkscape
* [[Preferences subsystem]] - creating and using preference values
* XML subsystem (WIP) - how to manipulate the XML representation of a document
* Display subsystem (WIP) - how to make things appear on the canvas
* Tools subsystem (WIP) - how to create a new tool
* [[Creating a new SPObject]]
* Extensions
** [[Extension subsystem]] - an overview of the functionality provided by extensions and the possible implementations
** [[Script extensions]]
** [[Python modules for extensions]] - some helpful routines for use in Python script extensions
* [[Creating Live Path Effects]]
* [[Boost shared pointers]]
* [[Using libsigc++ signals]]
* [[Windows development on Linux]]

==== Miscellaneous ====
* [[INX extension descriptor format]]
* [[Inkscape-specific XML attributes]] - documentation of attributes from Inkscape's XML namespace

* [[Extension repository]]: an Internet central for Inkscape Extensions
* [[Related programs]]

| style="width:50%;|
==== Continuous Integration (Automated testing) ====
* [http://jenkins.inkscape.org Our main testing website (Jenkins)]
* [[How to contribute to automated tests]]
* [[Jenkins server setup]]

==== Development Discussion ====
* [[Roadmap]]: the main todo list
* [[Dependencies]] - what libs are needed to build Inkscape
* [[C++11]] - What C++11 features can be used
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]]
* [[Coding Style|Coding Style Discussion]]
* [[FileTypes]]
* [[ApplicationIcons]] (Application + Interface)
* [[Icons]]
* [[InkscapeColor]]
* [[PrintingSubsystem]]
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite
* [[CSS Support]]
* [[Google Summer Of Code]]
* [[Improved Media Management]]
* [[UI MockupScreenshots]]
* [[Swatch Book]]
* [[Tablet Dialog]]
* [[ViewBoxToDo]] View box support info
* [[Caching]]
* [[UI and Document coordinates‎]]
* [[Mipmapping]]
* [[GtkMMification]]: replace C boilerplate with gtkmm objects

===Lib2Geom===
*[[lib2geom]]
*[[lib2geom Goals]]
*[[lib2geom FAQ]]
*[[lib2geom SVN Repository Guide]]
*[[WorkingWith2GeomFAQ]]: real-life questions answered about using 2Geom in real code
*[[lib2geom py2geom]]: python bindings to 2geom. With this you can use the power of 2geom in python scripts.

|- style="vertical-align:top;"
| style="width:50%;|
==== User Interface Discussion ====
* [[Translation_information]]
* [[AddingInterfaceVerbs]]
* [[AccessibleGraphics]]
* [[ObjectManager]]
* [[DialogsReorganization]]
* [[ModalInterfaces]]
* [[TextUsability]]: text tool /dialog dialog
* [[KeyboardShortcutsToDo]]
** [[KeyboardProfiles]]: how you can help
* [[StatusbarAPI]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]

| style="width:50%; |
|}

* [[WikiAttic]]: pages that are no longer relevant but kept for historical value

__NOTOC__

[[Category:About Inkscape]]
[[Category:User Documentation]]

Jenkins server setup

2015-01-22T00:09:21Z

Johanengelen: Enable access on port 80 instead of 8080

== Installed software ==
The software that was installed on our Ubuntu testing server (jenkins.inkscape.org).

apt-get install emacs24-nox

=====Inkscape build dependencies=====
apt-get install bzr
apt-get build-dep inkscape
apt-get install autopoint

=====Several packages for our Jenkins jobs=====
For scan-build static analysis:
apt-get install clang-3.5
For render testing we need a modified version of perceptualdiff that can handle transparency!!!
So we have to build our own version of perceptualdiff...
sudo apt-get install libfreeimage3 libopenjpeg2 libraw9
sudo apt-get install libfreeimage-dev
cd ~
bzr checkout --lightweight lp:inkscape-rendertest inkscape-rendertest
cd inkscape-rendertest/perceptualdiff-1.1.1-alphamod
cmake .
make
sudo cp perceptualdiff /usr/bin
For building 2Geom:
apt-get install cmake
For 2Geom documentation:
apt-get install doxygen graphviz texlive-latex-base ghostscript

=====Install Jenkins=====
Follow the instructions on [https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Jenkins wiki]:
wget -q -O - https://jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install jenkins

sudo /etc/init.d/jenkins start
Jenkins is now accessible through port 8080.

==Setup Jenkins==
We should be able to store Jenkins' config in an SCM, but didn't spend the time to figure that out.
* Manage Jenkins -> Global security
** Enable security
** Access control -> Jenkins' own user database, allow users to sign up. Anyone can do anything. Save.
* Sign yourself up.
* Back to Global security
** Access control -> Authorization -> matrix-based security.
*** Add your username to the matrix and give yourself full auth.
*** The anonymous user needs "Read" rights on:
**** Overall . Read
**** Job . Read
**** View . Read
** Access control -> disallow users to sign up (no reason for it, and may confuse people)
** Save.

=====Installed Jenkins plugins=====
Manage Jenkins -> Plugin Manager.
* Bazaar plugin
* Shared workspace plugin
* Clang Scan-build Plugin
* Coverity plugin
* Doxygen plug-in
* HTML Publisher Plugin
* xUnit Plugin

=====Config Jenkins some more=====
* Manage Jenkins -> Configure System
* Doxygen installations
** name: doxygen
** path: /usr/bin/doxygen (ignore the warning, you need the executable in there)

=====Before setting up Inkscape and 2Geom jobs=====
We first need to set up shared workspaces, so we can spread the tasks over several jobs.
* Manage Jenkins -> Configure system -> Workspace sharing
* Add Inkscape shared workspace
** name: inkscape_trunk
** repo: lp:inkscape
* Add 2Geom shared workspace
** name: lib2geom_trunk
** repo: lp:lib2geom

=====Jobs=====
Now you can set up jobs. We will have to save the jobs settings somewhere... Hard work to type it all out here.

=====Enable access on port 80, instead of 8080=====

See here: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+on+Port+80+or+443+using+iptables

We will use "iptables" to route traffix on port 80 to Jenkins.

sudo iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
Then store the settings (otherwise the settings will be void when the iptables service restarts) by installing iptables-persistent.
sudo apt-get install iptables-persistent

==== TO DO ====
* figure out how to reroute traffic such that jenkins.inkscape.org works instead of only jenkins.inkscape.org:8080

Jenkins server setup

2015-01-21T23:57:59Z

Johanengelen: add ghostscript for doxygen

Jenkins server setup

2015-01-21T23:51:06Z

Johanengelen: add latex install note

Jenkins server setup

2015-01-18T23:23:43Z

Johanengelen: /* Inkscape build dependencies */

Working with Bazaar

2014-11-21T19:54:32Z

Johanengelen: /* Publishing your work on Launchpad */

This page contains an introduction to the Bazaar distributed version control system. It focuses on the use of Bazaar to develop Inkscape, but should be useful to all would-be users of Bazaar.

You can choose either to use the command line or to use ''Bazaar Explorer'' (get the package ''bzr-explorer'' and follow the [http://doc.bazaar.canonical.com/explorer/en/tutorials/foss-contribute.html Bazaar Explorer Tutorial].

==Why version control is useful==

NOTE: skip this section if you have experience with any version control system.

If you ever worked on some large document in a group without any dedicated software, you have probably encountered the problem of simultaneous modification. When two people add something to the document at the same time, then send their version to each other, no one has the correct version. One of them has to redo their work in the other's version to merge the changes. This process is tedious and time-consuming, and the time spent on merging grows significantly when more people are added to the project.

Fortunately, for text files, this task is simple enough that it can be done automatically by a special program. When merging is done by software, people have more time to focus on productive work.

Version control systems (VCS) are programs designed to eliminate the overhead of merging. They manage a set of text files and allow many people to simultaneously work on them, then periodically submit their changes to a shared location. When two people change the same file, the changes are automatically merged together. Version control systems also store the complete history of changes. When someone makes a mistake and only spots it much later, it can be easily corrected, without affecting later work by other people.

==Version control basics==

Most version control systems use some shared location to publish the most up-to-date version of the project. (We will from now on assume that the project contains the source code for a program.) We will call this place the '''trunk'''. The first thing to do when starting work on a project is to download its source code, which is called creating a '''checkout'''. The files in your checkout are called the '''working copy'''. A checkout contains copies of files belonging to the project, where you can make changes. When you are ready to send your changes to others, you '''commit''' them, and they are stored in the shared location for others to see. The state of the project after someone's changes is called a '''revision''', and each revision in Bazaar is assigned a sequential number, called the '''revision number'''. Revision 0 is the empty project and revision 1 is the initial commit of the project's files. To receive the latest changes introduced by others, you '''update''' your checkout. The update command does not remove any of your uncommitted changes - they are automatically merged.

Bazaar uses the following commands for the above functionality.
$ bzr checkout ''project_trunk_url''
This checks out the source code of a project stored at the specified URL.
$ bzr commit
This sends your changes to the shared location, so others can see them. It will display an editor window, where you should enter the summary of your changes. This description will be visible when using the <tt>bzr log</tt> command.
$ bzr update
This updates your working copy to the latest public revision. Your uncommitted changes are left in place and automatically merged with others' changes.

===Useful basic commands===
$ bzr revert ''file''
This undoes all of your changes to the specified file and restores it to the state it was in after the last update.
$ bzr add ''file''
When you create a new file it is initially '''unversioned''', which means the version control system doesn't track changes to it. You need to tell the VCS that you want to include it in the project, or make it '''versioned'''. The <tt>add</tt> command is used to do this. The next <tt>commit</tt> command will then add this file to the shared location.
$ bzr rm ''file''
This removes a file and its contents from version control and deletes it from disk. The next <tt>commit</tt> command will remove it from the shared location. Use the <tt>--keep</tt> option if you want to remove the shared location but keep it as an unversioned file in your working copy.

===Inspecting project history===

Display last 20 sets of changes (revisions):
$ bzr log -l20

Display all changes to some file since the beginning of project history:
$ bzr log ''file''

===Inspecting changes===

Display all uncommitted changes:
$ bzr diff

Display all changes, both committed and uncommitted, from revision 340:
$ bzr diff -r340

Display changes introduced by revision 436:
$ bzr diff -c436

Display changes between revisions 252 and 260:
$ bzr diff -r252..260

===Undoing mistakes===

To remove all your uncommitted changes:
$ bzr revert

To revert a specific file to the state from revision 230:
$ bzr revert -r230 ''file''

Let's say you committed some change, but then after some time realized it was very wrong. To back it out without affecting any later changes, you need to find the revision number of the change using the <tt>bzr log</tt> command. Let's say want to undo changes from revision 340. To do this, write:
$ bzr merge -r340..339

In the same way, you can undo any set of contiguous revisions, e.g.
$ bzr merge -r340..320

To undo sets of non-contiguous revisions, you have to use one command per set. All commands after the first need to use the --force option (by default Bazaar will refuse to do a merge if here are uncommitted changes).
$ bzr merge -r340..339
$ bzr merge -r327..326 --force
$ bzr merge -r289..286 --force

To actually make the above changes in the shared location, you need to follow them with <tt>bzr commit</tt>. The exception is <tt>bzr revert</tt>, which restores the state to the last committed revision, so there is nothing to commit after it.

===Conflict resolution===

Sometimes two people change the same file in a way that cannot be automatically merged, for example, they change the same line to something different. When this happens, you need to merge the problematic bits manually. You might encounter output like this:

$ bzr update
M src/painting-algorithm.cpp
M src/ui/widget/spinner.h
M src/ui/widget/spinner.cpp
M src/ui/widget/awesome-widget.cpp
Text conflict in src/ui/widget/spinner.cpp
1 conflict encountered.
Updated to revision 1337 of branch [some URL]

After that, the directory <tt>src/ui/widget</tt> will contain four related files.
* <tt>spinner.cpp</tt>: this will contain an unified view of the conflicts in the file. Conflicts will be marked with lines with multiple consecutive angle brackets.
* <tt>spinner.cpp.BASE</tt>: latest common ancestor version of the file. In other words, both you and other people started from this version before conflicting changes were made.
* <tt>spinner.cpp.THIS</tt>: the file with your changes, with conflicting changes by others removed.
* <tt>spinner.cpp.OTHER</tt>: the file with other people's changes, with your conflicting changes removed.

To display the list of conflicts again, use the command:
$ bzr conflicts

To resolve the conflict, you need to modify the contents of the <tt>spinner.cpp</tt>. You can do this either by manually editing the file, by overwriting it with <tt>spinner.cpp.BASE</tt>, <tt>spinner.cpp.THIS</tt> or <tt>spinner.cpp.OTHER</tt>, or by using special options to the resolve command. Once you are done, you need to tell Bazaar about it:
$ bzr resolve src/ui/widget/spinner.cpp

You can tell Bazaar to use your version or others' version, respectively, with the following commands:
$ bzr resolve --take-this ''file''
$ bzr resolve --take-other ''file''

The above command will delete the files <tt>spinner.cpp.BASE</tt>, <tt>spinner.cpp.THIS</tt> and <tt>spinner.cpp.OTHER</tt>. Manually deleting those files has the same effect as executing <tt>bzr resolve</tt>. If you resolve all the conflicts at once, you can tell Bazaar to clean up everything:
$ bzr resolve --all

More information is available here: [http://doc.bazaar.canonical.com/latest/en/user-guide/resolving_conflicts.html Bazaar manual - Conflict handling].

===Determining who made a change===

Sometimes it is useful to see who last changed some lines in a file.
$ bzr annotate ''file''
This will display the entire ''file''. Each line will be prefixed with the revision when the line was last changed and the person which committed that revision. Another name for this command, which might be easier to remember, is <tt>bzr blame</tt>.

==Distributed VCS concepts in Bazaar==

This section assumes that you are familiar with the basic concepts of version control, like working copy, committing, updating, conflicts.

; '''Branch'''
: is a working copy of the project's code. Typically you use one branch per set of related changes, for example a new output extension. Once your work is finished, you ''merge'' your branch into a larger project. Initially, there is only one branch, the trunk; all other branches are its (probably indirect) descendants. To create a new branch, you have to copy an existing one. When branches A and B have a common ancestor branch but each contain changes not present in the other, they have '''diverged'''. For example, when you work on an improved rectangle tool in your own branch and at the same time somebody else applies a PDF export bugfix to the trunk, your rectangle tool branch becomes diverged from the trunk.
; '''Checkout'''
: is a copy of code contained in a branch that is not stored on your computer (a remote branch). Committing to a checkout will immediately apply the changes to the remote branch. Commits will not succeed if somebody else modified the branch while you were working - you need to have an up-to-date working copy - or when you're offline.
; '''Trunk'''
: is the main branch, which represents cutting-edge working code. You should start from it when doing any new development.
; '''Merge'''
: is the process of reconciling changes made between two branches since they diverged. This operation is asymmetric. When you merge A into B, all changes made to A since it was branched from B are applied to B. A is not changed. When you work on some feature, you typically work in a branch, periodically merging the trunk into your branch (to sync up with the latest changes), then you merge your work into the trunk. Merging is similar to applying a patch - it only changes your working copy. To apply a merge, you need to commit the changes it introduced. Merging un-diverges branches.
; '''Repository'''
: is a place where branches of a project are stored. Having a shared repository reduces the storage requirements of multiple branches of one project. Instead of O(number of branches) space, the Bazaar data takes up O(total size of changes in all branches) space.
; '''Bind'''
: is the process of converting a non-diverged local branch into a checkout of the remote branch.
; '''Push'''
: is the process of publishing an exact copy (a mirror) of your branch in some other location. The difference between pushing and checkouts is that a checked out remote branch is updated every time you commit, while a pushed remote branch is updated only when you push to it - you can commit any amount of changes between pushes. You can only push to a branch if the mirror has not diverged from your local copy. This can happen if more than 1 person can push to the same location.
; '''Pull'''
: is the process of creating a local exact copy (mirror) of a branch, in principle a reverse of pushing.

==First steps==

First you need to tell Bazaar your name. This will appear on all your commits. You should use your real e-mail, but you can obfuscate it if you are afraid of spam.

Obfuscated e-mail examples:
$ bzr whoami "John Q. Public <john dot q dot public at-sign bigmail dot com>"
$ bzr whoami "John Q. Public <removethis.john.q.public@bigmail.com>"
Unobfuscated e-mail example:
$ bzr whoami "John Q. Public <john.q.public@bigmail.com>"

If you have an account on Launchpad and want to commit changes there, you need to specify your Launchpad login. You can skip this if you do not intend to commit.
$ bzr launchpad-login johnq

Then fetch Inkscape's trunk
$ bzr checkout lp:inkscape

To carry out a later update of Inkscape's trunk
$ bzr update lp:inkscape

==Using a centralized (SVN-like) workflow==

In this case, every commit that you make is immediately sent to the central repository. There are two ways of achieving this:

===SVN-style checkout===

Get the latest Inkscape code as a checkout, as described above.
$ bzr checkout lp:inkscape

Now work as in SVN:
<do work>
$ bzr commit
<error, someone else has changed things>
$ bzr update
<check all is okay>
$ bzr commit

If you add new files, add them to version control with <tt>bzr add ''file''</tt>. You can recursively add all new files by writing simply <tt>bzr add</tt> in the top level directory.

===Binding a Bazaar branch===

Branch Inkscape's code:
$ bzr branch lp:inkscape

Then transform your branch into a checkout:
$ cd inkscape
$ bzr bind lp:inkscape

Now work as in SVN:
<do work>
$ bzr commit
<error, someone else has changed things>
$ bzr update
<check all is okay>
$ bzr commit

===Differences from SVN===

* Commits will fail if your checkout is not up to date, even if there would be no conflicts.
* The revision number is an attribute of the working tree, not of individual files. It is not possible to have different portions of the working tree at different revisions.
* <tt>bzr commit ''file''</tt> works like <tt> svn commit ''file'' && svn update ''project-root''</tt>. After a successful partial commit, the entire tree's revision is increased by 1.
* No special server is needed to publish a branch. You can push branches to anywhere, including simple FTP shares. In our scenario, Launchpad works like a central repository, but it's not required to publish everything there.
* You create branches locally. To simulate creating a SVN-style branch on Launchpad, you need to create a local branch, push it, then bind it to the pushed location. At the end of these commands you end up with a checkout of <tt>lp:~inkscape.dev/inkscape/killer-feature</tt>:
$ bzr branch trunk killer-feature
$ cd killer-feature
<do work>
$ bzr push lp:~inkscape.dev/inkscape/killer-feature
$ bzr bind :push

===Append-only branches===

In the centralized workflow, you often want to ensure that revision numbering is immutable. In Bazaar, the revision log and numbering can differ depending on which way you merge (e.g. feature into trunk vs trunk into feature). To enforce immutable, monotonically increasing revision numbers on a branch, you can create it as append-only:
$ bzr init --append-revisions-only
To set the append-only flag on an already existing branch, use the following command:
$ bzr config -d ''url://of/branch'' append_revisions_only=True
You can learn the URL of a remote branch by using the command <tt>bzr info</tt>. Launchpad branches have URLs such as <tt>bzr+ssh://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/</tt>

==Using a decentralized workflow==

In this case you will be working locally until you are ready to publish your changes. The basic idea is to perform the work in a ''branch'' of the Inkscape codebase, since committing to a branch stores the changes locally in the branch itself. Then, to share the work with the rest of the Inkscape community, the changes in the branch are merged across to a ''checkout'' of the Inkscape repository. As the previous centralized workflow section describes, committing to a checkout sends the changes directly to the remote repository, making them part of the official Inkscape codebase.

'''NOTE:''' this workflow has been updated to avoid the "other people's commits become subrevisions of your commit" problem.

This will assume this directory layout:
inkscape
+-trunk
| +-doc
| +-share
| +-src
| +-po
| +-...
+-myproject
+-some-other-branch

In this layout, "trunk" is the checkout used for uploading changes to the central Inkscape repository, while "myproject" and "some-other-branch" are local branches used for working on specific features.

===Repository setup===

To speed things up, it's good to create a local shared repository. This way revision histories will only be stored in one place, instead of in every branch, so local branching will be faster and the branches will take up less space.

Create a shared repository and enter it:
$ bzr init-repo inkscape
$ cd inkscape

===Working locally===

Get Inkscape's code
$ bzr branch lp:inkscape myproject

Now work:
$ cd myproject
... work work work ...
$ bzr commit -m "Some changes"
... more work work work ...
$ bzr commit -m "More changes"
... create new file ...
$ bzr add new-file.c
$ bzr commit -m "Added new file with kittens"

===Advanced local features===

To undo a commit:
$ bzr uncommit
This will leave your working tree in the state it was just before you wrote "bzr commit". This is useful for example if you forgot to add a file, and want to keep a clean revision history. '''This will not work on an Inkscape trunk checkout.'''

Let's say you started from r770, made 200 local commits, but you decided that what you did since r954 is completely wrong. You want to go back to revision 954 and do it differently. Here's one way to do this. First branch locally to preserve your work (maybe later you'll find out there's some way to save it). Then uncommit everything up to r954 and revert.
$ bzr branch myproject myproject-dead-end
$ cd myproject
$ bzr uncommit -r 954
$ bzr revert

Sometimes a big change gets committed while you are working on a feature. If you want to check whether your code still works after the big change, merge from trunk.
$ bzr merge

In this case, you can omit where you are merging from, because the default is to merge from the branch you started from (the parent).

To cherry-pick specific revisions from another branch:
$ bzr merge -r340..360 ''branch_location''
Or to cherry-pick a single revision:
$ bzr merge -c340 ''branch_location''

===Publishing your work on Launchpad===

To publish branches on Launchpad, you have to add an SSH key to your account. If you don't have one yet, generate it:
$ ssh-keygen
... follow instructions ...

Once you created the key, go to your Launchpad profile page, edit SSH keys and paste the contents of the key file (by default it's in <tt>~/.ssh/id_rsa.pub</tt> or <tt>~/.ssh/id_dsa.pub</tt>) into the window. You can now use the Launchpad integration features.

Login to Launchpad, if you didn't do it yet. You only need to do this once on each computer. You need to use your login name, not the display name.
$ bzr launchpad-login johnq

Publish your branch on Launchpad. If you push it under your username, only you will be able to modify it. If you have commit access and publish your branch under the username <tt>inkscape.dev</tt>, all Inkscape developers will be able to change it.
$ bzr push lp:~johnq/inkscape/myproject
$ bzr push lp:~inkscape.dev/inkscape/myproject

The push location will be saved. After more commits, you can simply write
$ bzr push

It's sometimes convenient to update the Launchpad copy after each commit. To save on typing, you can bind your working tree to the remote branch. This way every commit will be immediately published on the remote branch. Note that you won't be able to commit while offline.
$ bzr bind :push

'''Note that it is very helpful if other Inkscape developers can commit to your branch.''' For example, if someone is reviewing your code, it is much easier to make some quick edits than to tell you to make the edits. (for example, Johan will become very angry when he cannot commit small edits, he will stop reviewing right there, and never look at your branch again!)
The easiest way to make your branch commitable to others is to upload it as:

bzr push lp:~inkscape.dev/inkscape/myproject

However, you must be a member of [https://launchpad.net/~inkscape.dev inkscape.dev] (have commit rights) to
do this. If you are not in inkscape.dev, you'll need to create a team
consisting of yourself and the Inkscape Developers group, and upload
as that team. (You can create a team from the front page of
Launchpad.)

===Putting your work in the trunk===

Once your new killer feature you made in a branch is ready, you need to merge your changes into a checkout of the trunk. If you don't have one, do (in the directory ''containing'' myproject):
$ bzr checkout lp:inkscape trunk
$ cd trunk

If you already have one on hand, make sure it's up to date:
$ cd trunk
$ bzr update

Now that you have a local checkout of the current trunk:
$ bzr merge ../myproject
$ bzr commit -m 'added my feature'

Alternatively, if you don't have a checkout but a branch:
$ bzr merge ../myproject
$ bzr commit -m 'added my feature'
$ bzr push

Note that you need to do the above sequence on a branch that has not diverged from the trunk, otherwise it will fail, as the trunk is append-only.

The third method is to merge trunk into your local branch, then push:
$ bzr merge ../trunk
$ bzr commit -m 'added my feature'
$ bzr push

'''WARNING:''' This last method should be avoided if possible. If any work was done in trunk since you branched, all of it will be converted into subrevisions of your merge commit and revision numbers will change. This method will also fail with append-only branches, such as Inkscape's trunk on Launchpad.

====Undoing a wrong-way merge====
:''NOTE: Inkscape and Lib2geom trunks are append-only, so you will be prevented from doing the mistake discussed here, but this information is provided here in case it is useful for other projects.''

Let's say you merged trunk into a feature branch, then pushed that as the new trunk, and this "erased" some revisions. In reality the revisions are still present, but they became subrevisions of the merge commit. To restore the old revision numbers with your merge as the last revision, do this. First, find the revision into which you want to merge the feature changes. This will usually be the second parent of the mangling merge revision.
$ bzr log --show-ids
$ bzr visualise ''(requires bzr-gtk plugin)

Now branch from this revision:
$ bzr branch lp:myproject -r johnq@example.com-20111230042529-0iwskf9kff2xdmzg

Merge your changes the correct way and commit:
$ bzr merge lp:myproject
$ bzr commit

Replace the trunk with the correct version with unmangled history:
$ bzr push --overwrite lp:myproject

You can now convert the fixed local branch into a checkout of your project's trunk:
$ bzr bind :push

===Working with patch files===

If you don't have permission to commit to the trunk, you can bundle your branch's changes into a patch instead:
$ bzr send -o mychanges.patch

To apply patches produced by the above command, just do this:
$ bzr patch somechanges.patch

===Local branching===

Naturally, all this also works locally. For example, when you're in the <tt>inkscape</tt> directory, you can write <tt>bzr branch trunk export-dialog</tt> to create a new branch of the trunk called <tt>export-dialog</tt>, where you'll work only on improving the export dialog. Similarly, you can merge between local branches.

==Using Git-style branches==

Git stores many branches in one directory, and allows you to switch between them. This is also possible in Bazaar. One way is to use native Bazaar facilities, the other is to use the [https://launchpad.net/bzr-colo bzr-colo] plugin. We'll cover the native way, since the plugin has good documentation.

First, create a no-working-trees shared repository. The repo directory can be hidden if you want.
$ bzr init-repo --no-trees .inkscape-repo

Fetch the trunk and any other branches you want into our repository. (You can also push your local branches.)
$ bzr branch lp:inkscape .inkscape-repo/trunk
$ bzr branch lp:inkscape/0.48.x .inkscape-repo/0.48.x
$ bzr push killer-feature .inkscape-repo/killer-feature

Create your working tree by making a lightweight checkout of a desired branch. The <tt>--lightweight</tt> parameter is imp[ortant, otherwise you can run into problems.
$ bzr checkout --lightweight .inkscape-repo/trunk inkscape
$ cd inkscape

If you have an existing checkout of the trunk, use the following command:
$ cd inkscape
$ bzr reconfigure --lightweight-checkout --bind-to ../.inkscape-repo/trunk

Now you can work in the <tt>inkscape</tt> directory like you would on a normal branch. If you want to switch to a different branch, use:
$ bzr switch ../.inkscape-repo/killer-feature

To create a new branch in the repository:
$ bzr switch -b ../.inkscape-repo/killer-feature-2

==Best Practices for Inkscape Project==

===Registering Bugfixes===

Launchpad will automatically link a bug report to a branch and mark it "Fix Available" once somebody commits using the flag --fixes, e.g. (if you fix those two bugs in one commit):
bzr commit --fixes lp:123456 --fixes lp:123457 -m 'patch description'
Then, bugs can be changed automatically from "Fix Available" to "Fix Released"

[http://doc.bazaar-vcs.org/bzr.dev/en/tutorials/using_bazaar_with_launchpad.html#changing-the-state-in-launchpad-while-committing-in-bazaar Read more: "Changing the state in Launchpad while committing in Bazaar"]

===Test branches before committing merges===

Whenever a branch is merged into Inkscape trunk, the automated tests should be run to check for a few potential errors. This is achieved by running the "make check" command after merging (but before committing any changes). See the example below.

===Proper way of merging===

To repeat, don't do something like:
$ bzr branch lp:inkscape myproject
... work ...
$ bzr commit
$ bzr merge # NOOOO!!! We are doomed!
$ bzr push lp:inkscape

It would obfuscate the revision history: trunk commits that happened between the time you branched and the time you pushed would get grouped into one. Additionally, to prevent this obfuscation, Inkscape's trunk is set to append-only, so the above sequence of commands would fail. Do the merge the other way around:

$ bzr branch trunk myproject
$ cd myproject
... work ...
$ bzr commit
$ cd ../trunk
$ bzr merge ../myproject # correct!
$ make check # Run automated testing
$ bzr commit

You'll need a trunk checkout, but the revision history will be much less confusing, and it's useful to have a trunk checkout anyway for minor fixes.

===Fixing a bug in both trunk and a release branch===

This will assume this directory layout:
inkscape
+-trunk
| +-src
| +-...
+-0.48.x
| +-src
| +-...

Fix the bug in trunk and commit it, let's say it will be revision 1234.
Go to the release branch directory, e.g. 0.48.x, and write

$ bzr merge -r 1233..1234 ../trunk

The operation can take a while. Resolve any conflicts, fix any compilation failures, then commit to the release branch, or post the diff to a Launchpad bug report.

==External links==
* [http://doc.bazaar-vcs.org/latest/en/ Bazaar manual]

[[Category:Developer Documentation]]

Hackfest2015

2014-11-19T22:01:01Z

Johanengelen: /* The Pitch */

This page details the planning of an Inkscape Hackfest in April 2015

== Discusson ==

See the [[Board_Meetings]] page for minutes of past discussions and the time and place of the next discussion.

== Description ==

A hackfest! We will work on Inkscape bugs, new features, and packaging as well as website issues; in fact anything that can benefit from developers and users being physically in the same space.

Maybe even some Gtk+ issues: http://wiki.inkscape.org/wiki/index.php/GTK%2B_Issues

== The Pitch ==

Inkscape enables digital artists to produce professional quality work and beginners to create simple drawings or just noodle a bit. It allows everyone to explore their creativity. Inkscape is also used by engineers and scientists to create clear drawings to explain their ideas.
The Inkscape software is provided for free to all, as a fully open source, community-developed, socially owned project.

We need your help to further improve the program so many people love, and make sure it has a bright future!

Our developers work remotely in all corners of the world and rarely have the chance to work together in person. We've noticed that in-person meetings bring about stronger relationships and more creative results. Being together in one room allows us to work on things that are harder to do remotely: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

We will be meeting before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense hacking.

Please consider donating to cover travel, room, and board so our volunteer developers can attend the hackfest in person.

* Organizations that use Inkscape to draw testimonials from: http://wiki.inkscape.org/wiki/index.php/UsedBy

* Some of the nifty new features: http://inkscapetutorials.wordpress.com/category/0-91-new-features/

# TODO: Needs some photos of our developers, or images of what we'll be working on

Suggested donation amounts:
* $5 - Buy an Inkscape developer a beverage
* $50 - Food & Incidentals for one developer
* $500 - Lunch for the hackfest
* $2000 - Sponsor a developer

== Date ==

Sunday, April 26th through Tuesday, April 28th; just before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting 2015] (LGM2015) which takes place from [http://lists.freedesktop.org/archives/create/2014-May/004961.html April 29th through May 2nd 2015] (note: email states 30th through 2nd but an email on libre-graphics-meeting states that one day has been added at the beginning).

== Schedule ==

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) Late night hacking

== Location ==

Toronto at the same venue as LGM. We have a room reserved for us that can hold up to 30 people. It has movable tables with built in power outlets and a 40" TV in lieu of a projector.

== Budget ==

We had 8 attendees at the last LGM, and are hoping for perhaps 12 people this time.
Roughly, assuming costs will be in the $1000-2000 range per person for travel, room, and board, that gives a budget of $9-18k

To get more specific we'll need to:
* Estimate of hotel costs per night: $50 per person for shared double in two star hotel, $30 per person in hostel
* Estimate of airfare costs from Europe ($900), West Coast ($750), East Coast ($300), etc.
* Plan a daily food/incidentals stipend amount (~$30)

Cost estimate for 3 days pre-LGM in Toronto:
* From Paris: airfare $900 + $200 hotel + $100 food = $1200
* From Boston: airfare $300 + $200 hotel + $100 food = $600
* From Zurich: airfare $900 + $200 hotel + $100 food = $1200
* From Los Angeles: airfare $750 + $200 hotel + $100 food = $1150

We're considering a model similar to what we did with reimbursement limits for the GSoC reunion:

* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits (About 18 developers qualify, not all currently active)
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits (About 17 additional qualify)
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits (About 24 additional qualify)
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2015 (About 50 additional qualify)

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

maybe if we had some kind of form letter folks could give to their employer
i save you this much $$ per year in adobe whatever license fees. would you support my work for this company by contributing some percentage of that back to the inkscape project

* http://wiki.inkscape.org/wiki/index.php/UsedBy

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** Making contacts with development team
** News item with clear marking of who sponsored the event

== Action items ==

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| [DONE] Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Bryce
| [DONE] Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| Martin Owens
| Hear back from LGM about Torronto co-sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| [DONE] Get a list of [[http://wiki.inkscape.org/wiki/index.php/UsedBy companies using inkscape]]
|-
| 15 sep 2014
| Tav
| [DONE] Summarize and mail devlist
|-
| 20 sep 2014
| Tav
| [DONE] Set up a new wiki page for planning second Hackfest w/ RedHat
|-
| 20 sep 2014
| Bryce
| [DONE] Draft a preliminary promotional fundraising blurb
|-
| 20 sep 2014
| ryanlerch
| Work on a video for fundraiser
|-
| 20 sep 2014
| everyone
| [DONE] Consider indiegogo vs. hosting our own paypal donation page
|-
| 15 oct 2014
| everyone
| [DONE] Decide plan for implementing website/db support for fundraiser campaigns
|-
| 15 oct 2014
| karen
| Can we use Inkscape's existing paypal account or should we set up a separate one for fundraising
|-
| 15 oct 2014
| karen
| If we set the product_id on the donation page, can SFC provide us with a summary (or the raw data) with this info, so we can tally hackfest contribs?
|-
| 15 oct 2014
|
| Mockup layout on Staging for a fundraiser/donation page (using text from Pitch)
|-
| 12 nov 2014
|
| Decide where in inkscape.org's site menu to place Hackfest related pages
|-
| 12 nov 2014
|
| Create a Hackfest page in the main website
|-
| 12 nov 2014
|
| Write a page for Toronto transportation for A) how to get to/from airport, and B) how to get around the city
|-
| 12 nov 2014
|
| Write a set of posts for Inkscape blog / news feed (to be finalized + published as the event nears)
|-
| 12 nov 2014
|
| Find someone local to Toronto to help with local logistics
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to French
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to Spanish (and/or other major languages)

|}

== Brainstorm area ==
Put things here that you think could use a bit of discussion/thought.

Places to announce the fundraiser, once it's set up?
* Inkscape's g+ page
* inkscape-users@
* twitter
* dA
* the website
* <karenesq> I bet LWN would be interested
* <doctormon> Possible interest: http://zipfelchappe.readthedocs.org/en/latest/
* <ryanlerch> i can promote on inkscapetuts and fedoramagazine too

=== 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 (maximum one day) when done in a group. Before determining specific tasks, what kind of tasks should we try to tackle?
* Fleshing out documentation
** Code documentation
** Architecture docs
** Coding howtos
** Tutorials
** User documentation
** Translation of same
* A bug that requires knowledge of large part of codebase.
* Writing test cases
* 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.
** Conversion of build system
** Performance optimizations
** Coordinate flip.
* 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.
** Infrastructure setup
* Design / strategy collaboration
** SVG 2 fallbacks
** New plugin/extension system
* Planning
** Post-1.0 roadmap definition
** Conference attendance for upcoming year
** Future hackfests :-)
* Pictures pictures pictures
** Try to make nice pictures that show what has happened. Can then also be used for PR for next edition.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===

We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub
* Take a group picture!!!

Hackfest2015

2014-11-19T21:19:04Z

Johanengelen: /* Tasks to tackle */

This page details the planning of an Inkscape Hackfest in April 2015

== Discusson ==

See the [[Board_Meetings]] page for minutes of past discussions and the time and place of the next discussion.

== Description ==

A hackfest! We will work on Inkscape bugs, new features, and packaging as well as website issues; in fact anything that can benefit from developers and users being physically in the same space.

Maybe even some Gtk+ issues: http://wiki.inkscape.org/wiki/index.php/GTK%2B_Issues

== The Pitch ==

Inkscape enables digital artists to do produce professional quality work, beginners to create simple drawings or just noodle a bit, and everyone to explore their creativity. The Inkscape software is provided for free to all, as a fully open source, community-developed, socially owned project.

We need your help to make sure Inkscape has a bright future!

Our developers work remotely in all corners of the world and rarely have the chance to work together in person. We've noticed that in-person meetings bring about stronger relationships and more creative results. Being together in one room allows us to work on things that are harder to do remotely: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

We will be meeting before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense hacking.

Please consider donating to cover travel, room, and board so our volunteer developers can attend the hackfest in person.

* Organizations that use Inkscape to draw testimonials from: http://wiki.inkscape.org/wiki/index.php/UsedBy

* Some of the nifty new features: http://inkscapetutorials.wordpress.com/category/0-91-new-features/

# TODO: Needs some photos of our developers, or images of what we'll be working on

Suggested donation amounts:
* $5 - Buy an Inkscape developer a beverage
* $50 - Food & Incidentals for one developer
* $500 - Lunch for the hackfest
* $2000 - Sponsor a developer

== Date ==

Sunday, April 26th through Tuesday, April 28th; just before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting 2015] (LGM2015) which takes place from [http://lists.freedesktop.org/archives/create/2014-May/004961.html April 29th through May 2nd 2015] (note: email states 30th through 2nd but an email on libre-graphics-meeting states that one day has been added at the beginning).

== Schedule ==

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) Late night hacking

== Location ==

Toronto at the same venue as LGM. We have a room reserved for us that can hold up to 30 people. It has movable tables with built in power outlets and a 40" TV in lieu of a projector.

== Budget ==

We had 8 attendees at the last LGM, and are hoping for perhaps 12 people this time.
Roughly, assuming costs will be in the $1000-2000 range per person for travel, room, and board, that gives a budget of $9-18k

To get more specific we'll need to:
* Estimate of hotel costs per night: $50 per person for shared double in two star hotel, $30 per person in hostel
* Estimate of airfare costs from Europe ($900), West Coast ($750), East Coast ($300), etc.
* Plan a daily food/incidentals stipend amount (~$30)

Cost estimate for 3 days pre-LGM in Toronto:
* From Paris: airfare $900 + $200 hotel + $100 food = $1200
* From Boston: airfare $300 + $200 hotel + $100 food = $600
* From Zurich: airfare $900 + $200 hotel + $100 food = $1200
* From Los Angeles: airfare $750 + $200 hotel + $100 food = $1150

We're considering a model similar to what we did with reimbursement limits for the GSoC reunion:

* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits (About 18 developers qualify, not all currently active)
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits (About 17 additional qualify)
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits (About 24 additional qualify)
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2015 (About 50 additional qualify)

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

maybe if we had some kind of form letter folks could give to their employer
i save you this much $$ per year in adobe whatever license fees. would you support my work for this company by contributing some percentage of that back to the inkscape project

* http://wiki.inkscape.org/wiki/index.php/UsedBy

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** Making contacts with development team
** News item with clear marking of who sponsored the event

== Action items ==

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| [DONE] Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Bryce
| [DONE] Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| Martin Owens
| Hear back from LGM about Torronto co-sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| [DONE] Get a list of [[http://wiki.inkscape.org/wiki/index.php/UsedBy companies using inkscape]]
|-
| 15 sep 2014
| Tav
| [DONE] Summarize and mail devlist
|-
| 20 sep 2014
| Tav
| [DONE] Set up a new wiki page for planning second Hackfest w/ RedHat
|-
| 20 sep 2014
| Bryce
| [DONE] Draft a preliminary promotional fundraising blurb
|-
| 20 sep 2014
| ryanlerch
| Work on a video for fundraiser
|-
| 20 sep 2014
| everyone
| [DONE] Consider indiegogo vs. hosting our own paypal donation page
|-
| 15 oct 2014
| everyone
| [DONE] Decide plan for implementing website/db support for fundraiser campaigns
|-
| 15 oct 2014
| karen
| Can we use Inkscape's existing paypal account or should we set up a separate one for fundraising
|-
| 15 oct 2014
| karen
| If we set the product_id on the donation page, can SFC provide us with a summary (or the raw data) with this info, so we can tally hackfest contribs?
|-
| 15 oct 2014
|
| Mockup layout on Staging for a fundraiser/donation page (using text from Pitch)
|-
| 12 nov 2014
|
| Decide where in inkscape.org's site menu to place Hackfest related pages
|-
| 12 nov 2014
|
| Create a Hackfest page in the main website
|-
| 12 nov 2014
|
| Write a page for Toronto transportation for A) how to get to/from airport, and B) how to get around the city
|-
| 12 nov 2014
|
| Write a set of posts for Inkscape blog / news feed (to be finalized + published as the event nears)
|-
| 12 nov 2014
|
| Find someone local to Toronto to help with local logistics
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to French
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to Spanish (and/or other major languages)

|}

== Brainstorm area ==
Put things here that you think could use a bit of discussion/thought.

Places to announce the fundraiser, once it's set up?
* Inkscape's g+ page
* inkscape-users@
* twitter
* dA
* the website
* <karenesq> I bet LWN would be interested
* <doctormon> Possible interest: http://zipfelchappe.readthedocs.org/en/latest/
* <ryanlerch> i can promote on inkscapetuts and fedoramagazine too

=== 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 (maximum one day) when done in a group. Before determining specific tasks, what kind of tasks should we try to tackle?
* Fleshing out documentation
** Code documentation
** Architecture docs
** Coding howtos
** Tutorials
** User documentation
** Translation of same
* A bug that requires knowledge of large part of codebase.
* Writing test cases
* 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.
** Conversion of build system
** Performance optimizations
** Coordinate flip.
* 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.
** Infrastructure setup
* Design / strategy collaboration
** SVG 2 fallbacks
** New plugin/extension system
* Planning
** Post-1.0 roadmap definition
** Conference attendance for upcoming year
** Future hackfests :-)
* Pictures pictures pictures
** Try to make nice pictures that show what has happened. Can then also be used for PR for next edition.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===

We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub
* Take a group picture!!!

Hackfest2015

2014-11-19T21:05:25Z

Johanengelen: /* Non-coding stuff */

This page details the planning of an Inkscape Hackfest in April 2015

== Discusson ==

See the [[Board_Meetings]] page for minutes of past discussions and the time and place of the next discussion.

== Description ==

A hackfest! We will work on Inkscape bugs, new features, and packaging as well as website issues; in fact anything that can benefit from developers and users being physically in the same space.

Maybe even some Gtk+ issues: http://wiki.inkscape.org/wiki/index.php/GTK%2B_Issues

== The Pitch ==

Inkscape enables digital artists to do produce professional quality work, beginners to create simple drawings or just noodle a bit, and everyone to explore their creativity. The Inkscape software is provided for free to all, as a fully open source, community-developed, socially owned project.

We need your help to make sure Inkscape has a bright future!

Our developers work remotely in all corners of the world and rarely have the chance to work together in person. We've noticed that in-person meetings bring about stronger relationships and more creative results. Being together in one room allows us to work on things that are harder to do remotely: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

We will be meeting before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense hacking.

Please consider donating to cover travel, room, and board so our volunteer developers can attend the hackfest in person.

* Organizations that use Inkscape to draw testimonials from: http://wiki.inkscape.org/wiki/index.php/UsedBy

* Some of the nifty new features: http://inkscapetutorials.wordpress.com/category/0-91-new-features/

# TODO: Needs some photos of our developers, or images of what we'll be working on

Suggested donation amounts:
* $5 - If you owe an Inkscape developer a beverage
* $50 - Food & Incidentals for one developer
* $500 - Lunch for the hackfest
* $2000 - Sponsor a developer

== Date ==

Sunday, April 26th through Tuesday, April 28th; just before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting 2015] (LGM2015) which takes place from [http://lists.freedesktop.org/archives/create/2014-May/004961.html April 29th through May 2nd 2015] (note: email states 30th through 2nd but an email on libre-graphics-meeting states that one day has been added at the beginning).

== Schedule ==

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) Late night hacking

== Location ==

Toronto at the same venue as LGM. We have a room reserved for us that can hold up to 30 people. It has movable tables with built in power outlets and a 40" TV in lieu of a projector.

== Budget ==

We had 8 attendees at the last LGM, and are hoping for perhaps 12 people this time.
Roughly, assuming costs will be in the $1000-2000 range per person for travel, room, and board, that gives a budget of $9-18k

To get more specific we'll need to:
* Estimate of hotel costs per night: $50 per person for shared double in two star hotel, $30 per person in hostel
* Estimate of airfare costs from Europe ($900), West Coast ($750), East Coast ($300), etc.
* Plan a daily food/incidentals stipend amount (~$30)

Cost estimate for 3 days pre-LGM in Toronto:
* From Paris: airfare $900 + $200 hotel + $100 food = $1200
* From Boston: airfare $300 + $200 hotel + $100 food = $600
* From Zurich: airfare $900 + $200 hotel + $100 food = $1200
* From Los Angeles: airfare $750 + $200 hotel + $100 food = $1150

We're considering a model similar to what we did with reimbursement limits for the GSoC reunion:

* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits (About 18 developers qualify, not all currently active)
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits (About 17 additional qualify)
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits (About 24 additional qualify)
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2015 (About 50 additional qualify)

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

maybe if we had some kind of form letter folks could give to their employer
i save you this much $$ per year in adobe whatever license fees. would you support my work for this company by contributing some percentage of that back to the inkscape project

* http://wiki.inkscape.org/wiki/index.php/UsedBy

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** Making contacts with development team
** News item with clear marking of who sponsored the event

== Action items ==

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| [DONE] Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Bryce
| [DONE] Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| Martin Owens
| Hear back from LGM about Torronto co-sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| [DONE] Get a list of [[http://wiki.inkscape.org/wiki/index.php/UsedBy companies using inkscape]]
|-
| 15 sep 2014
| Tav
| [DONE] Summarize and mail devlist
|-
| 20 sep 2014
| Tav
| [DONE] Set up a new wiki page for planning second Hackfest w/ RedHat
|-
| 20 sep 2014
| Bryce
| [DONE] Draft a preliminary promotional fundraising blurb
|-
| 20 sep 2014
| ryanlerch
| Work on a video for fundraiser
|-
| 20 sep 2014
| everyone
| [DONE] Consider indiegogo vs. hosting our own paypal donation page
|-
| 15 oct 2014
| everyone
| [DONE] Decide plan for implementing website/db support for fundraiser campaigns
|-
| 15 oct 2014
| karen
| Can we use Inkscape's existing paypal account or should we set up a separate one for fundraising
|-
| 15 oct 2014
| karen
| If we set the product_id on the donation page, can SFC provide us with a summary (or the raw data) with this info, so we can tally hackfest contribs?
|-
| 15 oct 2014
|
| Mockup layout on Staging for a fundraiser/donation page (using text from Pitch)
|-
| 12 nov 2014
|
| Decide where in inkscape.org's site menu to place Hackfest related pages
|-
| 12 nov 2014
|
| Create a Hackfest page in the main website
|-
| 12 nov 2014
|
| Write a page for Toronto transportation for A) how to get to/from airport, and B) how to get around the city
|-
| 12 nov 2014
|
| Write a set of posts for Inkscape blog / news feed (to be finalized + published as the event nears)
|-
| 12 nov 2014
|
| Find someone local to Toronto to help with local logistics
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to French
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to Spanish (and/or other major languages)

|}

== Brainstorm area ==
Put things here that you think could use a bit of discussion/thought.

Places to announce the fundraiser, once it's set up?
* Inkscape's g+ page
* inkscape-users@
* twitter
* dA
* the website
* <karenesq> I bet LWN would be interested
* <doctormon> Possible interest: http://zipfelchappe.readthedocs.org/en/latest/
* <ryanlerch> i can promote on inkscapetuts and fedoramagazine too

=== 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 (maximum one day) when done in a group. Before determining specific tasks, what kind of tasks should we try to tackle?
* Fleshing out documentation
** Code documentation
** Architecture docs
** Coding howtos
** Tutorials
** User documentation
** Translation of same
* A bug that requires knowledge of large part of codebase.
* Writing test cases
* 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.
** Conversion of build system
** Performance optimizations
** Coordinate flip.
* 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.
** Infrastructure setup
* Design / strategy collaboration
** SVG 2 fallbacks
** New plugin/extension system
* Planning
** Post-1.0 roadmap definition
** Conference attendance for upcoming year
** Future hackfests :-)

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===

We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub
* Take a group picture!!!

Jenkins server setup

2014-11-12T22:30:08Z

Johanengelen: /* Several packages for our Jenkins jobs */

Jenkins server setup

2014-11-12T22:07:23Z

Johanengelen: /* Several packages for our Jenkins jobs */

Jenkins server setup

2014-11-12T20:49:48Z

Johanengelen: /* Before setting up Inkscape and 2Geom jobs */

Jenkins server setup

2014-11-12T20:48:06Z

Johanengelen: /* Installed Jenkins plugins */

Jenkins server setup

2014-11-12T20:32:03Z

Johanengelen: /* Install Jenkins */

Jenkins server setup

2014-11-12T20:13:37Z

Johanengelen: /* Setup Jenkins= */

Jenkins server setup

2014-11-12T20:13:13Z

Johanengelen: /* Setup Jenkins */

Jenkins server setup

2014-11-12T20:08:39Z

Johanengelen: /* Setup Jenkins */

Inkscape

2014-11-12T19:53:01Z

Johanengelen: /* Continuous Integration (Automated testing) */ fix link

This is a freeform area for Inkscape development and discussion.
Curious about [[WikiSyntax]]?

Other languages: [[Inkscape en español|Wiki en español]], [[L'Inkscape en Català|Wiki en Català]], [[Inkscape em Português|Wiki em Português]], [[Startseite|Wiki auf deutsch]]...

{| cellspacing="11" style="width:100%;"
|-style="vertical-align:top;"
| style="width:33%;background-color: #E6E6E6; padding:.5em;"|
=== Project Info ===
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[Features of Inkscape|Features]]
* [[FAQ]] - Frequently Asked Questions
* [[Supported operating systems]]
* [[Tools]] - Supporting Tools and Applications
* [[Galleries]]
* [[Inkscape coverage|Coverage]] - Awards, articles, presentations, books about Inkscape
* [[Inkscape popularity|Popularity]]
* [[Contact information]] - the developers' e-mails and SVN nicknames
* [[InkscapeInvariants|Inkscape's Mission]]
* [[CommunicationChannels|Communication Channels]]: how to reach us
* [[AnnouncementToSodipodi|Announcement To Sodipodi]]: this started it all
* [[Branding]]
* [[ContactInfo|Contact Information]]: who's behind Inkscape
* [[Travel Reimbursement Policy]]

|style="width:33%;;background-color: white; padding:.5em;"|

=== User Documentation ===
* [[Installing Inkscape|Installation]]
* [[International and Local Communities]]
* [[Inkscape glossary]]
* [[User manual information]] - where to find the free Inkscape manual and how to contribute to it
* [http://inkscape.org/doc/ Tutorials]
* [[Inkscape SVG vs. plain SVG]]
* [[Output format requirements]] - what's needed to save in some formats
* [[Effect requirements]] - what's needed to use some effects
* [[Effect reference]] - what each effect does
* [[Connector tool tutorial]]
* [[Installing fonts]]
* [[Emergency save]] - recovery in case Inkscape crashed
* [[Release notes]]
** for version [[Release notes/0.91|0.91]] (active development)
** '''for version [[Release notes/0.48.5|0.48.5]] (current release)'''
** older versions: [[Release notes/0.48.4|0.48.4]] [[Release notes/0.48.3|0.48.3]], [[Release notes/0.48.2|0.48.2]], [[Release notes/0.48.1|0.48.1]], [[Release notes/0.48|0.48]], [[Release notes/0.47|0.47]]
* [[Announcing Releases]]
* [[Tricks and tips]] - miscellaneous advice, may be slightly outdated

|style="width:33%;background-color: #E6E6E6; padding:.5em;"|

=== Help Inkscape Without Coding ===
* [[Bug management]]
* [[Testing]]
* [[Translation information]]
* [[Editing Inkscape's website|Website]]
* [[Inkscape Classes]]
* [[Conferences]]
* [[Marketing Scratchpad]]

* [[HelpWanted]]
* [[BugTriageProjects]]
* [[CreatingDists]]: how to build packages
* [[StableBranchUpdates]]
* [[UpdatingTrackerItems]]
* [[TutorialsAndHelp]]
* [[How_To_Start_A_Page]] how to use the wiki
* [[CreatingScreencasts]]
* [[AboutScreenContest]]
|}

{| cellspacing="0" style="width: 100%; background-color: white; border-width:1px; border-style:solid; border-color:#62C012; align:left; padding:11px 0em 0em 11px;"
|- style="vertical-align:top;"
| colspan="2"|

=== Developer Documentation ===
|- style="vertical-align:top;"
| style="width:50%;|
==== First Steps ====
* [[Working with Bazaar]] - How to obtain the source code. A quick start on how to use our version control system
* [[Compiling Inkscape|Compilation]]
* [[Using Eclipse]]
* [[Developer manual]] - various important information, be sure to read this before coding
* [[Debugging Inkscape|Debugging]] - random tips to help debug problems
* [[Project organization]] - procedures, hierarchy, developer roles and the likes
* [[Janitorial tasks]] - small tasks that need doing
* [[Doxygen documentation]]
* [[Working with SVN]] - besides the code in Bazaar, we still have some things in SVN.

==== Developer tutorials ====
* [[Architectural overview]] - a high-level look at Inkscape
* [[Preferences subsystem]] - creating and using preference values
* XML subsystem (WIP) - how to manipulate the XML representation of a document
* Display subsystem (WIP) - how to make things appear on the canvas
* Tools subsystem (WIP) - how to create a new tool
* [[Creating a new SPObject]]
* Extensions
** [[Extension subsystem]] - an overview of the functionality provided by extensions and the possible implementations
** [[Script extensions]]
** [[Python modules for extensions]] - some helpful routines for use in Python script extensions
* [[Creating Live Path Effects]]
* [[Boost shared pointers]]
* [[Using libsigc++ signals]]
* [[Windows development on Linux]]

==== Miscellaneous ====
* [[INX extension descriptor format]]
* [[Inkscape-specific XML attributes]] - documentation of attributes from Inkscape's XML namespace

* [[Extension repository]]: an Internet central for Inkscape Extensions
* [[Related programs]]

| style="width:50%;|
==== Continuous Integration (Automated testing) ====
* [http://jenkins.inkscape.org:8080 Our main testing website (Jenkins)]
* [[How to contribute to automated tests]]
* [[Jenkins server setup]]

==== Development Discussion ====
* [[Roadmap]]: the main todo list
* [[Dependencies]] - what libs are needed to build Inkscape
* [[C++11]] - What C++11 features can be used
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]]
* [[Coding Style|Coding Style Discussion]]
* [[FileTypes]]
* [[ApplicationIcons]] (Application + Interface)
* [[Icons]]
* [[InkscapeColor]]
* [[PrintingSubsystem]]
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite
* [[CSS Support]]
* [[Google Summer Of Code]]
* [[Improved Media Management]]
* [[UI MockupScreenshots]]
* [[Swatch Book]]
* [[Tablet Dialog]]
* [[ViewBoxToDo]] View box support info
* [[Caching]]
* [[UI and Document coordinates‎]]
* [[Mipmapping]]
* [[GtkMMification]]: replace C boilerplate with gtkmm objects

===Lib2Geom===
*[[lib2geom]]
*[[lib2geom Goals]]
*[[lib2geom FAQ]]
*[[lib2geom SVN Repository Guide]]
*[[WorkingWith2GeomFAQ]]: real-life questions answered about using 2Geom in real code
*[[lib2geom py2geom]]: python bindings to 2geom. With this you can use the power of 2geom in python scripts.

|- style="vertical-align:top;"
| style="width:50%;|
==== User Interface Discussion ====
* [[Translation_information]]
* [[AddingInterfaceVerbs]]
* [[AccessibleGraphics]]
* [[ObjectManager]]
* [[DialogsReorganization]]
* [[ModalInterfaces]]
* [[TextUsability]]: text tool /dialog dialog
* [[KeyboardShortcutsToDo]]
** [[KeyboardProfiles]]: how you can help
* [[StatusbarAPI]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]

| style="width:50%; |
|}

* [[WikiAttic]]: pages that are no longer relevant but kept for historical value

__NOTOC__

[[Category:About Inkscape]]
[[Category:User Documentation]]

Jenkins server setup

2014-11-12T19:44:58Z

Johanengelen: /* Setup Jenkins */

Jenkins server setup

2014-11-12T19:42:14Z

Johanengelen: /* Jenkins */

Jenkins server setup

2014-11-12T19:34:08Z

Johanengelen: /* Jenkins */

Inkscape

2014-11-12T19:32:00Z

Johanengelen: /* Continuous Integration (Automated testing) */ Actually... prevent access while installing

This is a freeform area for Inkscape development and discussion.
Curious about [[WikiSyntax]]?

Other languages: [[Inkscape en español|Wiki en español]], [[L'Inkscape en Català|Wiki en Català]], [[Inkscape em Português|Wiki em Português]], [[Startseite|Wiki auf deutsch]]...

{| cellspacing="11" style="width:100%;"
|-style="vertical-align:top;"
| style="width:33%;background-color: #E6E6E6; padding:.5em;"|
=== Project Info ===
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[Features of Inkscape|Features]]
* [[FAQ]] - Frequently Asked Questions
* [[Supported operating systems]]
* [[Tools]] - Supporting Tools and Applications
* [[Galleries]]
* [[Inkscape coverage|Coverage]] - Awards, articles, presentations, books about Inkscape
* [[Inkscape popularity|Popularity]]
* [[Contact information]] - the developers' e-mails and SVN nicknames
* [[InkscapeInvariants|Inkscape's Mission]]
* [[CommunicationChannels|Communication Channels]]: how to reach us
* [[AnnouncementToSodipodi|Announcement To Sodipodi]]: this started it all
* [[Branding]]
* [[ContactInfo|Contact Information]]: who's behind Inkscape
* [[Travel Reimbursement Policy]]

|style="width:33%;;background-color: white; padding:.5em;"|

=== User Documentation ===
* [[Installing Inkscape|Installation]]
* [[International and Local Communities]]
* [[Inkscape glossary]]
* [[User manual information]] - where to find the free Inkscape manual and how to contribute to it
* [http://inkscape.org/doc/ Tutorials]
* [[Inkscape SVG vs. plain SVG]]
* [[Output format requirements]] - what's needed to save in some formats
* [[Effect requirements]] - what's needed to use some effects
* [[Effect reference]] - what each effect does
* [[Connector tool tutorial]]
* [[Installing fonts]]
* [[Emergency save]] - recovery in case Inkscape crashed
* [[Release notes]]
** for version [[Release notes/0.91|0.91]] (active development)
** '''for version [[Release notes/0.48.5|0.48.5]] (current release)'''
** older versions: [[Release notes/0.48.4|0.48.4]] [[Release notes/0.48.3|0.48.3]], [[Release notes/0.48.2|0.48.2]], [[Release notes/0.48.1|0.48.1]], [[Release notes/0.48|0.48]], [[Release notes/0.47|0.47]]
* [[Announcing Releases]]
* [[Tricks and tips]] - miscellaneous advice, may be slightly outdated

|style="width:33%;background-color: #E6E6E6; padding:.5em;"|

=== Help Inkscape Without Coding ===
* [[Bug management]]
* [[Testing]]
* [[Translation information]]
* [[Editing Inkscape's website|Website]]
* [[Inkscape Classes]]
* [[Conferences]]
* [[Marketing Scratchpad]]

* [[HelpWanted]]
* [[BugTriageProjects]]
* [[CreatingDists]]: how to build packages
* [[StableBranchUpdates]]
* [[UpdatingTrackerItems]]
* [[TutorialsAndHelp]]
* [[How_To_Start_A_Page]] how to use the wiki
* [[CreatingScreencasts]]
* [[AboutScreenContest]]
|}

{| cellspacing="0" style="width: 100%; background-color: white; border-width:1px; border-style:solid; border-color:#62C012; align:left; padding:11px 0em 0em 11px;"
|- style="vertical-align:top;"
| colspan="2"|

=== Developer Documentation ===
|- style="vertical-align:top;"
| style="width:50%;|
==== First Steps ====
* [[Working with Bazaar]] - How to obtain the source code. A quick start on how to use our version control system
* [[Compiling Inkscape|Compilation]]
* [[Using Eclipse]]
* [[Developer manual]] - various important information, be sure to read this before coding
* [[Debugging Inkscape|Debugging]] - random tips to help debug problems
* [[Project organization]] - procedures, hierarchy, developer roles and the likes
* [[Janitorial tasks]] - small tasks that need doing
* [[Doxygen documentation]]
* [[Working with SVN]] - besides the code in Bazaar, we still have some things in SVN.

==== Developer tutorials ====
* [[Architectural overview]] - a high-level look at Inkscape
* [[Preferences subsystem]] - creating and using preference values
* XML subsystem (WIP) - how to manipulate the XML representation of a document
* Display subsystem (WIP) - how to make things appear on the canvas
* Tools subsystem (WIP) - how to create a new tool
* [[Creating a new SPObject]]
* Extensions
** [[Extension subsystem]] - an overview of the functionality provided by extensions and the possible implementations
** [[Script extensions]]
** [[Python modules for extensions]] - some helpful routines for use in Python script extensions
* [[Creating Live Path Effects]]
* [[Boost shared pointers]]
* [[Using libsigc++ signals]]
* [[Windows development on Linux]]

==== Miscellaneous ====
* [[INX extension descriptor format]]
* [[Inkscape-specific XML attributes]] - documentation of attributes from Inkscape's XML namespace

* [[Extension repository]]: an Internet central for Inkscape Extensions
* [[Related programs]]

| style="width:50%;|
==== Continuous Integration (Automated testing) ====
* [http://jenkins.inkscape.org Our main testing website (Jenkins)]
* [[How to contribute to automated tests]]
* [[Jenkins server setup]]

==== Development Discussion ====
* [[Roadmap]]: the main todo list
* [[Dependencies]] - what libs are needed to build Inkscape
* [[C++11]] - What C++11 features can be used
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]]
* [[Coding Style|Coding Style Discussion]]
* [[FileTypes]]
* [[ApplicationIcons]] (Application + Interface)
* [[Icons]]
* [[InkscapeColor]]
* [[PrintingSubsystem]]
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite
* [[CSS Support]]
* [[Google Summer Of Code]]
* [[Improved Media Management]]
* [[UI MockupScreenshots]]
* [[Swatch Book]]
* [[Tablet Dialog]]
* [[ViewBoxToDo]] View box support info
* [[Caching]]
* [[UI and Document coordinates‎]]
* [[Mipmapping]]
* [[GtkMMification]]: replace C boilerplate with gtkmm objects

===Lib2Geom===
*[[lib2geom]]
*[[lib2geom Goals]]
*[[lib2geom FAQ]]
*[[lib2geom SVN Repository Guide]]
*[[WorkingWith2GeomFAQ]]: real-life questions answered about using 2Geom in real code
*[[lib2geom py2geom]]: python bindings to 2geom. With this you can use the power of 2geom in python scripts.

|- style="vertical-align:top;"
| style="width:50%;|
==== User Interface Discussion ====
* [[Translation_information]]
* [[AddingInterfaceVerbs]]
* [[AccessibleGraphics]]
* [[ObjectManager]]
* [[DialogsReorganization]]
* [[ModalInterfaces]]
* [[TextUsability]]: text tool /dialog dialog
* [[KeyboardShortcutsToDo]]
** [[KeyboardProfiles]]: how you can help
* [[StatusbarAPI]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]

| style="width:50%; |
|}

* [[WikiAttic]]: pages that are no longer relevant but kept for historical value

__NOTOC__

[[Category:About Inkscape]]
[[Category:User Documentation]]

Inkscape

2014-11-12T19:30:30Z

Johanengelen: /* Continuous Integration (Automated testing) */ Fix link

This is a freeform area for Inkscape development and discussion.
Curious about [[WikiSyntax]]?

Other languages: [[Inkscape en español|Wiki en español]], [[L'Inkscape en Català|Wiki en Català]], [[Inkscape em Português|Wiki em Português]], [[Startseite|Wiki auf deutsch]]...

{| cellspacing="11" style="width:100%;"
|-style="vertical-align:top;"
| style="width:33%;background-color: #E6E6E6; padding:.5em;"|
=== Project Info ===
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[Features of Inkscape|Features]]
* [[FAQ]] - Frequently Asked Questions
* [[Supported operating systems]]
* [[Tools]] - Supporting Tools and Applications
* [[Galleries]]
* [[Inkscape coverage|Coverage]] - Awards, articles, presentations, books about Inkscape
* [[Inkscape popularity|Popularity]]
* [[Contact information]] - the developers' e-mails and SVN nicknames
* [[InkscapeInvariants|Inkscape's Mission]]
* [[CommunicationChannels|Communication Channels]]: how to reach us
* [[AnnouncementToSodipodi|Announcement To Sodipodi]]: this started it all
* [[Branding]]
* [[ContactInfo|Contact Information]]: who's behind Inkscape
* [[Travel Reimbursement Policy]]

|style="width:33%;;background-color: white; padding:.5em;"|

=== User Documentation ===
* [[Installing Inkscape|Installation]]
* [[International and Local Communities]]
* [[Inkscape glossary]]
* [[User manual information]] - where to find the free Inkscape manual and how to contribute to it
* [http://inkscape.org/doc/ Tutorials]
* [[Inkscape SVG vs. plain SVG]]
* [[Output format requirements]] - what's needed to save in some formats
* [[Effect requirements]] - what's needed to use some effects
* [[Effect reference]] - what each effect does
* [[Connector tool tutorial]]
* [[Installing fonts]]
* [[Emergency save]] - recovery in case Inkscape crashed
* [[Release notes]]
** for version [[Release notes/0.91|0.91]] (active development)
** '''for version [[Release notes/0.48.5|0.48.5]] (current release)'''
** older versions: [[Release notes/0.48.4|0.48.4]] [[Release notes/0.48.3|0.48.3]], [[Release notes/0.48.2|0.48.2]], [[Release notes/0.48.1|0.48.1]], [[Release notes/0.48|0.48]], [[Release notes/0.47|0.47]]
* [[Announcing Releases]]
* [[Tricks and tips]] - miscellaneous advice, may be slightly outdated

|style="width:33%;background-color: #E6E6E6; padding:.5em;"|

=== Help Inkscape Without Coding ===
* [[Bug management]]
* [[Testing]]
* [[Translation information]]
* [[Editing Inkscape's website|Website]]
* [[Inkscape Classes]]
* [[Conferences]]
* [[Marketing Scratchpad]]

* [[HelpWanted]]
* [[BugTriageProjects]]
* [[CreatingDists]]: how to build packages
* [[StableBranchUpdates]]
* [[UpdatingTrackerItems]]
* [[TutorialsAndHelp]]
* [[How_To_Start_A_Page]] how to use the wiki
* [[CreatingScreencasts]]
* [[AboutScreenContest]]
|}

{| cellspacing="0" style="width: 100%; background-color: white; border-width:1px; border-style:solid; border-color:#62C012; align:left; padding:11px 0em 0em 11px;"
|- style="vertical-align:top;"
| colspan="2"|

=== Developer Documentation ===
|- style="vertical-align:top;"
| style="width:50%;|
==== First Steps ====
* [[Working with Bazaar]] - How to obtain the source code. A quick start on how to use our version control system
* [[Compiling Inkscape|Compilation]]
* [[Using Eclipse]]
* [[Developer manual]] - various important information, be sure to read this before coding
* [[Debugging Inkscape|Debugging]] - random tips to help debug problems
* [[Project organization]] - procedures, hierarchy, developer roles and the likes
* [[Janitorial tasks]] - small tasks that need doing
* [[Doxygen documentation]]
* [[Working with SVN]] - besides the code in Bazaar, we still have some things in SVN.

==== Developer tutorials ====
* [[Architectural overview]] - a high-level look at Inkscape
* [[Preferences subsystem]] - creating and using preference values
* XML subsystem (WIP) - how to manipulate the XML representation of a document
* Display subsystem (WIP) - how to make things appear on the canvas
* Tools subsystem (WIP) - how to create a new tool
* [[Creating a new SPObject]]
* Extensions
** [[Extension subsystem]] - an overview of the functionality provided by extensions and the possible implementations
** [[Script extensions]]
** [[Python modules for extensions]] - some helpful routines for use in Python script extensions
* [[Creating Live Path Effects]]
* [[Boost shared pointers]]
* [[Using libsigc++ signals]]
* [[Windows development on Linux]]

==== Miscellaneous ====
* [[INX extension descriptor format]]
* [[Inkscape-specific XML attributes]] - documentation of attributes from Inkscape's XML namespace

* [[Extension repository]]: an Internet central for Inkscape Extensions
* [[Related programs]]

| style="width:50%;|
==== Continuous Integration (Automated testing) ====
* [http://jenkins.inkscape.org:8080 Our main testing website (Jenkins)]
* [[How to contribute to automated tests]]
* [[Jenkins server setup]]

==== Development Discussion ====
* [[Roadmap]]: the main todo list
* [[Dependencies]] - what libs are needed to build Inkscape
* [[C++11]] - What C++11 features can be used
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]]
* [[Coding Style|Coding Style Discussion]]
* [[FileTypes]]
* [[ApplicationIcons]] (Application + Interface)
* [[Icons]]
* [[InkscapeColor]]
* [[PrintingSubsystem]]
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite
* [[CSS Support]]
* [[Google Summer Of Code]]
* [[Improved Media Management]]
* [[UI MockupScreenshots]]
* [[Swatch Book]]
* [[Tablet Dialog]]
* [[ViewBoxToDo]] View box support info
* [[Caching]]
* [[UI and Document coordinates‎]]
* [[Mipmapping]]
* [[GtkMMification]]: replace C boilerplate with gtkmm objects

===Lib2Geom===
*[[lib2geom]]
*[[lib2geom Goals]]
*[[lib2geom FAQ]]
*[[lib2geom SVN Repository Guide]]
*[[WorkingWith2GeomFAQ]]: real-life questions answered about using 2Geom in real code
*[[lib2geom py2geom]]: python bindings to 2geom. With this you can use the power of 2geom in python scripts.

|- style="vertical-align:top;"
| style="width:50%;|
==== User Interface Discussion ====
* [[Translation_information]]
* [[AddingInterfaceVerbs]]
* [[AccessibleGraphics]]
* [[ObjectManager]]
* [[DialogsReorganization]]
* [[ModalInterfaces]]
* [[TextUsability]]: text tool /dialog dialog
* [[KeyboardShortcutsToDo]]
** [[KeyboardProfiles]]: how you can help
* [[StatusbarAPI]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]

| style="width:50%; |
|}

* [[WikiAttic]]: pages that are no longer relevant but kept for historical value

__NOTOC__

[[Category:About Inkscape]]
[[Category:User Documentation]]

Jenkins server setup

2014-11-12T19:29:20Z

Johanengelen: /* Jenkins */

Jenkins server setup

2014-11-12T19:25:40Z

Johanengelen: Created page with " == Installed software == The software that was installed on our Ubuntu testing server (jenkins.inkscape.org). apt-get install emacs24-nox =====Inkscape build dependenci..."

Inkscape

2014-11-12T19:20:49Z

Johanengelen: /* Development Discussion */

This is a freeform area for Inkscape development and discussion.
Curious about [[WikiSyntax]]?

Other languages: [[Inkscape en español|Wiki en español]], [[L'Inkscape en Català|Wiki en Català]], [[Inkscape em Português|Wiki em Português]], [[Startseite|Wiki auf deutsch]]...

{| cellspacing="11" style="width:100%;"
|-style="vertical-align:top;"
| style="width:33%;background-color: #E6E6E6; padding:.5em;"|
=== Project Info ===
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[Features of Inkscape|Features]]
* [[FAQ]] - Frequently Asked Questions
* [[Supported operating systems]]
* [[Tools]] - Supporting Tools and Applications
* [[Galleries]]
* [[Inkscape coverage|Coverage]] - Awards, articles, presentations, books about Inkscape
* [[Inkscape popularity|Popularity]]
* [[Contact information]] - the developers' e-mails and SVN nicknames
* [[InkscapeInvariants|Inkscape's Mission]]
* [[CommunicationChannels|Communication Channels]]: how to reach us
* [[AnnouncementToSodipodi|Announcement To Sodipodi]]: this started it all
* [[Branding]]
* [[ContactInfo|Contact Information]]: who's behind Inkscape
* [[Travel Reimbursement Policy]]

|style="width:33%;;background-color: white; padding:.5em;"|

=== User Documentation ===
* [[Installing Inkscape|Installation]]
* [[International and Local Communities]]
* [[Inkscape glossary]]
* [[User manual information]] - where to find the free Inkscape manual and how to contribute to it
* [http://inkscape.org/doc/ Tutorials]
* [[Inkscape SVG vs. plain SVG]]
* [[Output format requirements]] - what's needed to save in some formats
* [[Effect requirements]] - what's needed to use some effects
* [[Effect reference]] - what each effect does
* [[Connector tool tutorial]]
* [[Installing fonts]]
* [[Emergency save]] - recovery in case Inkscape crashed
* [[Release notes]]
** for version [[Release notes/0.91|0.91]] (active development)
** '''for version [[Release notes/0.48.5|0.48.5]] (current release)'''
** older versions: [[Release notes/0.48.4|0.48.4]] [[Release notes/0.48.3|0.48.3]], [[Release notes/0.48.2|0.48.2]], [[Release notes/0.48.1|0.48.1]], [[Release notes/0.48|0.48]], [[Release notes/0.47|0.47]]
* [[Announcing Releases]]
* [[Tricks and tips]] - miscellaneous advice, may be slightly outdated

|style="width:33%;background-color: #E6E6E6; padding:.5em;"|

=== Help Inkscape Without Coding ===
* [[Bug management]]
* [[Testing]]
* [[Translation information]]
* [[Editing Inkscape's website|Website]]
* [[Inkscape Classes]]
* [[Conferences]]
* [[Marketing Scratchpad]]

* [[HelpWanted]]
* [[BugTriageProjects]]
* [[CreatingDists]]: how to build packages
* [[StableBranchUpdates]]
* [[UpdatingTrackerItems]]
* [[TutorialsAndHelp]]
* [[How_To_Start_A_Page]] how to use the wiki
* [[CreatingScreencasts]]
* [[AboutScreenContest]]
|}

{| cellspacing="0" style="width: 100%; background-color: white; border-width:1px; border-style:solid; border-color:#62C012; align:left; padding:11px 0em 0em 11px;"
|- style="vertical-align:top;"
| colspan="2"|

=== Developer Documentation ===
|- style="vertical-align:top;"
| style="width:50%;|
==== First Steps ====
* [[Working with Bazaar]] - How to obtain the source code. A quick start on how to use our version control system
* [[Compiling Inkscape|Compilation]]
* [[Using Eclipse]]
* [[Developer manual]] - various important information, be sure to read this before coding
* [[Debugging Inkscape|Debugging]] - random tips to help debug problems
* [[Project organization]] - procedures, hierarchy, developer roles and the likes
* [[Janitorial tasks]] - small tasks that need doing
* [[Doxygen documentation]]
* [[Working with SVN]] - besides the code in Bazaar, we still have some things in SVN.

==== Developer tutorials ====
* [[Architectural overview]] - a high-level look at Inkscape
* [[Preferences subsystem]] - creating and using preference values
* XML subsystem (WIP) - how to manipulate the XML representation of a document
* Display subsystem (WIP) - how to make things appear on the canvas
* Tools subsystem (WIP) - how to create a new tool
* [[Creating a new SPObject]]
* Extensions
** [[Extension subsystem]] - an overview of the functionality provided by extensions and the possible implementations
** [[Script extensions]]
** [[Python modules for extensions]] - some helpful routines for use in Python script extensions
* [[Creating Live Path Effects]]
* [[Boost shared pointers]]
* [[Using libsigc++ signals]]
* [[Windows development on Linux]]

==== Miscellaneous ====
* [[INX extension descriptor format]]
* [[Inkscape-specific XML attributes]] - documentation of attributes from Inkscape's XML namespace

* [[Extension repository]]: an Internet central for Inkscape Extensions
* [[Related programs]]

| style="width:50%;|
==== Continuous Integration (Automated testing) ====
* [http://jenkins.inkscape.org Our main testing website (Jenkins)]
* [[How to contribute to automated tests]]
* [[Jenkins server setup]]

==== Development Discussion ====
* [[Roadmap]]: the main todo list
* [[Dependencies]] - what libs are needed to build Inkscape
* [[C++11]] - What C++11 features can be used
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]]
* [[Coding Style|Coding Style Discussion]]
* [[FileTypes]]
* [[ApplicationIcons]] (Application + Interface)
* [[Icons]]
* [[InkscapeColor]]
* [[PrintingSubsystem]]
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite
* [[CSS Support]]
* [[Google Summer Of Code]]
* [[Improved Media Management]]
* [[UI MockupScreenshots]]
* [[Swatch Book]]
* [[Tablet Dialog]]
* [[ViewBoxToDo]] View box support info
* [[Caching]]
* [[UI and Document coordinates‎]]
* [[Mipmapping]]
* [[GtkMMification]]: replace C boilerplate with gtkmm objects

===Lib2Geom===
*[[lib2geom]]
*[[lib2geom Goals]]
*[[lib2geom FAQ]]
*[[lib2geom SVN Repository Guide]]
*[[WorkingWith2GeomFAQ]]: real-life questions answered about using 2Geom in real code
*[[lib2geom py2geom]]: python bindings to 2geom. With this you can use the power of 2geom in python scripts.

|- style="vertical-align:top;"
| style="width:50%;|
==== User Interface Discussion ====
* [[Translation_information]]
* [[AddingInterfaceVerbs]]
* [[AccessibleGraphics]]
* [[ObjectManager]]
* [[DialogsReorganization]]
* [[ModalInterfaces]]
* [[TextUsability]]: text tool /dialog dialog
* [[KeyboardShortcutsToDo]]
** [[KeyboardProfiles]]: how you can help
* [[StatusbarAPI]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]

| style="width:50%; |
|}

* [[WikiAttic]]: pages that are no longer relevant but kept for historical value

__NOTOC__

[[Category:About Inkscape]]
[[Category:User Documentation]]

Hackfest2015

2014-09-15T20:28:59Z

Johanengelen: /* Action items */

This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.

Last updated: 2014-08-24
Meeting notes 2014-09-15 http://inkscape.org/en/paste/392/

== Description ==

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.

== Date ==

We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015) at the end of April 2015. Fill in the dates of that event here when available.

== Schedule ==

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

== Venue ==

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.

== Area ==

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.

== Stay ==

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.

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** News item with clear marking of who sponsored the event

== Action items ==

Please take yourself off the list if you've completed one.

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Bryce
| Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| Get a list of companies using inkscape
|-
| 15 sep 2014
| Tav
| Summarize and mail devlist
|}

== Brainstorm area ==
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 (maximum one day) 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.
* Strategy and implementation for SVG 2 fallbacks.
* Future work discussions (/not/ coding), for example:
** plugins.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===
We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub

Hackfest2015

2014-09-15T20:28:23Z

Johanengelen: /* Action items */

This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.

Last updated: 2014-08-24

== Description ==

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.

== Date ==

We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015) at the end of April 2015. Fill in the dates of that event here when available.

== Schedule ==

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

== Venue ==

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.

== Area ==

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.

== Stay ==

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.

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** News item with clear marking of who sponsored the event

== Action items ==

Please take yourself off the list if you've completed one.

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Karen Sandler (SFC)
|
|-
| 15 sep 2014
| Bryce
| Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| Get a list of companies using inkscape
|-
| 15 sep 2014
| Tav
| Summarize and mail devlist
|}

== Brainstorm area ==
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 (maximum one day) 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.
* Strategy and implementation for SVG 2 fallbacks.
* Future work discussions (/not/ coding), for example:
** plugins.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===
We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub

Hackfest2015

2014-09-15T20:27:20Z

Johanengelen: /* Action items */

This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.

Last updated: 2014-08-24

== Description ==

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.

== Date ==

We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015) at the end of April 2015. Fill in the dates of that event here when available.

== Schedule ==

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

== Venue ==

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.

== Area ==

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.

== Stay ==

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.

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** News item with clear marking of who sponsored the event

== Action items ==

I can ask Ruth if RH might have the budget and Cat at Google too

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Karen Sandler (SFC)
|
|-
| 15 sep 2014
| Bryce
| Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| Get a list of companies using inkscape
|}

== Brainstorm area ==
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 (maximum one day) 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.
* Strategy and implementation for SVG 2 fallbacks.
* Future work discussions (/not/ coding), for example:
** plugins.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===
We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub

Hackfest2015

2014-09-15T20:19:04Z

Johanengelen: add action items

This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.

Last updated: 2014-08-24

== Description ==

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.

== Date ==

We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015) at the end of April 2015. Fill in the dates of that event here when available.

== Schedule ==

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

== Venue ==

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.

== Area ==

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.

== Stay ==

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.

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** News item with clear marking of who sponsored the event

== Action items ==

== Brainstorm area ==
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 (maximum one day) 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.
* Strategy and implementation for SVG 2 fallbacks.
* Future work discussions (/not/ coding), for example:
** plugins.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===
We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub

Hackfest2015

2014-09-15T20:15:21Z

Johanengelen: /* Participants */

This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.

Last updated: 2014-08-24

== Description ==

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.

== Date ==

We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015) at the end of April 2015. Fill in the dates of that event here when available.

== Schedule ==

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

== Venue ==

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.

== Area ==

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.

== Stay ==

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.

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** News item with clear marking of who sponsored the event

== Brainstorm area ==
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 (maximum one day) 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.
* Strategy and implementation for SVG 2 fallbacks.
* Future work discussions (/not/ coding), for example:
** plugins.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===
We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub

Hackfest2015

2014-09-15T20:11:03Z

Johanengelen: /* Participants */

This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.

Last updated: 2014-08-24

== Description ==

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.

== Date ==

We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015) at the end of April 2015. Fill in the dates of that event here when available.

== Schedule ==

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

== Venue ==

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.

== Area ==

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.

== Stay ==

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.

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** News item with clear marking of who sponsored the event

== Brainstorm area ==
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 (maximum one day) 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.
* Strategy and implementation for SVG 2 fallbacks.
* Future work discussions (/not/ coding), for example:
** plugins.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===
Who do we expect to join, what kind of people? I (johan) have never been to a hackfest, and really have no clue :-)

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape?
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub

Hackfest2015

2014-09-15T20:08:04Z

Johanengelen: /* What are sponsors' interests? */

This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.

Last updated: 2014-08-24

== Description ==

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.

== Date ==

We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015) at the end of April 2015. Fill in the dates of that event here when available.

== Schedule ==

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

== Venue ==

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.

== Area ==

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.

== Stay ==

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.

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** News item with clear marking of who sponsored the event

== Brainstorm area ==
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 (maximum one day) 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.
* Strategy and implementation for SVG 2 fallbacks.
* Future work discussions (/not/ coding), for example:
** plugins.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===
Who do we expect to join, what kind of people? I (johan) have never been to a hackfest, and really have no clue :-)

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Users?
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
* Coders unfamiliar with Inkscape?
** Good programmers with experience?
** New programmers with little experience?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub

Hackfest2015

2014-09-15T20:02:57Z

Johanengelen: /* Sponsors */

This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.

Last updated: 2014-08-24

== Description ==

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.

== Date ==

We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015) at the end of April 2015. Fill in the dates of that event here when available.

== Schedule ==

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

== Venue ==

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.

== Area ==

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.

== Stay ==

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.

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

=== What are sponsors' interests? ===
If we know, we can offer them what they would want.

* PR among users
* Improving a product that they ship
* Improving a product that many of their employees use
* PR among coders

== Brainstorm area ==
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 (maximum one day) 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.
* Strategy and implementation for SVG 2 fallbacks.
* Future work discussions (/not/ coding), for example:
** plugins.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===
Who do we expect to join, what kind of people? I (johan) have never been to a hackfest, and really have no clue :-)

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Users?
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
* Coders unfamiliar with Inkscape?
** Good programmers with experience?
** New programmers with little experience?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub

Compiling Inkscape on Windows 64-bit

2014-09-10T19:28:05Z

Johanengelen: /* Known issues */

This is a work in progress. Please spend a few minutes improving this wiki page, thank you very very much!

== MinGW ==
Get MinGW 64-bit from here:
[http://mingw-w64.sourceforge.net/index.php MinGW-w64 on Sourceforge], taking the package from the Mingw-builds Project.

The version you need is POSIX with SJLJ exception handling, because inkscape-devlibs64 has been compiled with SJLJ exception handling, and POSIX is needed for C++11 thread capabilities.

Direct link to what I got: [http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z/download x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z]

== Devlibs 64 ==

Checkout lp:inkscape-devlibs64 into, e.g., c:\devlibs64.

Also see: [[Inkscape Devlibs 64-bit]]

== Building ==

set the paths correctly in mingwenv.bat! Specifically, I have:
IF "%DEVLIBS_PATH%"=="" set DEVLIBS_PATH=c:\devlibs64
IF "%MINGW_PATH%"=="" set MINGW_PATH=C:\mingw64\mingw64_posix

build using buildtool as usual, but with build-x64.xml:
btool -file build-x64.xml

== Known issues ==

Hackfest2015

2014-08-29T20:57:18Z

Johanengelen: /* Brainstorm area */

This page details the planning of an Inkscape Hackfest 2015 in Boston, Massachusetts, USA.

Last updated: 2014-08-24

== Description ==

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.

== Date ==

We hope to schedule the hackfast just after or just before the Libre Graphics Meeting 2015 (LGM2015) at the end of April 2015. Fill in the dates of that event here when available.

== Schedule ==

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

== Venue ==

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.

== Area ==

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.

== Stay ==

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.

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

== Brainstorm area ==
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 (maximum one day) 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 (/not/ coding), for example:
** plugins

For the drunk hacking sessions:
* fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===
Who do we expect to join, what kind of people? I (johan) have never been to a hackfest, and really have no clue :-)
* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Users?
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
* Coders unfamiliar with Inkscape?
** Good programmers with experience?
** New programmers with little experience?
We can make a list of possible tasks for each of these groups.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub

Hackfest2015

2014-08-29T20:48:06Z

Johanengelen: /* Brainstorm area */

Hackfest2015

2014-08-24T13:37:16Z

Johanengelen: /* Date */