- Inkscape Devel - Inkscape Mailman

Potential GSOC student: Contributing into InkScape
by Shavez Malick 21 Mar '19

21 Mar '19

Hi Inkscape! I am Shavez, a sophomore @IIT Indore. I really liked InkScape when I first used it. I am seeking participation in GSOC 2019. I have chosen InkScape as my org to contribute. I had my mid-term exams over the month of March, :( They went well, though :). I have cloned your repo and will be pushing couple of patches soon. I have fairly good exposure to programming, I participated in many coding-related events till now. I will really appreciate any suggestions related to this.

1 0

Re: [Inkscape-devel] LGM/Saarbrücken Hackfest
by Maren Hachmann 20 Mar '19

20 Mar '19

Okay, thanks you for your replies, Jabier, Marc, Mihaela, Thomas and Tav! (and for updating the Wiki page already :) ) I'll confirm the dates, and will include Thomas in the email, so he and Aude can contact each other for the signing/key arrangements. --------------------- Everyone: Next, it would be good if everyone interested in joining could put their name into the list of 'unconfirmed but likely attendees' on the Wiki: http://wiki.inkscape.org/wiki/index.php/Hackfest2019_Saarbr%C3%BCcken_Atten… This is so the board can arrange a vote for funding, as SFC requires us to give them the attendees' names in advance. If you want to join, but do not need or want project funding, please indicate this in the Wiki. If you already have decided *when* you want to be there, please include that info. It is helpful in determining how many people will be there at k8's office. Thanks! Maren Am 19.03.19 um 23:30 schrieb Marker: > Great Maren thanks for the call and for the write up. > > I think Q1 is perfect dates, realy not sure when I attend jet... > > > On Tue, 2019-03-19 at 23:15 +0100, Maren Hachmann wrote: >> Hi Inkscapers, >> >> today, I phoned Aude Poilroux, project manager working at k8, who had >> offered to help us with getting a space for the planned Hackfest >> before LGM. >> >> k8.design (Institut für strategische Ästhetik) >> ---------------------------------------------- >> >> A non-profit company (gGmbH) owned by the Saarbrücken arts >> university. >> They do work on organizing events, art cooperations, digital >> transformation, supporting and executing projects that originated in >> the >> university, and many other things that the university itself isn't >> allowed to do, because it's an educational institution, and not a >> business. Their offices are at Keplerstr. 3-5 in Saarbrücken. >> >> Meeting space >> ------------- >> >> Aude is offering us a part of k8's open-plan office for May 27th, >> 28th >> and 29th. The part is usually used as sitting area, but they want to >> put >> some additional chairs and tables in. She says the place can hold up >> to >> 20 persons (but then it will be a bit cramped). There is another >> adjacent office, that can hold about 10 persons, but it may not be >> available all the time. We could use it for discussing stuff, while >> working can be done in the larger room. I forgot to ask about >> whiteboard/blackboard/projector/flip chart or similar. There are lots >> of >> electricity outlets, but we might need to bring some German multiple >> socket outlets. They have WiFi. I'm not sure about wired LAN, but she >> says the internet connection is broad band and very fast. >> >> We could use the space from ~ 9:00 in the morning, and if we can name >> one responsible person, she is considering to give us a key, so we >> can >> stay as long as we need. >> >> There is no canteen, and no organized meals. However, the venue is >> located in a pedestrian zone with multiple places where one can buy >> food >> close by. One of them is a wholefood shop, which offers meals at >> reasonable prices. There are also a couple of bakeries, and then >> there's >> a microwave in the office. >> >> She is asking us to let her know the rough number of attendees by mid >> May. We would then also need to name a responsible person, who would >> need to sign for the group, and would guarantee for us not wreaking >> havoc in their offices. >> >> On the 29th, there will be an additional event called "From Code to >> Community", starting around midday, where local (as in ~ 100km >> radius) >> businesses and open source projects are meant to meet. The program >> isn't >> ready to be published yet, but it is planned that there will be >> keynotes >> by politicians and people from FSFE, talks about open source business >> applications, talks about open culture, a workshop on collaboration >> culture, booths from various open source projects (educational, LUGs, >> mapping, MSF, framasoft). The event is meant to attract students and >> businesses. It's going to take place in the same building where, at >> 18:00, the opening of LGM will take place. >> >> Aude is asking us if we would be able to staff a booth there, to >> present >> Inkscape to students and small businesses. The event is mostly in >> German, but people from Luxembourg and France are invited to attend >> too, >> so it might be useful to also have one of our French-speaking >> community >> members there. >> >> During LGM, they seem to have more rooms available than there will be >> conference tracks, so she says it should be possible to have a >> collaboration space for Inkscape. However, we probably won't be able >> to >> have the same place continuously, and we would have to ask when we >> need >> it. There is also plenty of sitting space available on the venue that >> is >> not in a separate room. >> >> >> So Q1: >> Shall I confirm the dates as written above? >> >> Q2: >> Would someone be interested in presenting Inkscape to local people >> before LGM on Wednesday? (I would be) >> >> And Q3: >> Is there anyone volunteering to be the one who holds the key (if we >> get >> one) and to sign the agreement? I will probably not stay late, so I'd >> like that to be someone else. >> >> It's probably not a problem to translate things to English, but >> someone >> from Germany would be preferred for this. >> >> Thanks! >> >> Please let me know what you think about Q1-Q3 quickly :) >> >> Maren >> >> >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel > >

