Earlier this year we developed a policy for fundraising and for funding
development work on Inkscape. Thanks to everyone that helped on this!
Now that the policy is fully official I've given it a spot on our
(Martin and other web folks, feel free to move it around if there's a
better spot for it...)
The intent of this is to delegate power to community members to organize
fundraisers and use the gained monies for paid development.
This isn't the *only* way we can do fundraisers or paid development, but
other things will require more direct board involvement. Hopefully this
will give us a more streamlined approach that folks can take advantage
For item #4.2 of the FAQ ("Are there non-coding ways to help?")
under Help Fellow Users > Write Tutorials, I want to include info on how to
submit tutorials for the official documentation. Or at least provide a link
to such info. (Also, I might want to contribute tutorials myself.)
So far, all I've found is this page
http://wiki.inkscape.org/wiki/index.php/User_manual_information, which I'm
not sure is even a relevant doc anymore. It says to subscribe to the Inks
Docs mailing list, but other links are dead (not found).
Is there any other info, that I haven't found yet? Or is
subscribing to the list, pretty much all that's needed (and then tutorial
writers will find out how to submit them, from the mailing list)?
Thanks for your help :-)
I'm still working on updating the FAQ, and splitting into User FAQ
and Development FAQ. Could some one or more of you, please review the
following (regarding Linux and Mac issues) and suggest any corrections which
may be needed? Since I only use Windows, I can't be sure about them.
Bryce indicated that some of it might be tmi (in a previous
message). I can say that generally the Alt key in Linux, as well as all the
Mac issues, do come up frequently. So I'd like to keep them in there. But
if any of it can be deleted or consolidated, ....or even if you know of
additional issues, I certainly will trust your judgment.
3.10 and the 5 sub-sections (3.10.1 through 3.10.5)
3.17 and its 9 or 10 sub-sections (3.17.1 through 220.127.116.11)
which you can see on the website http://inkscape.org/en/learn/faq/ or in the
Since there is so much text, I've attached just those portions in a
separate html file, for your convenience. You may note some minor changes
between the current faq (on wiki and inkscape.org) and my file, already, but
it's nearly identical. And I'm asking about the content, not the html code.
It just seems like html would be the easiest way to provide it. Anyway, I
suspect it's probably fairly current and correct already, so it shouldn't
take long :-)
Thank you very much :-)
Trunk/experimental has the ability to change the "Document Unit" in the
Document Preferences dialog. Changing the unit changes 'lengths'
throughout the document. This process has quite a few problems as
demonstrated by the number of bugs reported. In order to get a handle on
these problems, I've started a Wiki page to track the issues and to get
an idea about possible solutions:
The problems are quite complex. The simplest solution for the short-term
(on the 0.91 release time scale) might be to just disable document unit
Please look at the page and add your comments, bugs, etc.
I am trying to open in Inkspace (Mac OS X v0.48) a SVG file (wolfd_4.svg)
that is a pixel perfect version of a PNG (wolf3d_4.png).
Chrome and Safari are able to render the image well (chrome_rendition.png
However when loaded in Inkspace (inkspace_rendition.png), I can see gaps
between the squares that are supposed to be pixels.
Is there any way to fix this ?
Safari Mac OS X v7.0.6 (9537.78.2)
Chrome Mac OS X v37.0.2062.94
The experimental branch has been using 96 pixels per inch per the CSS
2.1 standard for over two months now without complaint. Is there any
objection to switching trunk to this value? As Inkscape has switched to
using 'pt' for text size by default, it is important that this change
happen to ensure that the size of text rendered in browsers match the
size of text rendered in Inkscape.
I've here at Free Software Day (Boston) and have just completed a
panel on the economics of Free Software development. Something which
came up and something I want to have a serious discussion about is the
implementation of an opportunity to donate screen like libreOffice:
If one clicks on this link, it waits a few seconds and gives you the
file. But as well as the file it also offers you an opportunity to
donate/contribute to the project.
I'd like to implement this for inkscape.org but it would have to be
blessed by the community since other developers are users may have
valid concerns which should be taken into account with this format.
Things I'm thinking about:
* Making sure we have suggested amounts
* Offering something in return? Maybe offer an ability to buy swag?
* What is SFC's position on these kinds of pages?
* Have an invitation to contribute other things. Time, bug tracking etc?
* Give donators a badge on their website user?
I'm looking for any contribution to this discussion, good or bad.
Please let me know what you think.
Best Regards, Martin Owens
* Hackfest LGM
* Hackfest FOSDEM
* Updating FSA
* Mac OSX
A group of interested Inkscape developers met via IRC with Karen
Sandler, the Executive Director of the Software Freedom Conservancy
(SFC). The primary motive for the meeting was to discuss organizing a
hackfest in conjunction with the 2015 Libre Graphics Meeting (LGM) at
the end of April in Toronto.
If you are interested in participating, please add your name at:
We also briefly discussed updating the Fiscal Sponsorship Agreement
(FSA) and the Mac OSX port.
We will meet again next week at the same time (Monday 19:00 UTC, 21:00
CEST, 15:00 EDT, 12:00 PDT) at inkscape-devel on freenode.
Advantage: No extra travel required. Cheaper hotels, etc.?
Disadvantage: Need to find local host.
Advantage: There are many possible places to hold the hackfest.
Disadvantage: Extra travel to/from Toronto. US Visa requirements.
Possible place: MIT
* Martin is contacting LGM to see if they can help us find space.
What will Inkscape pay for?
Travel, accommodation, food for sponsored attendees?
Equipment? Video projector?
We need to decide who to sponsor. Probably 10, maybe up to 20 people.
Preferably those with a "job to do" and not just passers-by.
Code and documentation, see web page for ideas (and add your own).
We should outreach to new contributors; maybe have a training period
the first morning.
We discussed who might sponsor a hackfest (and why they might).
* Karen will inquire with RedHat and Google.
* Bryce will contact Samsung.
* Intel? Canonical?
* ScislaC will compile a list of companies using Inkscape.
It might be possible to have a "warm-up" hackfest at FOSDEM. Hacking
is one of the main activities at this conference and there should be no
problem finding space. FOSDEM 2015 is the weekend of 31 January/1
February in Brussels.
Updating the FSA
Before we started discussing the hackfest, we briefly discussed updating
our Fiscal Sponsorship Agreement (FSA) with SFC. Inkscape was one of the
first groups to join FSA and our FSA is a bit out-dated. There are at
least two places where changes are needed:
1. The SFC is financed by its members. Member groups are required to
give 10% of the funds they raise to the SFC. Inkscape's agreement
predates this requirement. The SFC would like to see Inkscape's FSA
brought into alignment. The Inkscape board has agreed in principle to
2. Inkscape needs an active board to successfully manage Inkscape's
resources. At the moment, board member serve until they resign or until
they are removed by a majority vote of the community members. It would
good to have a criteria for removing inactive board members without the
need for a potentially disruptive vote by the community members.
Karen and Bradley will be at the Google Summer of Code Mentor's meet-up
as will three Inkscape board members. This will be a good time to
finalize the new agreement.
We discussed the status of the native Mac OSX port and the possibility
of paying a developer to finish it off. The port is done but there seem
to be problems with the underlying libraries (Wayland or gtk+/quartz).