https://wiki.inkscape.org/wiki/api.php?action=feedcontributions&user=BryceHarrington&feedformat=atomInkscape Wiki - User contributions [en]2024-03-28T09:23:59ZUser contributionsMediaWiki 1.36.1https://wiki.inkscape.org/wiki/index.php?title=Sponsors_list&diff=119026Sponsors list2020-10-27T03:30:26Z<p>BryceHarrington: Removed per request of dealsland.</p>
<hr />
<div>{| class="wikitable"<br />
! Sponsor<br />
! Type<br />
! Link<br />
! Joined<br />
! Expires<br />
|-<br />
|Canonical Ltd.<br />
|Infrastructure Sponsor<br />
|https://www.canonical.com/<br />
|? (long ago)<br />
|Never (text may need to be adapted when we only use ppa)<br />
|-<br />
|CloudScale.ch<br />
|Infrastructure Sponsor (Hosting)<br />
|https://cloudscale.ch<br />
|2018-03-09<br />
|"this offer's not dollar or time limited" (bryce, board meeting 2018-01-05)<br />
|-<br />
|fastly.com<br />
|Infrastructure Sponsor (CDN)<br />
|https://fastly.com<br />
|2014-12-24<br />
|not as long as they sponsor us<br />
|-<br />
|GitLab Inc.<br />
|Infrastructure Sponsor (Code hosting)<br />
|https://gitlab.com<br />
|February 2017<br />
|not as long as we use their services<br />
|-<br />
|Oregon State University Open Source Lab<br />
|Infrastructure Sponsor (Hosting)<br />
|https://osuosl.org/<br />
|? (very long ago)<br />
|not as long as we use their services<br />
|-<br />
|Software Freedom Conservancy<br />
|Infrastructure Sponsor (Finances and Legal)<br />
|http://sfconservancy.org/<br />
|? (before January 2014)<br />
|not as long as we are a member<br />
|-<br />
|Private Internet Access<br />
|Platinum Sponsor<br />
|https://www.privateinternetaccess.com/<br />
|2017-09-13<br />
|2018-09-13<br />
|-<br />
|Advance Systems, Inc.<br />
|Silver Sponsor<br />
|https://advancesystemsinc.com/<br />
|2016-12-09<br />
|2017-12-09<br />
|-<br />
|Betrugstest.com<br />
|Silver Sponsor<br />
|https://www.betrugstest.com/<br />
|2017-09-13<br />
|2019-10-15<br />
|-<br />
|VectorStock<br />
|Platinum Sponsor<br />
|https://www.vectorstock.com/<br />
|2018-11-25<br />
|2019-11-25<br />
|-<br />
|Néréide<br />
|Bronze Sponsor<br />
|https://www.nereide.fr/<br />
|2018-12-06<br />
|2019-12-06<br />
|-<br />
|Association PiNG<br />
|Bronze Sponsor<br />
|<br />
|2017-09-19<br />
|2018-09-19</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Leadership_Committee_Status_Updates&diff=117427Leadership Committee Status Updates2020-02-07T17:48:28Z<p>BryceHarrington: </p>
<hr />
<div>== Place and Time ==<br />
<br />
We meet in #inkscape-devel on [https://freenode.net/ freenode]. You can also join the [https://chat.inkscape.org/channel/team_devel #team-devel discussion channel on chat.inkscape.org] to partake in the meeting.<br />
<br />
Board meetings are typically the first Friday of each month.<br />
<br />
<em>Everybody in the Inkscape community is invited to participate.</em><br />
<br />
Next meeting: [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200207T10&p1=202 10:00 PDT/18:00 UTC/19:00 CET, (click for world clock)], Fri., Febuary 7, 2020. (Time is fixed to 10 AM Pacific Time.)<br />
<br />
Meetings should be announced in advance on [https://lists.sourceforge.net/lists/listinfo/inkscape-devel inkscape-devel] and [https://lists.sourceforge.net/lists/listinfo/inkscape-board inkscape-board] mailing lists.<br />
<br />
== Agenda ==<br />
* Hackfests<br />
** LGM/Rennes Hackfest<br />
** Next Hackfest<br />
*** Possible places:<br />
***# Boston (MIT/FSF)<br />
***# Paris (Palaiseau - Télécom ParisTech)<br />
***# Kiel<br />
***# Québec City<br />
***# Brussels (FOSDEM, 2nd & 3rd February)<br />
***# ? (GUADEC, summer)<br />
<br />
* GSoC<br />
** We've applied. (Tav/Mc)<br />
<br />
* Developer development<br />
** Books<br />
<br />
* Budget<br />
<br />
* Bug migration off Launchpad<br />
<br />
* Infrastructure<br />
** mailing list migration off SourceForge<br />
** Wiki migration off OSUOSL<br />
** Weblate service deployment<br />
<br />
* Software Release status<br />
** 2geom 1.1<br />
** Inkscape 0.92.5<br />
** Inkscape 1.0rc<br />
<br />
* Other Business<br />
<br />
* Need someone to handle escalated complaints re CoC, since Krzysztof Kosiński has resigned. Hopefully someone with training or experience with conflict resolution or mediation. Not much time needed, probably would never happen, but need to be ready just in case. Currently it's vacant.<br />
<br />
* Discuss the possibility of having something like a jobs board on the new forum. Something similar to https://forum.inkscapecommunity.com/index.php?board=12.0 Would need strict rules to prevent misuse, spam, liability, etc.<br />
<br />
* License : move from GPLv2+ to GPLv3+ -- necessary because of planned new deps and change in old deps<br />
<br />
== Other Agenda Items ==<br />
<br />
=== Action Items ===<br />
* Future hackfests<br />
** Hackfest organizational tips (Need to document this someplace)<br />
*** Process: Have folks propose options, and then trade off cost projections and benefits<br />
*** Try to organize group lodging (same hotel, rented/air-bnb house, http://www.linuxhotel.de/community.en.html, etc.)<br />
*** Send a scout ahead of time to help avoid slummy accommodations<br />
*** Catered lunches help keep everyone focused (we're already reimbursing on lunches, so cost differential isn't huge, and it saves hassle all around)<br />
*** Boots on the ground at a location can be a huge help if plans go awry<br />
*** Prefer locations with local inkscape community on the ground<br />
<br />
* [https://inkscape.org/en/support-us/funded-development/ Funded development] [bryce]<br />
* Add a C++-11 conversion project with tasks detailed to the Roadmap for 0.93 or later. [valavanisalex]<br />
* Regularly check [[Sponsors_list|sponsor status]]<br />
<br />
== Blocked Action Items ==<br />
<br />
* Privacy Policy [drmo] ~ Blocked waiting on time availability by SFC<br />
* Amend CoC reporting section ~ Waiting until we have a dedicated email, e.g. abuse@inkscape.org<br />
<br />
<br />
== Board Meeting Transcripts == <br />
<br />
=== 2020 ===<br />
<br />
=== 2019 ===<br />
<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-12-06.log.html 2019-12-06]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-11-01.log.html 2019-11-01]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-10-04.log.html 2019-10-04]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-09-06.log.html 2019-09-06]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-08-03.log.html 2019-08-03]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-07-26.log.html 2019-07-26]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-07-12.log.html 2019-07-12]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-06-07.log.html 2019-06-07]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-05-03.log.html 2019-05-03]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-04-05.log.html 2019-04-05]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-03-01.log.html 2019-03-01]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-02-01.log.html 2019-02-01]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2019-01-04.log.html 2019-01-04]<br />
<br />
=== 2018 ===<br />
<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2018-12-07.log.html 2018-12-07]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2018-11-02.log.html 2018-11-02]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2018-10-05.log.html 2018-10-05]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2018-09-07.log.html 2018-09-07]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2018-08-03.log.html 2018-08-03]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2018-07-06.log.html 2018-07-06]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2018-06-01.log.html 2018-06-01]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2018-05-04.log.html 2018-05-04]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/2018-04-06.log.html 2018-04-06]<br />
* [https://alpha.inkscape.org/board/meetings/transcripts/board_meeting_2018-03-02.html 2018-03-02]<br />
* [https://inkscape.org/gallery/item/12009/ 2018-02-02]<br />
* [https://inkscape.org/gallery/item/11875/ 2018-01-05]<br />
<br />
=== 2017 ===<br />
<br />
* [https://inkscape.org/paste/11743/ 2017-12-01]<br />
* [https://inkscape.org/paste/11651/ 2017-11-03]<br />
* [https://inkscape.org/gallery/item/11517/ 2017-10-06]<br />
* [https://inkscape.org/gallery/item/11377/ 2017-09-01]<br />
* [https://inkscape.org/gallery/item/11250/ 2017-08-04]<br />
* [https://inkscape.org/gallery/item/11176/ 2017-07-07]<br />
* [https://inkscape.org/gallery/item/11064/ 2017-06-02]<br />
* [https://inkscape.org/gallery/item/10844/ 2017-04-07]<br />
* [https://inkscape.org/gallery/item/10740/ 2017-03-03]<br />
* [https://inkscape.org/gallery/item/10651/ 2017-02-03]<br />
* [https://inkscape.org/gallery/item/10582/ 2017-01-06]<br />
<br />
=== 2016 ===<br />
<br />
* [https://inkscape.org/gallery/item/10484/ 2016-12-02]<br />
* [https://inkscape.org/gallery/item/10241/ 2016-11-04]<br />
* [https://inkscape.org/gallery/item/9971/ 2016-09-02]<br />
* [https://inkscape.org/gallery/item/9864/ 2016-08-05]<br />
* [https://inkscape.org/gallery/item/9766/ 2016-07-08]<br />
* [https://inkscape.org/gallery/item/9667/ 2016-06-03]<br />
* [https://inkscape.org/gallery/item/9563/ 2016-05-06]<br />
* [https://inkscape.org/gallery/item/9565/ 2016-04-01]<br />
<br />
* [https://inkscape.org/gallery/item/7276/ 2016-01-08]<br />
<br />
=== 2015 ===<br />
<br />
* [https://inkscape.org/gallery/item/7056/ 2015-12-04]<br />
* [https://inkscape.org/gallery/item/6886/ 2015-11-06]<br />
* [https://inkscape.org/gallery/item/6701/ 2015-10-02]<br />
<br />
=== 2014 ===<br />
<br />
* [https://inkscape.org/gallery/item/2498/ 2014-11-26]<br />
* [https://inkscape.org/gallery/item/2216/ 2014-11-19]<br />
* [https://inkscape.org/gallery/item/2210/ 2014-11-12]<br />
* [https://inkscape.org/gallery/item/2204/ 2014-11-05]<br />
* [https://inkscape.org/gallery/item/1436/ 2014-10-15]<br />
* [https://inkscape.org/gallery/item/950/ 2014-10-08]<br />
* [https://inkscape.org/gallery/item/854/ 2014-09-29]<br />
* [https://inkscape.org/gallery/item/392/ 2014-09-15]<br />
<br />
'''[https://inkscape.org/en/gallery/=pastebin/?q=meeting&order=-edited Website search for all transcripts]'''</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114831Fundraising Ideas2019-05-01T00:30:18Z<p>BryceHarrington: /* Art auctions / sales */</p>
<hr />
<div>This file outlines some blue-sky brainstorming thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
Note that these are not vetted ideas - some may not be permissible under our non-profit designation. Others may be permitted but may be controversial (e.g. ads), however we're listing them here as food for thought.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $NNk<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $20 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* T-Shirts, Hats, Mugs, Buttons, Stickers, Hoodies, Polos, etc.<br />
** cafepress.com<br />
** teespring.com<br />
<br />
* High quality clothing.<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
<br />
== Art auctions / sales ==<br />
<br />
Ask artists to provide their work to the project, either as a full donation, or a split of the proceeds. Then auction signed prints or originals, and offer direct purchase of unsigned prints.<br />
<br />
Perhaps the artist can decide the % to direct to specific Inkscape feature(s) of their choice.<br />
<br />
== Printed version of manual ==<br />
<br />
* We have already been getting book royalties from Packt, could expand on that with new books?<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
<br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
== App Stores ==<br />
<br />
In App Stores, instead of providing the built software entirely for free, provide it for a Suggested Donation.<br />
<br />
* Homebrew<br />
+ Target all the funds to Mac support<br />
<br />
* Windows<br />
+ Target all the funds to Windows support<br />
<br />
* Steam Store<br />
<br />
In cases where the store does not provide a "Suggested Donation" option, consider listing it for a fee but emphasize that the same packages are also available from inkscape.org for no charge.<br />
<br />
== adsense Ads ==<br />
<br />
Simple text ads integrated into the website<br />
<br />
== Carbon Ads ==<br />
<br />
This is a devel/foss friendly advertising system.<br />
<br />
== Purchased Ads ==<br />
<br />
Certain pages of the website are devoted to specialized advertisements, provided to specific companies with relation to Inkscape.<br />
<br />
== Youtube Channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Affiliate Links ==<br />
<br />
SEO companies will pay for sponsorship to get dofollow links to their site.<br />
<br />
== Amazon Commission ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
= Services =<br />
<br />
== Service Raffle ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffle tickets for $20-50 each - keep it a little high so you don’t have to sell so many and so that the buyers have a higher chance of winning. Encourage people to buy several, by offering discounts for multiple purchases (1 for $20, 2 for $36, 3 for $50, etc.)<br />
<br />
Services can include:<br />
* creating logos<br />
* Business card design<br />
* Brochure design<br />
* Christmas or birthday cards<br />
* Graduation announcements<br />
<br />
<br />
== Design Service Broker ==<br />
<br />
Recruit our artists to do contracted design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, drawing, programming, proposal writing, etc. Charge $50-75 suggested donation per person, with a goal of 15 to 20 people. Record a video and provide it online for suggested donation.<br />
<br />
<br />
== Priority User Support ==<br />
<br />
For a recurring fee, we provide prioritized question answering by a seasoned Inkscape pro, up to a fixed number of hours per week.<br />
<br />
== Technical Support ==<br />
<br />
For a recurring fee, we provide access to a developer to help troubleshoot problems and work on selected bugs as directed by the client.<br />
<br />
<br />
== Custom Interface Spins ==<br />
<br />
We provide builds of Inkscape with some basic interface customizations, such as simplifying it by removing some unneeded functionality. The result is still covered under the GPL. We provide packaged versions for them to give their users or distribute with their product. For additional fee we also allow them to tweak the branding to some degree. We maintain the spin against current master, for an annual charge.<br />
<br />
<br />
== Custom Extensions ==<br />
<br />
We implement extensions customized to their particular service or product, that they can offer from their website, or include in copies of Inkscape they distribute themselves. The extension is covered as GPL, but can be licensed differently for additional fees.<br />
<br />
== Hosting Services ==<br />
<br />
We provide use of our infrastructure services to projects or companies for an arranged fee or sponsorship payment.<br />
* Mailing lists<br />
* DNS<br />
* @<project>.org email aliases<br />
* Cloud computing nodes<br />
* Build systems (Mac, Windows)<br />
<br />
= Sponsorship =<br />
<br />
* Sponsor cannot receive any substantial benefits in return, else it counts as unrelated business income (i.e. taxed at 15-45%).<br />
** E.g. if nonprofit promotes a sponsor's products and/or services it counts as advertising. [https://www.aemcpas.com/cpa-firm/news/Sponsorship-Advertising.html]<br />
** "Per IRS rules, nonprofits can acknowledge sponsors by mentioning or displaying the following: company name, company logo, product lines and contact information (address, phone number, web address)."<br />
** "Nonprofits are also permitted to mention slogans and value-neutral descriptions of a sponsor’s goods or services in acknowledging their support."<br />
** "In addition, nonprofits can display or distribute a sponsor’s products to the general public at the sponsored activity or event."<br />
** No: Coupons, endorsements, or comparison to sponsor's competitors<br />
<br />
<br />
== Website General Fund Sponsors ==<br />
<br />
Our regular sponsorship levels, with reward being placement on the sponsors web page.<br />
<br />
== Event Sponsors ==<br />
<br />
Funds go directly towards hackfest travel attendance, or attendance at LGM, SCALE, and other conferences. We will display their logo in our booth banners and handout materials.<br />
<br />
= Misc Other Ideas =<br />
<br />
* Sell your frequent flyer miles to friends or donate them to the organization for a raffle. Watch the rules of the airline on this, but some airlines let you give away miles, and you may be able to sell your miles as long as you don’t go through a mileage broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
* Certifications / online classes<br />
<br />
* Windows store as option for paid download.<br />
<br />
More ideas:<br />
* http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf<br />
* http://www.ianbicking.org/blog/2019/03/open-source-doesnt-make-money-by-design.html</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114826Fundraising Ideas2019-05-01T00:29:07Z<p>BryceHarrington: </p>
<hr />
<div>This file outlines some blue-sky brainstorming thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
Note that these are not vetted ideas - some may not be permissible under our non-profit designation. Others may be permitted but may be controversial (e.g. ads), however we're listing them here as food for thought.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $NNk<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $20 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* T-Shirts, Hats, Mugs, Buttons, Stickers, Hoodies, Polos, etc.<br />
** cafepress.com<br />
** teespring.com<br />
<br />
* High quality clothing.<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
<br />
== Art auctions / sales ==<br />
<br />
Ask artists to provide their work to the project, either as a full donation, or a split of the proceeds. Then auction signed prints or originals, and offer direct purchase of unsigned prints.<br />
<br />
<br />
== Printed version of manual ==<br />
<br />
* We have already been getting book royalties from Packt, could expand on that with new books?<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
<br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
== App Stores ==<br />
<br />
In App Stores, instead of providing the built software entirely for free, provide it for a Suggested Donation.<br />
<br />
* Homebrew<br />
+ Target all the funds to Mac support<br />
<br />
* Windows<br />
+ Target all the funds to Windows support<br />
<br />
* Steam Store<br />
<br />
In cases where the store does not provide a "Suggested Donation" option, consider listing it for a fee but emphasize that the same packages are also available from inkscape.org for no charge.<br />
<br />
== adsense Ads ==<br />
<br />
Simple text ads integrated into the website<br />
<br />
== Carbon Ads ==<br />
<br />
This is a devel/foss friendly advertising system.<br />
<br />
== Purchased Ads ==<br />
<br />
Certain pages of the website are devoted to specialized advertisements, provided to specific companies with relation to Inkscape.<br />
<br />
== Youtube Channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Affiliate Links ==<br />
<br />
SEO companies will pay for sponsorship to get dofollow links to their site.<br />
<br />
== Amazon Commission ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
= Services =<br />
<br />
== Service Raffle ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffle tickets for $20-50 each - keep it a little high so you don’t have to sell so many and so that the buyers have a higher chance of winning. Encourage people to buy several, by offering discounts for multiple purchases (1 for $20, 2 for $36, 3 for $50, etc.)<br />
<br />
Services can include:<br />
* creating logos<br />
* Business card design<br />
* Brochure design<br />
* Christmas or birthday cards<br />
* Graduation announcements<br />
<br />
<br />
== Design Service Broker ==<br />
<br />
Recruit our artists to do contracted design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, drawing, programming, proposal writing, etc. Charge $50-75 suggested donation per person, with a goal of 15 to 20 people. Record a video and provide it online for suggested donation.<br />
<br />
<br />
== Priority User Support ==<br />
<br />
For a recurring fee, we provide prioritized question answering by a seasoned Inkscape pro, up to a fixed number of hours per week.<br />
<br />
== Technical Support ==<br />
<br />
For a recurring fee, we provide access to a developer to help troubleshoot problems and work on selected bugs as directed by the client.<br />
<br />
<br />
== Custom Interface Spins ==<br />
<br />
We provide builds of Inkscape with some basic interface customizations, such as simplifying it by removing some unneeded functionality. The result is still covered under the GPL. We provide packaged versions for them to give their users or distribute with their product. For additional fee we also allow them to tweak the branding to some degree. We maintain the spin against current master, for an annual charge.<br />
<br />
<br />
== Custom Extensions ==<br />
<br />
We implement extensions customized to their particular service or product, that they can offer from their website, or include in copies of Inkscape they distribute themselves. The extension is covered as GPL, but can be licensed differently for additional fees.<br />
<br />
== Hosting Services ==<br />
<br />
We provide use of our infrastructure services to projects or companies for an arranged fee or sponsorship payment.<br />
* Mailing lists<br />
* DNS<br />
* @<project>.org email aliases<br />
* Cloud computing nodes<br />
* Build systems (Mac, Windows)<br />
<br />
= Sponsorship =<br />
<br />
* Sponsor cannot receive any substantial benefits in return, else it counts as unrelated business income (i.e. taxed at 15-45%).<br />
** E.g. if nonprofit promotes a sponsor's products and/or services it counts as advertising. [https://www.aemcpas.com/cpa-firm/news/Sponsorship-Advertising.html]<br />
** "Per IRS rules, nonprofits can acknowledge sponsors by mentioning or displaying the following: company name, company logo, product lines and contact information (address, phone number, web address)."<br />
** "Nonprofits are also permitted to mention slogans and value-neutral descriptions of a sponsor’s goods or services in acknowledging their support."<br />
** "In addition, nonprofits can display or distribute a sponsor’s products to the general public at the sponsored activity or event."<br />
** No: Coupons, endorsements, or comparison to sponsor's competitors<br />
<br />
<br />
== Website General Fund Sponsors ==<br />
<br />
Our regular sponsorship levels, with reward being placement on the sponsors web page.<br />
<br />
== Event Sponsors ==<br />
<br />
Funds go directly towards hackfest travel attendance, or attendance at LGM, SCALE, and other conferences. We will display their logo in our booth banners and handout materials.<br />
<br />
= Misc Other Ideas =<br />
<br />
* Sell your frequent flyer miles to friends or donate them to the organization for a raffle. Watch the rules of the airline on this, but some airlines let you give away miles, and you may be able to sell your miles as long as you don’t go through a mileage broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
* Certifications / online classes<br />
<br />
* Windows store as option for paid download.<br />
<br />
More ideas:<br />
* http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf<br />
* http://www.ianbicking.org/blog/2019/03/open-source-doesnt-make-money-by-design.html</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114816Fundraising Ideas2019-04-29T21:59:07Z<p>BryceHarrington: </p>
<hr />
<div>This file outlines some blue-sky brainstorming thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
Note that these are not vetted ideas - some may not be permissible under our non-profit designation. Others may be permitted but may be controversial (e.g. ads), however we're listing them here as food for thought.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $NNk<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $20 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* T-Shirts, Hats, Mugs, Buttons, Stickers, Hoodies, Polos, etc.<br />
** cafepress.com<br />
<br />
* High quality clothing.<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
<br />
== Art auctions / sales ==<br />
<br />
Ask artists to provide their work to the project, either as a full donation, or a split of the proceeds. Then auction signed prints or originals, and offer direct purchase of unsigned prints.<br />
<br />
<br />
== Printed version of manual ==<br />
<br />
* We have already been getting book royalties from Packt, could expand on that with new books?<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
<br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
== App Stores ==<br />
<br />
In App Stores, instead of providing the built software entirely for free, provide it for a Suggested Donation.<br />
<br />
* Homebrew<br />
+ Target all the funds to Mac support<br />
<br />
* Windows<br />
+ Target all the funds to Windows support<br />
<br />
* Steam Store<br />
<br />
In cases where the store does not provide a "Suggested Donation" option, consider listing it for a fee but emphasize that the same packages are also available from inkscape.org for no charge.<br />
<br />
== adsense Ads ==<br />
<br />
Simple text ads integrated into the website<br />
<br />
== Carbon Ads ==<br />
<br />
This is a devel/foss friendly advertising system.<br />
<br />
== Purchased Ads ==<br />
<br />
Certain pages of the website are devoted to specialized advertisements, provided to specific companies with relation to Inkscape.<br />
<br />
== Youtube Channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Affiliate Links ==<br />
<br />
SEO companies will pay for sponsorship to get dofollow links to their site.<br />
<br />
== Amazon Commission ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
= Services =<br />
<br />
== Service Raffle ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffle tickets for $20-50 each - keep it a little high so you don’t have to sell so many and so that the buyers have a higher chance of winning. Encourage people to buy several, by offering discounts for multiple purchases (1 for $20, 2 for $36, 3 for $50, etc.)<br />
<br />
Services can include:<br />
* creating logos<br />
* Business card design<br />
* Brochure design<br />
* Christmas or birthday cards<br />
* Graduation announcements<br />
<br />
<br />
== Design Service Broker ==<br />
<br />
Recruit our artists to do contracted design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, drawing, programming, proposal writing, etc. Charge $50-75 suggested donation per person, with a goal of 15 to 20 people. Record a video and provide it online for suggested donation.<br />
<br />
<br />
== Priority User Support ==<br />
<br />
For a recurring fee, we provide prioritized question answering by a seasoned Inkscape pro, up to a fixed number of hours per week.<br />
<br />
== Technical Support ==<br />
<br />
For a recurring fee, we provide access to a developer to help troubleshoot problems and work on selected bugs as directed by the client.<br />
<br />
<br />
== Custom Interface Spins ==<br />
<br />
We provide builds of Inkscape with some basic interface customizations, such as simplifying it by removing some unneeded functionality. The result is still covered under the GPL. We provide packaged versions for them to give their users or distribute with their product. For additional fee we also allow them to tweak the branding to some degree. We maintain the spin against current master, for an annual charge.<br />
<br />
<br />
== Custom Extensions ==<br />
<br />
We implement extensions customized to their particular service or product, that they can offer from their website, or include in copies of Inkscape they distribute themselves. The extension is covered as GPL, but can be licensed differently for additional fees.<br />
<br />
== Hosting Services ==<br />
<br />
We provide use of our infrastructure services to projects or companies for an arranged fee or sponsorship payment.<br />
* Mailing lists<br />
* DNS<br />
* @<project>.org email aliases<br />
* Cloud computing nodes<br />
* Build systems (Mac, Windows)<br />
<br />
= Sponsorship =<br />
<br />
* Sponsor cannot receive any substantial benefits in return, else it counts as unrelated business income (i.e. taxed at 15-45%).<br />
** E.g. if nonprofit promotes a sponsor's products and/or services it counts as advertising. [https://www.aemcpas.com/cpa-firm/news/Sponsorship-Advertising.html]<br />
** "Per IRS rules, nonprofits can acknowledge sponsors by mentioning or displaying the following: company name, company logo, product lines and contact information (address, phone number, web address)."<br />
** "Nonprofits are also permitted to mention slogans and value-neutral descriptions of a sponsor’s goods or services in acknowledging their support."<br />
** "In addition, nonprofits can display or distribute a sponsor’s products to the general public at the sponsored activity or event."<br />
** No: Coupons, endorsements, or comparison to sponsor's competitors<br />
<br />
<br />
== Website General Fund Sponsors ==<br />
<br />
Our regular sponsorship levels, with reward being placement on the sponsors web page.<br />
<br />
== Event Sponsors ==<br />
<br />
Funds go directly towards hackfest travel attendance, or attendance at LGM, SCALE, and other conferences. We will display their logo in our booth banners and handout materials.<br />
<br />
= Misc Other Ideas =<br />
<br />
* Sell your frequent flyer miles to friends or donate them to the organization for a raffle. Watch the rules of the airline on this, but some airlines let you give away miles, and you may be able to sell your miles as long as you don’t go through a mileage broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
* Certifications / online classes<br />
<br />
* Windows store as option for paid download.<br />
<br />
More ideas:<br />
* http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf<br />
* http://www.ianbicking.org/blog/2019/03/open-source-doesnt-make-money-by-design.html</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Saarbr%C3%BCcken_Attendees&diff=114811Hackfest2019 Saarbrücken Attendees2019-04-29T21:07:21Z<p>BryceHarrington: /* People to Invite */</p>
<hr />
<div>Other pages: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 SCALE]]. <br />
<br />
Note: <br />
<br />
For the 27th and 28th, there can be no more than 20 persons in k8's office! If there are more, they would need to find a different place to meet (e.g. in a hotel room, or ask someone local).<br />
<br />
On 29th, those persons that staff the booth in the Open Source event can be discounted from the cap (currently 3).<br />
<br />
== Who is Attending? ==<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
|+ List of Attendees<br />
Hackfest<br />
|-<br />
! rowspan="2" | Who<br />
! rowspan="2" | Dates<br />
! rowspan="2" | Maximum Allocation<br />
! colspan="2" | Arrival<br />
! colspan="2" | Departure<br />
! rowspan="2" | Hotel<br />
|-<br />
! Date/Time<br />
! Detail<br />
! Date/Time<br />
! Detail<br />
|-<br />
| Tavmjong Bah <br />
| 5/27, 5/28, 5/29, 5/30, 6/1, (6/2)<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Thomas Holder<br />
| 5/27, 5/28, 5/29<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Jabier Arraiza<br />
| 5/27, 5/28, 5/29, 5/30, 6/1, 6/2<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Mihaela Jurković<br />
| 5/28 (?), 5/29, 5/30, 6/1, 6/2<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Marc Jeanmougin<br />
| <!-- dates --><br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Jürgen Weigert<br />
| 5/27, ?<br />
| TBD<br />
| <!-- arrival date + time --> 5/26<br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Tobias Ellinghaus<br />
| <!-- dates --><br />
| (no travel or accomodation assistance is needed)<br />
| local<br />
| <!-- arrival details, e.g. flight number --><br />
| local<br />
| <!-- departure details, e.g. flight number --><br />
| local<br />
|-<br />
| Cédric Gémy<br />
| <!-- dates --><br />
| TBD<br />
| <!-- arrival date + time --> 5/28 (evening)<br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Elisa de Castro Guerra<br />
| <!-- dates --><br />
| TBD<br />
| <!-- arrival date + time --> 5/28 (evening)<br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Boudewijn Rempt<br />
| <!-- dates --><br />
| (no travel or accomodation assistance is needed)<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| René de Hesselle<br />
| 5/27, 5/28, 5/29<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Max Gaukler<br />
| probably: 5/27, 5/28, 5/29<br />
| (no travel or accomodation assistance is needed)<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Alex Valavanis<br />
| 5/27, 5/28, 5/29<br />
| TBD<br />
| 5/26 1400 (Frankfurt)<br />
| LH943 (Manchester to Frankfurt)<br />
| 5/30 1650 (Frankfurt)<br />
| LH946 (Frankfurt to Manchester)<br />
| <!-- hotel --><br />
|-<br />
| Sample Person<br />
| <!-- dates --><br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-! Total<br />
!<br />
!<br />
! $ TBD<br />
!<br />
!<br />
!<br />
!<br />
!<br />
|}<br />
<br />
TBD: "To Be Determined"<br />
<br />
The Inkscape board has approved travel reimbursements of up to $2000 per person. Note: participants require the formality of a board vote.<br />
<br />
Separate allocations for:<br />
* Inkscape dinner, participants and guests (300€).<br />
* Snacks, etc. (100€).<br />
* Venue: Free.<br />
<br />
<sup>1</sup> Requires formality of board vote.<br />
<br />
== Unconfirmed but Likely Attendees ==<br />
<br />
* Alexandre Prokoudine (during LGM as visitor/guest)<br />
<br />
== Maybe ==<br />
<br />
* ede123 (Patrick)<br />
* Thomas Wiesner (@wiesi on gitlab, python console, attendence very unlikely)<br />
* Maren Hachmann<br />
<br />
== People to Invite ==<br />
<br />
* Shlomi Fish<br />
* Anatoly (@techtonik on gitlab)<br />
* Olli (https://gitlab.com/ollip)<br />
* Emmanuel Gil Peyrot (https://gitlab.com/linkmauve)<br />
* Khaled Hosny (font expert)<br />
* Antonio Hospite (https://gitlab.com/ao2)<br />
* Michael Soegtrop (https://gitlab.com/users/MSoegtrop)<br />
* Simon Wells (https://gitlab.com/xzcvczx)<br />
* Nicolas<br />
<br />
<br />
* Juan Duarte (see chat.inkscape.org) - invited for LGM via chat<br />
* Sebastian Wüst (plotting expert https://www.timewasters-place.com/) - invited via email<br />
<br />
<br />
* probono - invited via chat<br />
* Markus Schwienbacher - invited via gitlab<br />
* su_v - invited via email<br />
<br />
* <s>Sven Ebert (aka Dillerkind) - invited via forum</s><br />
* <s>Johan Engelen - invited via email, can't attend</s><br />
* <s>Martin Owens: can't attend</s><br />
* <s>Bryce Harrington: can't attend</s><br />
<br />
Possible others?<br />
* people on the mac-devel channel<br />
<br />
== Organizational info ==<br />
<br />
We need to report the rough number of attendees to k8 by mid<br />
May.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Saarbr%C3%BCcken_Attendees&diff=114806Hackfest2019 Saarbrücken Attendees2019-04-29T21:06:58Z<p>BryceHarrington: /* Maybe */ Apologies - I'm starting a new job and won't be able to attend</p>
<hr />
<div>Other pages: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 SCALE]]. <br />
<br />
Note: <br />
<br />
For the 27th and 28th, there can be no more than 20 persons in k8's office! If there are more, they would need to find a different place to meet (e.g. in a hotel room, or ask someone local).<br />
<br />
On 29th, those persons that staff the booth in the Open Source event can be discounted from the cap (currently 3).<br />
<br />
== Who is Attending? ==<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
|+ List of Attendees<br />
Hackfest<br />
|-<br />
! rowspan="2" | Who<br />
! rowspan="2" | Dates<br />
! rowspan="2" | Maximum Allocation<br />
! colspan="2" | Arrival<br />
! colspan="2" | Departure<br />
! rowspan="2" | Hotel<br />
|-<br />
! Date/Time<br />
! Detail<br />
! Date/Time<br />
! Detail<br />
|-<br />
| Tavmjong Bah <br />
| 5/27, 5/28, 5/29, 5/30, 6/1, (6/2)<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Thomas Holder<br />
| 5/27, 5/28, 5/29<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Jabier Arraiza<br />
| 5/27, 5/28, 5/29, 5/30, 6/1, 6/2<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Mihaela Jurković<br />
| 5/28 (?), 5/29, 5/30, 6/1, 6/2<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Marc Jeanmougin<br />
| <!-- dates --><br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Jürgen Weigert<br />
| 5/27, ?<br />
| TBD<br />
| <!-- arrival date + time --> 5/26<br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Tobias Ellinghaus<br />
| <!-- dates --><br />
| (no travel or accomodation assistance is needed)<br />
| local<br />
| <!-- arrival details, e.g. flight number --><br />
| local<br />
| <!-- departure details, e.g. flight number --><br />
| local<br />
|-<br />
| Cédric Gémy<br />
| <!-- dates --><br />
| TBD<br />
| <!-- arrival date + time --> 5/28 (evening)<br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Elisa de Castro Guerra<br />
| <!-- dates --><br />
| TBD<br />
| <!-- arrival date + time --> 5/28 (evening)<br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Boudewijn Rempt<br />
| <!-- dates --><br />
| (no travel or accomodation assistance is needed)<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| René de Hesselle<br />
| 5/27, 5/28, 5/29<br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Max Gaukler<br />
| probably: 5/27, 5/28, 5/29<br />
| (no travel or accomodation assistance is needed)<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-<br />
| Alex Valavanis<br />
| 5/27, 5/28, 5/29<br />
| TBD<br />
| 5/26 1400 (Frankfurt)<br />
| LH943 (Manchester to Frankfurt)<br />
| 5/30 1650 (Frankfurt)<br />
| LH946 (Frankfurt to Manchester)<br />
| <!-- hotel --><br />
|-<br />
| Sample Person<br />
| <!-- dates --><br />
| TBD<br />
| <!-- arrival date + time --><br />
| <!-- arrival details, e.g. flight number --><br />
| <!-- departure date + time --><br />
| <!-- departure details, e.g. flight number --><br />
| <!-- hotel --><br />
|-! Total<br />
!<br />
!<br />
! $ TBD<br />
!<br />
!<br />
!<br />
!<br />
!<br />
|}<br />
<br />
TBD: "To Be Determined"<br />
<br />
The Inkscape board has approved travel reimbursements of up to $2000 per person. Note: participants require the formality of a board vote.<br />
<br />
Separate allocations for:<br />
* Inkscape dinner, participants and guests (300€).<br />
* Snacks, etc. (100€).<br />
* Venue: Free.<br />
<br />
<sup>1</sup> Requires formality of board vote.<br />
<br />
== Unconfirmed but Likely Attendees ==<br />
<br />
* Alexandre Prokoudine (during LGM as visitor/guest)<br />
<br />
== Maybe ==<br />
<br />
* ede123 (Patrick)<br />
* Thomas Wiesner (@wiesi on gitlab, python console, attendence very unlikely)<br />
* Maren Hachmann<br />
<br />
== People to Invite ==<br />
<br />
* Shlomi Fish<br />
* Anatoly (@techtonik on gitlab)<br />
* Olli (https://gitlab.com/ollip)<br />
* Emmanuel Gil Peyrot (https://gitlab.com/linkmauve)<br />
* Khaled Hosny (font expert)<br />
* Antonio Hospite (https://gitlab.com/ao2)<br />
* Michael Soegtrop (https://gitlab.com/users/MSoegtrop)<br />
* Simon Wells (https://gitlab.com/xzcvczx)<br />
* Nicolas<br />
<br />
<br />
* Juan Duarte (see chat.inkscape.org) - invited for LGM via chat<br />
* Sebastian Wüst (plotting expert https://www.timewasters-place.com/) - invited via email<br />
<br />
<br />
* probono - invited via chat<br />
* Markus Schwienbacher - invited via gitlab<br />
* su_v - invited via email<br />
<br />
* <s>Sven Ebert (aka Dillerkind) - invited via forum</s><br />
* <s>Johan Engelen - invited via email, can't attend</s><br />
* <s>Martin Owens: can't attend</s><br />
<br />
Possible others?<br />
* people on the mac-devel channel<br />
<br />
== Organizational info ==<br />
<br />
We need to report the rough number of attendees to k8 by mid<br />
May.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114746Fundraising Ideas2019-04-23T01:54:23Z<p>BryceHarrington: /* Digital */</p>
<hr />
<div>This file outlines some blue-sky brainstorming thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
Note that these are not vetted ideas - some may not be permissible under our non-profit designation. Others may be permitted but may be controversial (e.g. ads), however we're listing them here as food for thought.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $NNk<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $20 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* T-Shirts, Hats, Mugs, Buttons, Stickers, Hoodies, Polos, etc.<br />
** cafepress.com<br />
<br />
* High quality clothing.<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
<br />
== Art auctions / sales ==<br />
<br />
Ask artists to provide their work to the project, either as a full donation, or a split of the proceeds. Then auction signed prints or originals, and offer direct purchase of unsigned prints.<br />
<br />
<br />
== Printed version of manual ==<br />
<br />
* We have already been getting book royalties from Packt, could expand on that with new books?<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
<br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
== App Stores ==<br />
<br />
In App Stores, instead of providing the built software entirely for free, provide it for a Suggested Donation.<br />
<br />
* Homebrew<br />
+ Target all the funds to Mac support<br />
<br />
* Windows<br />
+ Target all the funds to Windows support<br />
<br />
* Steam Store<br />
<br />
In cases where the store does not provide a "Suggested Donation" option, consider listing it for a fee but emphasize that the same packages are also available from inkscape.org for no charge.<br />
<br />
== adsense Ads ==<br />
<br />
Simple text ads integrated into the website<br />
<br />
== Carbon Ads ==<br />
<br />
This is a devel/foss friendly advertising system.<br />
<br />
== Purchased Ads ==<br />
<br />
Certain pages of the website are devoted to specialized advertisements, provided to specific companies with relation to Inkscape.<br />
<br />
== Youtube Channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Affiliate Links ==<br />
<br />
SEO companies will pay for sponsorship to get dofollow links to their site.<br />
<br />
== Amazon Commission ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
= Services =<br />
<br />
== Service Raffle ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffle tickets for $20-50 each - keep it a little high so you don’t have to sell so many and so that the buyers have a higher chance of winning. Encourage people to buy several, by offering discounts for multiple purchases (1 for $20, 2 for $36, 3 for $50, etc.)<br />
<br />
Services can include:<br />
* creating logos<br />
* Business card design<br />
* Brochure design<br />
* Christmas or birthday cards<br />
* Graduation announcements<br />
<br />
<br />
== Design Service Broker ==<br />
<br />
Recruit our artists to do contracted design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, drawing, programming, proposal writing, etc. Charge $50-75 suggested donation per person, with a goal of 15 to 20 people. Record a video and provide it online for suggested donation.<br />
<br />
<br />
== Priority User Support ==<br />
<br />
For a recurring fee, we provide prioritized question answering by a seasoned Inkscape pro, up to a fixed number of hours per week.<br />
<br />
== Technical Support ==<br />
<br />
For a recurring fee, we provide access to a developer to help troubleshoot problems and work on selected bugs as directed by the client.<br />
<br />
<br />
== Custom Interface Spins ==<br />
<br />
We provide builds of Inkscape with some basic interface customizations, such as simplifying it by removing some unneeded functionality. The result is still covered under the GPL. We provide packaged versions for them to give their users or distribute with their product. For additional fee we also allow them to tweak the branding to some degree. We maintain the spin against current master, for an annual charge.<br />
<br />
<br />
== Custom Extensions ==<br />
<br />
We implement extensions customized to their particular service or product, that they can offer from their website, or include in copies of Inkscape they distribute themselves. The extension is covered as GPL, but can be licensed differently for additional fees.<br />
<br />
== Hosting Services ==<br />
<br />
We provide use of our infrastructure services to projects or companies for an arranged fee or sponsorship payment.<br />
* Mailing lists<br />
* DNS<br />
* @<project>.org email aliases<br />
* Cloud computing nodes<br />
* Build systems (Mac, Windows)<br />
<br />
= Sponsorship =<br />
<br />
* Sponsor cannot receive any substantial benefits in return, else it counts as unrelated business income (i.e. taxed at 15-45%).<br />
** E.g. if nonprofit promotes a sponsor's products and/or services it counts as advertising. [https://www.aemcpas.com/cpa-firm/news/Sponsorship-Advertising.html]<br />
** "Per IRS rules, nonprofits can acknowledge sponsors by mentioning or displaying the following: company name, company logo, product lines and contact information (address, phone number, web address)."<br />
** "Nonprofits are also permitted to mention slogans and value-neutral descriptions of a sponsor’s goods or services in acknowledging their support."<br />
** "In addition, nonprofits can display or distribute a sponsor’s products to the general public at the sponsored activity or event."<br />
** No: Coupons, endorsements, or comparison to sponsor's competitors<br />
<br />
<br />
== Website General Fund Sponsors ==<br />
<br />
Our regular sponsorship levels, with reward being placement on the sponsors web page.<br />
<br />
== Event Sponsors ==<br />
<br />
Funds go directly towards hackfest travel attendance, or attendance at LGM, SCALE, and other conferences. We will display their logo in our booth banners and handout materials.<br />
<br />
= Misc Other Ideas =<br />
<br />
* Sell your frequent flyer miles to friends or donate them to the organization for a raffle. Watch the rules of the airline on this, but some airlines let you give away miles, and you may be able to sell your miles as long as you don’t go through a mileage broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
More ideas:<br />
* http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf<br />
* http://www.ianbicking.org/blog/2019/03/open-source-doesnt-make-money-by-design.html</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Free_Desktop_Graphic_Suite&diff=114731Free Desktop Graphic Suite2019-04-19T04:35:04Z<p>BryceHarrington: </p>
<hr />
<div>Common interface for graphic programs on the free desktop.<br />
<br />
Many artists use several applications in their workflow.<br />
This includes using one program for photo editing, one for illustration and one for page layout.<br />
To ease the user experience for someone using these apps, consistency in wording, looks and similar working tools needs to be adressed.<br />
<br />
The three programs that will be adressed are:<br />
* GNU Image Manipulator Program aka GIMP (bitmap image editing)<br />
* Inkscape (scalable graphics illustration) <br />
* Scribus (page layout)<br />
<br />
== [[Common dialogs]] ==<br />
<br />
== [[Tool consistency]] ==<br />
<br />
== Resources that can be shared: ==<br />
* Patterns (PNGs)<br />
* Gradients (SVGs)<br />
* Palettes (We need a standard here.) (suggestion: .xml format, based on .ai format (each text line with each colour name and its rgb, cmyk or whatever))<br />
* Clipart (SVG/PNG)<br />
:: We need some kind of universal, portable and standard svg rendering engine that can cope with InkscapeSvg. I think the ability to know that your source svg looks fine in the GIMP or several other programs on anyone else's computer would encourage people to use it a lot more (and would leapfrog the Adobe formats). It would also mean that when you used a vector image in another program you wouldn't have to rasterise it, so output would be better quality. [[User:Legio noctis|Legio noctis]] 14:56, 31 March 2010 (UTC) <br />
* Icons<br />
* Cursors <br />
* Color Management<br />
* Fonts<br />
* Symbols<br />
* Filters<br />
<br />
To help manage these resources it would probably be wise to try and incorporate some kind of Thumbnail Browser into any such suite. Unfortunately there is no obvious choice of cross platform and open source Thumbnail browser.<br />
<br />
:: Could all the open source projects agree on one location to store all these resources or links to them e.g. <tt>~/.graphicsresources</tt> or <tt> %appdata%\Graphic resources\</tt>?<br />
<br />
Could this system be turned into a new open source project/standard of its own? For example, say we called it something like 'Pixelshare', for lack of a graphic-y sounding name. We could then say that every Pixelshare-supporting program makes sure that a <tt>Pixelshare resources</tt> folder has been established. This would then contain a set directory structure, e.g. there could be a database (XML?) of the various programs/files/whatever is needed for efficient operation. For example:<br />
<tt><br />
/cursors<br /><br />
/icons<br /><br />
/images<br /><br />
: /Inkscape<br /><br />
::...insert here either actual files, shortcuts to files or database of files...<br /><br />
: /GIMP<br /><br />
information.xml<br /><br />
/sound<br /><br />
/videos<br /> <br />
</tt><br />
<br />
I suggest information.xml contains metadata about the programs, what they produce, formats etc, and the (potential) database inside the <tt>Inkscape</tt> folder actually contains information such as location of the image, when it was last opened, by what, created, by what, notes attached to it, whether it is a derivative of another file in the database etc.<br />
<br />
I will try to return to this page and expand on my ideas more solidly. Someone had a grand vision creating this page, and I don't want to see it come to nothing. [[User:Legio noctis|Legio noctis]] 18:27, 1 April 2010 (UTC)<br />
<br />
== A file sharing toolbar ==<br />
<br />
Some mockups:<br />
<br />
Standard toolbar:<br />
<br />
[[File:Opengraphics_toolbar_mockup_1.png|800px]]<br />
<br />
Toolbar with 'send to another application' menu open:<br />
<br />
[[File:Opengraphics_toolbar_mockup_2.png|800px]]<br />
<br />
Toolbar with 'my collections' menu open:<br />
<br />
[[File:Opengraphics_toolbar_mockup_3.png|800px]]<br />
<br />
Mini toolbar:<br />
<br />
[[File:Opengraphics_toolbar_mockup_4.png|800px]]<br />
<br />
Is this feasible? [[User:Legio noctis|Legio noctis]] 15:12, 31 March 2010 (UTC)<br />
<br />
== [[Feature Requests]] ==<br />
<br />
There are many features in the GIMP that Inkscape will want to copy such as the Dock Widgets for managing Palettes. <br />
<br />
There are also some enhancements to the GIMP like this [http://bugzilla.gnome.org/show_bug.cgi?id=133030 request for a standard toolbar] that would be helpful for Inkscape users. <br />
<br />
'''Links'''<br />
* [http://www.nabble.com/Desktop-f822.html Open Source Desktop Forum] - a large forum hosted by [http://www.nabble.com Nabble] on big open source desktop projects such as [http://www.nabble.com/Gnome-f1226.html Gnome], [http://www.nabble.com/Xfce-f830.html Xfce], [http://www.nabble.com/Rox-f827.html Rox], [http://www.nabble.com/Etoile-f823.html Etoile].<br />
<br />
* [http://software.newsforge.com/software/05/02/02/215259.shtml?tid=75&tid=131&tid=132 Article on free graphics software integration]<br />
<br />
* [http://www.osnews.com/story.php?news_id=9658 '''Achieving higher consistency between OSS graphics applications''' - Bryce Harringtons article on the issue]<br />
<br />
* [http://developer.gnome.org/projects/gup/hig/2.0/ Gnome Human Interface Guidelines]<br />
<br />
* [http://usability.kde.org/ KDE Usability project]<br />
<br />
* http://www.openusability.org/<br />
<br />
* http://www.freedesktop.org/<br />
<br />
* http://developer.gimp.org/standards.html<br />
<br />
* [http://www.freedesktop.org/wiki/Standards_2ficon_2dtheme_2dspec Unified icon spec on freedesktop.org]<br />
<br />
* http://openclipart.org/<br />
<br />
<br />
=== The Open Publishing Tools Organization (OPTO) ===<br />
<br />
This idea comes out of a discussion online with MRDOCS, about the need for Open Publishing Tools to unite and develop some sort of presence so that printers understand that there are other tools that are being used, other than QUARK, PHOTOSHOP, ILLUSTRATOR, and INDESIGN. There are other issues too that need to be dealt with, such as PANTONE's monopoly over the color industry. A project idea that OPTO could commission is/are open swatchbooks, which could be sold for the price of printing them (standard color formulas for printers) and could be downloaded as PDF files as well.<br />
<br />
Initial Applications that would fall under OPTO:<br />
<br />
* Scribus<br />
* Ghostscript<br />
* Inkscape<br />
* CUPS<br />
* [[The_Gimp]]<br />
* GIMP-Print<br />
<br />
==== Open Swatches ====<br />
<br />
pastels, grays, coated, uncoated, Web, sheetfed, Web Offset, metallics<br />
<br />
<br />
==== Font Management Software (like suitcase or atm) ====<br />
<br />
It should be relatively easy to slap together a GTK+ frontend for fontconfig that will allow the management of fonts, loading of new permanent and temporary fonts for a system, and then run 'fc-cache' to update a desktop to the new fonts installed. This is very necessary for designers whom work with MANY fonts and need to be able to load new ones without restarting their system. Commandline is not the most user-friendly for this type of task.<br />
<br />
Scribus, has a capability to package up all the images and layout files into a separate directory, which can then be tarred. Would be nice if the fonts could be managed in a compatible fashion. Already, packaging fonts is in the Scribus tracker as a request.<br />
<br />
For everyday installing, this is not needed with KDE, as of 3.2 it has KIOslave for fonts: fonts:// linked to ~/.fonts and a previewer for individual font faces. It works really well. Gnome has fontilus, but I have less experience with it. <br />
<br />
Perhaps focus should be on packaging with files ([[The_Gimp]] and other image files, Inkscape files and Scribus layouts) and making it easy to restore, files and fonts on other machines..<br />
<br />
Scribus has added preliminary support for [[The_Gimp]] integration in 29022004 1.2cvs. This allows a user to launch [[The_Gimp]] to edit an image from within Scribus and edit the file with return to Scribus after saving changes. Would be a nice option for Inkscape. <br />
<br />
--mrdocs<br />
<br />
See Also:<br />
* [[ScribusInteroperability]]<br />
* [[Related programs]]<br />
* [[InkscapeColor]]<br />
* [[OpenClipart]]<br />
<br />
[[Category:Developer Discussion]]<br />
[[Category:Needs Work]]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=New_feature_proposals&diff=114721New feature proposals2019-04-19T04:30:10Z<p>BryceHarrington: /* Review Inkscape RFE's and SodiPodi's Tasks */</p>
<hr />
<div>{{Outdated}}<br />
=== Proposals for New Features ===<br />
<br />
'''Please think twice when you edit this page: we use Launchpad's [https://blueprints.launchpad.net/inkscape/ blueprints] for all this now.'''<br />
<br />
This page is for links to pages describing concepts, proposals, and specs for new features, major architectural changes, large scale codebase refactorings, etc. As they are implemented, these links should be moved to more appropriate areas of the Wiki.<br />
The idea here is to enable everyone to hash out requirements and design of a potential new feature in detail prior to implementation. See also: <br />
<br />
[[Developer manual]] and [[Roadmap]].<br />
* [[User:Davidhewitt|Bottom Toolbar update proposal]]: Outlines my proposal for a UI facelift for the Bottom Tool bar. Also introduces a new mode of operation for the palette itself.<br />
* [[User:Bats|A user's list of suggestions/wishes]]: I recently finished a web project using Inkscape (mainly). This is a list of the things I wished it had, the things I liked but wanted to tweak and other observations as I was working. Perhaps it will help the programmers to see what a designer sees. I hope.<br />
* [[InkscapeNeeds]]<br />
* [[FeatureNotePad]]: use this for small notes and enhancement ideas, or for temporarily dumping feature requests (e.g. from mailing lists) before they are thought over, categorized, and put into pages of their own<br />
<br />
* <ins>[DONE]</ins> <del>[[DirectoryReorgProposal]]</del><br />
* <ins>[DONE]</ins> <del>[[NonRecursiveMakefile]]</del><br />
* [[NewTools]]<br />
* [[NetworkedEditing]]<br />
* [[SharingDefs]]: Not exactly new, but need conversion/upgrade.<br />
* [[AdvancedFileAccess]]<br />
* [[DocumentLayers]]<br />
* [[PlugIns]]: This could be script ideas as well.<br />
* [[HUD]]: Putting HUDs on the sp-canvas.<br />
* [[PathOps]]<br />
* [[InfoPalette]]<br />
* [[ColorPalette]]<br />
* [[UnitConversion]]<br />
* [[ScriptingLanguages]]: And options for handling extensibility.<br />
* [[TestingFramework]]: Creating testing framework.<br />
* [[PreferencesDialog]]<br />
* [[BreadthFirstUndo]]<br />
* [[CadInteroperability]]<br />
* [[FontKerning]]<br />
* [[PathfinderPalette]]<br />
* [[PreserveOverTransform]]<br />
* [http://users.pandora.be/blendix/verse/ GimpInteraktion]<br />
* [[ClipTemplates]]: SVG templates.<br />
* [[StockLibraryInterface]]<br />
* [[Cairoification]]: Replace SVG renderer.<br />
* [[OpenPublishingToolsOrganization]]<br />
* [[HelpMenu]]<br />
* [[FormObject]]<br />
* [[AST]]<br />
* [[SpellCheckForTextNodes]]<br />
* [[XML repair]]: Service for broken or weird files<br />
* [[MoreUsableWorkingFolders]]<br />
* [[SplitPaneUI]] View<br />
* [[Pre-installed gradients]]<br />
* [[rotate group of path points(knots)]]<br />
* [[Searching within Inkscape]]<br />
* [[UsingTheConnectorTool]]: (Various improvements to the Connector tool).<br />
* [[PureSVG]]: SVG that plays well with others.<br />
* [[Image links manager]]: A UI for better management of image links.<br />
* [[Clip Enhancements]]: Clip function extended to become a container object.<br />
* [[A better Bucket Fill tool fill]] : Suggestions for a better bucket fill tool that does not leave gaps and empty corner areas.<br />
<br />
=== Review Inkscape RFE's and [[SodiPodi]]'s Tasks ===<br />
<br />
Please review the following links, extract ideas, and develop them further for inclusion and discussion on this WIKI page.<br />
<br />
* [http://sourceforge.net/tracker/?group_id=93438&atid=604309 Inkscape RFE's]<br />
* [http://sourceforge.net/projects/sodipodi Sodipodi on Sourceforge]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=New_feature_proposals&diff=114716New feature proposals2019-04-19T04:29:57Z<p>BryceHarrington: The sodipodi website seems to have bitrotted; the url points to an adult website now</p>
<hr />
<div>{{Outdated}}<br />
=== Proposals for New Features ===<br />
<br />
'''Please think twice when you edit this page: we use Launchpad's [https://blueprints.launchpad.net/inkscape/ blueprints] for all this now.'''<br />
<br />
This page is for links to pages describing concepts, proposals, and specs for new features, major architectural changes, large scale codebase refactorings, etc. As they are implemented, these links should be moved to more appropriate areas of the Wiki.<br />
The idea here is to enable everyone to hash out requirements and design of a potential new feature in detail prior to implementation. See also: <br />
<br />
[[Developer manual]] and [[Roadmap]].<br />
* [[User:Davidhewitt|Bottom Toolbar update proposal]]: Outlines my proposal for a UI facelift for the Bottom Tool bar. Also introduces a new mode of operation for the palette itself.<br />
* [[User:Bats|A user's list of suggestions/wishes]]: I recently finished a web project using Inkscape (mainly). This is a list of the things I wished it had, the things I liked but wanted to tweak and other observations as I was working. Perhaps it will help the programmers to see what a designer sees. I hope.<br />
* [[InkscapeNeeds]]<br />
* [[FeatureNotePad]]: use this for small notes and enhancement ideas, or for temporarily dumping feature requests (e.g. from mailing lists) before they are thought over, categorized, and put into pages of their own<br />
<br />
* <ins>[DONE]</ins> <del>[[DirectoryReorgProposal]]</del><br />
* <ins>[DONE]</ins> <del>[[NonRecursiveMakefile]]</del><br />
* [[NewTools]]<br />
* [[NetworkedEditing]]<br />
* [[SharingDefs]]: Not exactly new, but need conversion/upgrade.<br />
* [[AdvancedFileAccess]]<br />
* [[DocumentLayers]]<br />
* [[PlugIns]]: This could be script ideas as well.<br />
* [[HUD]]: Putting HUDs on the sp-canvas.<br />
* [[PathOps]]<br />
* [[InfoPalette]]<br />
* [[ColorPalette]]<br />
* [[UnitConversion]]<br />
* [[ScriptingLanguages]]: And options for handling extensibility.<br />
* [[TestingFramework]]: Creating testing framework.<br />
* [[PreferencesDialog]]<br />
* [[BreadthFirstUndo]]<br />
* [[CadInteroperability]]<br />
* [[FontKerning]]<br />
* [[PathfinderPalette]]<br />
* [[PreserveOverTransform]]<br />
* [http://users.pandora.be/blendix/verse/ GimpInteraktion]<br />
* [[ClipTemplates]]: SVG templates.<br />
* [[StockLibraryInterface]]<br />
* [[Cairoification]]: Replace SVG renderer.<br />
* [[OpenPublishingToolsOrganization]]<br />
* [[HelpMenu]]<br />
* [[FormObject]]<br />
* [[AST]]<br />
* [[SpellCheckForTextNodes]]<br />
* [[XML repair]]: Service for broken or weird files<br />
* [[MoreUsableWorkingFolders]]<br />
* [[SplitPaneUI]] View<br />
* [[Pre-installed gradients]]<br />
* [[rotate group of path points(knots)]]<br />
* [[Searching within Inkscape]]<br />
* [[UsingTheConnectorTool]]: (Various improvements to the Connector tool).<br />
* [[PureSVG]]: SVG that plays well with others.<br />
* [[Image links manager]]: A UI for better management of image links.<br />
* [[Clip Enhancements]]: Clip function extended to become a container object.<br />
* [[A better Bucket Fill tool fill]] : Suggestions for a better bucket fill tool that does not leave gaps and empty corner areas.<br />
<br />
=== Review Inkscape RFE's and [[SodiPodi]]'s Tasks ===<br />
<br />
Please review the following links, extract ideas, and develop them further for inclusion and discussion on this WIKI page.<br />
<br />
* [http://sourceforge.net/tracker/?group_id=93438&atid=604309 Inkscape RFE's]<br />
* http://sourceforge.net/projects/sodipodi Sodipodi on Sourceforge]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Projects&diff=114711Projects2019-04-19T04:22:28Z<p>BryceHarrington: /* Other Misc. Ideas */</p>
<hr />
<div><br />
{{DevDiscussion}}<br />
<br />
This page lists proposed ideas for projects to improve Inkscape. The original list is from Krzysztof Kosiński. Consider it a permanent work-in-progress "brainstorm" list and feel free to add your own comments and project proposals. None of these are "official" and have not been thoroughly reviewed/debated and so may or may not fit with actual development plans.<br />
<br />
== General Codebase ==<br />
<br />
=== Migrate argument parsing to GOption and remove the dependency on popt ===<br />
<br />
Write test cases for this bug, so that the patches can be accepted into GLib:<br />
https://bugzilla.gnome.org/show_bug.cgi?id=522131<br />
If this proves hard, simply apply the patch to the devlibs. Once this<br />
is done, port argument parsing to GOption.<br />
<br />
=== Improve Icon Cache ===<br />
<br />
Convert the icon cache (icon.cpp) to create the PNGs with a directory<br />
structure and index file matching the icon theme specification. Use<br />
this to get rid of customized classes InkAction, SPIcon, and so on. ''Partially Done''<br />
<br />
=== Object Printing ===<br />
<br />
Replace the print functions in the SPxxx classes with a generic "Visitor" pattern and port the different export types (e.g. EMF, PDF, PS) to the new routines.<br />
<br />
=== Janitorial Work ===<br />
<br />
Clean up all unnecessary castings in C++ classes. Remove unnecessary use of "this". Etc.<br />
<br />
=== Code Review ===<br />
<br />
In depth code reviews of submitted patches. This is done by some other projects with great success. It speeds up getting patches committed which encourages contributions. It can also be a good learning experience.<br />
<br />
=== Rename s/SP/Ink/ ===<br />
<br />
Various functions and variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers). Renaming s/SP/Ink/ would be ok if there aren't better ideas. This is most prevalent in the object tree, which may or may not be worth changing, but everything that is not part of the object tree should definitely be converted.<br />
<br />
=== Retire Garbage Collector ===<br />
<br />
We use the Boehm garbage collector, but for smart pointers we can use<br />
support in C++-11 now, so most likely any Inkscape-specific gc code can<br />
probably go. Analyze where this code is, what uses it, and how to port<br />
it to use standard code, then delete our gc bits<br />
<br />
<br />
<br />
== Object Tree ==<br />
<br />
=== Robust ID handling refactoring ===<br />
<br />
Currently ID clash resolution is implemented as a giant switch over object types, listing every possible dependency. Replace this with virtual methods on objects, which provide information on what each object refers to. Improve behavior when a dependency of an object is deleted, and when IDs are changed / deleted from the XML editor.<br />
<br />
See id-class.cpp for specifics.<br />
<br />
<span style="color:blue">It should be possible to change ID and have<br />
Inkscape update all references. It should also not be automatically<br />
created for all objects. Tav</span><br />
<br />
priority: Longer term<br />
<br />
=== SAX parser ===<br />
Convert the current document parser from DOM to SAX, so that it<br />
creates our XML tree right away, instead of creating the libxml2 DOM<br />
tree, creating our tree to match it, then freeing the libxml2 tree.<br />
This should improve performance and allow more robust fixes for some<br />
problems.<br />
<br />
priority: Longer term<br />
<br />
=== Typed XML tree ===<br />
<br />
Improve XML tree so that it can store some attributes in parsed,<br />
binary form. The main target of this are the data URIs used to embed<br />
images, which could be stored as binary data only. This work should be<br />
done after completing task 3 (SAX parser), as this will make it<br />
easier.<br />
<br />
priority: Longer term<br />
<br />
=== XML Refactoring ===<br />
Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.<br />
<br />
=== Layer visibility performance improvement ===<br />
<br />
Right now, toggling layer visibility causes massive changes in the display tree, because the entire toggled layer is invalidated at the XML level. This results in very bad performance for an action which should be nearly instantaneous. Improve the control flow so that only the visibility of the object representing the layer is turned off, but the remainder of the display and object tree is left alone.<br />
<br />
priority: Longer term<br />
<br />
== Interface ==<br />
<br />
<br />
=== GTK 3 on Windows ===<br />
<br />
<strike><br />
Rebuild the Windows devlibs so that they contain GTK3 Make the<br />
Windows port work with them, possibly sending the appropriate patches<br />
to the GTK maintainers.<br />
</strike><br />
<br />
Status: Packaging work is completed, but bugs remain needing resolved.<br />
priority: Nearer term<br />
<br />
=== Context menu improvements ===<br />
<br />
Provide actions which are actually relevant in the context menu,<br />
depending on the context of the selection. Examples of such actions<br />
include: release mask, release clipping path, put text on path, embed<br />
/ extract image, unflow text, and so on.<br />
<br />
priority: Longer term<br />
<br />
=== Page size editing on the canvas ===<br />
<br />
Provide a way to edit the page size directly on the canvas, using a<br />
manipulator similar to the rectangle, instead of keying in numbers<br />
in the Document Properties dialog.<br />
<br />
priority: Longer term<br />
<br />
[[File:on_canvas.png]]<br />
<br />
=== On-canvas tool controls ===<br />
<br />
More tool controls could be available on-canvas right by the object <br />
being edited. An example of this would be having some of the text <br />
tool controls available right by where text editing is happening <br />
akin to what GIMP provides.<br />
<br />
priority: Longer term<br />
<br />
=== Numeric input on the canvas ===<br />
<br />
Right-clicking on nodes should bring up a numeric entry box which<br />
would allow you to specify its position numericaly. This could allow<br />
us to phase out some of the controls on the top bar. For dynamic<br />
offsets, the numeric entry would simply be the width of the offset<br />
<br />
priority: Longer term<br />
<br />
=== Unify document and desktop coordinates ===<br />
<br />
Change the desktop coordinates to match document coordinates. Make it<br />
so that document coordinates are specified in the coordinate system of<br />
the toplevel SVG element, so that it is possible to emulate other<br />
coordinate systems using a suitable transform attribute or viewBox.<br />
<br />
priority: Longer term<br />
<br />
=== Shape manipulators ===<br />
<br />
The idea here is to rewrite shape tools in the same paradigm as the<br />
node tool. Instead of storing all information about the shape in knots<br />
which differ only by their callbacks, allow to store information in a<br />
higher-level manipulator object. This would enable things like<br />
dragging the side of a rectangle and consistent outlining / update<br />
preferences for all shapes.<br />
<br />
priority: Longer term<br />
<br />
=== Improve the performance of layer visibility ===<br />
<br />
Right now, toggling layer visibility causes massive changes in the<br />
display tree, because the entire toggled layer is invalidated at the<br />
XML level. This results in very bad performance for an action which<br />
should nearly instantaneous. Improve the control flow so that only the<br />
visibility of the object representing the layer is turned off, but the<br />
remainder of the display and object tree is leaved alone.<br />
<br />
priority: Longer term<br />
<br />
=== Multi-page Documents ===<br />
We have a solid plan on how to do this without special svg 2.0 spec and<br />
it's technically pretty simple, involving layers and the way we currently<br />
specify layer type. It's a project which would attract a lot of<br />
attention, even if at first the support didn't include saving the<br />
pages to pdf or other such documents.<br />
<br />
priority: Nearer term<br />
<br />
=== Swatch Dialog ===<br />
<br />
Tomasz's GSoC project involved creation of a swatch dialog. It needs polished and landed.<br />
<br />
=== Gtk3/UI panels fixing ===<br />
<br />
=== Interface Design Guidelines ===<br />
* Take a holistic approach to UI design ([http://sourceforge.net/p/inkscape/mailman/message/33080043/ Original email])<br />
*# Analyze the existing UI, make a list of UI decisions that are inconsistent between each other.<br />
*# Look around, see how other project solves these things, figure out what's good/applicable for Inkscape (like designing particular custom widgets that are less pixel-hungry etc.).<br />
*# Design some sort of HIG (Human Interface Guidelines) for Inkscape<br />
*# Use it to plan redesigns existing dialogs/docks.<br />
*# Preserve dialog layouts between sessions<br />
<br />
== SVG Support ==<br />
<br />
<span style="color: green"><br />
=== [https://inkscape.org/en/projects/svg2-compliant-flowed-text/ SVG-compliant flowed text (FPRJ-003)] ===<br />
<br />
Move the existing flowed text XML representation into an svg:switch<br />
and provide an alternative fallback representation with SVG 1.1 text<br />
objects only.<br />
<br />
This should be done via SVG 2 CSS text wrapping<br />
which provides a simple SVG 1.1 fallback mechanism.</span><br />
<br />
priority: Short term<br />
owner: Tav<br />
<br />
<br />
=== Vector effects ===<br />
<br />
Refactor live path effects so that their XML representation matches<br />
that of SVG 2.0 vector effects. Put them in switches, so that the<br />
output is not limited to a single path. Integrate them better with<br />
core Inkscape. For instance, instead of four actions: inset, outset,<br />
dynamic offset, linked offset, there should be only one: offset. Using<br />
it on a normal path would create a dynamic offset, while using it on a<br />
clone would create a linked offset. The same principle would apply to<br />
vector effects: creating them on a normal path would move the path to<br />
defs and replace it with the vector effect, while creating them on<br />
clones would delete the clone and create a reference to the original<br />
path.<br />
<br />
Update: Vector effects will be dropped from SVG 2 but we can still refactor<br />
our own code to make it easier to use.<br />
<br />
priority: Longer term<br />
<br />
=== Better support for linked SVG images ===<br />
<br />
Create the document and rendering tree for linked SVG images. Use<br />
Inkscape's renderer instead of relying on the librsvg loader to avoid<br />
inconsistencies. Allow importing the linked image as a group via the<br />
context menu.<br />
<br />
There are two main conceptual ways of dealing with linked svg files, one is to treat svg files as 'bitmaps' using our own renderer to generate a bitmap and placing it inside much like we do with including outside png, jpeg files. This has implications involving exporting png with mismatched resolutions and pdf where text and vector elements are no longer vector in the output pdf.<br />
<br />
The second method is to treat the svg as an advanced 'clone' which has it's own defs section. This would preserve the vector nature of the included svg file and allow rendering via pdf and png to happen without much exception. The implications of this have not been thought through completely.<br />
<br />
priority: Medium term<br />
<br />
=== SVG 2 ===<br />
<br />
<span style="color:blue">Mesh gradients, hatches, etc. See [[SVG2|SVG2 page]]. Tav</span><br />
* [[SVG2]] support (with proper SVG 1.1 fallbacks)<br />
* Improve support for SVG switches: the first recognized element in a switch should appear directly in the SP tree, not as a child of the switch element.<br />
<br />
== Paths ==<br />
<br />
=== Rewrite of Geom::PathVector and Geom::Path ===<br />
<br />
Change PathVector to be a real object instead of a std::vector of<br />
Path, so that it can have useful methods, similar to curves.<br />
<br />
Move the copy-on-write idiom to the PathVector object, rather than<br />
using it in the Path.<br />
<br />
Investigate whether it is possible to store subpath data in a more<br />
compact way and make the Curve objects only convenience facades. Right<br />
now, if the path has only linear segments, every point is stored<br />
twice.<br />
<br />
Apply the following renames to match SVG terminology:<br />
*Path -> Subpath<br />
*PathVector -> Path<br />
<br />
priority: Longer term<br />
<br />
=== Boolean operations and stroking ===<br />
<br />
Add methods to PathVector objects:<br />
<br />
a) Set operators (& | - ^), which perform the relevant boolean<br />
operation on the paths. Use the algorithm from CGAL or devise a new<br />
robust algorithm.<br />
<br />
b) stroke(double line_width, LineJoin join, LineCap cap, double<br />
miter_limit), which performs the stroke-to-path operation.<br />
<br />
c) stroke(double line_width, LineJoin join, LineCap cap, double<br />
miter_limit, std::vector<double> const &dasharray), which performs<br />
stroke-to-path with dashing.<br />
<br />
priority: Longer term<br />
<br />
=== Remove SPCurve (refactoring) ===<br />
<br />
SPCurve is a thin wrapper around Geom::PathVector which exists for<br />
historical reasons. Its functionality should be added to PathVector,<br />
and SPCurve should be purged.<br />
<br />
priority: Medium term term<br />
<br />
=== Fill out arcs functionality ===<br />
<br />
<span style="color:blue">For accurate path Boolean operations with<br />
elliptical arcs, allow arcs in PathVectors and support Boolean<br />
operations between arcs and between elliptical arcs and S-Basis<br />
curves. Tav</span><br />
<br />
This is functionality that probably should be done in lib2geom.<br />
<br />
priority: Longer term<br />
<br />
=== Remove All Transforms from an SVG ===<br />
May be useful for aniation and CSS.<br />
<br />
=== PDF Cleanup Functionality ===<br />
* PDF cleanup function - ungroup everything, remove all unnecessary clipping and masking<br />
<br />
<br />
== Fonts ==<br />
<br />
=== Re-vamp our font management subsystem ===<br />
<br />
Need to be able to refresh when new fonts are installed.<br />
(The new gtk3 fonts dialog seems able to refresh itself.<br />
<br />
A 'refresh' button somewhere in the UI could address this, but if there<br />
are signals from the system, or a watcher process, that might make it<br />
more seamless.<br />
<br />
=== variable fonts usability/UX ===<br />
<br />
=== filters UI usability/UX ===<br />
<br />
== Print ==<br />
<br />
=== Color Management ===<br />
<br />
Analyze what users require for CMYK and other aspects of color management,<br />
including a review of what other software does, and what can currently be<br />
done with Inkscape. Examine off the shelf code that could be used (e.g. libcms).<br />
Define what needs implemented in Inkscape's dependencies (e.g. libcairo) vs.<br />
what can or must be done in Inkscape itself. Outline project(s) to implement<br />
the needed changes.<br />
See [[Color_management]].<br />
<br />
* Improve support for CMYK/spot colors<br />
** Minor UI streamlining<br />
** Eliminate the CMS tab<br />
** Change the CMYK tab to allow selecting the CMYK colors directly<br />
** Allow setting the document to CMYK, which sets a global CMYK profile<br />
** Stores RGB colors as RGB, CMYK colors as CMYK<br />
<br />
<br />
priority: short term<br />
<br />
== Animation ==<br />
<br />
There are several distinct types of animation workflows and objectives, such as:<br />
<br />
* CSS/SMIL animation - tweening/easing formulas for individual elements, aiming at e.g web display.<br />
* Sequential animation - each layer is a static frame that can be played back with a time delay, and recorded to a video stream<br />
* Keyframe animation - layers represent points on a timeline with objects whose states change through some interpolation mechanism<br />
* Javascript?<br />
<br />
While the intent, output, and UI for these may vary, the underlying machinery supporting them may have commonality, so the following projects may apply to one or more of the above types of animation.<br />
<br />
=== Object interpolation display ===<br />
<br />
Create routines to morph the properties and/or style of an object according to some proportion (such as elapsed time over a time period).<br />
<br />
This will need modification of object structures to support the animation attributes, following the SMIL and CSS animation specifications.<br />
<br />
contact: Tav<br />
priority: Medium term<br />
<br />
=== Object animation property editor UI/UX design ===<br />
<br />
Conceptualize how users would add and edit animation properties in Inkscape. What should be done in dialogs vs. in the main interface?<br />
Mockup ideas for how the UI could look. Describe the workflow the user would follow.<br />
<br />
=== Time keyed layer display ===<br />
<br />
Functionality to display/hide a list of layers in a fixed or variable sequence, or recorded to a sequential output format (e.g. a video output format or numbered raster images).<br />
<br />
priority: Medium term<br />
<br />
=== Frame transitions ===<br />
<br />
Expand on the above projects by organizing objects in sequential layers, where the layers can mark either transition points for a given object, or an object that replaces one or more objects in an earlier frame.<br />
<br />
priority: Longer term<br />
<br />
=== CSS/SVG Web Animations ===<br />
<br />
Export animation properties as corresponding CSS/SVG parameters to output files, following the model from the Web Animations specification so that both SMIL and CSS animations are supported. Inkscape Community/Tav<br />
<br />
priority: Longer term<br />
<br />
== Technical Writing ==<br />
<br />
=== Improve this Project List ===<br />
<br />
Review all the projects in this list. Cleanup grammar or phrasing to make the descriptions clearer. Expand on points that are vague. Add links to relevant bug reports, feature requests, blueprints, etc. Add "[Please fill in]" to items that need more information; identify particular questions needing addressed where possible.<br />
<br />
=== Release Notes Improvement ===<br />
<br />
Review the release notes for the next major Inkscape release. Update wording and phrasing to be more comprehensible for end users. Fill in missing items where possible. Create and add explanatory graphics (c.f as done in past release notes). Add Known Issues from the previous release that are still relevant.<br />
<br />
=== Inkscape Widgets Doxygen ===<br />
<br />
Over the years Inkscape has collected a number of custom UI objects, which have been consolidated to src/widgets/. Many of these are un- or under-documented. For each widget, write doxygen comments in the header file explaining what the widget is and does, and document the widget's public API. In some cases there may be doxygen in the .cpp file for public API functions - this should move to the header.<br />
<br />
=== Bring inkscape/doc up to date ===<br />
<br />
The doc directory in the Inkscape codebase is used for high level technical documentation including architecture, codebase introduction, and new developer orientation, however it has not been very well maintained and much is obsolete or incorrect. It also needs to be reformatted into Markdown, and appropriate scripts created to generate it into HTML/PDF/SVG. There may be additional developer documentation in Wiki that would be worth inclusion here.<br />
<br />
=== Code Doxygen Documentation ===<br />
<br />
Ensure all functions declared in header files have doxygen-compatible documentation. See items in [[Janitorial tasks]] for the style we're going for. All doxygen of the core Inkscape code (i.e. excluding 3rd party libraries included in src/*/) should have consistently written and formatted doxygen, which should include descriptions of input, output, and return parameters, identification of potential errors, a one-line brief statement and a more detailed explanation of the routine's purpose.<br />
<br />
== Tutorials ==<br />
<br />
* Solicit community-contributed tutorial contributions<br />
* Introduce new tutorials<br />
<br />
<br />
== Packaging and Release Management ==<br />
<br />
=== Library Package De-integration ===<br />
<br />
Several 3rd party codebases are included in Inkscape's codebase (i.e., src/lib*/, src/2geom, possibly livarot?). This has convenience for local patching of our own improvements and simplifies the number of components platform packagers need to deal with, however this increases the weight of our codebase and makes our package larger on platforms such as Linux that have good dependency sharing. Arguably, it may also hinder collaboration with the upstreams or other users of the libraries. Certainly it makes it difficult to roll out fixes to one of those libraries to our users. So, we want these libraries to be packaged and released separately from Inkscape.<br />
<br />
For each of these libraries, create a separate git repository in Inkscape's gitlab project for hosting our branch of that project's code. Make sure any of Inkscape's changes to it are clearly registered as distinct git commits. If there is an active upstream project maintaining that library, make sure each of our changes are registered in their patch or bug tracking systems.<br />
<br />
In theory, Inkscape should only be using the libraries' public APIs; doublecheck that this is indeed the case, and identify any instances where Inkscape code is bypassing it and accessing library internals directly. These should be filed as high priority bugs in Inkscape's bug tracker.<br />
<br />
Lastly, make sure that `make dist` passes successfully for each of our branched libraries, and generates a source tarball. Inform the Release Team of the need to start separately packaging and releasing these libraries in conjunction with Inkscape's release processes.<br />
<br />
== Bug Triage ==<br />
<br />
<br />
With as many bugs as we've accumulated, working on them can seem daunting. Where to start!? Below are some encapsulated projects to try to achieve. Together, the more of these projects that are completed the less daunting the remaining work will be, and the better Inkscape will become!<br />
<br />
The [[Bug management]] page in this wiki includes advice on how to judge bug status and importance levels.<br />
<br />
''Tip: Some of these tasks could be scripted and automated via the Launchpad email interface. See https://help.launchpad.net/BugTrackerEmailInterface''<br />
<br />
<strike><br />
=== (100% Complete) Update Status for Critical Bugs from New ===<br />
<br />
(DONE) Review each Critical bug with Status New, and change status to Incomplete if the last comment on the bug is a question, or Confirmed otherwise. -- Bryce<br />
<br />
<br />
=== (100% Complete) Update Status for Critical Bugs from Fix Committed ===<br />
<br />
Review each Critical bug with Status Fix Committed; most likely these are incorrect. If comments towards the end of the thread indicate a fix was committed to SVN, then it is okay to be in state Fix Committed. Otherwise, move it to a more accurate Status.<br />
<br />
=== (100% Complete) Update Status for High Priority Bugs from Fix Committed ===<br />
<br />
Review each High priority bug with Status Fix Committed; most likely these are incorrect. If comments towards the end of the thread indicate a fix was committed to SVN, then it is okay to be in state Fix Committed. Otherwise, move it to a more accurate Status.<br />
</strike><br />
<br />
=== Update Status for High Priority Bugs from New ===<br />
<br />
Review each High priority bug with Status New, and change status to Incomplete if the last comment on the bug is a question, or Confirmed otherwise.<br />
<br />
=== Tag OSX bugs ===<br />
<br />
Using the Advanced search, identify bugs that are reported against OSX and update them to include the tag 'osx'.<br />
<br />
=== Tag Windows bugs ===<br />
<br />
Using the Advanced search, identify bugs that are reported against Windows and update them to include the tag 'windows'. Some bugs are already tagged with 'win32'<br />
: Searched all entries with 'win' in it. Tagged all appropriate bug reports with 'win32'. Now only 'win32' tags exist, but no 'windows' tags. Renaming the tags via the database should be easier than doing it manually (if at all possible). Is this what you guys had in mind? --[[User:Cerno|Cerno]] 15:40, 30 June 2008 (UTC)<br />
<br />
=== Link Cairo bugs ===<br />
<br />
Do a search for 'cairo'. Review the bugs (there's only about a dozen), and for each, identify if the issue is a Cairo bug. If so, look in the cairo bug tracker at freedesktop.org for a matching bug (or enter a new one if there isn't one already) and link it in via the 'Also affects: +Project'.<br />
<br />
=== Set Importance on Confirmed / Fixed Bugs ===<br />
<br />
Do a search on Importance=Undecided and Status=Fix Committed,Confirmed,In Progress. (There's 18 of these presently). Review each and assign it an Importance (probably Medium or High in most cases, but use best judgement).<br />
<br />
=== Ping Old Low Priority Bugs ===<br />
<br />
Search on bugs with Importance=Low, sorted by Oldest First. Go through the bugs that are more than a year old and review them. If they don't seem to have gotten much activity (e.g. few comments), and don't seem to be worth keeping, mark them Incomplete, with the following text:<br />
<br />
"Thank you for taking the time to report this bug and helping to make Inkscape better. You reported this bug a long while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Inkscape release? Thanks in advance."<br />
<br />
or if it is a feature request:<br />
"Thank you for taking the time to report this feature request and helping to make Inkscape better. You requested this feature a long while ago and there hasn't been any activity in it recently. We were wondering; is this still on your wishlist? Can you try with latest Inkscape release and see if recent improvements have obsoleted your request? Thanks in advance."<br />
<br />
Wait about a month, then follow up with a search against these bugs that have not received a response; they can then be closed as Invalid.<br />
<br />
https://wiki.ubuntu.com/Bugs/Status<br />
<br />
=== Confirm all appropriate bugs marked Incomplete with responses ===<br />
<br />
Search on 'Incomplete with response', and review the feedback that's been given. If it appears the initial triager's information requests were met, and the bug seems legitimate, move it to Confirmed. If there seems to be further questions needing answered, ask them and leave it as incomplete.<br />
<br />
As well, specify a priority for these bugs. Generally, issues that cause crashes or data loss are high priority unless they only occur in very narrow situations. Issues which are purely cosmetic or involve very obscure or limited conditions are low priority, and everything else is Medium. Only use Critical priority for extremely serious bugs that will be affecting most everyone using Inkscape.<br />
<br />
=== Convert high priority wishlist bugs into blueprints ===<br />
<br />
Browse the collection of bugs marked ''wishlist''. Look for sets of related bugs that are all requesting essentially the same feature. Create a corresponding blueprint at [https://blueprints.launchpad.net/inkscape https://blueprints.launchpad.net/inkscape], and use ''Specify a URL'' to attach it to a wiki page. Then consolidate the wishlist bug reports together onto the blueprint page. Specify if you're willing to act as the Drafter for the spec, and carry it through to acceptance, or if you prefer someone else take that role.<br />
<br />
Once you've created the specification, use ''Link to bug'' to link each of the related bugs.<br />
<br />
=== Close old incomplete bugs with no response ===<br />
<br />
Do a query on bugs marked Incomplete with no response, and sort by age. All bugs older than 1 month with no reply can be closed as out of date.<br />
<br />
<br />
== Project Infrastructure ==<br />
<br />
=== Project Services Backup ===<br />
<br />
Create ansible scripts to install and configure a rsnapshot service for backing up other services hosted at cloudscale.ch. A big part of this task is making step-by-step documentation for non-rsnapshot aware people to easily follow in adding services to the rsnapshot config.<br />
<br />
A devel virtual machine will be provided for doing devel/testing of the ansible scripts; this vm can be blown away and rebuilt on request, and will match the provisioning for the production system that this service will be running on.<br />
<br />
=== Mediawiki Migration ===<br />
<br />
Currently we are hosting wiki.inkscape.org on an antique vm hosted at OSUOSL. This needs to be migrated to hosting at cloudscale.ch, and updated to the latest version of Mediawiki. There are several steps to this project:<br />
<br />
1. Create ansible scripting to install mediawiki on a cloudscale.ch vm.<br />
2. Create scripts to update our existing wiki content to latest mediawiki (hopefully trivial...)<br />
3. Install mediawiki on cloudscale.ch production vm<br />
4. Put old wiki into read-only mode<br />
5. Update wiki content and deploy to production vm<br />
6. Request DNS change<br />
7. Announce wiki migration is completed<br />
<br />
A devel virtual machine will be provided for doing devel/testing of the ansible scripts; this vm can be blown away and rebuilt on request, and will match the provisioning for the production system that this service will be running on.<br />
<br />
Once we have mediawiki installable via ansible, the next step would be to <br />
<br />
=== Content Management for main website ===<br />
<br />
Contact: martin/ryan<br />
<br />
== Other ==<br />
<br />
=== Extension system improvements ===<br />
<br />
Refactor the extension API. Clean up the kludgy class hierarchy,<br />
possibly using multiple inheritance. Use GInputStream and<br />
GOutputStream as parameters instead of file paths, so that things like<br />
the clipboard can have<br />
<br />
=== Renderer improvements ===<br />
<br />
* Experimental GPU rendering support (e.g. cairo-gl or something vulkan-based). Should be compile-time option defaulted to off.<br />
<br />
This is a big task which has several sub-tasks:<br />
<br />
a) Unify the interactive and non-interactive renderers. (It would be<br />
desirable to have one codebase, but we need to investigate a little<br />
more whether this is practical.)<br />
<br />
b) Pluggable renderers - allow writing rendering backends which use<br />
something other than Cairo, e.g, OpenGL, Skia, Mozilla Azure or GEGL.<br />
<br />
c) OpenGL renderer - implement an OpenGL 3.x+ canvas which would<br />
render Beziers using this method:<br />
http://http.developer.nvidia.com/GPUGems3/gpugems3_ch25.html<br />
<br />
Investigate whether this generalizes to S-basis and circular arcs.<br />
Since the described method does not handle stroking, this work depends<br />
on 5.<br />
<br />
Also check how OpenGL path rendering is implemented in Qt, since<br />
apparently the performance there is very good.<br />
http://zrusin.blogspot.com/2011/09/nv-path-rendering.html<br />
<br />
<br />
=== [https://inkscape.org/en/projects/box-blur/ Box blur (FPRJ-001)] ===<br />
<br />
<span style="color: green"><br />
Currently we always use a very accurate method to compute the Gaussian<br />
blur filter. Add an alternate method which approximates Gaussian blur<br />
using three stacked box blurs (simple averages). This is detailed in<br />
the SVG 1.1 SE specification.<br />
</span><br />
<br />
=== Marker Knockout ===<br />
<br />
Idea is to clean up markers where part of the line shows through. For example if a triangular arrowhead's tip is on the end point of a line with a relatively thick stroke, the rectangular end corners of the line shows up. Or if you're doing a mid-line marker that needs to have a transparent hole (e.g. a "subway station marker", it needs to show through.<br />
<br />
To implement this, draw the line on another surface and mask it with the knockout shape. The filters code uses this approach, as an example. See also the [https://www.w3.org/TR/svg-markers/ SVG Markers] specification.<br />
<br />
contact: Tav<br />
priority: Nearer term<br />
<br />
=== SVG Connectors ===<br />
<br />
Improve Inkscape's connectors, following the [[http://tavmjong.free.fr/SVG/CONNECTORS/index.xhtml proposed SVG connectors spec]].<br />
<br />
These would use live path effects for the lines, zero length paths to hold markers, and definable connector points.<br />
<br />
contact: Tav<br />
<br />
priority: Nearer term<br />
<br />
<br />
=== Restore Ancient Change History ===<br />
<br />
Inkscape's earliest development history is missing, with the first commit being "bzr r1" when we migrated to bzr. Prior history was in CVS and is missing. While not a huge priority, it would be nice to have this pre-bzr history resurrected and prepended to our git history.<br />
<br />
=== Rewrite / reintroduce 3D box ===<br />
** 3-dimensional grid, perspective deformed, with snapping<br />
<br />
=== Git Integration ===<br />
Due to the nature of SVG (text files), versioning might offer a really good way to effectively manage local historical changes even when inkscape is closed. [[https://git-scm.com/ Git]] is a popular versioning software, and is well known among open source contributors. I imagine a versioning system could be "enabled" through the user interface, and allow a user to tag "releases", branch copies if need be, and maintain a historical log of changes. Git could also have been a great way to maintain a branch of different versions of the svg file when the Inkscape project made the change of default dpi for old files recently.<br />
<br />
=== Other Misc. Ideas ===<br />
* Improve support for changing the name of the XML element node in response to SP tree changes.<br />
* Live path effects: investigate extending to cover generic vector transformations (vector effects). Provide live versions of several destructive operations: boolean ops, stroke to path, text to path, etc.<br />
* Javascript support<br />
* Evaluate pdf exporter to join features from scribus Export<br />
** Improved export for printing industry ([http://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/trinity-c6dc9287-cda7-4d8d-9a49-3201dd64f2d1-1412200320248%403capp-gmx-bs01/#msg32887957 Mailing list thread from October 2014])<br />
* Object navigator (like in ponyscape)<br />
* Inkscape for Android<br />
* CAD drawing functionality<br />
* More file format import compatibility<br />
** TopDraw<br />
* OCR of bitmap traces<br />
* Excentric radial gradients, see e.g. samples/orav.svg in the distribution. --bb<br />
<br />
= Finished Projects =<br />
<br />
=== [DONE] <s>[https://inkscape.org/en/projects/remove-all-use-of-glist-and-gslist/ Remove all use of GList and GSList]</s> ===<br />
<br />
<span style="color: green"><br />
These GLib data structures are poorly designed (they are simple lists<br />
without sentinels, leading to blunders such as O(N) performance when<br />
appending to a doubly-linked list) and not type-safe. Replace all uses<br />
with standard C++ containers or suitable Boost containers.<br />
</style><br />
<br />
=== [DONE] <s>Common build system for all platforms</s> ===<br />
<br />
Migrate and port all necessary features to the CMake build system and remove Autotools.<br />
<br />
=== [DONE] <s>Use a different data structure for Inkscape::Selection</s> ===<br />
<br />
Inkscape::Selection currently uses GSList as its data structure. This<br />
is suboptimal, since a very common operation is checking whether some<br />
object is selected. Change Inkscape::Selection so that its underlying<br />
structure is a boost::multi_index container which implements the same<br />
semantics as Java's LinkedHashSet.<br />
<br />
=== [DONE] <s>Remove dom/ directory</s> ===<br />
<br />
This directory contains strange code which is barely used. The only<br />
class which is actually used is the URI class.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape&diff=114701Inkscape2019-04-19T02:20:30Z<p>BryceHarrington: /* Development Discussion */ The 'Tracking Dependencies' page is more current and has more info than the 'Dependencies' page</p>
<hr />
<div>This is a freeform area for Inkscape development and discussion. Curious about [[wiki syntax]]?<br />
<br />
{| style="width: 100%;"<br />
|- style="vertical-align: top;"<br />
| style="width: 33%; background: #EEE; padding: 1em;" |<br />
== Project Info ==<br />
* [http://www.inkscape.org/ Inkscape Homepage]<br />
* [[About Inkscape]]<br />
* [[Features of Inkscape|Features]]<br />
* [[FAQ]] — Frequently Asked Questions<br />
* [[Supported operating systems]]<br />
* [[Tools]] — Supporting Tools and Applications<br />
* [[Galleries]]<br />
* [[Inkscape coverage|Coverage]] — Awards, articles, presentations, books about Inkscape<br />
* [[Inkscape popularity|Popularity]]<br />
* [[Inkscape invariants|Inkscape's Mission]]<br />
* [https://inkscape.org/en/community/ Communication] — How to reach us<br />
* [[Announcement to Sodipodi]] — This started it all<br />
* [[Branding]]<br />
* [[Travel Reimbursement Policy]]<br />
* [[Funded Project System Development]]<br />
* Hackfests<br />
** upcoming/proposed events: [[Hackfest2019 Saarbrücken|2019 Saarbrücken (LGM)]], [[Hackfest2019 SCALE|2019 Pasadena (SCALE)]]<br />
** past events: [[Hackfest2018 Kiel|2018 Kiel]], [[Hackfest2018 LGM|2018 Seville (LGM)]], [[Hackfest2018|2018 Boston]], [[Hackfest2017|2017 Paris]], [[Hackfest2016|2016 Leeds (LGM)]], [[Hackfest2015|2015 Toronto (LGM)]]<br />
<br />
| style="width: 33%; padding: 1em;" |<br />
== User Documentation ==<br />
* [[Installing Inkscape|Installation]]<br />
* [[International and Local Communities]]<br />
* [[Inkscape glossary]]<br />
* [[User manual information]] — Where to find the free Inkscape manual and how to contribute to it<br />
* [http://inkscape.org/en/learn/tutorials/ Tutorials]<br />
* [[Inkscape SVG vs. plain SVG]]<br />
* [[Output format requirements]] — What's needed to save in some formats<br />
* [[Extension requirements]] — What's needed to use some extensions (slightly outdated)<br />
* [[Extension reference]] — What each extension does (slightly outdated)<br />
* [[Connector tool tutorial]]<br />
* [[Installing fonts]]<br />
* [[Emergency save]] — Recovery in case Inkscape crashed<br />
* [[Release notes]]<br />
<!-- ** '''for version [[|]] (active development)''' --><br />
** '''for versions [[Release notes/0.92.4|0.92.4]] (current bugfix release) and [[Release notes/0.92|0.92]] (current major release)'''<br />
** older versions: [[Release notes/0.92.3|0.92.3]], [[Release notes/0.92.2|0.92.2]], [[Release notes/0.92.1|0.92.1]], [[Release notes/0.91|0.91]], [[Release notes/0.48.5|0.48.5]], [[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]]<br />
** future versions: [[Release notes/0.92.5|0.92.5]] (upcoming bugfix release) and [[Release notes/1.0|1.0]] (upcoming major release)<br />
* [[Announcing Releases]]<br />
* [[Release Process Debrief]]<br />
* [[Tricks and tips]] — Miscellaneous advice, may be slightly outdated<br />
<br />
| style="width: 33%; background: #EEE; padding: 1em;" |<br />
<br />
== Help Inkscape Without Coding ==<br />
* [[Help wanted]]<br />
* [[Bug management]]<br />
** [[Projects#Bug_Triage]]<br />
* [[Testing]]<br />
* [[Translation information]]<br />
* [[WebSite]]<br />
* [[Inkscape Classes]]<br />
* [[Conferences]]<br />
* [[Fundraising Ideas]]<br />
* [[Creating Inkscape distributions]] — How to build packages<br />
* [[Stable branch updates]]<br />
* [[Updating tracker items]]<br />
* [[Tutorials and help]]<br />
* [[How to start a page]] — How to use the wiki<br />
* [[Creating screencasts]]<br />
* [[About-Screen contest]]<br />
* [[social media|Participate in social media]]<br />
|}<br />
<br />
<div style="margin-top: 1em; padding: .5em 1em 1em; border: 1px solid #62C012;"><br />
<br />
== Developer Documentation ==<br />
{| style="width: 100%;"<br />
|- style="vertical-align: top;"<br />
| style="width: 50%; padding-right: 1em;" |<br />
=== First Steps ===<br />
* [[Working with Git]] — How to obtain the source code. A quick start on how to use our version control system.<br />
* [[Compiling Inkscape]]<br />
* [[Using Eclipse]] — Debug Inkscape on Windows using Eclipse (outdated)<br />
* [[Using Visual Studio]] — Debug Inkscape on Windows using Microsoft Visual Studio<br />
* [[Developer manual]] — Various important information, be sure to read this before coding<br />
* [[Debugging Inkscape|Debugging]] — Random tips to help debug problems<br />
* [[Janitorial tasks]] — Small tasks that need doing<br />
* [[Doxygen documentation]]<br />
* [[Working with CMake]] — Getting started with CMake coding for configuring and building Inkscape<br />
<br />
=== Developer tutorials ===<br />
* [[Architectural overview]] — A high-level look at Inkscape<br />
* [[Preferences subsystem]] — Creating and using preference values<br />
<!-- * XML subsystem — How to manipulate the XML representation of a document<br />
* Display subsystem — How to make things appear on the canvas<br />
* Tools subsystem — How to create a new tool --><br />
* Extensions<br />
** [[Extension subsystem]] — An overview of the functionality provided by extensions and the possible implementations<br />
** [[Script extensions]] — Extend Inkscape easily using scripting languages (Python, Perl, …)<br />
** [[Python modules for extensions]] — Some helpful routines for use in Python script extensions<br />
** [[INX extension descriptor format]]<br />
* [[Creating Live Path Effects]]<br />
* [[Boost shared pointers]]<br />
* [[Using libsigc++ signals]]<br />
* [[Windows development on Linux]]<br />
<br />
=== User Interface Discussion ===<br />
* [[Interface translation]]<br />
* [[Adding interface verbs]]<br />
* [[Accessible graphics]]<br />
* [[Object Manager]]<br />
* [[Dialogs reorganization]]<br />
* [[Modal interfaces]]<br />
* [[Text usability]] — Text tool and dialog<br />
* [[KeyboardShortcutsToDo]]<br />
** [[Keyboard profiles]] — How you can help <br />
* [[Statusbar API]]<br />
* [[Animation-(Timeline)]]<br />
* [[Free Desktop Graphic Suite]]<br />
* [[Skeletal Strokes]] — Brushes, Strokes, Pressure Sensibility...<br />
<br />
| style="width: 50%;" |<br />
<br />
=== Development Discussion ===<br />
* [[Roadmap]] — The main todo list<br />
* [[Tracking Dependencies|Dependencies]] — What libs are needed to build Inkscape<br />
* [[C++11]] — Which C++11 features can be used<br />
* [[New feature proposals]]<br />
* [[Extension architecture proposals]]<br />
* [[Coding Style|Coding Style Discussion]]<br />
* [[File types]]<br />
* [[Application icons]] — Application + Interface<br />
* [[Icons]]<br />
* [[Color management]]<br />
* [[Printing subsystem]]<br />
* [[SVG Tiny Compliance]]<br />
* [[SVG Test Suite Compliance]] — [[W3C]] full test suite<br />
* [[CSS Support]]<br />
* [[Google Summer of Code]]<br />
* [[Improved Media Management]]<br />
* [[UI Mockup Screenshots]]<br />
* [[Swatch Book]]<br />
* [[Tablet Dialog]]<br />
* [[ViewBoxToDo]] — View box support info<br />
* [[Caching]]<br />
* [[UI and Document coordinates]]<br />
* [[GtkMMification]] — Replace C boilerplate with gtkmm objects<br />
* [[CMake Tasks]] — Converting the Inkscape build system to CMake<br />
* [[Bug Reporting Workflow]] — Options for improving Inkscape bug workflow from user to developer<br />
* [[1.0 Release Bug Fix List]] — List of bugs that need to be fixed for 1.0<br />
* [[1.0 Release Planning]] — Roadmap and planning for 1.0 Release<br />
<br />
=== Miscellaneous ===<br />
* [[Inkscape-specific XML attributes]] — Documentation of attributes from Inkscape's XML namespace<br />
* [[Extension repository]] — An Internet central for Inkscape extensions<br />
* [[Related programs]]<br />
* [[Sponsors list]]<br />
<br />
=== [[Lib2geom]] ===<br />
* [[Lib2geom]]<br />
* [[Working with 2Geom FAQ]] — Real-life questions answered about using 2Geom in real code<br />
* [[Lib2geom py2geom]] — Python bindings to 2geom. With this you can use the power of 2geom in Python scripts.<br />
<br />
=== Historical pages ===<br />
These pages are outdated, but linked here for posterity.<br />
<br />
* [[Working with Bazaar]] — Our former control version system, no longer used. See [[Working with Git]] for current instructions.<br />
* [[Creating a new SPObject]]<br />
<br />
|}<br />
</div><br />
<br />
== See also ==<br />
* [[:Category:Wiki Attic|Wiki Attic]] — Pages that are no longer relevant but kept for historical value<br />
<br />
__NOTOC__<br />
<br />
[[Category:Top level categories]]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape&diff=114696Inkscape2019-04-19T02:05:19Z<p>BryceHarrington: /* First Steps */ Drop now-dead link</p>
<hr />
<div>This is a freeform area for Inkscape development and discussion. Curious about [[wiki syntax]]?<br />
<br />
{| style="width: 100%;"<br />
|- style="vertical-align: top;"<br />
| style="width: 33%; background: #EEE; padding: 1em;" |<br />
== Project Info ==<br />
* [http://www.inkscape.org/ Inkscape Homepage]<br />
* [[About Inkscape]]<br />
* [[Features of Inkscape|Features]]<br />
* [[FAQ]] — Frequently Asked Questions<br />
* [[Supported operating systems]]<br />
* [[Tools]] — Supporting Tools and Applications<br />
* [[Galleries]]<br />
* [[Inkscape coverage|Coverage]] — Awards, articles, presentations, books about Inkscape<br />
* [[Inkscape popularity|Popularity]]<br />
* [[Inkscape invariants|Inkscape's Mission]]<br />
* [https://inkscape.org/en/community/ Communication] — How to reach us<br />
* [[Announcement to Sodipodi]] — This started it all<br />
* [[Branding]]<br />
* [[Travel Reimbursement Policy]]<br />
* [[Funded Project System Development]]<br />
* Hackfests<br />
** upcoming/proposed events: [[Hackfest2019 Saarbrücken|2019 Saarbrücken (LGM)]], [[Hackfest2019 SCALE|2019 Pasadena (SCALE)]]<br />
** past events: [[Hackfest2018 Kiel|2018 Kiel]], [[Hackfest2018 LGM|2018 Seville (LGM)]], [[Hackfest2018|2018 Boston]], [[Hackfest2017|2017 Paris]], [[Hackfest2016|2016 Leeds (LGM)]], [[Hackfest2015|2015 Toronto (LGM)]]<br />
<br />
| style="width: 33%; padding: 1em;" |<br />
== User Documentation ==<br />
* [[Installing Inkscape|Installation]]<br />
* [[International and Local Communities]]<br />
* [[Inkscape glossary]]<br />
* [[User manual information]] — Where to find the free Inkscape manual and how to contribute to it<br />
* [http://inkscape.org/en/learn/tutorials/ Tutorials]<br />
* [[Inkscape SVG vs. plain SVG]]<br />
* [[Output format requirements]] — What's needed to save in some formats<br />
* [[Extension requirements]] — What's needed to use some extensions (slightly outdated)<br />
* [[Extension reference]] — What each extension does (slightly outdated)<br />
* [[Connector tool tutorial]]<br />
* [[Installing fonts]]<br />
* [[Emergency save]] — Recovery in case Inkscape crashed<br />
* [[Release notes]]<br />
<!-- ** '''for version [[|]] (active development)''' --><br />
** '''for versions [[Release notes/0.92.4|0.92.4]] (current bugfix release) and [[Release notes/0.92|0.92]] (current major release)'''<br />
** older versions: [[Release notes/0.92.3|0.92.3]], [[Release notes/0.92.2|0.92.2]], [[Release notes/0.92.1|0.92.1]], [[Release notes/0.91|0.91]], [[Release notes/0.48.5|0.48.5]], [[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]]<br />
** future versions: [[Release notes/0.92.5|0.92.5]] (upcoming bugfix release) and [[Release notes/1.0|1.0]] (upcoming major release)<br />
* [[Announcing Releases]]<br />
* [[Release Process Debrief]]<br />
* [[Tricks and tips]] — Miscellaneous advice, may be slightly outdated<br />
<br />
| style="width: 33%; background: #EEE; padding: 1em;" |<br />
<br />
== Help Inkscape Without Coding ==<br />
* [[Help wanted]]<br />
* [[Bug management]]<br />
** [[Projects#Bug_Triage]]<br />
* [[Testing]]<br />
* [[Translation information]]<br />
* [[WebSite]]<br />
* [[Inkscape Classes]]<br />
* [[Conferences]]<br />
* [[Fundraising Ideas]]<br />
* [[Creating Inkscape distributions]] — How to build packages<br />
* [[Stable branch updates]]<br />
* [[Updating tracker items]]<br />
* [[Tutorials and help]]<br />
* [[How to start a page]] — How to use the wiki<br />
* [[Creating screencasts]]<br />
* [[About-Screen contest]]<br />
* [[social media|Participate in social media]]<br />
|}<br />
<br />
<div style="margin-top: 1em; padding: .5em 1em 1em; border: 1px solid #62C012;"><br />
<br />
== Developer Documentation ==<br />
{| style="width: 100%;"<br />
|- style="vertical-align: top;"<br />
| style="width: 50%; padding-right: 1em;" |<br />
=== First Steps ===<br />
* [[Working with Git]] — How to obtain the source code. A quick start on how to use our version control system.<br />
* [[Compiling Inkscape]]<br />
* [[Using Eclipse]] — Debug Inkscape on Windows using Eclipse (outdated)<br />
* [[Using Visual Studio]] — Debug Inkscape on Windows using Microsoft Visual Studio<br />
* [[Developer manual]] — Various important information, be sure to read this before coding<br />
* [[Debugging Inkscape|Debugging]] — Random tips to help debug problems<br />
* [[Janitorial tasks]] — Small tasks that need doing<br />
* [[Doxygen documentation]]<br />
* [[Working with CMake]] — Getting started with CMake coding for configuring and building Inkscape<br />
<br />
=== Developer tutorials ===<br />
* [[Architectural overview]] — A high-level look at Inkscape<br />
* [[Preferences subsystem]] — Creating and using preference values<br />
<!-- * XML subsystem — How to manipulate the XML representation of a document<br />
* Display subsystem — How to make things appear on the canvas<br />
* Tools subsystem — How to create a new tool --><br />
* Extensions<br />
** [[Extension subsystem]] — An overview of the functionality provided by extensions and the possible implementations<br />
** [[Script extensions]] — Extend Inkscape easily using scripting languages (Python, Perl, …)<br />
** [[Python modules for extensions]] — Some helpful routines for use in Python script extensions<br />
** [[INX extension descriptor format]]<br />
* [[Creating Live Path Effects]]<br />
* [[Boost shared pointers]]<br />
* [[Using libsigc++ signals]]<br />
* [[Windows development on Linux]]<br />
<br />
=== User Interface Discussion ===<br />
* [[Interface translation]]<br />
* [[Adding interface verbs]]<br />
* [[Accessible graphics]]<br />
* [[Object Manager]]<br />
* [[Dialogs reorganization]]<br />
* [[Modal interfaces]]<br />
* [[Text usability]] — Text tool and dialog<br />
* [[KeyboardShortcutsToDo]]<br />
** [[Keyboard profiles]] — How you can help <br />
* [[Statusbar API]]<br />
* [[Animation-(Timeline)]]<br />
* [[Free Desktop Graphic Suite]]<br />
* [[Skeletal Strokes]] — Brushes, Strokes, Pressure Sensibility...<br />
<br />
| style="width: 50%;" |<br />
<br />
=== Development Discussion ===<br />
* [[Roadmap]] — The main todo list<br />
* [[Dependencies]] — What libs are needed to build Inkscape<br />
* [[C++11]] — Which C++11 features can be used<br />
* [[New feature proposals]]<br />
* [[Extension architecture proposals]]<br />
* [[Coding Style|Coding Style Discussion]]<br />
* [[File types]]<br />
* [[Application icons]] — Application + Interface<br />
* [[Icons]]<br />
* [[Color management]]<br />
* [[Printing subsystem]]<br />
* [[SVG Tiny Compliance]]<br />
* [[SVG Test Suite Compliance]] — [[W3C]] full test suite<br />
* [[CSS Support]]<br />
* [[Google Summer of Code]]<br />
* [[Improved Media Management]]<br />
* [[UI Mockup Screenshots]]<br />
* [[Swatch Book]]<br />
* [[Tablet Dialog]]<br />
* [[ViewBoxToDo]] — View box support info<br />
* [[Caching]]<br />
* [[UI and Document coordinates]]<br />
* [[GtkMMification]] — Replace C boilerplate with gtkmm objects<br />
* [[CMake Tasks]] — Converting the Inkscape build system to CMake<br />
* [[Bug Reporting Workflow]] — Options for improving Inkscape bug workflow from user to developer<br />
* [[1.0 Release Bug Fix List]] — List of bugs that need to be fixed for 1.0<br />
* [[1.0 Release Planning]] — Roadmap and planning for 1.0 Release<br />
<br />
=== Miscellaneous ===<br />
* [[Inkscape-specific XML attributes]] — Documentation of attributes from Inkscape's XML namespace<br />
* [[Extension repository]] — An Internet central for Inkscape extensions<br />
* [[Related programs]]<br />
* [[Sponsors list]]<br />
<br />
=== [[Lib2geom]] ===<br />
* [[Lib2geom]]<br />
* [[Working with 2Geom FAQ]] — Real-life questions answered about using 2Geom in real code<br />
* [[Lib2geom py2geom]] — Python bindings to 2geom. With this you can use the power of 2geom in Python scripts.<br />
<br />
=== Historical pages ===<br />
These pages are outdated, but linked here for posterity.<br />
<br />
* [[Working with Bazaar]] — Our former control version system, no longer used. See [[Working with Git]] for current instructions.<br />
* [[Creating a new SPObject]]<br />
<br />
|}<br />
</div><br />
<br />
== See also ==<br />
* [[:Category:Wiki Attic|Wiki Attic]] — Pages that are no longer relevant but kept for historical value<br />
<br />
__NOTOC__<br />
<br />
[[Category:Top level categories]]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape&diff=114691Inkscape2019-04-19T02:04:00Z<p>BryceHarrington: /* Lib2geom */ Drop non-existent links</p>
<hr />
<div>This is a freeform area for Inkscape development and discussion. Curious about [[wiki syntax]]?<br />
<br />
{| style="width: 100%;"<br />
|- style="vertical-align: top;"<br />
| style="width: 33%; background: #EEE; padding: 1em;" |<br />
== Project Info ==<br />
* [http://www.inkscape.org/ Inkscape Homepage]<br />
* [[About Inkscape]]<br />
* [[Features of Inkscape|Features]]<br />
* [[FAQ]] — Frequently Asked Questions<br />
* [[Supported operating systems]]<br />
* [[Tools]] — Supporting Tools and Applications<br />
* [[Galleries]]<br />
* [[Inkscape coverage|Coverage]] — Awards, articles, presentations, books about Inkscape<br />
* [[Inkscape popularity|Popularity]]<br />
* [[Inkscape invariants|Inkscape's Mission]]<br />
* [https://inkscape.org/en/community/ Communication] — How to reach us<br />
* [[Announcement to Sodipodi]] — This started it all<br />
* [[Branding]]<br />
* [[Travel Reimbursement Policy]]<br />
* [[Funded Project System Development]]<br />
* Hackfests<br />
** upcoming/proposed events: [[Hackfest2019 Saarbrücken|2019 Saarbrücken (LGM)]], [[Hackfest2019 SCALE|2019 Pasadena (SCALE)]]<br />
** past events: [[Hackfest2018 Kiel|2018 Kiel]], [[Hackfest2018 LGM|2018 Seville (LGM)]], [[Hackfest2018|2018 Boston]], [[Hackfest2017|2017 Paris]], [[Hackfest2016|2016 Leeds (LGM)]], [[Hackfest2015|2015 Toronto (LGM)]]<br />
<br />
| style="width: 33%; padding: 1em;" |<br />
== User Documentation ==<br />
* [[Installing Inkscape|Installation]]<br />
* [[International and Local Communities]]<br />
* [[Inkscape glossary]]<br />
* [[User manual information]] — Where to find the free Inkscape manual and how to contribute to it<br />
* [http://inkscape.org/en/learn/tutorials/ Tutorials]<br />
* [[Inkscape SVG vs. plain SVG]]<br />
* [[Output format requirements]] — What's needed to save in some formats<br />
* [[Extension requirements]] — What's needed to use some extensions (slightly outdated)<br />
* [[Extension reference]] — What each extension does (slightly outdated)<br />
* [[Connector tool tutorial]]<br />
* [[Installing fonts]]<br />
* [[Emergency save]] — Recovery in case Inkscape crashed<br />
* [[Release notes]]<br />
<!-- ** '''for version [[|]] (active development)''' --><br />
** '''for versions [[Release notes/0.92.4|0.92.4]] (current bugfix release) and [[Release notes/0.92|0.92]] (current major release)'''<br />
** older versions: [[Release notes/0.92.3|0.92.3]], [[Release notes/0.92.2|0.92.2]], [[Release notes/0.92.1|0.92.1]], [[Release notes/0.91|0.91]], [[Release notes/0.48.5|0.48.5]], [[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]]<br />
** future versions: [[Release notes/0.92.5|0.92.5]] (upcoming bugfix release) and [[Release notes/1.0|1.0]] (upcoming major release)<br />
* [[Announcing Releases]]<br />
* [[Release Process Debrief]]<br />
* [[Tricks and tips]] — Miscellaneous advice, may be slightly outdated<br />
<br />
| style="width: 33%; background: #EEE; padding: 1em;" |<br />
<br />
== Help Inkscape Without Coding ==<br />
* [[Help wanted]]<br />
* [[Bug management]]<br />
** [[Projects#Bug_Triage]]<br />
* [[Testing]]<br />
* [[Translation information]]<br />
* [[WebSite]]<br />
* [[Inkscape Classes]]<br />
* [[Conferences]]<br />
* [[Fundraising Ideas]]<br />
* [[Creating Inkscape distributions]] — How to build packages<br />
* [[Stable branch updates]]<br />
* [[Updating tracker items]]<br />
* [[Tutorials and help]]<br />
* [[How to start a page]] — How to use the wiki<br />
* [[Creating screencasts]]<br />
* [[About-Screen contest]]<br />
* [[social media|Participate in social media]]<br />
|}<br />
<br />
<div style="margin-top: 1em; padding: .5em 1em 1em; border: 1px solid #62C012;"><br />
<br />
== Developer Documentation ==<br />
{| style="width: 100%;"<br />
|- style="vertical-align: top;"<br />
| style="width: 50%; padding-right: 1em;" |<br />
=== First Steps ===<br />
* [[Working with Git]] — How to obtain the source code. A quick start on how to use our version control system.<br />
* [[Compiling Inkscape]]<br />
* [[Using Eclipse]] — Debug Inkscape on Windows using Eclipse (outdated)<br />
* [[Using Visual Studio]] — Debug Inkscape on Windows using Microsoft Visual Studio<br />
* [[Developer manual]] — Various important information, be sure to read this before coding<br />
* [[Debugging Inkscape|Debugging]] — Random tips to help debug problems<br />
* [[Project organization]] — Procedures, hierarchy, developer roles and the likes<br />
* [[Janitorial tasks]] — Small tasks that need doing<br />
* [[Doxygen documentation]]<br />
* [[Working with CMake]] — Getting started with CMake coding for configuring and building Inkscape<br />
<br />
=== Developer tutorials ===<br />
* [[Architectural overview]] — A high-level look at Inkscape<br />
* [[Preferences subsystem]] — Creating and using preference values<br />
<!-- * XML subsystem — How to manipulate the XML representation of a document<br />
* Display subsystem — How to make things appear on the canvas<br />
* Tools subsystem — How to create a new tool --><br />
* Extensions<br />
** [[Extension subsystem]] — An overview of the functionality provided by extensions and the possible implementations<br />
** [[Script extensions]] — Extend Inkscape easily using scripting languages (Python, Perl, …)<br />
** [[Python modules for extensions]] — Some helpful routines for use in Python script extensions<br />
** [[INX extension descriptor format]]<br />
* [[Creating Live Path Effects]]<br />
* [[Boost shared pointers]]<br />
* [[Using libsigc++ signals]]<br />
* [[Windows development on Linux]]<br />
<br />
=== User Interface Discussion ===<br />
* [[Interface translation]]<br />
* [[Adding interface verbs]]<br />
* [[Accessible graphics]]<br />
* [[Object Manager]]<br />
* [[Dialogs reorganization]]<br />
* [[Modal interfaces]]<br />
* [[Text usability]] — Text tool and dialog<br />
* [[KeyboardShortcutsToDo]]<br />
** [[Keyboard profiles]] — How you can help <br />
* [[Statusbar API]]<br />
* [[Animation-(Timeline)]]<br />
* [[Free Desktop Graphic Suite]]<br />
* [[Skeletal Strokes]] — Brushes, Strokes, Pressure Sensibility...<br />
<br />
| style="width: 50%;" |<br />
<br />
=== Development Discussion ===<br />
* [[Roadmap]] — The main todo list<br />
* [[Dependencies]] — What libs are needed to build Inkscape<br />
* [[C++11]] — Which C++11 features can be used<br />
* [[New feature proposals]]<br />
* [[Extension architecture proposals]]<br />
* [[Coding Style|Coding Style Discussion]]<br />
* [[File types]]<br />
* [[Application icons]] — Application + Interface<br />
* [[Icons]]<br />
* [[Color management]]<br />
* [[Printing subsystem]]<br />
* [[SVG Tiny Compliance]]<br />
* [[SVG Test Suite Compliance]] — [[W3C]] full test suite<br />
* [[CSS Support]]<br />
* [[Google Summer of Code]]<br />
* [[Improved Media Management]]<br />
* [[UI Mockup Screenshots]]<br />
* [[Swatch Book]]<br />
* [[Tablet Dialog]]<br />
* [[ViewBoxToDo]] — View box support info<br />
* [[Caching]]<br />
* [[UI and Document coordinates]]<br />
* [[GtkMMification]] — Replace C boilerplate with gtkmm objects<br />
* [[CMake Tasks]] — Converting the Inkscape build system to CMake<br />
* [[Bug Reporting Workflow]] — Options for improving Inkscape bug workflow from user to developer<br />
* [[1.0 Release Bug Fix List]] — List of bugs that need to be fixed for 1.0<br />
* [[1.0 Release Planning]] — Roadmap and planning for 1.0 Release<br />
<br />
=== Miscellaneous ===<br />
* [[Inkscape-specific XML attributes]] — Documentation of attributes from Inkscape's XML namespace<br />
* [[Extension repository]] — An Internet central for Inkscape extensions<br />
* [[Related programs]]<br />
* [[Sponsors list]]<br />
<br />
=== [[Lib2geom]] ===<br />
* [[Lib2geom]]<br />
* [[Working with 2Geom FAQ]] — Real-life questions answered about using 2Geom in real code<br />
* [[Lib2geom py2geom]] — Python bindings to 2geom. With this you can use the power of 2geom in Python scripts.<br />
<br />
=== Historical pages ===<br />
These pages are outdated, but linked here for posterity.<br />
<br />
* [[Working with Bazaar]] — Our former control version system, no longer used. See [[Working with Git]] for current instructions.<br />
* [[Creating a new SPObject]]<br />
<br />
|}<br />
</div><br />
<br />
== See also ==<br />
* [[:Category:Wiki Attic|Wiki Attic]] — Pages that are no longer relevant but kept for historical value<br />
<br />
__NOTOC__<br />
<br />
[[Category:Top level categories]]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114671Fundraising Ideas2019-04-12T20:37:28Z<p>BryceHarrington: /* Sponsorship */</p>
<hr />
<div>This file outlines some blue-sky brainstorming thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
Note that these are not vetted ideas - some may not be permissible under our non-profit designation. Others may be permitted but may be controversial (e.g. ads), however we're listing them here as food for thought.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $NNk<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $20 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* T-Shirts, Hats, Mugs, Buttons, Stickers, Hoodies, Polos, etc.<br />
** cafepress.com<br />
<br />
* High quality clothing.<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
<br />
== Art auctions / sales ==<br />
<br />
Ask artists to provide their work to the project, either as a full donation, or a split of the proceeds. Then auction signed prints or originals, and offer direct purchase of unsigned prints.<br />
<br />
<br />
== Printed version of manual ==<br />
<br />
* We have already been getting book royalties from Packt, could expand on that with new books?<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
<br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
== App Stores ==<br />
<br />
In App Stores, instead of providing the built software entirely for free, provide it for a Suggested Donation.<br />
<br />
Homebrew "Suggested Donation" with download<br />
+ Target all the funds to Mac support<br />
<br />
In cases where the store does not provide a "Suggested Donation" option, consider listing it for a fee but emphasize that the same packages are also available from inkscape.org for no charge.<br />
<br />
== adsense Ads ==<br />
<br />
Simple text ads integrated into the website<br />
<br />
== Purchased Ads ==<br />
<br />
Certain pages of the website are devoted to specialized advertisements, provided to specific companies with relation to Inkscape.<br />
<br />
== Youtube Channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Affiliate Links ==<br />
<br />
SEO companies will pay for sponsorship to get dofollow links to their site.<br />
<br />
== Amazon Commission ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
<br />
= Services =<br />
<br />
== Service Raffle ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffle tickets for $20-50 each - keep it a little high so you don’t have to sell so many and so that the buyers have a higher chance of winning. Encourage people to buy several, by offering discounts for multiple purchases (1 for $20, 2 for $36, 3 for $50, etc.)<br />
<br />
Services can include:<br />
* creating logos<br />
* Business card design<br />
* Brochure design<br />
* Christmas or birthday cards<br />
* Graduation announcements<br />
<br />
<br />
== Design Service Broker ==<br />
<br />
Recruit our artists to do contracted design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, drawing, programming, proposal writing, etc. Charge $50-75 suggested donation per person, with a goal of 15 to 20 people. Record a video and provide it online for suggested donation.<br />
<br />
<br />
== Priority User Support ==<br />
<br />
For a recurring fee, we provide prioritized question answering by a seasoned Inkscape pro, up to a fixed number of hours per week.<br />
<br />
== Technical Support ==<br />
<br />
For a recurring fee, we provide access to a developer to help troubleshoot problems and work on selected bugs as directed by the client.<br />
<br />
<br />
== Custom Interface Spins ==<br />
<br />
We provide builds of Inkscape with some basic interface customizations, such as simplifying it by removing some unneeded functionality. The result is still covered under the GPL. We provide packaged versions for them to give their users or distribute with their product. For additional fee we also allow them to tweak the branding to some degree. We maintain the spin against current master, for an annual charge.<br />
<br />
<br />
== Custom Extensions ==<br />
<br />
We implement extensions customized to their particular service or product, that they can offer from their website, or include in copies of Inkscape they distribute themselves. The extension is covered as GPL, but can be licensed differently for additional fees.<br />
<br />
== Hosting Services ==<br />
<br />
We provide use of our infrastructure services to projects or companies for an arranged fee or sponsorship payment.<br />
* Mailing lists<br />
* DNS<br />
* @<project>.org email aliases<br />
* Cloud computing nodes<br />
* Build systems (Mac, Windows)<br />
<br />
= Sponsorship =<br />
<br />
* Sponsor cannot receive any substantial benefits in return, else it counts as unrelated business income (i.e. taxed at 15-45%).<br />
** E.g. if nonprofit promotes a sponsor's products and/or services it counts as advertising. [https://www.aemcpas.com/cpa-firm/news/Sponsorship-Advertising.html]<br />
** "Per IRS rules, nonprofits can acknowledge sponsors by mentioning or displaying the following: company name, company logo, product lines and contact information (address, phone number, web address)."<br />
** "Nonprofits are also permitted to mention slogans and value-neutral descriptions of a sponsor’s goods or services in acknowledging their support."<br />
** "In addition, nonprofits can display or distribute a sponsor’s products to the general public at the sponsored activity or event."<br />
** No: Coupons, endorsements, or comparison to sponsor's competitors<br />
<br />
<br />
== Website General Fund Sponsors ==<br />
<br />
Our regular sponsorship levels, with reward being placement on the sponsors web page.<br />
<br />
== Event Sponsors ==<br />
<br />
Funds go directly towards hackfest travel attendance, or attendance at LGM, SCALE, and other conferences. We will display their logo in our booth banners and handout materials.<br />
<br />
= Misc Other Ideas =<br />
<br />
* Sell your frequent flyer miles to friends or donate them to the organization for a raffle. Watch the rules of the airline on this, but some airlines let you give away miles, and you may be able to sell your miles as long as you don’t go through a mileage broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
More ideas:<br />
* http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf<br />
* http://www.ianbicking.org/blog/2019/03/open-source-doesnt-make-money-by-design.html</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Leadership_Committee_Status_Updates&diff=114591Leadership Committee Status Updates2019-04-05T17:02:37Z<p>BryceHarrington: </p>
<hr />
<div>== Place and Time ==<br />
<br />
We meet in #inkscape-devel on [https://freenode.net/ freenode].<br />
<br />
Board meetings are typically the first Friday of each month.<br />
<br />
<em>Everybody in the Inkscape community is invited to participate.</em><br />
<br />
Next meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=5&year=2019&hour=17&min=00&sec=0&p1=0 10:00 PDT/17:00 UTC/19:00 CEST, (click for world clock)], Fri, 5th April, 2019. (Time is fixed to 10 AM Pacific Time.)<br />
<br />
Meetings should be announced in advance on [https://lists.sourceforge.net/lists/listinfo/inkscape-devel inkscape-devel] and [https://lists.sourceforge.net/lists/listinfo/inkscape-board inkscape-board] mailing lists.<br />
<br />
== Agenda ==<br />
* Hackfest [http://libregraphicsmeeting.org/2019/ LGM 2019]<br />
** May 30th-June 3rd (Saarbrucken, Germany)<br />
** Travelers should have arrangements made<br />
<br />
* GSoC<br />
<br />
* Budget<br />
<br />
* Bug migration off Launchpad<br />
<br />
* Infrastructure<br />
** mailing list migration off SourceForge<br />
** Wiki migration off OSUOSL<br />
** Weblate service deployment<br />
<br />
* Software Release status<br />
** 2geom 1.1<br />
** Inkscape 0.92.5<br />
** Inkscape 1.0beta<br />
<br />
* Other Business<br />
<br />
== Other Agenda Items ==<br />
* Sponsor acceptance policy<br />
* Funded development [bryce]<br />
** Identify Manager/Reviewer/Second for each of the jobs<br />
** How should we advertise the jobs?<br />
* Outreachy: Next round starts in August [https://www.outreachy.org/mentor/]<br />
<br />
=== Action Items ===<br />
* Future hackfests<br />
** Hackfest organizational tips (Need to document this someplace)<br />
*** Process: Have folks propose options, and then trade off cost projections and benefits<br />
*** Try to organize group lodging (same hotel, rented/air-bnb house, http://www.linuxhotel.de/community.en.html, etc.)<br />
*** Send a scout ahead of time to help avoid slummy accommodations<br />
*** Catered lunches help keep everyone focused (we're already reimbursing on lunches, so cost differential isn't huge, and it saves hassle all around)<br />
*** Boots on the ground at a location can be a huge help if plans go awry<br />
*** Prefer locations with local inkscape community on the ground<br />
<br />
* [https://inkscape.org/en/support-us/funded-development/ Funded development] [bryce]<br />
* Add a C++-11 conversion project with tasks detailed to the Roadmap for 0.93 or later. [valavanisalex]<br />
* Regularly check [[Sponsors_list|sponsor status]]<br />
<br />
== Blocked Action Items ==<br />
<br />
* Privacy Policy [drmo] ~ Blocked waiting on time availability by SFC<br />
* Amend CoC reporting section ~ Waiting until we have a dedicated email, e.g. abuse@inkscape.org<br />
<br />
<br />
== Board Meeting Transcripts == <br />
<br />
=== 2019 ===<br />
<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2019-03-01.log.html 2019-03-01]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2019-02-01.log.html 2019-02-01]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2019-01-04.log.html 2019-01-04]<br />
<br />
=== 2018 ===<br />
<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-12-07.log.html 2018-12-07]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-11-02.log.html 2018-11-02]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-10-05.log.html 2018-10-05]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-09-07.log.html 2018-09-07]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-08-03.log.html 2018-08-03]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-07-06.log.html 2018-07-06]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-06-01.log.html 2018-06-01]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-05-04.log.html 2018-05-04]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-04-06.log.html 2018-04-06]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/board_meeting_2018-03-02.html 2018-03-02]<br />
* [https://inkscape.org/gallery/item/12009/ 2018-02-02]<br />
* [https://inkscape.org/gallery/item/11875/ 2018-01-05]<br />
<br />
=== 2017 ===<br />
<br />
* [https://inkscape.org/paste/11743/ 2017-12-01]<br />
* [https://inkscape.org/paste/11651/ 2017-11-03]<br />
* [https://inkscape.org/gallery/item/11517/ 2017-10-06]<br />
* [https://inkscape.org/gallery/item/11377/ 2017-09-01]<br />
* [https://inkscape.org/gallery/item/11250/ 2017-08-04]<br />
* [https://inkscape.org/gallery/item/11176/ 2017-07-07]<br />
* [https://inkscape.org/gallery/item/11064/ 2017-06-02]<br />
* [https://inkscape.org/gallery/item/10844/ 2017-04-07]<br />
* [https://inkscape.org/gallery/item/10740/ 2017-03-03]<br />
* [https://inkscape.org/gallery/item/10651/ 2017-02-03]<br />
* [https://inkscape.org/gallery/item/10582/ 2017-01-06]<br />
<br />
=== 2016 ===<br />
<br />
* [https://inkscape.org/gallery/item/10484/ 2016-12-02]<br />
* [https://inkscape.org/gallery/item/10241/ 2016-11-04]<br />
* [https://inkscape.org/gallery/item/9971/ 2016-09-02]<br />
* [https://inkscape.org/gallery/item/9864/ 2016-08-05]<br />
* [https://inkscape.org/gallery/item/9766/ 2016-07-08]<br />
* [https://inkscape.org/gallery/item/9667/ 2016-06-03]<br />
* [https://inkscape.org/gallery/item/9563/ 2016-05-06]<br />
* [https://inkscape.org/gallery/item/9565/ 2016-04-01]<br />
<br />
* [https://inkscape.org/gallery/item/7276/ 2016-01-08]<br />
<br />
=== 2015 ===<br />
<br />
* [https://inkscape.org/gallery/item/7056/ 2015-12-04]<br />
* [https://inkscape.org/gallery/item/6886/ 2015-11-06]<br />
* [https://inkscape.org/gallery/item/6701/ 2015-10-02]<br />
<br />
=== 2014 ===<br />
<br />
* [https://inkscape.org/gallery/item/2498/ 2014-11-26]<br />
* [https://inkscape.org/gallery/item/2216/ 2014-11-19]<br />
* [https://inkscape.org/gallery/item/2210/ 2014-11-12]<br />
* [https://inkscape.org/gallery/item/2204/ 2014-11-05]<br />
* [https://inkscape.org/gallery/item/1436/ 2014-10-15]<br />
* [https://inkscape.org/gallery/item/950/ 2014-10-08]<br />
* [https://inkscape.org/gallery/item/854/ 2014-09-29]<br />
* [https://inkscape.org/gallery/item/392/ 2014-09-15]<br />
<br />
'''[https://inkscape.org/en/gallery/=pastebin/?q=meeting&order=-edited Website search for all transcripts]'''</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Leadership_Committee_Status_Updates&diff=114586Leadership Committee Status Updates2019-04-05T17:01:50Z<p>BryceHarrington: /* Agenda */</p>
<hr />
<div>== Place and Time ==<br />
<br />
We meet in #inkscape-devel on [https://freenode.net/ freenode].<br />
<br />
Board meetings are typically the first Friday of each month.<br />
<br />
<em>Everybody in the Inkscape community is invited to participate.</em><br />
<br />
Next meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=5&year=2019&hour=17&min=00&sec=0&p1=0 10:00 PDT/17:00 UTC/19:00 CEST, (click for world clock)], Fri, 5th April, 2019. (Time is fixed to 10 AM Pacific Time.)<br />
<br />
Meetings should be announced in advance on [https://lists.sourceforge.net/lists/listinfo/inkscape-devel inkscape-devel] and [https://lists.sourceforge.net/lists/listinfo/inkscape-board inkscape-board] mailing lists.<br />
<br />
* Hackfest [http://libregraphicsmeeting.org/2019/ LGM 2019]<br />
** May 30th-June 3rd (Saarbrucken, Germany)<br />
** Travelers should have arrangements made<br />
<br />
* GSoC<br />
<br />
* Budget<br />
<br />
* Bug migration off Launchpad<br />
<br />
* Infrastructure<br />
** mailing list migration off SourceForge<br />
** Wiki migration off OSUOSL<br />
** Weblate service deployment<br />
<br />
* Software Release status<br />
** 2geom 1.1<br />
** Inkscape 0.92.5<br />
** Inkscape 1.0beta<br />
<br />
* Other Business<br />
<br />
== Other Agenda Items ==<br />
* Sponsor acceptance policy<br />
* Funded development [bryce]<br />
** Identify Manager/Reviewer/Second for each of the jobs<br />
** How should we advertise the jobs?<br />
* Outreachy: Next round starts in August [https://www.outreachy.org/mentor/]<br />
<br />
=== Action Items ===<br />
* Future hackfests<br />
** Hackfest organizational tips (Need to document this someplace)<br />
*** Process: Have folks propose options, and then trade off cost projections and benefits<br />
*** Try to organize group lodging (same hotel, rented/air-bnb house, http://www.linuxhotel.de/community.en.html, etc.)<br />
*** Send a scout ahead of time to help avoid slummy accommodations<br />
*** Catered lunches help keep everyone focused (we're already reimbursing on lunches, so cost differential isn't huge, and it saves hassle all around)<br />
*** Boots on the ground at a location can be a huge help if plans go awry<br />
*** Prefer locations with local inkscape community on the ground<br />
<br />
* [https://inkscape.org/en/support-us/funded-development/ Funded development] [bryce]<br />
* Add a C++-11 conversion project with tasks detailed to the Roadmap for 0.93 or later. [valavanisalex]<br />
* Regularly check [[Sponsors_list|sponsor status]]<br />
<br />
== Blocked Action Items ==<br />
<br />
* Privacy Policy [drmo] ~ Blocked waiting on time availability by SFC<br />
* Amend CoC reporting section ~ Waiting until we have a dedicated email, e.g. abuse@inkscape.org<br />
<br />
<br />
== Board Meeting Transcripts == <br />
<br />
=== 2019 ===<br />
<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2019-03-01.log.html 2019-03-01]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2019-02-01.log.html 2019-02-01]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2019-01-04.log.html 2019-01-04]<br />
<br />
=== 2018 ===<br />
<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-12-07.log.html 2018-12-07]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-11-02.log.html 2018-11-02]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-10-05.log.html 2018-10-05]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-09-07.log.html 2018-09-07]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-08-03.log.html 2018-08-03]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-07-06.log.html 2018-07-06]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-06-01.log.html 2018-06-01]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-05-04.log.html 2018-05-04]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-04-06.log.html 2018-04-06]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/board_meeting_2018-03-02.html 2018-03-02]<br />
* [https://inkscape.org/gallery/item/12009/ 2018-02-02]<br />
* [https://inkscape.org/gallery/item/11875/ 2018-01-05]<br />
<br />
=== 2017 ===<br />
<br />
* [https://inkscape.org/paste/11743/ 2017-12-01]<br />
* [https://inkscape.org/paste/11651/ 2017-11-03]<br />
* [https://inkscape.org/gallery/item/11517/ 2017-10-06]<br />
* [https://inkscape.org/gallery/item/11377/ 2017-09-01]<br />
* [https://inkscape.org/gallery/item/11250/ 2017-08-04]<br />
* [https://inkscape.org/gallery/item/11176/ 2017-07-07]<br />
* [https://inkscape.org/gallery/item/11064/ 2017-06-02]<br />
* [https://inkscape.org/gallery/item/10844/ 2017-04-07]<br />
* [https://inkscape.org/gallery/item/10740/ 2017-03-03]<br />
* [https://inkscape.org/gallery/item/10651/ 2017-02-03]<br />
* [https://inkscape.org/gallery/item/10582/ 2017-01-06]<br />
<br />
=== 2016 ===<br />
<br />
* [https://inkscape.org/gallery/item/10484/ 2016-12-02]<br />
* [https://inkscape.org/gallery/item/10241/ 2016-11-04]<br />
* [https://inkscape.org/gallery/item/9971/ 2016-09-02]<br />
* [https://inkscape.org/gallery/item/9864/ 2016-08-05]<br />
* [https://inkscape.org/gallery/item/9766/ 2016-07-08]<br />
* [https://inkscape.org/gallery/item/9667/ 2016-06-03]<br />
* [https://inkscape.org/gallery/item/9563/ 2016-05-06]<br />
* [https://inkscape.org/gallery/item/9565/ 2016-04-01]<br />
<br />
* [https://inkscape.org/gallery/item/7276/ 2016-01-08]<br />
<br />
=== 2015 ===<br />
<br />
* [https://inkscape.org/gallery/item/7056/ 2015-12-04]<br />
* [https://inkscape.org/gallery/item/6886/ 2015-11-06]<br />
* [https://inkscape.org/gallery/item/6701/ 2015-10-02]<br />
<br />
=== 2014 ===<br />
<br />
* [https://inkscape.org/gallery/item/2498/ 2014-11-26]<br />
* [https://inkscape.org/gallery/item/2216/ 2014-11-19]<br />
* [https://inkscape.org/gallery/item/2210/ 2014-11-12]<br />
* [https://inkscape.org/gallery/item/2204/ 2014-11-05]<br />
* [https://inkscape.org/gallery/item/1436/ 2014-10-15]<br />
* [https://inkscape.org/gallery/item/950/ 2014-10-08]<br />
* [https://inkscape.org/gallery/item/854/ 2014-09-29]<br />
* [https://inkscape.org/gallery/item/392/ 2014-09-15]<br />
<br />
'''[https://inkscape.org/en/gallery/=pastebin/?q=meeting&order=-edited Website search for all transcripts]'''</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114356Fundraising Ideas2019-03-22T15:54:56Z<p>BryceHarrington: </p>
<hr />
<div>This file outlines some blue-sky brainstorming thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
Note that these are not vetted ideas - some may not be permissible under our non-profit designation. Others may be permitted but may be controversial (e.g. ads), however we're listing them here as food for thought.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $NNk<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $20 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* T-Shirts, Hats, Mugs, Buttons, Stickers, Hoodies, Polos, etc.<br />
** cafepress.com<br />
<br />
* High quality clothing.<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
<br />
== Art auctions / sales ==<br />
<br />
Ask artists to provide their work to the project, either as a full donation, or a split of the proceeds. Then auction signed prints or originals, and offer direct purchase of unsigned prints.<br />
<br />
<br />
== Printed version of manual ==<br />
<br />
* We have already been getting book royalties from Packt, could expand on that with new books?<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
<br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
== App Stores ==<br />
<br />
In App Stores, instead of providing the built software entirely for free, provide it for a Suggested Donation.<br />
<br />
Homebrew "Suggested Donation" with download<br />
+ Target all the funds to Mac support<br />
<br />
In cases where the store does not provide a "Suggested Donation" option, consider listing it for a fee but emphasize that the same packages are also available from inkscape.org for no charge.<br />
<br />
== adsense Ads ==<br />
<br />
Simple text ads integrated into the website<br />
<br />
== Purchased Ads ==<br />
<br />
Certain pages of the website are devoted to specialized advertisements, provided to specific companies with relation to Inkscape.<br />
<br />
== Youtube Channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Affiliate Links ==<br />
<br />
SEO companies will pay for sponsorship to get dofollow links to their site.<br />
<br />
== Amazon Commission ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
<br />
= Services =<br />
<br />
== Service Raffle ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffle tickets for $20-50 each - keep it a little high so you don’t have to sell so many and so that the buyers have a higher chance of winning. Encourage people to buy several, by offering discounts for multiple purchases (1 for $20, 2 for $36, 3 for $50, etc.)<br />
<br />
Services can include:<br />
* creating logos<br />
* Business card design<br />
* Brochure design<br />
* Christmas or birthday cards<br />
* Graduation announcements<br />
<br />
<br />
== Design Service Broker ==<br />
<br />
Recruit our artists to do contracted design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, drawing, programming, proposal writing, etc. Charge $50-75 suggested donation per person, with a goal of 15 to 20 people. Record a video and provide it online for suggested donation.<br />
<br />
<br />
== Priority User Support ==<br />
<br />
For a recurring fee, we provide prioritized question answering by a seasoned Inkscape pro, up to a fixed number of hours per week.<br />
<br />
== Technical Support ==<br />
<br />
For a recurring fee, we provide access to a developer to help troubleshoot problems and work on selected bugs as directed by the client.<br />
<br />
<br />
== Custom Interface Spins ==<br />
<br />
We provide builds of Inkscape with some basic interface customizations, such as simplifying it by removing some unneeded functionality. The result is still covered under the GPL. We provide packaged versions for them to give their users or distribute with their product. For additional fee we also allow them to tweak the branding to some degree. We maintain the spin against current master, for an annual charge.<br />
<br />
<br />
== Custom Extensions ==<br />
<br />
We implement extensions customized to their particular service or product, that they can offer from their website, or include in copies of Inkscape they distribute themselves. The extension is covered as GPL, but can be licensed differently for additional fees.<br />
<br />
== Hosting Services ==<br />
<br />
We provide use of our infrastructure services to projects or companies for an arranged fee or sponsorship payment.<br />
* Mailing lists<br />
* DNS<br />
* @<project>.org email aliases<br />
* Cloud computing nodes<br />
* Build systems (Mac, Windows)<br />
<br />
= Sponsorship =<br />
<br />
== Website General Fund Sponsors ==<br />
<br />
Our regular sponsorship levels, with reward being placement on the sponsors web page.<br />
<br />
== Event Sponsors ==<br />
<br />
Funds go directly towards hackfest travel attendance, or attendance at LGM, SCALE, and other conferences. We will display their logo in our booth banners and handout materials.<br />
<br />
<br />
= Misc Other Ideas =<br />
<br />
* Sell your frequent flyer miles to friends or donate them to the organization for a raffle. Watch the rules of the airline on this, but some airlines let you give away miles, and you may be able to sell your miles as long as you don’t go through a mileage broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
More ideas:<br />
* http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf<br />
* http://www.ianbicking.org/blog/2019/03/open-source-doesnt-make-money-by-design.html</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=114176Inkscape Classes2019-03-19T21:16:55Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 16 !! Sat, Mar 23 !! Sat, Mar 30 !! Sat, Apr 6 !! Sat, Apr 13<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| [https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fundraising+for+FOSS+Projects&iso=20190316T19&p1=%3A&ah=1&am=30 <span title="Convert to local time">⏰</span>] '''Fundraising for FOSS Projects''' <br> '''(1½ hr)''' ''[[https://chat.inkscape.org/channel/collaboration_space Watch Party at the #Collaboration_space chat channel]]'' || || || || <br />
|-<br />
! 20:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together [https://chat.inkscape.org/channel/collaboration_space on Rocket.Chat in channel #collaboration_space] at the given time ([https://www.worldtimeserver.com/convert_time_in_UTC.aspx convert UTC to local time zone]), to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
== '''Fundraising for open source projects:''' ==<br />
''Hosts:'' Michèle, Bryce<br />
* https://www.youtube.com/watch?v=nGKSnMdBFsk - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
See also [[Fundraising_Ideas]]<br />
<br />
== Other Topics Ideas ==<br />
<br />
* Bradley Kuhn SCALE 2019 presentation on FOSS sustainability - (video link tbd; summary at https://lwn.net/SubscriberLink/783169/910bdd575799ed63/)<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Writing Extensions 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=114171Inkscape Classes2019-03-16T17:56:59Z<p>BryceHarrington: /* Fundraising for open source projects: */</p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 16 !! Sat, Mar 23 !! Sat, Mar 30 !! Sat, Apr 6 !! Sat, Apr 13<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| [https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fundraising+for+FOSS+Projects&iso=20190316T19&p1=%3A&ah=1&am=30 <span title="Convert to local time">⏰</span>] '''Fundraising for FOSS Projects''' <br> '''(1½ hr)''' ''[[https://chat.inkscape.org/channel/collaboration_space Watch Party at the #Collaboration_space chat channel]]'' || || || || <br />
|-<br />
! 20:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together [https://chat.inkscape.org/channel/collaboration_space on Rocket.Chat in channel #collaboration_space] at the given time ([https://www.worldtimeserver.com/convert_time_in_UTC.aspx convert UTC to local time zone]), to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
== '''Fundraising for open source projects:''' ==<br />
''Hosts:'' Michèle, Bryce<br />
* https://www.youtube.com/watch?v=nGKSnMdBFsk - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
See also [[Fundraising_Ideas]]<br />
<br />
== Other Topics Ideas ==<br />
<br />
* Bradley Kuhn presentations (from SCALE, if available)<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Writing Extensions 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114111Fundraising Ideas2019-03-13T05:35:01Z<p>BryceHarrington: </p>
<hr />
<div>This file outlines some blue-sky brainstorming thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
Note that these are not vetted ideas - some may not be permissible under our non-profit designation. Others may be permitted but may be controversial (e.g. ads), however we're listing them here as food for thought.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $NNk<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $20 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* T-Shirts, Hats, Mugs, Buttons, Stickers, Hoodies, Polos, etc.<br />
** cafepress.com<br />
<br />
* High quality clothing.<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
<br />
== Art auctions / sales ==<br />
<br />
Ask artists to provide their work to the project, either as a full donation, or a split of the proceeds. Then auction signed prints or originals, and offer direct purchase of unsigned prints.<br />
<br />
<br />
== Printed version of manual ==<br />
<br />
* We have already been getting book royalties from Packt, could expand on that with new books?<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
<br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
== App Stores ==<br />
<br />
In App Stores, instead of providing the built software entirely for free, provide it for a Suggested Donation.<br />
<br />
Homebrew "Suggested Donation" with download<br />
+ Target all the funds to Mac support<br />
<br />
In cases where the store does not provide a "Suggested Donation" option, consider listing it for a fee but emphasize that the same packages are also available from inkscape.org for no charge.<br />
<br />
== adsense Ads ==<br />
<br />
Simple text ads integrated into the website<br />
<br />
== Purchased Ads ==<br />
<br />
Certain pages of the website are devoted to specialized advertisements, provided to specific companies with relation to Inkscape.<br />
<br />
== Youtube Channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Affiliate Links ==<br />
<br />
SEO companies will pay for sponsorship to get dofollow links to their site.<br />
<br />
== Amazon Commission ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
<br />
= Services =<br />
<br />
== Service Raffle ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffle tickets for $20-50 each - keep it a little high so you don’t have to sell so many and so that the buyers have a higher chance of winning. Encourage people to buy several, by offering discounts for multiple purchases (1 for $20, 2 for $36, 3 for $50, etc.)<br />
<br />
Services can include:<br />
* creating logos<br />
* Business card design<br />
* Brochure design<br />
* Christmas or birthday cards<br />
* Graduation announcements<br />
<br />
<br />
== Design Service Broker ==<br />
<br />
Recruit our artists to do contracted design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, drawing, programming, proposal writing, etc. Charge $50-75 suggested donation per person, with a goal of 15 to 20 people. Record a video and provide it online for suggested donation.<br />
<br />
<br />
== Priority User Support ==<br />
<br />
For a recurring fee, we provide prioritized question answering by a seasoned Inkscape pro, up to a fixed number of hours per week.<br />
<br />
== Technical Support ==<br />
<br />
For a recurring fee, we provide access to a developer to help troubleshoot problems and work on selected bugs as directed by the client.<br />
<br />
<br />
== Custom Interface Spins ==<br />
<br />
We provide builds of Inkscape with some basic interface customizations, such as simplifying it by removing some unneeded functionality. The result is still covered under the GPL. We provide packaged versions for them to give their users or distribute with their product. For additional fee we also allow them to tweak the branding to some degree. We maintain the spin against current master, for an annual charge.<br />
<br />
<br />
== Custom Extensions ==<br />
<br />
We implement extensions customized to their particular service or product, that they can offer from their website, or include in copies of Inkscape they distribute themselves. The extension is covered as GPL, but can be licensed differently for additional fees.<br />
<br />
== Hosting Services ==<br />
<br />
We provide use of our infrastructure services to projects or companies for an arranged fee or sponsorship payment.<br />
* Mailing lists<br />
* DNS<br />
* @<project>.org email aliases<br />
* Cloud computing nodes<br />
* Build systems (Mac, Windows)<br />
<br />
<br />
= Sponsorship =<br />
<br />
== Website General Fund Sponsors ==<br />
<br />
Our regular sponsorship levels, with reward being placement on the sponsors web page.<br />
<br />
== Event Sponsors ==<br />
<br />
Funds go directly towards hackfest travel attendance, or attendance at LGM, SCALE, and other conferences. We will display their logo in our booth banners and handout materials.<br />
<br />
<br />
= Misc Other Ideas =<br />
<br />
* Sell your frequent flyer miles to friends or donate them to the organization for a raffle. Watch the rules of the airline on this, but some airlines let you give away miles, and you may be able to sell your miles as long as you don’t go through a mileage broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
<br />
<br />
More ideas:<br />
http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114106Fundraising Ideas2019-03-13T05:05:55Z<p>BryceHarrington: </p>
<hr />
<div>This file outlines some thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $NNk<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $28 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* T-Shirts, Hats, Mugs, Buttons, Stickers, etc.<br />
** cafepress.com<br />
<br />
* High quality clothing.<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
<br />
== Art auctions / sales ==<br />
<br />
Ask artists to provide their work to the project, either as a full donation, or a split of the proceeds. Then auction signed prints or originals, and offer direct purchase of unsigned prints.<br />
<br />
<br />
== Printed version of manual ==<br />
<br />
* We have already been getting book royalties from Packt<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
, provided <br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
== adsense Ads ==<br />
<br />
Simple text ads integrated into the website<br />
<br />
== Purchased Ads ==<br />
<br />
Certain pages of the website are devoted to specialized advertisements, provided to specific companies with relation to Inkscape.<br />
<br />
== Youtube Channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Affiliate Links ==<br />
<br />
SEO companies will pay for sponsorship to get dofollow links to their site.<br />
<br />
== Amazon Commission ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
<br />
= Services =<br />
<br />
== Service Raffle ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffle tickets for $20-50 each - keep it a little high so you don’t have to sell so many and so that the buyers have a higher chance of winning. Encourage people to buy several, by offering discounts for multiple purchases (1 for $20, 2 for $36, 3 for $50, etc.)<br />
<br />
Services can include:<br />
* creating logos<br />
* Business card design<br />
* Brochure design<br />
* Christmas or birthday cards<br />
* Graduation announcements<br />
<br />
<br />
== Design Service Broker ==<br />
<br />
Recruit our artists to do contracted design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, drawing, programming, proposal writing, etc. Charge $50-75 suggested donation per person, with a goal of 15 to 20 people. Record a video and provide it online for suggested donation.<br />
<br />
<br />
= Sponsorship =<br />
<br />
== Website General Fund Sponsors ==<br />
<br />
Our regular sponsorship levels, with reward being placement on the sponsors web page.<br />
<br />
<br />
== Direct sponsorship of our hackfest events ==<br />
<br />
Funds go directly towards hackfest travel attedance.<br />
<br />
<br />
= Misc Other Ideas =<br />
<br />
* Sell your frequent flyer miles to friends or donate them to the organization for a raffle. Watch the rules of the airline on this, but some airlines let you give away miles, and you may be able to sell your miles as long as you don’t go through a mileage broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
* Homebrew "Suggested Donation" with download<br />
+ Target all the funds to Mac support<br />
<br />
<br />
More ideas:<br />
http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114101Fundraising Ideas2019-03-12T22:32:03Z<p>BryceHarrington: </p>
<hr />
<div>This file outlines some thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $5k<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $28 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* Sales of T-Shirts, Hats, Mugs, etc.<br />
<br />
* cafepress.com<br />
<br />
* High quality clothing though.<br />
<br />
* Sell buttons, T-shirts, etc. Distribute to bookstores or novelty shops<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
== Art auctions / sales ==<br />
<br />
* Art donations from artists, sold, and proceeds split<br />
<br />
* Ask artists to donate a work to the project, and then have a charity auction for the pieces (including the copyright??) Use the proceeds to fund development projects.<br />
<br />
* Art prints auctions<br />
<br />
<br />
== Printed version of manual ==<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
<br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
<br />
== Youtube channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Amazon Affiliation ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
<br />
= Services =<br />
<br />
== Design services ==<br />
<br />
* Logothon - we enlist our users in producing logos for other open source projects or companies. 50% goes to artist, 50% to Inkscape.<br />
<br />
* Business Card Designs - Recruit our artists to do business card design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
* If you have an artistic bent, offer to design greeting cards to specification for organizations or individuals for a fee. If you are good at calligraphy, sell your skills to schools for graduation announcements, friends for classy but low-cost wedding invitations, or just fun certificates such as “World’s Greatest Dad” for Father’s Day or “Outstanding Friend.” Create unique Halloween costumes or masks. Donate the proceeds from your artistry.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, knitting, organic gardening, organizing, proposal writing, environmentalim pact reports, gourmet cooking, dog grooming, starting your own business. Charge $50-75 per person, with a goal of 15 to 20 people. Either absorb the cost of promotion, or have enough participants to cover it.<br />
<br />
<br />
== Organize a service raffle. ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffel tickets for $10-20 each - keep it a little high so you don’t have to sell so many and<br />
so that the buyers have a higher chance of winning. Services can include<br />
childcare for a weekend or for any weekend night two weekends in a row;<br />
one day of housecleaning; yard work; house painting (interior or exterior), etc. Sell the tickets to neighbors, work mates and to other<br />
board members. Encourage people to buy several by offering discounts for<br />
multiple purchases, such as one for $10, 2 for $20, but 3 for $25, 4 for<br />
$35, 5 for $40. If you are really bold or live in a more affluent area,<br />
or have few friends, sell the tickets for $50 each. A full day of<br />
housecleaning for $50 is a real bargain, and buyers have a high chance<br />
of winning with fewer tickets sold<br />
<br />
<br />
== Hold an “I’m Not Afraid” Auction ==<br />
<br />
You can do this with just a few friends or hundreds of people if you<br />
have enough items to auction. You survey a few people (and use your own<br />
common sense) about what things need to be done in their home or office<br />
that they are afraid of or would really rather not do. This is different<br />
from a service auction - there has to be an element of dread in the<br />
activity. For example, some people cannot wash their windows because<br />
their apartment is too high or the second story of their house is too<br />
high and they suffer from vertigo. If you are not afraid of heights,<br />
you can sell your window-washing service (bring a sturdy ladder). This<br />
goes for drain cleaning, minor roof repairs, antenna fixing, etc. Or,<br />
if you are unafraid of cockroaches or spiders, you can offer to clean<br />
out that dark corner or garage or basement for a small fee. Snakes can<br />
be found in gardens and woodsheds, but maybe that doesn’t bother<br />
you. The problem doesn’t need to be as serious as phobia. How about<br />
allergies to dust, pollen, weeds? If you don’t have them , you can mow,<br />
sweep, clean for a fee. By marketing it as an “I’m Not Afraid” Auction,<br />
you also have the option for people to name something they need done to<br />
a group of volunteers, and then have a volunteer say, “I’m not afraid<br />
to do that.” In that case , you will need a set fee for service.<br />
<br />
<br />
== Rebranding Auction ==<br />
<br />
<br />
Similar to the suggestion above is the “Details Auction.” This is for all your friends whose desks<br />
are overflowing with papers or who can’t get their receipts in order to<br />
give to the tax preparer or who complain t hey can never find<br />
anything. If you are a well-organized person, offer to clean up their<br />
desk, get their Rolodex in order, file their papers, etc. If you like<br />
to shop, sell that to people who don’t and do their holiday shopping for<br />
them, or buy birthday, baby shower or niece/nephew presents for<br />
them. Anything that people feel they cannot control is the organized<br />
person’s fundraising dream come true.<br />
<br />
<br />
= Misc Other Ideas =<br />
<br />
* Direct sponsorship of our hackfest events<br />
<br />
* Lead or get someone to lead a nature walk, an architectural tour, a<br />
historic tour, a sailing trip, a rafting trip, or a horseback ride.<br />
Charge $15-$25 per person, or charge $35 and provide lunch. Advertise<br />
the event in the newspaper to draw in people from outside your<br />
organization.<br />
<br />
* Sell your frequent flyer miles to friends or<br />
donate them to the organization for a raffle. Watch the rules of the<br />
airline on this, but some airlines let you give away miles, and you may<br />
be able to sell your miles as long as you don’t go through a mileage<br />
broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* Solicit small businesses, churches,<br />
synagogues or service clubs for $1000. If you are active in a church or<br />
you own your own business and are involved in business organizations or<br />
service clubs, this can be very effective. You can often raise<br />
$200-$1000 with a simple proposal and oral presentation.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
* Website Revenue<br />
+ adsense<br />
+ purchased ads<br />
+ Affiliate "dofollow" links<br />
<br />
* Homebrew "Suggested Donation" with download<br />
+ Target all the funds to Mac support<br />
<br />
<br />
More ideas:<br />
http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Fundraising_Ideas&diff=114096Fundraising Ideas2019-03-12T17:43:49Z<p>BryceHarrington: </p>
<hr />
<div>This file outlines some thoughts regarding handling of donations and other income for the Inkscape Project.<br />
<br />
= Direct Asks =<br />
<br />
== Donation solicitation ==<br />
<br />
* We currently already provide a paypal link for visitors to donate to us.<br />
<br />
* Ask Inkscape users and contributors to each ask 5 or 10 of their friends, family, and co-workers to donate to the Inkscape project's PayPal account.<br />
<br />
* Suggest people ask for donations to Inkscape in lieu of gifts. Birthdays, Christmas presents, and other events.<br />
<br />
* Find out which of your friends (perhaps this is true for you also) work in corporations with matching gift programs. Then ask them to donate and get their gift matched for your organization and ask them to ask their co-workers to donate and get their gifts matched.<br />
<br />
* Have Inkscape fans reach out to their friends and family interested in supporting art and/or FOSS. Decide a range or a fixed amount for the ask. Send them a brochure from the organization and an envelope or easy link to make payment.<br />
Re-contact those people who don’t respond in two weeks.<br />
<br />
* Ask people who use Inkscape in their business to send an appeal to their clients and customers, like, “You are one of my best customers. As such, I let you know about sales coming up and good things happening in my store. Today, I want to tell<br />
you about another good thing—what I do when I am not minding the store.” Then go on to describe the group and ask for a donation. Also post the letter on your website with a link to Inkscape's paypal page.<br />
<br />
== Fundathon ==<br />
<br />
Call for donations to increase the fund by $5k<br />
<br />
== Challenge campaign ==<br />
<br />
Set a challenge of raising $10,000. Give part of the $10,000. Then ask your friends to join you in giving $50, $100, or whatever amount you gave. This is most effective because you are not asking them to do anything you haven’t done.<br />
<br />
Challenge gifts can be quite small. Tell people you’ll give $5 for every $25 they give, or will match every $50 gift up to ten gifts. For added suspense, make this challenge during a fundraising event. You or the host can announce, “We now have the Dave Buckstretch Challenge. For the next five minutes, Dave will give $5 for every new member that joins Worthy Cause.”<br />
<br />
== Adoption Campaign ==<br />
<br />
Create a take-off on the “adopt-a-highway” technique by naming budget items of your group as available for adoption. You could develop a flyer that reads, “The following items have been found near death from negligence and abuse. Won’t you help? $25 per month will ensure that our computer is maintained. $100 per month will release our photocopy machine from toiling with no toner and a dying motor. (We can lease a new one.)”<br />
<br />
<br />
== Ongoing subscriptions ==<br />
<br />
Pledge $28 (or whatever) a month, and get two others to do likewise. <br />
<br />
<br />
== Conference Booth ==<br />
<br />
Print nice donation envelopes to include in our conference booths.<br />
Give some to conservancy to have at their booths.<br />
<br />
Send people to events to man booths with the express aim of raising<br />
money and spreading awareness. Maybe do in conjunction with<br />
conservancy?<br />
<br />
<br />
== Fundraising Events ==<br />
<br />
Get a famous or popular person to do a special event. Watch the costs on this, or you may lose money.<br />
<br />
<br />
= Products =<br />
<br />
<br />
== Merchandise ==<br />
<br />
* Sales of T-Shirts, Hats, Mugs, etc.<br />
<br />
* cafepress.com<br />
<br />
* High quality clothing though.<br />
<br />
* Sell buttons, T-shirts, etc. Distribute to bookstores or novelty shops<br />
<br />
* Raffle or contest items signed by inkscape devs at hackfests<br />
<br />
== Art auctions / sales ==<br />
<br />
* Art donations from artists, sold, and proceeds split<br />
<br />
* Ask artists to donate a work to the project, and then have a charity auction for the pieces (including the copyright??) Use the proceeds to fund development projects.<br />
<br />
* Art prints auctions<br />
<br />
<br />
== Printed version of manual ==<br />
<br />
<br />
== CD's of Inkscape + Open Clip Art Library ==<br />
<br />
Sell for $20, split 50/50 with OCAL<br />
<br />
<br />
= Digital =<br />
<br />
<br />
== Youtube channel ==<br />
<br />
Showcase work done by users. Show off features under development. Share status about the project.<br />
<br />
Build a large enough audience to earn money from ad and other revenue.<br />
<br />
== Amazon Affiliation ==<br />
<br />
Amazon pays 2.5-6.0% commission on affiliate sale.<br />
<br />
* Think of stores or services related to your organization or where a lot of your members shop.<br />
Ask the store to donate a percentage of profits for a certain day or<br />
week, or even forever. You can also explore this with mail-order<br />
firms. Then you advertise widely to friends, family and members that<br />
Joe’s Florist will give 2% of each sale during Valentine’s weekend to<br />
anyone identifying themselves with your group.<br />
<br />
== Instructional Videos ==<br />
<br />
Class tutorials on using Inkscape, with good quality voice over. Revenue comes from subscription fees to access the classes.<br />
<br />
Consider using experienced teachers, actors, or artists that can give real sophistication to our materials, paid either upfront or with a revenue split.<br />
<br />
Alternatively, let the classes be organized and charged for by a 3rd party group, who donates a portion of their revenue to the project, perhaps in exchange for being linked to from the inkscape.org site.<br />
<br />
<br />
= Services =<br />
<br />
== Design services ==<br />
<br />
* Logothon - we enlist our users in producing logos for other open source projects or companies. 50% goes to artist, 50% to Inkscape.<br />
<br />
* Business Card Designs - Recruit our artists to do business card design services, with a portion of the proceeds returned to the project. Serve as a broker to match design needs with artists.<br />
<br />
* If you have an artistic bent, offer to design greeting cards to specification for organizations or individuals for a fee. If you are good at calligraphy, sell your skills to schools for graduation announcements, friends for classy but low-cost wedding invitations, or just fun certificates such as “World’s Greatest Dad” for Father’s Day or “Outstanding Friend.” Create unique Halloween costumes or masks. Donate the proceeds from your artistry.<br />
<br />
<br />
== Teaching Classes ==<br />
<br />
Teach a seminar on a topic you know: fundraising, knitting, organic gardening, organizing, proposal writing, environmentalim pact reports, gourmet cooking, dog grooming, starting your own business. Charge $50-75 per person, with a goal of 15 to 20 people. Either absorb the cost of promotion, or have enough participants to cover it.<br />
<br />
<br />
== Organize a service raffle. ==<br />
<br />
Identify a simple but valuable service that one or more members of the group could provide in donation. Sell raffel tickets for $10-20 each - keep it a little high so you don’t have to sell so many and<br />
so that the buyers have a higher chance of winning. Services can include<br />
childcare for a weekend or for any weekend night two weekends in a row;<br />
one day of housecleaning; yard work; house painting (interior or exterior), etc. Sell the tickets to neighbors, work mates and to other<br />
board members. Encourage people to buy several by offering discounts for<br />
multiple purchases, such as one for $10, 2 for $20, but 3 for $25, 4 for<br />
$35, 5 for $40. If you are really bold or live in a more affluent area,<br />
or have few friends, sell the tickets for $50 each. A full day of<br />
housecleaning for $50 is a real bargain, and buyers have a high chance<br />
of winning with fewer tickets sold<br />
<br />
<br />
== Hold an “I’m Not Afraid” Auction ==<br />
<br />
You can do this with just a few friends or hundreds of people if you<br />
have enough items to auction. You survey a few people (and use your own<br />
common sense) about what things need to be done in their home or office<br />
that they are afraid of or would really rather not do. This is different<br />
from a service auction - there has to be an element of dread in the<br />
activity. For example, some people cannot wash their windows because<br />
their apartment is too high or the second story of their house is too<br />
high and they suffer from vertigo. If you are not afraid of heights,<br />
you can sell your window-washing service (bring a sturdy ladder). This<br />
goes for drain cleaning, minor roof repairs, antenna fixing, etc. Or,<br />
if you are unafraid of cockroaches or spiders, you can offer to clean<br />
out that dark corner or garage or basement for a small fee. Snakes can<br />
be found in gardens and woodsheds, but maybe that doesn’t bother<br />
you. The problem doesn’t need to be as serious as phobia. How about<br />
allergies to dust, pollen, weeds? If you don’t have them , you can mow,<br />
sweep, clean for a fee. By marketing it as an “I’m Not Afraid” Auction,<br />
you also have the option for people to name something they need done to<br />
a group of volunteers, and then have a volunteer say, “I’m not afraid<br />
to do that.” In that case , you will need a set fee for service.<br />
<br />
<br />
== Rebranding Auction ==<br />
<br />
<br />
Similar to the suggestion above is the “Details Auction.” This is for all your friends whose desks<br />
are overflowing with papers or who can’t get their receipts in order to<br />
give to the tax preparer or who complain t hey can never find<br />
anything. If you are a well-organized person, offer to clean up their<br />
desk, get their Rolodex in order, file their papers, etc. If you like<br />
to shop, sell that to people who don’t and do their holiday shopping for<br />
them, or buy birthday, baby shower or niece/nephew presents for<br />
them. Anything that people feel they cannot control is the organized<br />
person’s fundraising dream come true.<br />
<br />
<br />
= Misc Other Ideas =<br />
<br />
* Direct sponsorship of our hackfest events<br />
<br />
* Lead or get someone to lead a nature walk, an architectural tour, a<br />
historic tour, a sailing trip, a rafting trip, or a horseback ride.<br />
Charge $15-$25 per person, or charge $35 and provide lunch. Advertise<br />
the event in the newspaper to draw in people from outside your<br />
organization.<br />
<br />
* Sell your frequent flyer miles to friends or<br />
donate them to the organization for a raffle. Watch the rules of the<br />
airline on this, but some airlines let you give away miles, and you may<br />
be able to sell your miles as long as you don’t go through a mileage<br />
broker.<br />
<br />
* Get members and friends to include the group for bequests in their wills.<br />
<br />
* Solicit small businesses, churches,<br />
synagogues or service clubs for $1000. If you are active in a church or<br />
you own your own business and are involved in business organizations or<br />
service clubs, this can be very effective. You can often raise<br />
$200-$1000 with a simple proposal and oral presentation.<br />
<br />
* A monthly kid's magazine sold for $20/yr<br />
+ PDF electronic copy for less?<br />
+ Coloring pages<br />
+ Drawing tips and tricks<br />
+ Stickers<br />
<br />
<br />
More ideas:<br />
http://www.nonprofitalliance.org/system/res/25/original/Board_Member_Packet.pdf</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Saarbr%C3%BCcken_Topics&diff=114021Hackfest2019 Saarbrücken Topics2019-03-08T07:35:51Z<p>BryceHarrington: Created page with "Other pages: Hackfest2019 Saarbrücken, Hackfest2019 SCALE Topics, Hackfest2018 Kiel Topics. == Topics for Inkscape Hackfest 2019 in Saarbrücken == === Inkscape..."</p>
<hr />
<div>Other pages: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 SCALE Topics]], [[Hackfest2018 Kiel Topics]].<br />
<br />
== Topics for Inkscape Hackfest 2019 in Saarbrücken ==<br />
<br />
=== Inkscape 1.0 release ===<br />
* Fix priority bugs<br />
* Testing<br />
* Announcement preparations<br />
<br />
=== Recruiting of new developers ===<br />
* Extensions seems to be a popular path.<br />
* Encourage people to write extensions.<br />
* Organized outreach/recruitment efforts?<br />
* Review developer onboarding guidelines<br />
* What are the major questions new devs have<br />
* What areas of the codebase do we need stronger institutional memory in?<br />
<br />
=== Infrastructure ===<br />
* Bug migration<br />
* WebLate</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Saarbr%C3%BCcken_Attendees&diff=114011Hackfest2019 Saarbrücken Attendees2019-03-07T20:42:15Z<p>BryceHarrington: /* Unconfirmed but Likely Attendees */</p>
<hr />
<div>Other pages: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 SCALE]]. <br />
<br />
== Confirmed Attendees ==<br />
<br />
<br />
<br />
== Unconfirmed but Likely Attendees ==<br />
<br />
* Marc Jeanmougin<br />
* Tavmjong Bah<br />
* Jürgen Weigert (arrival May-29th afternoon)<br />
* Max Gaukler<br />
* Tobias Ellinghaus (houz) - local<br />
* Maren Hachmann<br />
<br />
== Maybe ==<br />
<br />
== People to Invite ==<br />
<br />
* ede123 (Patrick)<br />
* speleo3 (Thomas Holder)<br />
* prkos (Mihaela)<br />
* Shlomi Fish<br />
* Jabier<br />
* Martin Owens<br />
* Anatoly (@techtonik on gitlab)<br />
* Thomas Wiesner (@wiesi on gitlab)<br />
* Juan Duarte (see chat.inkscape.org)<br />
* Olli (https://gitlab.com/ollip)<br />
* Alex Valavanis<br />
* Emmanuel Gil Peyrot (https://gitlab.com/linkmauve)<br />
* Sebastian Wüst (plotting expert https://www.timewasters-place.com/)<br />
* Alexandre Prokoudine (as guest? Might be there anyway.)<br />
* Khaled Hosny (font expert)<br />
* Antonio Hospite (https://gitlab.com/ao2)<br />
* Michael Soegtrop (https://gitlab.com/users/MSoegtrop)<br />
* Simon Wells (https://gitlab.com/xzcvczx)<br />
* probono<br />
* Nicolas<br />
* su_v<br />
* Johan Engelen<br />
* Bryce Harrington<br />
<br />
Possible others?<br />
* people on the mac-devel channel</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Saarbr%C3%BCcken_Attendees&diff=114006Hackfest2019 Saarbrücken Attendees2019-03-07T20:41:24Z<p>BryceHarrington: /* People to Invite */</p>
<hr />
<div>Other pages: [[Hackfest2019 Saarbrücken]], [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 SCALE]]. <br />
<br />
== Confirmed Attendees ==<br />
<br />
<br />
<br />
== Unconfirmed but Likely Attendees ==<br />
<br />
* Marc Jeanmougin<br />
* Tavmjong Bah<br />
* Jürgen Weigert (arrival May-29th afternoon)<br />
* Max Gaukler<br />
* Tobias Ellinghaus (houz) - local<br />
* Maren Hachmann<br />
<br />
== People to Invite ==<br />
<br />
* ede123 (Patrick)<br />
* speleo3 (Thomas Holder)<br />
* prkos (Mihaela)<br />
* Shlomi Fish<br />
* Jabier<br />
* Martin Owens<br />
* Anatoly (@techtonik on gitlab)<br />
* Thomas Wiesner (@wiesi on gitlab)<br />
* Juan Duarte (see chat.inkscape.org)<br />
* Olli (https://gitlab.com/ollip)<br />
* Alex Valavanis<br />
* Emmanuel Gil Peyrot (https://gitlab.com/linkmauve)<br />
* Sebastian Wüst (plotting expert https://www.timewasters-place.com/)<br />
* Alexandre Prokoudine (as guest? Might be there anyway.)<br />
* Khaled Hosny (font expert)<br />
* Antonio Hospite (https://gitlab.com/ao2)<br />
* Michael Soegtrop (https://gitlab.com/users/MSoegtrop)<br />
* Simon Wells (https://gitlab.com/xzcvczx)<br />
* probono<br />
* Nicolas<br />
* su_v<br />
* Johan Engelen<br />
* Bryce Harrington<br />
<br />
Possible others?<br />
* people on the mac-devel channel</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Saarbr%C3%BCcken&diff=113996Hackfest2019 Saarbrücken2019-03-07T20:12:59Z<p>BryceHarrington: </p>
<hr />
<div><br />
This page details the planning of Inkscape's 2019 hackfest in Saarbrücken, Germany, Monday May 27 to Sunday, June 2.<br />
<br />
Other pages: [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 Saarbrücken Attendees]].<br />
<br />
Old: [[Hackfest2019 SCALE]], [[Hackfest2018 Kiel]], [[Hackfest2018 LGM]], [[Hackfest2018]], [[Hackfest2017]], [[Hackfest2016]], [[Hackfest2015]].<br />
<br />
= Hackfest: Saarbrücken, Germany =<br />
<br />
==Description==<br />
<br />
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.<br />
The hackfest will take place in conjunction with the [https://libregraphicsmeeting.org/2019/ 2019 LGM conference].<br />
<br />
==Saarbrücken==<br />
<br />
[https://en.wikipedia.org/wiki/Saarbrücken Saarbrücken] is a city in the west of Germany, next to the border with France. It is about 2 hours from Paris and 3 hours from Frankfurt by train. There is a local airport (SCN) with some international flights.<br />
<br />
==Venue==<br />
<br />
The hackfest will take place at...<br />
<br />
===Catering===<br />
<br />
To do.<br />
<br />
===Facilities===<br />
<br />
* Wireless networking<br />
* Europlug type ...<br />
* Etc.<br />
<br />
===Nearby amenities===<br />
<br />
To do.<br />
<br />
==Hotels==<br />
<br />
To do.<br />
<br />
==Schedule==<br />
<br />
To do.<br />
<br />
==Hackfest Dinner==<br />
<br />
An informal dinner will be held one night. TBA.<br />
<br />
==Attendance==<br />
<br />
Anybody interested in Inkscape is welcome to attend. Funding support for travel expenses is based on past contributions to Inkscape. See the [[Hackfest2019 Saarbrücken Attendees]] page for more details.<br />
<br />
==Schedule==<br />
<br />
A schedule will be developed based on input from attendees and the Inkscape community. See the [[Hackfest2019 Saarbrücken Topics]] page for further details.<br />
<br />
==Helpers==<br />
<br />
The following folk have offered to assist with organization work, in limited capacities:<br />
<br />
* houz<br />
* Moini<br />
* octycs<br />
* Mc<br />
* Tav<br />
<br />
[[Category:Hackfest]]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Saarbr%C3%BCcken&diff=113991Hackfest2019 Saarbrücken2019-03-07T20:10:54Z<p>BryceHarrington: </p>
<hr />
<div><br />
This page details the planning of Inkscape's 2019 hackfest in Saarbrücken, Germany.<br />
<br />
Other pages: [[Hackfest2019 Saarbrücken Topics]], [[Hackfest2019 Saarbrücken Attendees]].<br />
<br />
Old: [[Hackfest2019 SCALE]], [[Hackfest2018 Kiel]], [[Hackfest2018 LGM]], [[Hackfest2018]], [[Hackfest2017]], [[Hackfest2016]], [[Hackfest2015]].<br />
<br />
= Hackfest: Saarbrücken, Germany=<br />
<br />
==Description==<br />
<br />
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.<br />
The hackfest will take place in conjunction with the [https://libregraphicsmeeting.org/2019/ 2019 LGM conference].<br />
<br />
==Saarbrücken==<br />
<br />
[https://en.wikipedia.org/wiki/Saarbrücken Saarbrücken] is a city in the west of Germany, next to the border with France. It is about 2 hours from Paris and 3 hours from Frankfurt by train. There is a local airport (SCN) with some international flights.<br />
<br />
==Venue==<br />
<br />
The hackfest will take place at...<br />
<br />
===Catering===<br />
<br />
To do.<br />
<br />
===Facilities===<br />
<br />
* Wireless networking<br />
* Europlug type ...<br />
* Etc.<br />
<br />
===Nearby amenities===<br />
<br />
To do.<br />
<br />
==Hotels==<br />
<br />
To do.<br />
<br />
==Schedule==<br />
<br />
To do.<br />
<br />
==Hackfest Dinner==<br />
<br />
An informal dinner will be held one night. TBA.<br />
<br />
==Attendance==<br />
<br />
Anybody interested in Inkscape is welcome to attend. Funding support for travel expenses is based on past contributions to Inkscape. See the [[Hackfest2019 Saarbrücken Attendees]] page for more details.<br />
<br />
==Schedule==<br />
<br />
A schedule will be developed based on input from attendees and the Inkscape community. See the [[Hackfest2019 Saarbrücken Topics]] page for further details.<br />
<br />
==Helpers==<br />
<br />
The following folk have offered to assist with organization work, in limited capacities:<br />
<br />
* houz<br />
* Moini<br />
* octycs<br />
* Mc<br />
* Tav<br />
<br />
[[Category:Hackfest]]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Recap&diff=113986Hackfest2019 Recap2019-03-07T20:08:38Z<p>BryceHarrington: /* Recap of Inkscape's Hackfest in Pasadena */</p>
<hr />
<div>== Recap of Inkscape's Hackfest in Pasadena ==<br />
<br />
Other pages: [[Hackfest2019 SCALE]], [[https://gitlab.com/inkscape/inbox/issues/188 Hackfest2019 Agenda]] [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE Attendees]].<br />
<br />
We've just completed another great hackfest here in rainy California, and wanted to share some accomplishments of the event.<br />
<br />
=== The 1.0 release plan was fleshed out ===<br />
<br />
* We will have a chill/frost/freeze sequence beginning March 15th, and will encourage a general focus on critical bugs. We will have a "Final Features" list of a narrow list of allowed features to land before the 1.0 release. A formalized definition of "blocker" bugs, vs "critical" bugs was agreed to, and will be made part of the release process.<br />
<br />
=== The Roadmap will be rejuvenated with a new monthly process ===<br />
<br />
* Going forward, a new team will be formed to meet monthly and review/approve/forecast feature development work. This meeting will look at both "Big Ideas" that need long range planning, and smaller UX changes that need more than one person to decide. It will also track status of what the extended developer community is up to, and thus help turn the Roadmap into more of a Forecast.<br />
<br />
=== A vision document on our UI strategy ===<br />
<br />
* We see a need for a collaboratively developed document that lays out our intended design strategy for the UI. We didn't get into details on how to make this happen, though.<br />
<br />
=== A "Big Ideas" tracker will be established in gitlab ===<br />
<br />
* (We need a better name for this.) These will hold "blueprint" scale feature requests, that will need planning, analysis, and scheduling via the roadmap. We will explore kanban-like approaches for managing this list in building the roadmap.<br />
<br />
=== For Mac OS/X, we want to make initial steps by 1.0 ===<br />
<br />
* Our first objective will be packaging a demo app. This could be a scripted build of gtk3-demo-application, for example; that way if there are problems, it will be more familiar to upstream. If this can be achieved by beta, we may be able to invest more to getting a package ready by 1.0.<br />
<br />
* A follow up would be to convert the raw build script into equivalent CMake commands. This should reveal lessons on how to do this for Inkscape.<br />
<br />
* Additional steps were scoped out, and will need further definition in gitlab. The master bug for this should probably move to the "Big Ideas" tracker at this point.<br />
<br />
=== For CMYK, Color Management, and PDF/Print, we have a detailed plan of development tasks needed. ===<br />
<br />
* This will be published in the "Big Ideas" gitlab tracker.<br />
<br />
=== We will establish Paypal buttons for dedicated funds to start collection of donations for several targeted efforts: ===<br />
<br />
A. Native Mac OS/X Packaging<br />
B. Color Management<br />
C. Internships promoting diversity (e.g. Outreachy)<br />
<br />
=== Budget planning work was begun ===<br />
<br />
* Areas of interest for funding include hackfests, increased conference attendance for speakers, increased Vectors team budget, and resources towards increased fundraising and sponsorship management. The board will continue work via email.<br />
<br />
=== A brand/trademark issue exists which needs visibility ===<br />
<br />
* We will be making this (and things people can do to help) public soon. Preparatory tasks were identified and split up between us.<br />
<br />
=== Video interviews of attendees were collected ===<br />
<br />
* These videos will provide material for Vectors team outreach and communications efforts in coming weeks and months.<br />
<br />
=== A greeter guideline was conceptualized ===<br />
<br />
* The initial interactions with a new contributor are critical for getting them happily engaged, and directed to where they want to work. A personal touch counts, so we want actual people doing greeting work. The greeter guideline will give easy reference info that can be given in chat, etc. for how to get involved in different areas.<br />
<br />
=== Teacher curriculum grant program ===<br />
<br />
* We discussed using grant programs to develop teaching materials for educators to bring Inkscape into the classroom. This felt out of scope for us right now, but we may revisit the idea some day in the future.<br />
<br />
=== Codebase subsystem contacts ===<br />
<br />
* It can be unclear who to contact for advice when working on certain areas of the code. We will try to identify in per-directory README's the individuals who have experience with that code and who are available to be contacted with questions.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Recap&diff=113981Hackfest2019 Recap2019-03-07T20:08:20Z<p>BryceHarrington: </p>
<hr />
<div>== Recap of Inkscape's Hackfest in Pasadena ==<br />
<br />
Other pages: [[Hackfest2019]], [[https://gitlab.com/inkscape/inbox/issues/188 Hackfest2019 Agenda]] [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE Attendees]].<br />
<br />
We've just completed another great hackfest here in rainy California, and wanted to share some accomplishments of the event.<br />
<br />
=== The 1.0 release plan was fleshed out ===<br />
<br />
* We will have a chill/frost/freeze sequence beginning March 15th, and will encourage a general focus on critical bugs. We will have a "Final Features" list of a narrow list of allowed features to land before the 1.0 release. A formalized definition of "blocker" bugs, vs "critical" bugs was agreed to, and will be made part of the release process.<br />
<br />
=== The Roadmap will be rejuvenated with a new monthly process ===<br />
<br />
* Going forward, a new team will be formed to meet monthly and review/approve/forecast feature development work. This meeting will look at both "Big Ideas" that need long range planning, and smaller UX changes that need more than one person to decide. It will also track status of what the extended developer community is up to, and thus help turn the Roadmap into more of a Forecast.<br />
<br />
=== A vision document on our UI strategy ===<br />
<br />
* We see a need for a collaboratively developed document that lays out our intended design strategy for the UI. We didn't get into details on how to make this happen, though.<br />
<br />
=== A "Big Ideas" tracker will be established in gitlab ===<br />
<br />
* (We need a better name for this.) These will hold "blueprint" scale feature requests, that will need planning, analysis, and scheduling via the roadmap. We will explore kanban-like approaches for managing this list in building the roadmap.<br />
<br />
=== For Mac OS/X, we want to make initial steps by 1.0 ===<br />
<br />
* Our first objective will be packaging a demo app. This could be a scripted build of gtk3-demo-application, for example; that way if there are problems, it will be more familiar to upstream. If this can be achieved by beta, we may be able to invest more to getting a package ready by 1.0.<br />
<br />
* A follow up would be to convert the raw build script into equivalent CMake commands. This should reveal lessons on how to do this for Inkscape.<br />
<br />
* Additional steps were scoped out, and will need further definition in gitlab. The master bug for this should probably move to the "Big Ideas" tracker at this point.<br />
<br />
=== For CMYK, Color Management, and PDF/Print, we have a detailed plan of development tasks needed. ===<br />
<br />
* This will be published in the "Big Ideas" gitlab tracker.<br />
<br />
=== We will establish Paypal buttons for dedicated funds to start collection of donations for several targeted efforts: ===<br />
<br />
A. Native Mac OS/X Packaging<br />
B. Color Management<br />
C. Internships promoting diversity (e.g. Outreachy)<br />
<br />
=== Budget planning work was begun ===<br />
<br />
* Areas of interest for funding include hackfests, increased conference attendance for speakers, increased Vectors team budget, and resources towards increased fundraising and sponsorship management. The board will continue work via email.<br />
<br />
=== A brand/trademark issue exists which needs visibility ===<br />
<br />
* We will be making this (and things people can do to help) public soon. Preparatory tasks were identified and split up between us.<br />
<br />
=== Video interviews of attendees were collected ===<br />
<br />
* These videos will provide material for Vectors team outreach and communications efforts in coming weeks and months.<br />
<br />
=== A greeter guideline was conceptualized ===<br />
<br />
* The initial interactions with a new contributor are critical for getting them happily engaged, and directed to where they want to work. A personal touch counts, so we want actual people doing greeting work. The greeter guideline will give easy reference info that can be given in chat, etc. for how to get involved in different areas.<br />
<br />
=== Teacher curriculum grant program ===<br />
<br />
* We discussed using grant programs to develop teaching materials for educators to bring Inkscape into the classroom. This felt out of scope for us right now, but we may revisit the idea some day in the future.<br />
<br />
=== Codebase subsystem contacts ===<br />
<br />
* It can be unclear who to contact for advice when working on certain areas of the code. We will try to identify in per-directory README's the individuals who have experience with that code and who are available to be contacted with questions.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Recap&diff=113976Hackfest2019 Recap2019-03-07T19:52:53Z<p>BryceHarrington: </p>
<hr />
<div>== Recap of Inkscape's Hackfest in Pasadena ==<br />
<br />
Other pages: [[https://gitlab.com/inkscape/inbox/issues/188 Hackfest2019 Agenda]] [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE Attendees]], [[Hackfest2019 Recap]].<br />
<br />
We've just completed another great hackfest here in rainy California, and wanted to share some accomplishments of the event.<br />
<br />
=== The 1.0 release plan was fleshed out ===<br />
<br />
* We will have a chill/frost/freeze sequence beginning March 15th, and will encourage a general focus on critical bugs. We will have a "Final Features" list of a narrow list of allowed features to land before the 1.0 release. A formalized definition of "blocker" bugs, vs "critical" bugs was agreed to, and will be made part of the release process.<br />
<br />
=== The Roadmap will be rejuvenated with a new monthly process ===<br />
<br />
* Going forward, a new team will be formed to meet monthly and review/approve/forecast feature development work. This meeting will look at both "Big Ideas" that need long range planning, and smaller UX changes that need more than one person to decide. It will also track status of what the extended developer community is up to, and thus help turn the Roadmap into more of a Forecast.<br />
<br />
=== A vision document on our UI strategy ===<br />
<br />
* We see a need for a collaboratively developed document that lays out our intended design strategy for the UI. We didn't get into details on how to make this happen, though.<br />
<br />
=== A "Big Ideas" tracker will be established in gitlab ===<br />
<br />
* (We need a better name for this.) These will hold "blueprint" scale feature requests, that will need planning, analysis, and scheduling via the roadmap. We will explore kanban-like approaches for managing this list in building the roadmap.<br />
<br />
=== For Mac OS/X, we want to make initial steps by 1.0 ===<br />
<br />
* Our first objective will be packaging a demo app. This could be a scripted build of gtk3-demo-application, for example; that way if there are problems, it will be more familiar to upstream. If this can be achieved by beta, we may be able to invest more to getting a package ready by 1.0.<br />
<br />
* A follow up would be to convert the raw build script into equivalent CMake commands. This should reveal lessons on how to do this for Inkscape.<br />
<br />
* Additional steps were scoped out, and will need further definition in gitlab. The master bug for this should probably move to the "Big Ideas" tracker at this point.<br />
<br />
=== For CMYK, Color Management, and PDF/Print, we have a detailed plan of development tasks needed. ===<br />
<br />
* This will be published in the "Big Ideas" gitlab tracker.<br />
<br />
=== We will establish Paypal buttons for dedicated funds to start collection of donations for several targeted efforts: ===<br />
<br />
A. Native Mac OS/X Packaging<br />
B. Color Management<br />
C. Internships promoting diversity (e.g. Outreachy)<br />
<br />
=== Budget planning work was begun ===<br />
<br />
* Areas of interest for funding include hackfests, increased conference attendance for speakers, increased Vectors team budget, and resources towards increased fundraising and sponsorship management. The board will continue work via email.<br />
<br />
=== A brand/trademark issue exists which needs visibility ===<br />
<br />
* We will be making this (and things people can do to help) public soon. Preparatory tasks were identified and split up between us.<br />
<br />
=== Video interviews of attendees were collected ===<br />
<br />
* These videos will provide material for Vectors team outreach and communications efforts in coming weeks and months.<br />
<br />
=== A greeter guideline was conceptualized ===<br />
<br />
* The initial interactions with a new contributor are critical for getting them happily engaged, and directed to where they want to work. A personal touch counts, so we want actual people doing greeting work. The greeter guideline will give easy reference info that can be given in chat, etc. for how to get involved in different areas.<br />
<br />
=== Teacher curriculum grant program ===<br />
<br />
* We discussed using grant programs to develop teaching materials for educators to bring Inkscape into the classroom. This felt out of scope for us right now, but we may revisit the idea some day in the future.<br />
<br />
=== Codebase subsystem contacts ===<br />
<br />
* It can be unclear who to contact for advice when working on certain areas of the code. We will try to identify in per-directory README's the individuals who have experience with that code and who are available to be contacted with questions.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Recap&diff=113971Hackfest2019 Recap2019-03-07T19:52:20Z<p>BryceHarrington: </p>
<hr />
<div>== Recap of Inkscape's Hackfest in Pasadena ==<br />
<br />
Other pages: [[https://gitlab.com/inkscape/inbox/issues/188 Hackfest2019 Agenda]] [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE Attendees]], [[Hackfest2019 Recap]].<br />
<br />
We've just completed another great hackfest here in rainy California, and wanted to share some accomplishments of the event.<br />
<br />
=== The 1.0 release plan was fleshed out ===<br />
<br />
* We will have a chill/frost/freeze sequence beginning March 15th, and will encourage a general focus on critical bugs. We will have a "Final Features" list of a narrow list of allowed features to land before the 1.0 release. A formalized definition of "blocker" bugs, vs "critical" bugs was agreed to, and will be made part of the release process.<br />
<br />
=== The Roadmap will be rejuvenated with a new monthly process ===<br />
<br />
* Going forward, a new team will be formed to meet monthly and review/approve/forecast feature development work. This meeting will look at both "Big Ideas" that need long range planning, and smaller UX changes that need more than one person to decide. It will also track status of what the extended developer community is up to, and thus help turn the Roadmap into more of a Forecast.<br />
<br />
=== A vision document on our UI strategy ===<br />
<br />
* We see a need for a collaboratively developed document that lays out our intended design strategy for the UI. We didn't get into details on how to make this happen, though.<br />
<br />
=== A "Big Ideas" tracker will be established in gitlab ===<br />
<br />
* (We need a better name for this.) These will hold "blueprint" scale feature requests, that will need planning, analysis, and scheduling via the roadmap. We will explore kanban-like approaches for managing this list in building the roadmap.<br />
<br />
=== For Mac OS/X, we want to make initial steps by 1.0 ===<br />
<br />
* Our first objective will be packaging a demo app. This could be a scripted build of gtk3-demo-application, for example; that way if there are problems, it will be more familiar to upstream. If this can be achieved by beta, we may be able to invest more to getting a package ready by 1.0.<br />
<br />
* A follow up would be to convert the raw build script into equivalent CMake commands. This should reveal lessons on how to do this for Inkscape.<br />
<br />
* Additional steps were scoped out, and will need further definition in gitlab. The master bug for this should probably move to the "Big Ideas" tracker at this point.<br />
<br />
=== For CMYK, Color Management, and PDF/Print, we have a detailed plan of development tasks needed. ===<br />
<br />
* This will be published in the "Big Ideas" gitlab tracker.<br />
<br />
=== We will establish Paypal buttons for dedicated funds to start collection of donations for several targeted efforts: ===<br />
<br />
A. Native Mac OS/X Packaging<br />
B. Color Management<br />
C. Internships promoting diversity (e.g. Outreachy)<br />
<br />
=== Budget planning work was begun ===<br />
<br />
* Areas of interest for funding include hackfests, increased conference attendance for speakers, increased Vectors team budget, and resources towards increased fundraising and sponsorship management. The board<br />
will continue work via email.<br />
<br />
=== A brand/trademark issue exists which needs visibility ===<br />
<br />
* We will be making this (and things people can do to help) public soon. Preparatory tasks were identified and split up between us.<br />
<br />
=== Video interviews of attendees were collected ===<br />
<br />
* These videos will provide material for Vectors team outreach and communications efforts in coming weeks and months.<br />
<br />
=== A greeter guideline was conceptualized ===<br />
<br />
* The initial interactions with a new contributor are critical for getting them happily engaged, and directed to where they want to work. A personal touch counts, so we want actual people doing greeting work. The greeter guideline will give easy reference info that can be given in chat, etc. for how to get involved in different areas.<br />
<br />
=== Teacher curriculum grant program ===<br />
<br />
* We discussed using grant programs to develop teaching materials for educators to bring Inkscape into the classroom. This felt out of scope for us right now, but we may revisit the idea some day in the future.<br />
<br />
=== Codebase subsystem contacts ===<br />
<br />
* It can be unclear who to contact for advice when working on certain areas of the code. We will try to identify in per-directory README's the individuals who have experience with that code and who are available to be contacted with questions.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Recap&diff=113966Hackfest2019 Recap2019-03-07T19:51:25Z<p>BryceHarrington: </p>
<hr />
<div>== Recap of Inkscape's Hackfest in Pasadena ==<br />
<br />
Other pages: [[https://gitlab.com/inkscape/inbox/issues/188 Hackfest2019 Agenda]] [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE Attendees]], [[Hackfest2019 Recap]].<br />
<br />
We've just completed another great hackfest here in rainy California, and wanted to share some accomplishments of the event.<br />
<br />
== The 1.0 release plan was fleshed out ==<br />
<br />
* We will have a chill/frost/freeze sequence beginning March 15th, and will encourage a general focus on critical bugs. We will have a "Final Features" list of a narrow list of allowed features to land before the 1.0 release. A formalized definition of "blocker" bugs, vs "critical" bugs was agreed to, and will be made part of the release process.<br />
<br />
== The Roadmap will be rejuvenated with a new monthly process ==<br />
<br />
* Going forward, a new team will be formed to meet monthly and review/approve/forecast feature development work. This meeting will look at both "Big Ideas" that need long range planning, and smaller UX changes that need more than one person to decide. It will also track status of what the extended developer community is up to, and thus help turn the Roadmap into more of a Forecast.<br />
<br />
== A vision document on our UI strategy ==<br />
<br />
* We see a need for a collaboratively developed document that lays out our intended design strategy for the UI. We didn't get into details on how to make this happen, though.<br />
<br />
== A "Big Ideas" tracker will be established in gitlab ==<br />
<br />
* (We need a better name for this.) These will hold "blueprint" scale feature requests, that will need planning, analysis, and scheduling via the roadmap. We will explore kanban-like approaches for managing this list in building the roadmap.<br />
<br />
== For Mac OS/X, we want to make initial steps by 1.0 ==<br />
<br />
* Our first objective will be packaging a demo app. This could be a scripted build of gtk3-demo-application, for example; that way if there are problems, it will be more familiar to upstream. If this can be achieved by beta, we may be able to invest more to getting a package ready by 1.0.<br />
<br />
* A follow up would be to convert the raw build script into equivalent CMake commands. This should reveal lessons on how to do this for Inkscape.<br />
<br />
* Additional steps were scoped out, and will need further definition in gitlab. The master bug for this should probably move to the "Big Ideas" tracker at this point.<br />
<br />
== For CMYK, Color Management, and PDF/Print, we have a detailed plan of development tasks needed. ==<br />
<br />
* This will be published in the "Big Ideas" gitlab tracker.<br />
<br />
== We will establish Paypal buttons for dedicated funds to start collection of donations for several targeted efforts: ==<br />
<br />
A. Native Mac OS/X Packaging<br />
B. Color Management<br />
C. Internships promoting diversity (e.g. Outreachy)<br />
<br />
== Budget planning work was begun ==<br />
<br />
* Areas of interest for funding include hackfests, increased conference attendance for speakers, increased Vectors team budget, and resources towards increased fundraising and sponsorship management. The board<br />
will continue work via email.<br />
<br />
== A brand/trademark issue exists which needs visibility ==<br />
<br />
* We will be making this (and things people can do to help) public soon. Preparatory tasks were identified and split up between us.<br />
<br />
== Video interviews of attendees were collected ==<br />
<br />
* These videos will provide material for Vectors team outreach and communications efforts in coming weeks and months.<br />
<br />
== A greeter guideline was conceptualized ==<br />
<br />
* The initial interactions with a new contributor are critical for getting them happily engaged, and directed to where they want to work. A personal touch counts, so we want actual people doing greeting work. The greeter guideline will give easy reference info that can be given in chat, etc. for how to get involved in different areas.<br />
<br />
== Teacher curriculum grant program ==<br />
<br />
* We discussed using grant programs to develop teaching materials for educators to bring Inkscape into the classroom. This felt out of scope for us right now, but we may revisit the idea some day in the future.<br />
<br />
== Codebase subsystem contacts ==<br />
<br />
* It can be unclear who to contact for advice when working on certain areas of the code. We will try to identify in per-directory README's the individuals who have experience with that code and who are available to be contacted with questions.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Recap&diff=113961Hackfest2019 Recap2019-03-07T19:45:38Z<p>BryceHarrington: </p>
<hr />
<div>== Recap of Inkscape's Hackfest in Pasadena ==<br />
<br />
Other pages: [[https://gitlab.com/inkscape/inbox/issues/188 Hackfest2019 Agenda]] [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE Attendees]], [[Hackfest2019 Recap]].<br />
<br />
<br />
<br />
We've just completed another great hackfest here in rainy California,<br />
and wanted to share some accomplishments of the event.<br />
<br />
''The 1.0 release plan was fleshed out''<br />
<br />
* We will have a chill/frost/freeze sequence beginning March 15th, and will encourage a general focus on critical bugs. We will have a "Final Features" list of a narrow list of allowed features to land before the 1.0 release. A formalized definition of "blocker" bugs, vs "critical" bugs was agreed to, and will be made part of the release process.<br />
<br />
''The Roadmap will be rejuvenated with a new monthly process''<br />
<br />
* Going forward, a new team will be formed to meet monthly and review/approve/forecast feature development work. This meeting will look at both "Big Ideas" that need long range planning, and smaller UX changes that need more than one person to decide. It will also track status of what the extended developer community is up to, and thus help turn the Roadmap into more of a Forecast.<br />
<br />
''A vision document on our UI strategy''<br />
<br />
* We see a need for a collaboratively developed document that lays out our intended design strategy for the UI. We didn't get into details on how to make this happen, though.<br />
<br />
''A "Big Ideas" tracker will be established in gitlab''<br />
<br />
* (We need a better name for this.) These will hold "blueprint" scale feature requests, that will need planning, analysis, and scheduling via the roadmap. We will explore kanban-like approaches for managing this list in building the roadmap.<br />
<br />
''For Mac OS/X, we want to make initial steps by 1.0''<br />
<br />
* Our first objective will be packaging a demo app. This could be a scripted build of gtk3-demo-application, for example; that way if there are problems, it will be more familiar to upstream. If this can be achieved by beta, we may be able to invest more to getting a package ready by 1.0.<br />
<br />
* A follow up would be to convert the raw build script into equivalent CMake commands. This should reveal lessons on how to do this for Inkscape.<br />
<br />
* Additional steps were scoped out, and will need further definition in gitlab. The master bug for this should probably move to the "Big Ideas" tracker at this point.<br />
<br />
''For CMYK, Color Management, and PDF/Print, we have a detailed plan of development tasks needed.''<br />
<br />
* This will be published in the "Big Ideas" gitlab tracker.<br />
<br />
''We will establish Paypal buttons for dedicated funds to start collection of donations for several targeted efforts:''<br />
<br />
A. Native Mac OS/X Packaging<br />
B. Color Management<br />
C. Internships promoting diversity (e.g. Outreachy)<br />
<br />
''Budget planning work was begun''<br />
<br />
* Areas of interest for funding include hackfests, increased conference attendance for speakers, increased Vectors team budget, and resources towards increased fundraising and sponsorship management. The board<br />
will continue work via email.<br />
<br />
''A brand/trademark issue exists which needs visibility''<br />
<br />
* We will be making this (and things people can do to help) public soon. Preparatory tasks were identified and split up between us.<br />
<br />
''Video interviews of attendees were collected''<br />
<br />
* These videos will provide material for Vectors team outreach and communications efforts in coming weeks and months.<br />
<br />
''A greeter guideline was conceptualized''<br />
<br />
* The initial interactions with a new contributor are critical for getting them happily engaged, and directed to where they want to work. A personal touch counts, so we want actual people doing greeting work. The greeter guideline will give easy reference info that can be given in chat, etc. for how to get involved in different areas.<br />
<br />
''Teacher curriculum grant program''<br />
<br />
* We discussed using grant programs to develop teaching materials for educators to bring Inkscape into the classroom. This felt out of scope for us right now, but we may revisit the idea some day in the future.<br />
<br />
''Codebase subsystem contacts''<br />
<br />
* It can be unclear who to contact for advice when working on certain areas of the code. We will try to identify in per-directory README's the individuals who have experience with that code and who are available to be contacted with questions.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_SCALE&diff=113956Hackfest2019 SCALE2019-03-07T19:44:39Z<p>BryceHarrington: </p>
<hr />
<div><br />
This page details the planning of Inkscape's 2019 hackfest in Pasadena, California.<br />
<br />
Other pages: [[https://gitlab.com/inkscape/inbox/issues/188 Hackfest2019 Agenda]] [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE Attendees]], [[Hackfest2019 Recap]].<br />
<br />
Future: [[Hackfest2019 Saarbrücken]]<br />
<br />
Old: [[Hackfest2018 Kiel]], [[Hackfest2018 LGM]], [[Hackfest2018]], [[Hackfest2017]], [[Hackfest2016]], [[Hackfest2015]].<br />
<br />
= Hackfest: Pasadena, California =<br />
<br />
==Description==<br />
<br />
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.<br />
The hackfest will take place March 4th through March 6th, which is before the [http://www.socallinuxexpo.org/scale/17x/ 2019 Southern California Linux Expo (SCALE)] which takes place from March 7th through 10th.<br />
<br />
==Pasadena==<br />
<br />
[https://en.wikipedia.org/wiki/Pasadena,_California Pasadena] is a city 16 km to the northeast of downtown Los Angeles. Pasadena can be reached from the Los Angeles International Airport (LAX) by bus/metro in about an hour.<br />
<br />
* An easy way to get there is take the FlyLAX bus to the downtown rail station and then take the Gold line to Pasadena<br />
* https://www.flylax.com/en/flyaway-bus<br />
* https://www.metro.net/riding/paid_parking/gold-line/<br />
<br />
==Venue==<br />
<br />
The hackfest will take place at [https://pasadena.edu/ Pasadena City College]. From the college:<br />
<br />
The Creveling Lounge has been reserved in the name of your organization for the three-day event, requested tables and chairs. The doors to The Creveling Lounge will be open thirty minutes prior to start-time for the event; and room will remain available to your group for thirty minutes after requested end-time. The thirty-minute time period prior to and after start/end times for the event allows you to set up the room as needed prior to actual time for event to start – with time at the end of each day to gather belongings and check to ensure all is in order prior to leaving the reserved room.<br />
<br />
Please see the attached “Screen Shot”: Creveling Lounge is close to the corner of Hill Street and Colorado Blvd. Parking lots are available to visitors with purchase of a Parking Permit with a daily cost of two dollars per day. The kiosks for purchasing Parking Permits accepts credit card payment as well as paper currency. Coins are not processed by the parking kiosks.<br />
<br />
* Creveling Lounge info: https://pasadena.edu/business-administrative-services/staging-services/venues/creveling.php<br />
* Campus Map: https://www.pasadena.edu/about/campus-maps.php<br />
<br />
===Catering===<br />
<br />
We've decided to not use the catering from the college, but will bring some snacks and enjoy nearby lunch places on Colorado.<br />
<br />
===Facilities===<br />
<br />
* Wireless networking<br />
* US type ...<br />
* Etc.<br />
<br />
===Nearby amenities===<br />
<br />
To do.<br />
<br />
==Hotels==<br />
<br />
* Howard Johnson is across from the college: https://www.wyndhamhotels.com/hojo/pasadena-california/howard-johnson-pasadena/<br />
<br />
==Schedule==<br />
<br />
To do.<br />
<br />
==Hackfest Dinner==<br />
<br />
An informal dinner will be held one night. We have a list of possible restaurants, we will decide on Monday as part of our initial planning.<br />
<br />
==Attendance==<br />
<br />
Anybody interested in Inkscape is welcome to attend. Funding support for travel expenses is based on past contributions to Inkscape. See the [[Hackfest2019 SCALE Attendees]] page for more details.<br />
<br />
==Schedule==<br />
<br />
A schedule will be developed based on input from attendees and the Inkscape community. See the [[Hackfest2019 SCALE Topics]] page for further details.<br />
<br />
[[Category:Hackfest]]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_Recap&diff=113951Hackfest2019 Recap2019-03-07T19:42:09Z<p>BryceHarrington: Created page with "Recap of Inkscape's Hackfest in Pasadena We've just completed another great hackfest here in rainy California, and wanted to share some accomplishments of the event. ''The 1..."</p>
<hr />
<div>Recap of Inkscape's Hackfest in Pasadena<br />
<br />
We've just completed another great hackfest here in rainy California,<br />
and wanted to share some accomplishments of the event.<br />
<br />
''The 1.0 release plan was fleshed out''<br />
<br />
* We will have a chill/frost/freeze sequence beginning March 15th, and will encourage a general focus on critical bugs. We will have a "Final Features" list of a narrow list of allowed features to land before the 1.0 release. A formalized definition of "blocker" bugs, vs "critical" bugs was agreed to, and will be made part of the release process.<br />
<br />
''The Roadmap will be rejuvenated with a new monthly process''<br />
<br />
* Going forward, a new team will be formed to meet monthly and review/approve/forecast feature development work. This meeting will look at both "Big Ideas" that need long range planning, and smaller UX changes that need more than one person to decide. It will also track status of what the extended developer community is up to, and thus help turn the Roadmap into more of a Forecast.<br />
<br />
''A vision document on our UI strategy''<br />
<br />
* We see a need for a collaboratively developed document that lays out our intended design strategy for the UI. We didn't get into details on how to make this happen, though.<br />
<br />
''A "Big Ideas" tracker will be established in gitlab''<br />
<br />
* (We need a better name for this.) These will hold "blueprint" scale feature requests, that will need planning, analysis, and scheduling via the roadmap. We will explore kanban-like approaches for managing this list in building the roadmap.<br />
<br />
''For Mac OS/X, we want to make initial steps by 1.0''<br />
<br />
* Our first objective will be packaging a demo app. This could be a scripted build of gtk3-demo-application, for example; that way if there are problems, it will be more familiar to upstream. If this can be achieved by beta, we may be able to invest more to getting a package ready by 1.0.<br />
<br />
* A follow up would be to convert the raw build script into equivalent CMake commands. This should reveal lessons on how to do this for Inkscape.<br />
<br />
* Additional steps were scoped out, and will need further definition in gitlab. The master bug for this should probably move to the "Big Ideas" tracker at this point.<br />
<br />
''For CMYK, Color Management, and PDF/Print, we have a detailed plan of development tasks needed.''<br />
<br />
* This will be published in the "Big Ideas" gitlab tracker.<br />
<br />
''We will establish Paypal buttons for dedicated funds to start collection of donations for several targeted efforts:''<br />
<br />
A. Native Mac OS/X Packaging<br />
B. Color Management<br />
C. Internships promoting diversity (e.g. Outreachy)<br />
<br />
''Budget planning work was begun''<br />
<br />
* Areas of interest for funding include hackfests, increased conference attendance for speakers, increased Vectors team budget, and resources towards increased fundraising and sponsorship management. The board<br />
will continue work via email.<br />
<br />
''A brand/trademark issue exists which needs visibility''<br />
<br />
* We will be making this (and things people can do to help) public soon. Preparatory tasks were identified and split up between us.<br />
<br />
''Video interviews of attendees were collected''<br />
<br />
* These videos will provide material for Vectors team outreach and communications efforts in coming weeks and months.<br />
<br />
''A greeter guideline was conceptualized''<br />
<br />
* The initial interactions with a new contributor are critical for getting them happily engaged, and directed to where they want to work. A personal touch counts, so we want actual people doing greeting work. The greeter guideline will give easy reference info that can be given in chat, etc. for how to get involved in different areas.<br />
<br />
''Teacher curriculum grant program''<br />
<br />
* We discussed using grant programs to develop teaching materials for educators to bring Inkscape into the classroom. This felt out of scope for us right now, but we may revisit the idea some day in the future.<br />
<br />
''Codebase subsystem contacts''<br />
<br />
* It can be unclear who to contact for advice when working on certain areas of the code. We will try to identify in per-directory README's the individuals who have experience with that code and who are available to be contacted with questions.</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Hackfest2019_SCALE&diff=113946Hackfest2019 SCALE2019-03-07T19:16:31Z<p>BryceHarrington: </p>
<hr />
<div><br />
This page details the planning of Inkscape's 2019 hackfest in Pasadena, California.<br />
<br />
Other pages: [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE Attendees]], [[Hackfest2019 Recap]].<br />
<br />
Future: [[Hackfest2019 Saarbrücken]]<br />
<br />
Old: [[Hackfest2018 Kiel]], [[Hackfest2018 LGM]], [[Hackfest2018]], [[Hackfest2017]], [[Hackfest2016]], [[Hackfest2015]].<br />
<br />
= Hackfest: Pasadena, California =<br />
<br />
==Description==<br />
<br />
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.<br />
The hackfest will take place March 4th through March 6th, which is before the [http://www.socallinuxexpo.org/scale/17x/ 2019 Southern California Linux Expo (SCALE)] which takes place from March 7th through 10th.<br />
<br />
==Pasadena==<br />
<br />
[https://en.wikipedia.org/wiki/Pasadena,_California Pasadena] is a city 16 km to the northeast of downtown Los Angeles. Pasadena can be reached from the Los Angeles International Airport (LAX) by bus/metro in about an hour.<br />
<br />
* An easy way to get there is take the FlyLAX bus to the downtown rail station and then take the Gold line to Pasadena<br />
* https://www.flylax.com/en/flyaway-bus<br />
* https://www.metro.net/riding/paid_parking/gold-line/<br />
<br />
==Venue==<br />
<br />
The hackfest will take place at [https://pasadena.edu/ Pasadena City College]. From the college:<br />
<br />
The Creveling Lounge has been reserved in the name of your organization for the three-day event, requested tables and chairs. The doors to The Creveling Lounge will be open thirty minutes prior to start-time for the event; and room will remain available to your group for thirty minutes after requested end-time. The thirty-minute time period prior to and after start/end times for the event allows you to set up the room as needed prior to actual time for event to start – with time at the end of each day to gather belongings and check to ensure all is in order prior to leaving the reserved room.<br />
<br />
Please see the attached “Screen Shot”: Creveling Lounge is close to the corner of Hill Street and Colorado Blvd. Parking lots are available to visitors with purchase of a Parking Permit with a daily cost of two dollars per day. The kiosks for purchasing Parking Permits accepts credit card payment as well as paper currency. Coins are not processed by the parking kiosks.<br />
<br />
* Creveling Lounge info: https://pasadena.edu/business-administrative-services/staging-services/venues/creveling.php<br />
* Campus Map: https://www.pasadena.edu/about/campus-maps.php<br />
<br />
===Catering===<br />
<br />
We've decided to not use the catering from the college, but will bring some snacks and enjoy nearby lunch places on Colorado.<br />
<br />
===Facilities===<br />
<br />
* Wireless networking<br />
* US type ...<br />
* Etc.<br />
<br />
===Nearby amenities===<br />
<br />
To do.<br />
<br />
==Hotels==<br />
<br />
* Howard Johnson is across from the college: https://www.wyndhamhotels.com/hojo/pasadena-california/howard-johnson-pasadena/<br />
<br />
==Schedule==<br />
<br />
To do.<br />
<br />
==Hackfest Dinner==<br />
<br />
An informal dinner will be held one night. We have a list of possible restaurants, we will decide on Monday as part of our initial planning.<br />
<br />
==Attendance==<br />
<br />
Anybody interested in Inkscape is welcome to attend. Funding support for travel expenses is based on past contributions to Inkscape. See the [[Hackfest2019 SCALE Attendees]] page for more details.<br />
<br />
==Schedule==<br />
<br />
A schedule will be developed based on input from attendees and the Inkscape community. See the [[Hackfest2019 SCALE Topics]] page for further details.<br />
<br />
[[Category:Hackfest]]</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113836Inkscape Classes2019-03-03T02:30:05Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 16 !! Sat, Mar 23 !! Sat, Mar 30 !! Sat, Apr 6 !! Sat, Apr 13<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| '''Fundraising for FOSS Projects''' <br> '''(1½ hr)''' ''[[https://chat.inkscape.org/channel/collaboration_space Watch Party]]'' || || || || <br />
|-<br />
! 20:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat in channel #collaboration_space at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
== '''Fundraising for open source projects:''' ==<br />
''Hosts:'' Michele, Bryce<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
<br />
<br />
== Other Topics Ideas ==<br />
<br />
* Bradley Kohn presentations (from SCALE, if available)<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113831Inkscape Classes2019-03-03T02:29:01Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 16 !! Sat, Mar 23 !! Sat, Mar 30 !! Sat, Apr 6 !! Sat, Apr 13<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| '''Fundraising for FOSS Projects (1½ hr)''' <br> ''[[https://chat.inkscape.org/channel/collaboration_space Watch Party]]'' || || || || <br />
|-<br />
! 20:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat in channel #collaboration_space at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
== '''Fundraising for open source projects:''' ==<br />
''Hosts:'' Michele, Bryce<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
<br />
<br />
== Other Topics Ideas ==<br />
<br />
<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113826Inkscape Classes2019-03-03T02:28:21Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 16 !! Sat, Mar 23 !! Sat, Mar 30 !! Sat, Apr 6 !! Sat, Apr 13<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| '''Fundraising for FOSS Projects''' <br> ''[[https://chat.inkscape.org/channel/collaboration_space Watch Party]]'' || || || || <br />
|-<br />
! 20:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat in channel #collaboration_space at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
== '''Fundraising for open source projects:''' ==<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
<br />
<br />
== Other Topics Ideas ==<br />
<br />
<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113821Inkscape Classes2019-03-03T02:27:47Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 16 !! Sat, Mar 23 !! Sat, Mar 30 !! Sat, Apr 6 !! Sat, Apr 13<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| '''Fundraising for FOSS Projects''' <br> ''<a href="https://chat.inkscape.org/channel/collaboration_space">Watch Party</a>'' || || || || <br />
|-<br />
! 20:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat in channel #collaboration_space at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
== '''Fundraising for open source projects:''' ==<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
<br />
<br />
== Other Topics Ideas ==<br />
<br />
<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113816Inkscape Classes2019-03-03T02:26:23Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 16 !! Sat, Mar 23 !! Sat, Mar 30 !! Sat, Apr 6 !! Sat, Apr 13<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| '''Fundraising for FOSS Projects''' <br> ''Michele'' || || || || <br />
|-<br />
! 20:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat in channel #collaboration_space at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
== '''Fundraising for open source projects:''' ==<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
<br />
<br />
== Other Topics Ideas ==<br />
<br />
<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113811Inkscape Classes2019-03-03T02:25:25Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 16 !! Sat, Mar 23 !! Sat, Mar 30 !! Sat, Apr 6 !! Sat, Apr 13<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| || || '''Fundraising for FOSS Projects''' <br> ''Michele'' || ||<br />
|-<br />
! 20:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat in channel #collaboration_space at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
== '''Fundraising for open source projects:''' ==<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
<br />
<br />
== Other Topics Ideas ==<br />
<br />
<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113806Inkscape Classes2019-03-03T02:24:44Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 16 !! Sat, Mar 23 !! Sat, Mar 30 !! Sat, Apr 6 !! Sat, Apr 13<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| || || '''Fundraising for FOSS Projects''' <br> ''Michele'' || ||<br />
|-<br />
! 20:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
== '''Fundraising for open source projects:''' ==<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
<br />
<br />
== Other Topics Ideas ==<br />
<br />
<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113801Inkscape Classes2019-03-03T02:05:35Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 29 !! Sun, Mar 30 !! Mon, Mar 31 !! Tues, Apr 1 !! Wed, Apr 2<br />
|-<br />
! 20:00 UTC<br />
| || || '''[[Class:Creating Icons using Inkscape|Creating Icons using Inkscape]]''' <br> ''Example 0'' || || '''[[Class:Using Clones|Using Clones]]''' <br> ''Example 1''<br />
|-<br />
! 21:00 UTC<br />
| || || '''[[Class:Inkscape Roadmap|Inkscape Roadmap]]''' <br> ''Example 2'' || ||<br />
|-<br />
! 23:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
<br />
== Topics/Videos To Schedule ==<br />
<br />
''Fundraising for open source projects:''<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
== Other Topics Ideas ==<br />
<br />
<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port<br />
* Intro to Django Development<br />
* Creating Web REST APIs using Django<br />
* C++-11 Best Practices<br />
* Introduction to the SVG File Format<br />
* Using Git<br />
* Using Gitlab<br />
* Introduction to Development with Gtk+<br />
* What's New in Gtk+ 3<br />
* What's Coming in Gtk+ 4<br />
* Writing Grant and/or Fellowship Applications</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113796Inkscape Classes2019-03-03T01:55:26Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 29 !! Sun, Mar 30 !! Mon, Mar 31 !! Tues, Apr 1 !! Wed, Apr 2<br />
|-<br />
! 20:00 UTC<br />
| || || '''[[Class:Creating Icons using Inkscape|Creating Icons using Inkscape]]''' <br> ''Example 0'' || || '''[[Class:Using Clones|Using Clones]]''' <br> ''Example 1''<br />
|-<br />
! 21:00 UTC<br />
| || || '''[[Class:Inkscape Roadmap|Inkscape Roadmap]]''' <br> ''Example 2'' || ||<br />
|-<br />
! 23:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
<br />
== Topics/Videos To Schedule ==<br />
<br />
''Fundraising for open source projects:''<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Anatomy of Successful Open Source Communities and Projects (10 min)<br />
* https://www.youtube.com/watch?v=MigSMCc8bmM - How to raise money for open source projects (25 min)<br />
* https://www.youtube.com/watch?v=TYFdjY63XTQ - Fundraising for Projects (61 min)<br />
<br />
== Other Topics Ideas ==<br />
<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape_Classes&diff=113791Inkscape Classes2019-03-03T01:51:55Z<p>BryceHarrington: </p>
<hr />
<div>{{Other languages|en=Inkscape Classes}}<br />
__NOTOC__<br />
<br />
Welcome to the Inkscape Watch Party! These are videos on topics to help invest key knowledge into the Inkscape development community.<br />
<br />
== Inkscape Watch Schedule ==<br />
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"<br />
! !! Sat, Mar 29 !! Sun, Mar 30 !! Mon, Mar 31 !! Tues, Apr 1 !! Wed, Apr 2<br />
|-<br />
! 18:00 UTC<br />
| || || || ||<br />
|-<br />
! 19:00 UTC<br />
| || || || ||<br />
|-<br />
! 20:00 UTC<br />
| || || '''[[Class:Creating Icons using Inkscape|Creating Icons using Inkscape]]''' <br> ''Bernard Gray'' || || '''[[Class:Using Clones|Using Clones]]''' <br> ''Bernard Gray''<br />
|-<br />
! 21:00 UTC<br />
| || || '''[[Class:Inkscape Roadmap|Inkscape Roadmap]]''' <br> ''Bryce Harrington'' || ||<br />
|-<br />
! 22:00 UTC<br />
| || || || '''[[Class:Creating Scientific Posters|Creating Scientific Posters]]''' <br> ''Albert Cardona'' ||<br />
|-<br />
! 23:00 UTC<br />
| || || || ||<br />
|-<br />
|}<br />
<br />
We will arrange to get together on Rocket.Chat at the given time, to watch the given video together.<br />
This way we can share ideas and insights, and do some peer to peer Q&A.<br />
You can of course watch the videos whenever you want.<br />
<br />
<br />
== Topics/Videos To Schedule ==<br />
<br />
<br />
<br />
== Other Topics Ideas ==<br />
<br />
* The Open Clip Art Library<br />
* Google SoC<br />
* Translation 101<br />
* Refactoring 101<br />
* Scripting Effects 101<br />
* Bug Triage<br />
* Debugging Inkscape<br />
* Maintaining the Inkscape Windows Port</div>BryceHarringtonhttps://wiki.inkscape.org/wiki/index.php?title=Leadership_Committee_Status_Updates&diff=113756Leadership Committee Status Updates2019-03-01T18:02:44Z<p>BryceHarrington: /* Agenda */</p>
<hr />
<div>== Place and Time ==<br />
<br />
We meet in #inkscape-devel on [https://freenode.net/ freenode].<br />
<br />
Board meetings are typically the first Friday of each month.<br />
<br />
<em>Everybody in the Inkscape community is invited to participate.</em><br />
<br />
Next meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?month=3&day=1&year=2019&hour=18&min=00&sec=0&p1=0 10:00 PDT/18:00 UTC/19:00 CET, (click for world clock)], Fri, 1st March, 2019. (Time is fixed to 10 AM Pacific Time.)<br />
<br />
Meetings should be announced in advance on [https://lists.sourceforge.net/lists/listinfo/inkscape-devel inkscape-devel] and [https://lists.sourceforge.net/lists/listinfo/inkscape-board inkscape-board] mailing lists.<br />
<br />
== Agenda ==<br />
* Infrastructure<br />
** Instagram: https://www.instagram.com/inkscapeofficial/<br />
** mailman3 status<br />
** Wiki migration<br />
** Weblate service deployment<br />
<br />
* Sponsorship<br />
** Using gitlab issues for tracking<br />
** Renewal of old sponsors<br />
** 2 new bronze, 1 gold, 1 tbd<br />
** SFC bookkeeping is still slow<br />
** Sponsor acceptance policy<br />
** Sponsor soliciting / outreach<br />
<br />
* Should we set up some new teams under delegation from the board?<br />
** Funding - Fundraisers, merchandising, sponsorship management, etc.<br />
** Accounting - Travel & other reimbursements<br />
** Legal - Trademarks, etc.<br />
<br />
* Hackfest [http://www.socallinuxexpo.org/scale/17x/ SCALE]<br />
** Review agenda<br />
*** Ideas to present to Bradley?<br />
** Calls for donations<br />
<br />
* Hackfest [http://libregraphicsmeeting.org/2019/ LGM 2019]<br />
** May 30th-June 3rd (Saarbrucken, Germany)<br />
** Next steps for organizing it<br />
<br />
* GSoC<br />
** Mentors needed<br />
** Guiding prospective students<br />
** Project ideas list<br />
** Development starter docs<br />
<br />
* Other Business<br />
<br />
== Other Agenda Items ==<br />
* Sponsor acceptance policy<br />
* Funded development [bryce]<br />
** Identify Manager/Reviewer/Second for each of the jobs<br />
** How should we advertise the jobs?<br />
* Outreachy: Next round starts in August [https://www.outreachy.org/mentor/]<br />
<br />
=== Action Items ===<br />
* Future hackfests<br />
** Hackfest organizational tips (Need to document this someplace)<br />
*** Process: Have folks propose options, and then trade off cost projections and benefits<br />
*** Try to organize group lodging (same hotel, rented/air-bnb house, http://www.linuxhotel.de/community.en.html, etc.)<br />
*** Send a scout ahead of time to help avoid slummy accommodations<br />
*** Catered lunches help keep everyone focused (we're already reimbursing on lunches, so cost differential isn't huge, and it saves hassle all around)<br />
*** Boots on the ground at a location can be a huge help if plans go awry<br />
*** Prefer locations with local inkscape community on the ground<br />
<br />
* [https://inkscape.org/en/support-us/funded-development/ Funded development] [bryce]<br />
* Add a C++-11 conversion project with tasks detailed to the Roadmap for 0.93 or later. [valavanisalex]<br />
* Regularly check [[Sponsors_list|sponsor status]]<br />
<br />
== Blocked Action Items ==<br />
<br />
* Privacy Policy [drmo] ~ Blocked waiting on time availability by SFC<br />
* Amend CoC reporting section ~ Waiting until we have a dedicated email, e.g. abuse@inkscape.org<br />
<br />
<br />
== Board Meeting Transcripts == <br />
<br />
=== 2019 ===<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2019-02-01.log.html 2019-02-01]<br />
<br />
=== 2018 ===<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2019-01-04.log.html 2019-01-04]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-12-07.log.html 2018-12-07]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-11-02.log.html 2018-11-02]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-10-05.log.html 2018-10-05]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-09-07.log.html 2018-09-07]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-08-03.log.html 2018-08-03]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-07-06.log.html 2018-07-06]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-06-01.log.html 2018-06-01]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-05-04.log.html 2018-05-04]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/2018-04-06.log.html 2018-04-06]<br />
* [http://alpha.inkscape.org/board/meetings/transcripts/board_meeting_2018-03-02.html 2018-03-02]<br />
* [https://inkscape.org/gallery/item/12009/ 2018-02-02]<br />
* [https://inkscape.org/gallery/item/11875/ 2018-01-05]<br />
<br />
=== 2017 ===<br />
* [https://inkscape.org/paste/11743/ 2017-12-01]<br />
* [https://inkscape.org/paste/11651/ 2017-11-03]<br />
* [https://inkscape.org/gallery/item/11517/ 2017-10-06]<br />
* [https://inkscape.org/gallery/item/11377/ 2017-09-01]<br />
* [https://inkscape.org/gallery/item/11250/ 2017-08-04]<br />
* [https://inkscape.org/gallery/item/11176/ 2017-07-07]<br />
* [https://inkscape.org/gallery/item/11064/ 2017-06-02]<br />
* [https://inkscape.org/gallery/item/10844/ 2017-04-07]<br />
* [https://inkscape.org/gallery/item/10740/ 2017-03-03]<br />
* [https://inkscape.org/gallery/item/10651/ 2017-02-03]<br />
* [https://inkscape.org/gallery/item/10582/ 2017-01-06]<br />
<br />
=== 2016 ===<br />
<br />
* [https://inkscape.org/gallery/item/10484/ 2016-12-02]<br />
* [https://inkscape.org/gallery/item/10241/ 2016-11-04]<br />
* [https://inkscape.org/gallery/item/9971/ 2016-09-02]<br />
* [https://inkscape.org/gallery/item/9864/ 2016-08-05]<br />
* [https://inkscape.org/gallery/item/9766/ 2016-07-08]<br />
* [https://inkscape.org/gallery/item/9667/ 2016-06-03]<br />
* [https://inkscape.org/gallery/item/9563/ 2016-05-06]<br />
* [https://inkscape.org/gallery/item/9565/ 2016-04-01]<br />
<br />
* [https://inkscape.org/gallery/item/7276/ 2016-01-08]<br />
<br />
=== 2015 ===<br />
<br />
* [https://inkscape.org/gallery/item/7056/ 2015-12-04]<br />
* [https://inkscape.org/gallery/item/6886/ 2015-11-06]<br />
* [https://inkscape.org/gallery/item/6701/ 2015-10-02]<br />
<br />
=== 2014 ===<br />
<br />
* [https://inkscape.org/gallery/item/2498/ 2014-11-26]<br />
* [https://inkscape.org/gallery/item/2216/ 2014-11-19]<br />
* [https://inkscape.org/gallery/item/2210/ 2014-11-12]<br />
* [https://inkscape.org/gallery/item/2204/ 2014-11-05]<br />
* [https://inkscape.org/gallery/item/1436/ 2014-10-15]<br />
* [https://inkscape.org/gallery/item/950/ 2014-10-08]<br />
* [https://inkscape.org/gallery/item/854/ 2014-09-29]<br />
* [https://inkscape.org/gallery/item/392/ 2014-09-15]<br />
<br />
'''[https://inkscape.org/en/gallery/=pastebin/?q=meeting&order=-edited Website search for all transcripts]'''</div>BryceHarrington