- Inkscape Devel - Inkscape Mailman

Gitlab Migration (for reals this time)
by Ted Gould 05 Jun '17

05 Jun '17

Howdy folks, (sorry about the accidental first send) As we've discussed more that once we're looking to move a Bazaar repositories on Launchpad over to Git repositories on GitLab. We're now closing in on the time for that migration. We've discussed a schedule in the board meeting this afternoon and I wanted to make sure everyone is aware of the plan. We're expecting 24-hours of "downtime" as part of this. ==== Step 1 ==== Wed, 7 Jun evening US time We're going to make the Bazaar repositories owned by the project owned by the board and then start migrating them to Git. This will hopefully mean that accidental commits won't happen. The migration to Git will take a few hours, giving it over night to complete (allow for some network hiccups). ==== Step 2 ==== Wed, 8 Jun morning US time Push the Git repo and branches to GitLab, this should take a little while, but will hopefully be done by the afternoon. We should be generally good to go after that, but will verify a couple of downloads. ==== Step 3 ==== Party! I'll send an e-mail to the mailing lists for each phase as we go through them with a status update. If you have an open branch on LP, it should be migrated. Please make sure to push before Wed. night the 7th. It would be even better if they could be merged but that shouldn't be required. You should be able to pick up your branch from Gitlab on the other side. Ted

3 4

Inkscape Phone
by Jabier Arraiza 05 Jun '17

05 Jun '17

Hi all. Is posible add a mobile phone for Inkscape proyect. The growing services based in mobile some of them mobile only, maybe require an oficial mobile phone. The goal is not use calls or data changes and use throught WIFI. Cheers, Jabier.

12 27

Re: [Inkscape-devel] [Inkscape-docs] News item about the new manual work?
by Maren Hachmann 04 Jun '17

04 Jun '17

Hi Carl (and Brynn, see bottom), Am 04.06.2017 um 15:55 schrieb Carl Symons: > > I have been holding off on any further editing and proofreading pending a > resolution of the following information for myself. > > There are places in the manual where additional information would be useful. > Information that is not in the original version. Should it be added? If yes, > to what extent should the content be tweaked? This depends on the amount of detail you want to add. It should fit into the book's concept of giving 'just the necessary basics'. Everything that is not strictly necessary, and does not *largely* improve the helpfulness of the book for someone who knows *nothing* about vector graphics, should be left to the detailed manual for advanced users. This is just an introduction, for people who want to learn by do(odl)ing, and who will pick up the concepts as they advance. It is meant to be easy - in writing style, with short sentences, as well as in contents. Would you like to pick up proofreading again where you left? You're welcome to make edits that fit the above description any time, without having to ask for permission. > Also ... there was some discussion about reorganizing the manual, changing > chapter order and the like. > > Apologies if this has been discussed previously. I've only recently joined the > manual effort. > > It would help to know if the project is mostly about translation or if it's > more extensive than that. Guidance please. @Brynn + Carl: I think we might postpone the changing of chapter order to a later point of time, so we will get a first, 'working' copy faster, and so people have a chance to gain insight into the conceptualization of the book. Also, that discussion got us sidetracked a bit, it seems, if it lead to Carl not knowing what to do next (and if). If anything, changing the order is a matter of drag and drop, and can be done any time, it shouldn't stop us from working. (I was thinking having a skeleton ready at Hackfest time might be useful, in case Elisa and Cédric would like to help work on this then - but of course, I don't know what their plans are for Paris). Kind Regards, Maren

1 0

Re: [Inkscape-devel] [Inkscape-docs] News item about the new manual work?
by Maren Hachmann 04 Jun '17

04 Jun '17

Thank you, Marietta, Carl, and Martin for pointing me into the right direction (hopefully) and for calling for help, and volunteering your time :) I'm glad to know that people are still interested in helping, but might just not have known how (or, in CR's case, are too busy with other stuff - believe me, I understand). Guess I got too used to the standard open source theme of 'grab a task and do it if you're up to it' - and I'm also kind of shy about telling others what to do. I'm sorry about not getting that I should take on a more active, guiding role, to make it easier for new members to join. @Marietta: What do you think about Martin's suggestion? Kind Regards, Maren Am 04.06.2017 um 22:52 schrieb Martin Owens: > On Sun, 2017-06-04 at 13:20 -0500, Marietta Walker wrote: >> If I can help, I will be glad to do so, but I do have limitations >> in knowing the software. > > You would make a good editor then, both in the generic sense for > English grammar and the functional sense in 'do you understand this' > > Is this something you'd be good at helping with? > > Best Regards, Martin Owens > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ Inkscape-docs mailing > list Inkscape-docs(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-docs >

1 0

Extension
by Jabier Arraiza 04 Jun '17

