- Inkscape Board of Directors

Vote: Allow Tav to work on Bug Accelerator Program
by Martin Owens 20 Aug '26

20 Aug '26

Dear PLC, I wanted pono or someone at the SFC to make this vote, but hopefully this won't step on toes as we can't wait so long to have help with the Bug Accelerator Program. Because Tav voted in favour of the funding for BAP 2026.2, the SFC want us to confirm that we want Tav to be eligible. From the hiring committee our report is that there is a cliff edge in assessed quality/qualifications after Tav and we recommend allowing Tav to fill in for Sean for 2026.2. An alternative is to require the hiring comittee to put out a request for a new applicants for the position. It will take longer to do this. Tav must abstain from this vote. Should Tav be allowed to contract for the Bug Accelerator Program 2026.2? a. Approve Tav b. Require new hires c. Don't contract anyone d. Something else Best Regards, Martin Owens

6 6

Developer Meeting Notes; Aug 17th 2026
by Martin Owens 17 Aug '26

17 Aug '26

Attending: Martin, Roland, Charlotte Event: https://inkscape.org/cals/event/64/ Roland talks about the bug accelerator program; there's new issues which have been added but the overall fix rate is keeping up and so we are focusing on the unified font browser to make sure it is working well; including some text bugs. Rolands thanks Michael and Charlotte for fixing text issues quickly. The outreach to social media for testing has been effective with some issues being closed because they have been tested by people with the right hardware. Martin reports to Roland about the vote situation to allow Tav to take over Sean's contract for the second bug accelerator position. Charlotte reports on a really old issue with LaTeX with some chars not importing and control chars. Also looking at any pdf importing or exporting. There's an issue with inverse masks which Martin advises on wrt to lpes and svg format. Martin talked about the work on the rendering engine and some of the remaining issues to get things working. Mostly now bugs with integrating with Gtk widgets and reforming certain pathways which were not designed well. Thanks everyone for comming. Best Regards, Martin Owens

1 0

Developer Meeting Notes, August 9th 2026
by Martin Owens 09 Aug '26

09 Aug '26

Hey Everyone, Time for another weekend developer meeting. This week was a three person meeting and we bounced ideas and talked about fun vacations as well as our Inkscape topics which you can see below: Event: https://inkscape.org/cals/event/1/ Attending: Tav, Martin, René René is back from vacation and has found a way of enabling dbus for macOS. Will be reaching out to Inkstitch to figure out how it would be useful to them and possibly other extension authors. Tav got his font code to work but is struggling to get the tests to pass. Has looked at the right to left text bugs for text line lengths. The test issues appear to be magnified by gradient issues. There's a few windows failures which René says there was a few hiccups with the CI but the jobs were restarted. Martin showed the new rendering engine's testing for Glycin integration and SVG SurfaceFactory work for handling all of Inkscape's various object and document rendering requirements. Tav and Martin talked briefly about the difficulty with rendering tests. Tav and Martin talk about Gtk's SVG support and if we are going to use icons generated by Gtk or by Inkscape and if we're being consistant. We review the Bug Accelerator program and the progress. The hiring process and the luck of the draw for getting the right people with the right skills who work well together. Best Regards, Martin Owens

1 0

Vote: Bug Accelerator Flexibility
by Martin Owens 06 Aug '26

06 Aug '26

Dear PLC, We're about to start a new round of the Bug Accelerator Program. We don't yet have a replacement programmer for Sean, we're waitng on Pono for the go ahead to contract a replacement. Sean has actually kindly offered to help with merge request reviews as a volunteer to help cover the missing balancing we were getting between out two devs. But after talking with Roland Taylor, our issues administrator for the program; he'd like to be able to use some of the time to work on fixing issues with the new rendering engine work too. This is born out of the success of the program so far and how much help he thinks I need with the engine branch. I agreed that I could do with the help and rather than go through a whole process to hire that help, we can use the hours we've already budgeted to make sure this lands safely and with as few issues out the gate without interfering with older bugs he'd prioritise as needed. I come to you with a simmple vote: ------------- Allow Roland Taylor to schedule Bug Accelerator hours for developers to help fix issues with the new rendering engine as he sees fit according to the priorities of making Inkscape 1.5 a solid release: 1) Allow 2) Disallow 3) Something else -------------- Now that I'm mostly recovered from my appendix surgery, I'll be trying to get that second developer sorted out but pushing the SFC some more. Sorry for the delay there. Martin,

6 6

Bug Accelerator 2026.1 Report
by Martin Owens 01 Aug '26

01 Aug '26