1 0

rules and guidelines for new forum - first draft
by brynn 19 Mar '19

19 Mar '19

Hi Friends, As it turned out, only me and a couple of other people were interested in drafting the rules and guidelines for the new forum. So we can get more eyes on it, and possibly more professional opinions about it, I'd like to ask the community to have a look at it. I have no background in writing such documents, so it's purely a layperson's whack at it. I feel quite confident about the contents, based on my years of experience in Inkscape forums. But the format of the document, and possibly some of the language might need some technical advice. So any an all comments and suggestions about the format or language are very welcome. https://gitlab.com/inkscape/vectors/content/blob/master/articles/Forum%20Ru… (I've left it locked to editing, so everyone sees the same doc, for this first review. Then I'll unlock it afterwards.) Thank you very much, brynn PS - I'm also posting about this in the forums.

3 8

Re: [Inkscape-devel] [Inkscape-user] Fundrasing for FOSS Projects - meetup this saturday
by unknown＠example.com 19 Mar '19

19 Mar '19

On Sun, 2019-03-17 at 13:47 -0700, Andrew Kurn wrote: > Why does Inkscape need money? The low budget requirements are for things like hackfest travel, hotels, stickers, posters, hardware, DNS, trademark registration, legal defense, (and then accountancy because of said needs for money). Depending on the source of money, there can be lots of things Inkscape could do with a good budget. We've been using money for a long time now. > Can you give some idea of how much we spend each year and how > much we take in? Doesn't need to be a full income statement, > but hit the high points. Bryce publishes an account each year. I think he'll be happy to post it again here. Best Regards, Martin Owens

2 1

Watch Parties - starting Mar 16th
by Bryce Harrington 16 Mar '19

16 Mar '19

Topic: Fundraising for FOSS Projects When: Sat, Mar 16th 19:00 UTC to 21:00 UTC Where: chat.inkscape.org in channel #collaboration_space This Saturday, Michèle and I will be watching and discussing a series of videos on fundraising for open source projects. Afterwards, we can bounce ideas around for how to improve Inkscape's funding. Please join us, we'd love the company. :-) For links to the videos, and some tentative plans for future topics for Watch Parties, please see: http://wiki.inkscape.org/wiki/index.php/Inkscape_Classes Bryce

1 1

Bug management for inkscape/inkscape
by Patrick Storz 14 Mar '19

14 Mar '19