04 Jun '17

Hi all. There is a pending merge with a python extension. https://code.launchpad.net/~rwhite8282/inkscape/frame-extension/+merge/2873… There is two things to do with it: * Review it, I could do but not too much expertice on python. * Decide if is a extension suitable to grow default ones or maybe is better include into inkscape.org/extensions. Cheers, Jabier.

1 0

Re: [Inkscape-devel] All hands to Merge Requests!
by Martin Owens 04 Jun '17

04 Jun '17

Hi Michael, This sounds very much like it should have gone into trunk /before/ going into 0.92 or 0.93. The process is that items are merged into trunk/main and then are forked to the release branch, these forks then get merges from trunk (and rarely fixes just for that branch). If it was working for 0.92 and still works in trunk and has been reviewed, merge it in. The deadline is Wed 7th June, so it's practically now! Best Regards, Martin Owens On Sun, 2017-06-04 at 17:12 +0200, Michael Soegtrop wrote: > Dear Martin, > > I am sure the answer is somewhere in the lengthy discussion on moving > to > git but I must admit I didn't follow it. What I need to know is what > the > deadline is. > > The stuff was working fine in 0.92 and reviewed OK (by Jabier), it > just > didn't make it in time for 0.93. So all that needs to be done is > merge > it from 0.92 to 0.93 (or the current baseline). > > There is one additional LPE in this branch which is intended for > making > designs for stitching machines. This is also working, but it could > need > some improvements in the path optimization algorithms (a TSP). But I > think this can be fixed later (enable this LPE only in development > builds). > > Best regards, > > Michael > > On 04.06.2017 17:01, Martin Owens wrote: > > > > Michael, > > > > If you don't think it can be completed in the time left, then we > > should > > look for the git branch when the migration is complete. If it's not > > there, you may have to copy across your changes and commit them > > into a > > new branch. > > > > But if you need help with your branch, this is a good time to ask. > > > > Best Regards, Martin Owens > > > > On Sun, 2017-06-04 at 14:11 +0200, Michael Soegtrop wrote: > > > > > > Dear Martin, > > > > > > I am not sure how to proceed with my bool lpe. Shoul dit be > > > finalized > > > in > > > bzr until some deadline, or should I move it over somehow > > > (manually) > > > to git? > > > > > > Best regards, > > > > > > Michael

1 0

Re: [Inkscape-devel] All hands to Merge Requests!
by Martin Owens 04 Jun '17

04 Jun '17

Michael, If you don't think it can be completed in the time left, then we should look for the git branch when the migration is complete. If it's not there, you may have to copy across your changes and commit them into a new branch. But if you need help with your branch, this is a good time to ask. Best Regards, Martin Owens On Sun, 2017-06-04 at 14:11 +0200, Michael Soegtrop wrote: > Dear Martin, > > I am not sure how to proceed with my bool lpe. Shoul dit be finalized > in > bzr until some deadline, or should I move it over somehow (manually) > to git? > > Best regards, > > Michael

1 0

Board Meeting Minutes ~ 2017-05-03
by Bryce Harrington 04 Jun '17

04 Jun '17