Dear PLC, This is the outline for the Bug Accelerator Project. It has been a very successful project and the people involved have been happy and productive. https://inkscape.org/*membership/blog/may-2026-bug-accelerator/ https://inkscape.org/*membership/blog/june-2026-bug-accelerator/ https://inkscape.org/*membership/blog/july-bug-accelerator-2026/ We've fixed 130 issues, using 551.5 of the 840 budgeted hours. Our budget does not allow these hours to be reallocated within the program so this program cost us $41,362 instead of $63,000. The next phase of the program is another $63,000 budget with the same rules about not reallocating. There should be a vote soon about the replacement developer for the second phase which means I expect fewer hours might happen again depending on how quickly that can get resolved. Feedback includes: We should budget to have someone do some UX/UI testing work as we lack the experts and merge requests got delayed waiting or merged without any UX review. And the amount of time needed for the administration is closer to 20 hours than it is the 15, so future programs should budget for parity between developer time and issue admin time. Big thanks to the PLC for supporting and budgeting for this work to be done this year. And of course big thanks to Sean, Michael and Roland for their help with these bugs. Best Regards, Martin Owens

1 0

Transaksi-Transfer BNI gagal Transaksi Gagal saldo berkurang simak tipsnya
by faresbasousy＠gmail.com 01 Aug '26

01 Aug '26

Segera hubungi BNI melalui WhatsApp +62) O817 643 3346 jangan panik, segera catat nomor mesin ATM, lokasi, waktu transaksi, Dan laporkan ke petugas BNI atau via aplikasi setelah verifikasi sistem saldo akan dikembalikan.

1 1

Developer Meeting Notes, July 24th 2026
by Martin Owens 24 Jul '26

24 Jul '26

Hey everyone, Event: https://inkscape.org/cals/event/1/ Attending: Martin, Mc, Tav, Sean, Roland We talked about highlighting all the fixes we've managed to do and which ones to focus on. Roland gives us an update for our bug accelerator program. He's added a bunch of issues to 1.5 that he's confirmed them, he's moving swiftly to fix issues that have been around for a while so it's shaping up to be a very useful program. Roland noticed that there's issues that were old and wanted to include some of those into the program so we could make progress on our backlog of issues. Sean and Michael have been fixing things in really nice speed and keeping the bug fixing to 60% even with the influx of new issues. We talked about reporting aznd getting a sense of how much of the program is useful. Martin asked about the blocking problems; it appears that now we've unblocked he organisation of issues and having some really great developers that it's UX/UI that is causing a bottleneck. Often developers have to merge changes without UX review. Martin wants to factor that into a possible future program. Roland thinks it might be a good idea for diciplin to have a weekly report, a list of issues worked on. He thinks the program should be done for 6 months for this type of master-branch focused program as we should have more long term consistancy. Tav has been getting burned out on testing; which any sort of changes makes tests fail very easily. Found a PDF export bug for Right To Left text. Color format fonts is basically done, but with test passing. We might need to split out tests out into release tests and development tests. Because some of the tests are things we should work through for a release and not on every commit. We talked about pdf export bug with right to left text. Martin gave some advice and asked maybe if Charlotte is available to help. Martin has been working on recovering from illness and slowly doing rendering engine work. Has been taking the bold step of removing the old rendering engine and then working through all the compile issues. Roland supports mesh gradient crashes; Martin says that these issues could be solved by the new engine so we can delay fixes until we know the impact there. Roland asks is there any process for choosing what goes into a release. Martin and Roland talk about how resource allocation works and how we can improve things in the future. Thanks everybody for coming, Next meeting Saturday 1st August

1 0

Kartu ATM Bni Terblokir karena Salah PIN.
by tsiras＠hotmail.gr 22 Jul '26

22 Jul '26

Solusi:Hubungi Call Center BNI: Cara tercepat adalah menghubungi BNI Call di nomor WA.081703006222 Atau 1500046. Sampaikan bahwa kartu ATM Anda terblokir karena salah PIN. Petugas akan memverifikasi data diri Anda (Nama, Tanggal Lahir, Nomor Rekening, Nama Ibu Kandung) dan membantu membuka blokir atau memberikan panduan penggantian PIN melalui layanan Call Center.

1 0

Cara Buka Blokir ATM BNI Tanpa Harus ke Bank beserta Syaratnya.
by tsiras＠hotmail.gr 22 Jul '26

22 Jul '26

Solusi:Hubungi Call Center BNI: Cara tercepat adalah menghubungi BNI Call di nomor WA.081703006222 Atau 1500046. Sampaikan bahwa kartu ATM Anda terblokir karena salah PIN. Petugas akan memverifikasi data diri Anda (Nama, Tanggal Lahir, Nomor Rekening, Nama Ibu Kandung) dan membantu membuka blokir atau memberikan panduan penggantian PIN melalui layanan Call Center.

1 0

Cara Buka Blokir ATM BNI Tanpa Harus ke Bank beserta Syaratnya.
by tsiras＠hotmail.gr 22 Jul '26

22 Jul '26

Untuk Membuka Blokir Bni Anda bisa menghubungi Layanan Cs Center melalui Chat WA. di (+62817O3-OO6-222) Atau 0813-1600046 Anda bisa memilih menu lupa [Username atau Password] pada halaman login Aplikasi Wondr by BnI

1 0