Hi all, it seems the message of our move of issue tracking to GitLab is slowly spreading and we're seeing a steady flow of new reports in our inkscape/inkscape issue tracker on Gitlab (https://gitlab.com/inkscape/inkscape/issues). As most of us had the opportunity to get some first-hand experience with the new issue tracking by now and with the amount of bugs still being manageable, it seems to be a good time to discuss and decide on some guidelines for this tracker, so we can make most efficient use of it. Having worked with the tracker fo some time here's my list of items (in no particular order) that I feel need attention. Please add to it as needed and most importantly discuss, so we can find solutions that work well for all of us. (We can obviously break individual topics out into GitLab issues eventually, once we have set a rough direction). * *Milestones:* On Launchpad (LP) we used Milestones for targeting bugs (only occasionally, though) but more importantly for tracking in which release a fix landed. The latter seems of particular importance, as release notes rely on it heavily. I suggest to continue this practice and expand it to merge requests. However this requires us all to make sure to actually set milestones properly. Currently we often just close bugs without giving it further thought (GitLab even does that automatically for us if a suitable commit message is used), which would make it almost impossible to keep track of the issues fixed in a particular release. Even more so for MRs... * *Importance:* I feel that we need some mechanism to prioritize bugs. What is your take on creating a set of prioritized labels of the form "Importance: High" to replace LPs importance field? I propose to use "Critical -> High -> Medium -> Low". Even above critical I'd put the already existing label "Blocker". At the end of the list I'd rank "Feature request". Does this sound reasonable? Or is it too fine grained? Is handling "Blocker" and "Feature request" as additional importance labels fine or should they be separate? * *Labels: * o A general question is what labels we want to apply and how many there should be. I'm a bit torn here, as a short list makes it easier to keep track of the existing labels and avoids similar issues being tagged differently, especially if there are multiple similar choices or one tag is a sub/superset of another. A longer list would help us categorize issues better though. (For example: Do we want a tag for every packaging option we have, e.g. AppImage, Flatpak, msi, exe, Windows Store, ...? Do we want a tag for every Linux distribution or just a single "Linux" tag?). o Another question is if we want to categorize them (e.g. "OS/Linux", "OS/Windows", "OS/Mac") or if we strip the category? The former ensures similar tags are sorted together (otherwise they're sorted alphabetically) and *if* one remembers the category name it makes it easy to get all relevant tags by simply typing "OS", but then again tagging with just "Windows" seems more natural and the category might add noise. Also it obviously requires some thought in order to create useful categories (in contrast to just applying "random" tags that fit and creating new ones on-the-fly). As I'm somebody who likes order I tend to prefer categorization, but this is something I'd like your opinion on. (Important note: The search is clever enough to give you "OS/Windows" if you search for "win"). * *Status *On LP we had a detailed status field (new, confirmed, triaged, in progress, fix commited, fix released - also: incomplete, opinion, invalid, won't fix). Which of those do we want to replicate in GitLab (and how?). We could obviously create a label for each of them, but I have a feeling without a dedicated field it'd not be used consistently. One idea: o "new/confirmed" should be covered by "inkscape/inkscape" vs "inkscape/inbox". Only confirmed issues should ever end up in "inkscape/inkscape" (everything else should be confirmed or moved to the inbox for triaging). o "triaged" would be replaced by the presence (or absence) of an "Importance:" label should we choose to use them. o "in progress": We already have a corresponding label and could use it. Alternatively we could define that all assigned bugs are "in progress" (i.e. only assign bugs if the assignee is going to work on them eventually; un-assign otherwise) o "fix commited/fix released": I don't know how to replicate this reasonably. Is it even required? o "incomplete": We have "Need info" but such bugs should usually not be kept in "inkscape/inkscape" for extended periods of time (if the info is not given, close or move back to "inbox") o "opinion": should never exist in "inkscape/inkscape" o "invalid": Do we need a label? Or shall we just close in this case and forget about it? o "won't fix": should usually not make it into "inkscape/inkscape" - do we want a label or shall we just close (i.e. same question as as for invalid?) * *Assignee* As suggested above we could use the assignee field to put devs who are going to work on an issue eventually (i.e. indicate "this issue is being looked into / will be looked into shortly"). Alternatively we could use it to indicate devs who are likely to be able to fix the issue and are most suited for detailed triaging and further investigation (i.e. indicate "we know somebody who might be able to help, please wait until they find the time to check"). This could be used to distribute and direct the workload a bit. However we can likely do that with simple @mentioning? Sorry for the long text (I hope you all read up to this ;-)), it certainly got longer than intended... I'm looking forward to your opinions, though! Cheers Patrick

6 20

Wiki account request
by Ryan Jarvis 13 Mar '19

13 Mar '19

Hello, I've been helping on the inkscape extension front and would like access to the wiki to edit some of the related pages. Thanks!

2 2

Saarbrüken Hackfest + LGM 2019 Funding
by Bryce Harrington 11 Mar '19

11 Mar '19

The Inkscape Board has approved funding for holding a hackfest in Germany this May, for 2 days preceeding the Libre Graphics Meeting. Many details are still in process of being worked out, but if you're interested in attending please save a spot in your calendar for Monday May 27 to Sunday, June 2. If you'd like to share your knowledge of the city, or contribute planning in other ways, please join in editing the wiki page: http://wiki.inkscape.org/wiki/index.php/Hackfest2019_Saarbr%C3%BCcken Add yourself to the Likely Attendees list if you think you'll be able to come, and if you wish to be considered for travel funding. Bryce ----- Forwarded message from Bryce Harrington <bryce@...961...> ----- Date: Wed, 6 Mar 2019 22:49:23 -0800 From: Bryce Harrington <bryce@...961...> To: inkscape-board@...6... Cc: approvals@...3696..., accounting@...3057..., inkscape@...3057... Subject: Re: [REFERENDUM] Saarbrüken Hackfest 2019 Funding Resolution: ----------- Inkscape will be reimbursing travel expenses for individuals attending the hackfest and Libre Graphics Meeting in Saarbrücken, Germany in May 2019. This will cover transportation, lodging, and food costs following the reimbursement rules specified by the Software Conservancy. The exact list of approved attendees is still to be determined, but we expect it will be in the range of 5-15 individuals, as has been typical in past events. A second vote will be held to approve specific travelers, and their names and email addresses will be communicated to Conservancy at that time. A listing of prospective invitees is available at: http://wiki.inkscape.org/wiki/index.php/Hackfest2019_Saarbr%C3%BCcken_Atten… The board will sponsor a dinner out for Hackfest attendees and their guests for up to 300 € total. (If the number of confirmed attendees exceeds 10, the board may increase this amount in a future vote.) The event host will ensure there are snacks and beverages, and procure other incidentals as needed for attendees. They will be reimbursed for up to a total of 100 €. Votes: ------ | Board Member | 1. | 2. | 3. | | -------------------- |:--:|:--:|:--:| | Bryce Harrington | a. | a. | a. | | Josh Andler | a. | a. | a. | | Tavmjong Bah | a. | a. | a. | | Ted Gould | a. | a. | a. | | Martin Owens | a. | a. | a. | | Marc Jeanmougin | a. | a. | a. | | Chris Rogers | a. | a. | a. | Proposal: --------- Voting is needed on funding for sponsorship of attendees at the Saarbrücken Hackfest planned for May 2019. 1. Travel Sponsorship to Saarbrücken, Germany. - [ ] a. Reimburse pre-approved attendees (TBD) for up to a flat amount of $2000 per person. - [ ] b. Reimburse using the ranked system used for the Boston hackfest. - [ ] c. Reimburse with open ended limits to extent permitted by Software Conservancy policy. - [ ] d. Other: _______ - [ ] e. No, do not fund. 2. Board-sponsored Dinner. The Inkscape Board will fund a dinner out for Hackfest attendees and their guests. An estimated 10 people averaging 30 € each gives a budget of 300 €. - [ ] a. Yes, for estimated cost of up to 300 €. - [ ] b. Recommend a change: ___________ - [ ] c. No, do not fund. 3. Refreshments. The event host will ensure there are snacks and beverages, and procure other incidentals as needed for attendees. An estimate of 10 attendees * 2 days * 5 € suggests a budget of 100€. - [ ] a. Authorize reimbursement of up to 100 € to the event host for snacks, beverages, and other incidentals relating to the event hosting. - [ ] b. Authorize a different amount: _______ - [ ] c. Do not authorize reimbursement for refreshments Background: ----------- The Libre Graphics Meeting will be held in Germany in May. We wish to also hold a 2-day hackfest preceeding it. Travel grants will be provided to attendees of these events. The exact list of approved attendees will be determined separately. We anticipate attendance in the 10-15 person range. A listing of prospective invitees is available at: http://wiki.inkscape.org/wiki/index.php/Hackfest2019_Saarbr%C3%BCcken_Atten… Further details about the hackfest are available from http://wiki.inkscape.org/wiki/index.php/Hackfest2019_Saarbrücken ----- End forwarded message -----

4 5

Recap of Inkscape's Hackfest in Pasadena
by Bryce Harrington 07 Mar '19

07 Mar '19

We've just completed another great hackfest here in rainy California, and wanted to share some accomplishments of the event. * The 1.0 release plan was fleshed out 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. * The Roadmap will be rejuvenated with a new monthly process. 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. * A vision document on our UI strategy 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. * A "Big Ideas" tracker will be established in gitlab. (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. * For Mac OS/X, we want to make initial steps by 1.0 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. 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. 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. * For CMYK, Color Management, and PDF/Print, we have a detailed plan of development tasks needed. This will be published in the "Big Ideas" gitlab tracker. * We will establish Paypal buttons for dedicated funds to start collection of donations for several targeted efforts: A. Native Mac OS/X Packaging B. Color Management C. Internships promoting diversity (e.g. Outreachy) * Budget planning work was begun 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. * A brand/trademark issue exists which needs visibility We will be making this (and things people can do to help) public soon. Preparatory tasks were identified and split up between us. * Video interviews of attendees were collected These videos will provide material for Vectors team outreach and communications efforts in coming weeks and months. * A greeter guideline was conceptualized 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. * Teacher curriculum grant program 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. * Codebase subsystem contacts 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. SCALE

1 0

Friendly Membership and Mentorship (hackfest meeting)
by Martin Owens 06 Mar '19

06 Mar '19

Dear Inkscape, We had an involved discussion about membership in the Inkscape project; how we can be welcoming and how we can organise ourselves for both casual and formal mentoring. Why: 1. To increase the number of contributors to the Inkscape project. 2. To actively improve the diversity of the project. 3. To inspire developers to develop for users needs. How: We already have a code of conduct, which is a firm code that everyone who is a part of Inkscape must abide to in order to be a part of this community. But on top of this, we wish to draft a "Universal Greeting" policy. This establishes the ways in which existing contributors interact with new contributors and users who may become contributors. We wish all Inkscape project contributors to be casual mentors to all other contributors and be mindful of our roles as guides. The goal is to improve the welcoming atmosphere of all of our official channels by providing a clear declaration of what being a good greeter is as well as a clear list of possible responses to each of the various questions, suggestions and criticisms of the project. Contributors do not have to sign up to the policy, but may be asked to not respond to new contributors until a greeter has had a chance to direct the new person to the right places for kind of contribution they want to make. Tasks: * [ ] Draft Universal Greeting Declaration. How to basics * [ ] Document of Topics and good responses. The next topic involves the old Inkscape Roadmap. This is sometimes known as the Inkscape Forecast as it's less of a document of what Inkscape will do, or even wishes it could do, but a way to document what things contributors are known to be working on and interested in. To improve this whole process of direction in the project and improve how new features land we wish to create a "Forecast Party", these are monthly events which would be hosted on Rocket Chat (and IRC) where we would. A. In the meeting before a release, review the whole forecast and decide on the big picture direction of the project. B. After a new release, have a landing space for new contributors to the project where we talk about the exiting possibilities and act as a meet and greet for everyone. C. All other months would be a focus on a specific forecast or wish list item. For example on month may be CMYK, another month may be multi-page. The idea is to get experts and excited people into the same room and talking about the next steps for the feature, throwing open the doors to the Inkscape project and promoting the events as a way to get into moving Inkscape forwards. Show and tell, videos and other media are expected to be parts of the meeting. Tasks: * [ ] Create a rocket chat channel for the new event * [ ] Talk with vectors team about how to promote the events into the wider community * [ ] Talk with other developers about promoting the events in developer spaces * [ ] Schedule some events to kick of the project. An introductory meeting to talk about the forecast list itself and what we should be meeting about next. * [ ] Set up a Forecast Inkscape project, only the forecast managers can post new issues to the kanban board, but it would be used to monitor and understand the Inkscape forecast in detail as well as document previous discussions. We wanted to talk about more active mentorship programs, actively inviting students from universities with an focus on diversity. We want to reach out to Outreachy and talk to other groups about how to attract new students. Tasks: * [ ] Meeting with Mo about Outreachy at Libre Planet * [ ] Decide how much money we want to spend on a mentorship program (board meeting) * [ ] Decide how to attract students and if we want mentors and students to be online or if we want programs run through existing university programs and networks. Martin,

3 2