- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] [Inkscape-user] the Scale setting and Display units
by brynn 14 Sep '17

14 Sep '17

Thanks, Maren. I will try to find some time to read those. But I was really hoping for a shorter answer. It's not that I mind learning new things. But if it takes that much reading to understand a program's feature, then I think the feature needs to be redesigned, so that users are eased into it. (Original message posted to User list, but now copying to the devel list) If this would help for developers or advanced users know how to answer, here is the basic question. How to change the display units, so that the file is using those units, and so that the drawing is as close to the real life units as the user's screen resolution permits (like for printing or cutting). Also, an issue was raised in a forum, that symbols and some extensions don't work properly if the scale is not set a certain way. ("don't work properly" means that the resulting sizes aren't correct.) In this case, I mean for a new drawing in the current version of Inkscape (not opening a file which was started in an earlier version). Thanks again, brynn -----Original Message----- From: Maren Hachmann Sent: Thursday, September 14, 2017 3:49 PM To: inkscape-user(a)lists.sourceforge.net Subject: Re: [Inkscape-user] the Scale setting and Display units Suggested reading: https://www.patreon.com/posts/units-part-i-13563546 https://www.patreon.com/posts/units-part-ii-13566508 https://www.patreon.com/posts/units-part-iii-13741251 https://www.patreon.com/posts/units-part-iv-13993147 (Articles written by Marc Jeanmougin, for his patrons on Patreon and for the whole Inkscape community) Maren Am 14.09.2017 um 23:11 schrieb brynn: > Hi Friends, > Sending up a signal flare from the not-so-technially-inclined > user community. Please either explain the Scale setting and how users > can easily change the Display units; or fix the UX so we can use it. > > Thank you so very much, > brynn > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-user mailing list > Inkscape-user(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-user > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-user mailing list Inkscape-user(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user

1 0

Re: [Inkscape-devel] [Inkscape-user] the Scale setting and Display units
by brynn 14 Sep '17

14 Sep '17

Developers often seem to answer, so I thought I was getting both here. But now copied to the devel list. Thanks, brynn -----Original Message----- From: Martin Owens Sent: Thursday, September 14, 2017 3:40 PM To: Inkscape User Community Subject: Re: [Inkscape-user] the Scale setting and Display units You should make sure this flare goes to the devel mailing list too. On Thu, 2017-09-14 at 15:11 -0600, brynn wrote: > Hi Friends, > Sending up a signal flare from the not-so-technially-inclined > user > community. Please either explain the Scale setting and how users can > easily > change the Display units; or fix the UX so we can use it. > > Thank you so very much, > brynn > > > > ------------------------------------------------------------------- > ----------- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-user mailing list > Inkscape-user(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-user ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-user mailing list Inkscape-user(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user

1 0

Election Inkscape Vectors Team: Results
by unknown＠example.com 14 Sep '17

14 Sep '17

Dear Inkscape Developer, The election for Inkscape Vectors Team is now concluded. -- RESULTS -- * Martin Owens (Elected) * Tavmjong Bah ---- Full Results: http://www.inkscape.org/en/*inkscape-vectors/elections/test-election-2017/

4 3

Blur branch
by Jabier Arraiza 13 Sep '17

13 Sep '17

Hi all. I want to know the status of the blur branch, I think it introduce a great improvement but need to be tested well so the faster is landed in trunk the better. I don`t undertand his changes, also dont remember the branch location, recently cleanup my mailbox..., I remember Tav made some comments to it to be done. Cheers, Jabier.

1 0

[brett@...3057...: Upcoming changes to the travel policy]
by Bryce Harrington 13 Sep '17

13 Sep '17

FYI #2, this one does affect us but is good news: 1. More flexibility in selecting flights for time vs. lowest cost 2. Slightly higher limits for international flights 3. Bit more flexibility in approvals and reimbursement ----- Forwarded message from Brett Smith <brett@...3057...> ----- Date: Tue, 12 Sep 2017 10:38:27 -0400 From: Brett Smith <brett@...3057...> To: project-reps@...3057... Subject: Upcoming changes to the travel policy Reply-To: policies-discuss@...3057... Hi again everyone, Now for the good news. At their most recent meeting, Conservancy’s board approved the proposed changes to the travel policy that were recently submitted to policies-discuss. Let me give a quick recap of those changes so I can discuss next steps for PLCs. First, the new policy provides additional budget to book flights that save substantial time over the cheapest available fare. This was the most common request we heard, and definitely we recognize the value of saving people’s time. In order to keep the rules simple, the budget increases at specific time savings marks. You can see the new rules here <https://k.sfconservancy.org/policies/files/783dcdd92fc61f3f150e1c65782c0fe5…>. Second, the policy increases the cost of international flights that require preapproval, from $1,500 to $1,650. This change is just to keep pace with fares we’re seeing; the $1,500 limit has been in place since at least 2012, and of course fares have risen since then. This should reduce the number of flights that require preapproval. There are also a couple of changes that just provide additional flexibility in handling reimbursement requests. The new rules clarify that our 90-day limit on reimbursement requests starts from the last day of travel, not the day the expense was incurred. (This is how we’ve treated it since the 90-day rule was introduced, but now it’s official.) Expenses that require preapproval can be approved by any officer of Conservancy, not just the executive director. This should help us be more responsive to your requests. There are also non-rules changes, like updates to the currency rates we use (forced on us because the Bank of Canada stopped providing them) and Markdown formatting. For more background, see the messages to policies-discuss <https://lists.sfconservancy.org/pipermail/policies-discuss/2017-August/thre…> and the Git history <https://k.sfconservancy.org/policies/changelog?branch=2017-08-proposed-upda…>. Next steps: We would like to make these changes effective in a week, on 20 September. The reason for the gap is we want to give you time to discuss them internally. Because these changes potentially mean increased project expenses, we understand you might not be prepared to take those on. If you would like to follow the old policies, or other rules that are stricter than ours, you can always do that. Just let us know through your project alias, and we’ll handle your reimbursement requests accordingly. If we don’t hear from you, we’ll follow the new rules for any reimbursed expenses incurred on or after 20 September. I really hope you all like these changes; our goal in pushing them forward was really to try to address head-on a lot of the feedback I’ve heard about flight reimbursements and preapprovals while I’ve been helping with our bookkeeping, and I’m optimistic we’ve made good progress there. If you have any questions about the changes, feel free to ask us through your project alias, or on policies-discuss if it’s appropriate for public discussion. Best regards, -- Brett Smith ----- End forwarded message -----

1 0

[brett@...3057...: Rackspace OSS discount ends at the end of the year]
by Bryce Harrington 13 Sep '17

13 Sep '17

FYI. Although, this doesn't affect us. ----- Forwarded message from Brett Smith <brett@...3057...> ----- Date: Tue, 12 Sep 2017 09:46:41 -0400 From: Brett Smith <brett@...3057...> To: project-reps@...3057... Subject: Rackspace OSS discount ends at the end of the year Reply-To: Brett Smith <brett@...3057...> Hi everyone, I have good news and bad news for you today, so I’ll start with the bad news. Many of you are relying on Rackspace’s OSS discount to host servers for your project. Unfortunately, Rackspace just informed us yesterday that they’ll be ending the program at the end of the year. The entire business is shifting focus away from running their own cloud infrastructure, to providing support in the Big Three clouds, so as part of that they’re ending incentive programs structured around their cloud. Conservancy hosts our own servers through this program, and so we’re already reaching out to other cloud providers to see if they might be willing to offer something similar. We realize it would be ideal if we could find a similar replacement program that covers each of you separately, and we’ll be trying to do that first. If you have contacts at hosting providers that we should be talking to about providing such a service, please let us know; this is a big enough deal that we’re eager to talk to anybody who might help. If they’re sufficiently generous, we may consider recognizing them as an in-kind sponsor on our web site. If you’re affected by this, it would probably be prudent to start planning how you’ll migrate your servers off Rackspace to another provider. I realize that’s difficult to fully plan without knowing where you’re going, but at least it would be helpful to review your system configurations and make sure you understand what you need to migrate. You might also consider if there are ways you could consolidate or streamline your servers. Rackspace’s OSS discount program is /extremely/ generous; we might find a similar program that is merely /very/ generous. Alternatively, if you’re willing to pay Rackspace for hosting, you can do that too if you have the funds. Your Rackspace bills (which are usually zeroed about by the discount) are in our Subversion server along with the rest of your financial records, usually under |Expenses/Rackspace/|. If you need help with accessing that, just let me know. If you don’t currently have an OSS discount account with Rackspace, but you were thinking about getting one, I’m afraid that’s no longer available. If you want to talk with us about this change for any reason, it’s probably best to do so through your specific project alias. I’m following all those conversations and can follow up there. I’ll keep you updated about our progress in finding a replacement program. Best regards, -- Brett Smith ----- End forwarded message -----

1 0

Election Inkscape Vectors Team: Voting Open
by unknown＠example.com 11 Sep '17

11 Sep '17

Dear Inkscape Developer, The election for the Inkscape Vectors Team team is now open for voting. Please go to the link below to fill in your ballot. You have 3 days (Sept. 14, 2017) to complete your ballot. Only members of the Inkscape Developer team have ballots and members who join after this point will not be added to the election. ---- Vote: http://www.inkscape.org/en/*inkscape-vectors/elections/test-election-2017/

1 0

Updating the FAQ with pictures and diagrams
by C R 10 Sep '17

10 Sep '17

Brynn brought it to attention that the FAQ could use some updating to include pictures and diagrams to help explain. I'm already looking at the Raster vs. Vector sections, but would like to know other hot-button questions (questions which we get a lot) that the FAQ doesn't quite address clearly enough, or possibly could address better with graphics. Thanks! -C

2 3

CMake Address/Memory/Thread/Undefined Sanitizer support
by Michael Soegtrop 09 Sep '17

09 Sep '17

Dear Jabier, as discussed, I tested the Sanitzer builds with Debian 9 - works well. I can now configure 4 sanitizer variants with CMake D Parameters like this: -D SANITIZE_ADDRESS=ON -D SANITIZE_MEMORY=OFF -D SANITIZE_THREAD=OFF -D SANITIZE_UNDEFINED=ON address and undefined can be enabled together, the other two options require separate builds with only one option enabled. When I set export ASAN_OPTIONS=halt_on_error=0 before you start inkscape, it will not stop on errors. Then you get the output in sanitizer-sample-1.txt until inkscape reaches the main screen. It looks all like new/delete mismatches which usually come from forgetting to define a destructor virtual. If I disable these as well with: export ASAN_OPTIONS=new_delete_type_mismatch=0 it is clean until reaching main screen. The second attached file is from shutdown and shows just memory leaks. So chances are not bad that the Sanitizer will be useful for specific issues without a lot of upfront debugging. The detection and configuration of the sanitizers is done by CMake scripts I took from another project (compatible licenses). You get all 4 variants with gcc 6.xx. With earlier variants only the address sanitizer works. The changes to the inkscape CMake files are minimal, all is in separate CMake modules. I will do some more tests on Saturday and do a pull request then, but you can already look at it here: https://gitlab.com/MSoegtrop/inkscape/commits/sanitizer It is just one commit you can easily merge. Best regards, Michael P.S.: attachments as ZIP didn't get through and are way large unzipped. If someone is interested in the Sanitizer errors, please send me a mail.

2 3

Funded development thoughts (long)
by Bryce Harrington 08 Sep '17

08 Sep '17

There's been interest of late in figuring out some options for funding development work on Inkscape. I'm thrilled to hear this as I also think it's an important direction for Inkscape's longer term health, and something I've been working on directly myself for some time now. I promised Martin I'd write a thorough response to his proposal, including the course of action I think we should undertake, which makes for a long read, so I apologize upfront about the length. ------------------------------------------------------------------------ First, let me share my thoughts on Patreon and why we should not rely on it for our *project* needs. Patreon looks interesting for individual developers, but for the Inkscape project in general what we really need is a mechanism to direct and focus funds towards the issues our donors, users, and developers care about collectively, and to provide them with a level of accountability that the funds are being put to good use for tangible, predictable benefits. Patreon is undirected, simply providing funding for whatever the recipient wishes to do. It provides no mechanisms for review, guidance, or transparency. Martin suggested advertising placement on the Inkscape website and utilizing trademark legal enforcement as a carrot/stick mechanism to help ensure the recipients are at least working actively on Inkscape. However, website placement is likely going to be contentious since it relies on donors selecting who to fund. They'll either pick the most popular, the guy at the top of the list, the biggest self-promotor, or randomly. We can strive very hard to make it "fair" but with money involved there will always be complaints, and someone feeling that someone else is getting more funding priority than they "deserve". Despite our best of intentions, this feels likely to turn into a can of worms. The use of trademark enforcement is an interesting angle, by restricting who can label themselves as "Inkscape Developers". However, I believe trademark law does not work that way, and even if it did would be difficult to enforce, requiring the involvement of the Conservancy to issue cease-and-desist letters -- I think we'd end up deciding the marginal benefits would not make up for the time, manpower, and stress investments of dealing with abusers flouting our trademark rules. It may work adequately as a gentlemen's agreement, but if someone truly challenges it, I fear our enforcement will be revealed to be a paper tiger. But we needn't overthink it to that level - fundamentally, restricting how other developers define themselves within our community is at odds with our egalitarian principles, and does not respect the development freedom we cherish. If someone wants to refer to themselves as an Inkscape Developer, we should encourage it. ------------------------------------------------------------------------ Fortunately, we can achieve a much better approach by focusing our efforts more intently into the funded projects system already under way. Paid developer work has been long discussed in our project. We've looked at bounty systems, direct patron sponsorship, straight up contracting, and so on, that other projects have experimented with. We approached the Software Conservancy with these ideas and hashed them out into a workable system, after months of discussion and drafting. The essence of the system is straightforward: 1. We post a list of approved jobs, similar to our GSoC lists. 2. Money from donations can be directed towards jobs the donors want to see done. Small donations can be aggregated together to provide big funding for larger efforts. 3. We carefully vet developers who wish to take jobs, similar to how we vet GSoC students, but also judge their past work, history of Inkscape involvement, etc. 4. Vetted developers can take approved jobs when the funding level reaches the amount they feel is appropriate to the work, by sending in a Job Proposal (similar to GSoC), that we review and accept. 5. Developers are required to post monthly reports, just like GSoC. Each job also defines an expected time limit, like with GSoC. 6. On job completion, a Reviewer checks that the requirements were met, and the payment is cut. The process is strongly modeled after Google Summer of Code, which has been proven effective for us historically. It builds in several checkpoints to ensure bad actors don't enter the system, and to ensure accountability and transparency into the development work. It also empowers and leverage donors to influence where their money gets invested, both to give them a level of ownership and to use their donation decisions as "crowd wisdom" to ensure we're putting money where it will most benefit the Inkscape community's needs. One important distinction from GSoC is that jobs don't need to be fixed sized to fit 3-month summer schedules. This system should work for quick turn-around 1-2 week projects, up to multi-month or even year-long efforts. Whatever we need. It also doesn't have to be feature work, but could target bug fixing, website work, documentation. Whatever we need. A final benefit - this system's already been reviewed and approved by Software Conservancy's lawyers. So, while there might be some bumps along the way, there is no reason we can't start using it immediately. What I have been working on myself is Django-based software that would enable us to scale the system up to handle a multitude of project ideas, track jobs in various states of completion, and coordiate work by arbitrary numbers of developers, vetters, and reviewers. It aims to also directly hook the donation system into the project listings so a donor has instant feedback of the effect of their funds. This is complex, as you can imagine, and with my time being in short supply it's been slow going. However, for small scale needs the software is superfluous, we can do all the same steps manually, tracking status in a google spreadsheet or whatever. And for the near term, I think we should. Here's what we'd need to do: * Designate several people to defined roles: 1. Fundraising coordinator. 2. Vetter (must be a board member) 3. Reviewer * Add more Job definitions. + For each Job we define Completion Criteria + Board can vote to make certain of them immediately fundable. * Organize an online fundraiser. + Set up is just as we've done for hackfest fundraising, but with a detailed list of what Jobs are specifically being funded. + Donated funds are distributed equally to the specific Jobs we list. + Board can vote to assign Inkscape funds, too. * Recruit developers to participate + We already know of several (Mc, Tav); put out a call for more + Vetter will receive job proposals and review applicants, check that they've been actively contributing, and look able to complete assigned work, have provided payment details, etc. + Once vetter gives OK on a given job proposal, work can begin immediately When the work is done, the Reviewer reviews it, and I notify Conservancy to cut a check or wire transfer to the person that did it. This system is set up to make payments after completion, rather than reliably regular monthly payments, and I know that will be an issue for people needing predictable income for covering monthly rent and so on. One way we can hack around that is instead of defining one big 3-month job, to break it up into three 1-month (160 hr, $2000+) jobs assigned to them that they perform sequentially. This will require more reviewer involvement, but that's not necessarily a bad thing. For all of this to work, though, I would need to recruit a number of you to help out in various roles. I don't think these roles will be time consuming, but you'd need to commit to being available regularly as stuff comes up. How does this plan sound in concept? Bryce

6 10