2015-08-20 16:46 GMT+02:00 Tavmjong Bah <tavmjong@...8...>:
Questions for the candidates:
The board's primary role has been to handle Inkscape's assets. How can
Inkscape's assets be used to grow the Inkscape community?
Our biggest assets are our brand, our existing community of users, and
the adoption of SVG on the Web. Probably the most important and high
profile case of such adoption is Wikimedia Commons.
To make users more involved with the project, I think the obvious
thing to do is reducing the barrier to entry for contributing. There
are many people in the community who don't know how to program, but
are excellent artists. A moderated repository of creative resources
(e.g. sets of symbols for the Symbol dialog, extensions, filter
presets, alternative icons, and so on) accessible through our website
would provide a simple entry point for new contributors. There should
be a way to browse and install these resources directly from Inkscape.
This is rather important - if we provide a way to conveniently share
resources via our website, many people might decide that licensing
their artwork under a permissive license is a reasonable price to pay
to be able to use them on every machine. Moderators of this repository
could be recruited from the community, so it would not require us to
spread our somewhat limited developer manpower even thinner.
We could introduce 'installers' for creative resources and extensions.
The current process of installing them is not very user friendly. It
should not be more difficult than double-clicking on a package.
Unfortunately, it would require someone to spend some development
cycles on Windows and OSX to make sure that these installers work
cross-platform.
From the development side of things, the best thing we can do for the
community is creating more extension points. The simple filter model
we have for extensions is very useful, but at the same time rather
limited. Some examples of new extension points would be:
* Complex filters with adjustable parameters. Right now one can create
a filter and set some parameters, but adjusting them afterwards
requires knowledge of the internals of the filter.
* Templates, especially procedurally generated ones. We already have a
'new from template' dialog that supports those.
* Live effects as extensions in a scripting language, such as Python.
This would require cleaning up the live effect API and bringing the
Python binding of 2Geom up to speed.
* Scripts. This requires the most initial work, but the payoff is
probably the biggest, and the feature is very useful even for people
who won't contribute anything to Inkscape.
Another issue I mentioned on the hackfest is domain-specific drawing
editors. I would classify this as a very long term goal. There is a
lot of demand for a vector drawing program that can be extended to
cover the needs of a specific community. For example, Inkscape could
be extended into a chemical structures editor or an UML editor. This
could be done either by better modularization, with those
domain-specific editors being standalone applications that link to
libinksomething.so, or by making Inkscape extensions sufficiently
powerful to allow such things.
Are there specific projects that you think the board should pursue?
How
would you contribute to them?
I have some experience with organizing large events; In 2012 I managed
a conference for chemical students with over 100 attendees. These
skills could be helpful when organizing hackfests or similar community
events.
I think the board could provide technical direction to Inkscape and
relieve some of our accumulated technical debt by funding specific
development tasks from general funds obtained from Patreon. AFAIU,
Patreon allows people to make a small recurring donation to an
organization or artist they like, but it's not tied to a specific
project. Kickstarter-style, project-oriented crowdsourcing could work
well for adding new exciting features, but we'll have to rely on
something else for maintenance stuff. I'm fairly good at code analysis
and design, and could handle the technical side of such an effort -
define goals for those maintenance projects, and if time permits also
implement some of them.
The long term funding goal should be to secure enough recurring
contributions to hire one or more full time developers, or at least
accumulate enough funds to hire a contractor for a longer period of
time.
Regards, Krzysztof