== Meeting Minutes for 2017-05-03 == I don't usually prepare meeting minutes, but there was a ton of discussion with a lot of follow ups and action items, so figure it could use some additional visibility. Summary of Action Items: + ACTION: Need to sharpen pencil on budget to see where we're at exactly. [bryce] + ACTION: Draft https://inkscape.org/en/support-us/hackfest-2017/ [Tavmjong] + ACTION: Make a news item for the hackfest fundraiser [Tavmjong, doctormon] + ACTION: Advertise hackfest fundraiser on twitter [Mc, Tavmjong] + ACTION: Advertise hackfest fundraiser on facebook [Tavmjong or designee] + ACTION: Advertise hackfest fundraiser on G+ [Tavmjong or designee] + ACTION: Advertise hackfest fundraiser on Instagram [Rob-Sterbal, Tavmjong] + ACTION: Investigate stickers & pricing for hackfest [jabiertxof] + ACTION: Decide GUADEC attendance [Alex] + ACTION: Propose donation "add-on" for Win10 store to inkscape-devel@ [Mc] + ACTION: Jot signed-mug raffle idea down on Fundraising_Ideas page [CRogers] + ACTION: Test the message patch from ML [tedg] + ACTION: Announce plan for gitlab migration [tedg] + ACTION: Discuss scripting ideas for bug migration [Mc, doctormon] + ACTION: Re-raise topic of bugtracker migration at a future time [Mc] + ACTION: Help Mc kickoff funded devel of a feature [bryce] + ACTION: Propose a batch t-shirt run (e.g. for hackfest) [tedg] + ACTION: Re-contact Mihaela to finish starting up Spreadshirt [doctormon, bryce] + ACTION: Experiment with first-call / last-call dates on board votes [bryce] + ACTION: Check on board member voting [bryce] Full log: https://inkscape.org/en/paste/11064/ === Paris Hackfest === * 5 devs + interest from a few others * Note that Conservancy has clarified travel reimbursement documentation + Process hasn't changed but it's explained better. + Hackfest travelers should doublecheck * Future hackfests may be short on cash + We have $8000 budgeted for hackfests currently + The 2017 hackfest allocates $13,000 expenses - Most people won't use their full allocation - Some people won't be able to attend - So actual expense should be far less than the allocation + ACTION: Need to sharpen pencil on budget to see where we're at exactly. [Bryce] * Should use this as opportunity to do fundraising for further hackfests + ACTION: Draft https://inkscape.org/en/support-us/hackfest-2017/ [Tavmjong] + ACTION: Make a news item for the hackfest fundraiser [Tavmjong, doctormon] + ACTION: Advertise hackfest fundraiser on twitter [Mc, Tavmjong] + ACTION: Advertise hackfest fundraiser on facebook [Tavmjong or designee] + ACTION: Advertise hackfest fundraiser on G+ [Tavmjong or designee] + ACTION: Advertise hackfest fundraiser on Instagram [Rob-Sterbal, Tavmjong] * Should we plan a community "open day" at the Hackfest? + Sticker give-aways to visitors of the event (if any) + Stacks to distribute to regular attendees to give out at other events + If it's done, designate a single day for visitors, to avoid distraction, and make sure to advertise the fact prominently + Purpose of hackfest is not community outreach, so perhaps should be left for a separate event. * The SFC-produced stickers might not get done in time for the hackfest, but the designs could be used for locally printed ones + Ryan Gorley recommends https://www.uprinting.com/vinyl-sticker-printing.html + Shoot for 20 per attendee, ~200 total + ACTION: Investigate stickers & pricing for hackfest [jabiertxof] * Virtual attendance (e.g. livestream, google hangouts, etc.) + If someone sets it up, post explanation on how to get set up === GUADEC - Gtk3 === * Coming up end of July in Manchester * Last year they said they could help us with Gtk3 stuff. * Would be worthwhile if Alex could go, pertaining Gtk3 + tghs (Mac gtk3) is in Leeds so can make it for attendance * ACTION: Decide GUADEC attendance [Alex] === Sticker Printing by Conservancy === * Stickers are designed from the about screen entrants. Artists were asked if they would be open to having their work printed on stickers. + https://inkscape.org/en/~doctormo/%E2%98%85stickers-2017-draw-freely + https://inkscape.org/en/~doctormo/%E2%98%85stickers-2017-landscape-inkscape * Designs were sent to SFC with a $100 budget (vote approved by board) + Waiting on Brett to get back to us on it === Funded Projects === * Various funded feature development ideas were floated during the meeting: + 1% zoom limit (chr[]) + hidpi support (Windows users want this particularly) + gtk3 migration may give a native-looking ui for mac os, and many people would pay for that * Various fundraising ideas were floated during the meeting: + Kickstarter fundraising based on feature sets that people ask for all the time has worked very well for Krita - krita succeeds well at advertizing becaue they work with awesome artists to promote them - They also deliver things that artists ask for as their primary goal. + Donation dummy "add-on" to Inkscape on the Windows store - ACTION: Propose donation "add-on" for Win10 store to inkscape-devel@ [Mc] + Raffle for an inkscape mug and/or t-shirt signed by hackfest devs - ACTION: Jot signed-mug raffle idea down on Fundraising_Ideas page [CRogers] + More ideas are being captured at: http://wiki.inkscape.org/wiki/index.php/Fundraising_Ideas === Gitlab Migration === * General desire is to get it achieved prior to the hackfest + The hackfest would be a good opportunity to f2f through the various followup work-items. + But should target getting it done a couple weeks prior, else major issues could be disruptive of the event. + So need to target getting it done in the next week or so. + Followup-workitems for post-migration: - Automating builds - Fix cmake bzr-isms - Update builds for windows - Update builds for mac - Fix jenkins - Rewriting inkscape.org to re-document git instead of bzr * Ted has done some dry runs. The 0.44 branches generate import errors, but everything else looks happy. + Ted wants ~24hr downtime to deal with migration issues, so need to disable commits for that interim. + ACTION: Test the message patch from ML [tedg] + ACTION: Announce plan for gitlab migration [tedg] * plan -- send notice to the list (today?), then 24hr later change ownership of inkscape.dev's branches or otherwise configure them so they can't be committed to, run the migration script, do any cleanup, and if all's well we reopen on gitlab 24 hr after that + Branches owned by individuals may need separate attention. People can continue hosting branches in LP for now, but we might revisit this later (esp. if/when we wish to close out the Inkscape LP project.) With gitlab, user branches are kept more separate (e.g. as forks) but we can import broadly and prune later. + Do the migration mid-week, as people seem to use W-E's for devel * Bug reporting will remain with Launchpad for now. + Launchpad's spam problem has been growing... + Existing bzr revno references from bug reports will continue to work, but going forward these will need to start referencing to git SHA's at gitlab. For now we won't have the easy shortcuts from bug reports to commits (or vice versa). + Non-trivial to import bugs to gitlab.com -- it doesn't permit setting the bug owners/commenters for one thing. - might be doable if we ran our own gitlab instance. - Maybe be acceptable of old bugs/comments are just left owned by inkscape.dev? + ACTION: Discuss scripting ideas for bug migration [Mc, DoctorMo] + ACTION: Re-raise topic of bugtracker migration at a future time [Mc] === Infrastructure backup/alternate hosting === * This effort is in early discussion/planning stage. Bryce and Martin have been working on it behind the scenes but now ready for some wider input and thinking. * Rationale for investigating alternatives: 1. Capacity has been a bit limited with OSUOSL; we've banged our head on this a few times now. 2. Responsiveness to IT requests has also been pretty slow. Two infrastructure moves have had to be scuttled/replanned due to this. 3. Outages occur periodically (generally due to #1 or #2 but sometimes unrelated). * Goal is having a primary host, with a second independent host we can bring up as cold failover in emergencies. + Geographically separated, e.g. Europe + Canada/US + Backup host would be kept simple - a mirror of the primary that can be manually switched on as needed. + Even if we stick with OSUOSL we still should have another host, just for best practices in case of failures. * Current hosting has been 100% sponsor supported. We have budget to pay for IT support but obviously would prefer sponsor support here. + We're not yet ready to start contacting or engaging, but close === Funded development project management system == * Bryce still plugging away at it * Manual funding of feature development also possibility + This would mainly involve recruiting and vetting developers to take on one of the already defined and funded projects + Also need to track devel progress and completion, and coordinate payment (via Conservancy) + Similar to GSoC but less teaching, and shorter durations + ACTION: Help Mc kickoff funded devel of a feature [Bryce] === Merchandise Sales === * Temporary-run batch T-Shirt sales + "Must pass this line, limited sale" + Could just use existing logo + Need to identify a good quality t-shirt supplier (Cotton Bureau?) https://cottonbureau.com/submit-a-design + ACTION: Propose a batch t-shirt run (e.g. for hackfest) [tedg] * Spreadshirt + On hold, no changes to report + Probably time to pick a kickoff date and run with what we have + ACTION: Re-contact Mihaela to finish starting up Spreadshirt [doctormon, bryce] * If anyone wants to take lead on setting up other merchandising options, contact bryce. We're pretty open to ideas, just need someone to make arrangements and set up the order/shop/etc. === GSoC === * Just started this week, first evaluation in a month * There will be an additional $500 per student for travel costs. + Does the board need to be involved in arranging or approving the expenditures? Probably, since it'll go through conservancy... + We'll wait until the issue comes up; board can do a quick enough vote on it. Contact bryce when you have specifics. === How's the Board Doing? === * More efficient voting + Need quicker turnaround + Not all board members are placing votes + ACTION: Experiment with first-call / last-call dates on board votes [bryce] + ACTION: Check on board member voting [bryce] * Automation of board work + Need tool to upload text files to the website's pastebin (I.e. to send IRC log snippets of board meetings, w/ metadata) === Other Business === None === Next Meeting === Same time & place, July 7th, 2017.

1 0

Website / GSOC
by Maren Hachmann 02 Jun '17

02 Jun '17

Hi all, just noticed someone updated the front page for this year's summer of code (when I wanted to do that). Was the change meant to be published, or is there a reason why it's not published yet? Could any website editors, when they make a change that requires translation (i.e. not typo corrections), please send a short notice to the translators mailing list to notify us about the page that has been changed and the nature of the change? We don't have any diffs for website edits anymore, and I'd find it unfortunate if we all had to rely on me noticing any changes for keeping translations of the website in sync. Thank you! Kind Regards, Maren

4 6

GitLab Migration Schedule
by Ted Gould 02 Jun '17

02 Jun '17

Howdy folks, As we've discussed more that once we're looking to move a Bazaar repositories on Launchpad over to Git repositories on GitLab. We're no closing in on the time for that migration. We've discussed a schedule in the board meeting this afternoon and I wanted to make sure everyone is aware of the plan. We're expecting 24-hours of "downtime" as part of this. Step 1:

1 0