July 2026 - Inkscape Board of Directors

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

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

Solusi tarik tunai di ATM Bank BNI uang tidak keluar tapi Saldo berkurang? Berikut solusinya
by mylife196＠gmail.com 19 Jul '26

19 Jul '26

Jika tarik tunai di ATM BNi gagal (uang tidak keluar) saldo terpotong, hubungi BNi melalui WhatsApp +(62/-08136034270) atau (0813-7090358) jangan panik, segera catat nomor mesin ATM, lokasi, waktu transaksi, Dan laporkan ke officer BNi atau via aplikasi setelah verifikasi sistem saldo akan dikembalikan.

1 0

Solusi tarik tunai di ATM Bank BNI uang tidak keluar tapi Saldo berkurang? Berikut solusinya
by mylife196＠gmail.com 19 Jul '26

19 Jul '26

Jika tarik tunai di ATM BNi gagal (uang tidak keluar) saldo terpotong, hubungi BNi melalui WhatsApp +(62/-08136034270) atau (0813-7090358) jangan panik, segera catat nomor mesin ATM, lokasi, waktu transaksi, Dan laporkan ke officer BNi atau via aplikasi setelah verifikasi sistem saldo akan dikembalikan.

1 0

BNI Tarik Uang di ATM Gagal Tapi Saldo Berkurang, Begini Solusinya
by mylife196＠gmail.com 19 Jul '26

19 Jul '26

Jika tarik tunai di ATM BNi gagal (uang tidak keluar) saldo terpotong, hubungi BNi melalui WhatsApp +(62/-08136034270) atau (0813-7090358) jangan panik, segera catat nomor mesin ATM, lokasi, waktu transaksi, Dan laporkan ke officer BNi atau via aplikasi setelah verifikasi sistem saldo akan dikembalikan.

1 0

Cara Mengatasi Transaksi BNI Transfer Gagal Tetapi Saldo Terpotong
by mylife196＠gmail.com 19 Jul '26

19 Jul '26

Jika transaksi BNI gagal namun saldo berkurang, hubungi layanan Call Center BNI: melalui WhatsApp ("08136034270") atau telepon 1500046. Jangan panik, segera simpan bukti transaksi (struk/screenshot) dan cek riwayat transaksi.

1 0

Jika Transaksi B𝖭i gagal transfer namun saldo berkurang? langkah ini yang harus dilakukan
by mylife196＠gmail.com 19 Jul '26

19 Jul '26

Jika tarik tunai di ATM BNi gagal (uang tidak keluar) saldo terpotong, hubungi BNi melalui WhatsApp +(62/-08136034270) atau (0813-7090358) jangan panik, segera catat nomor mesin ATM, lokasi, waktu transaksi, Dan laporkan ke officer BNi atau via aplikasi setelah verifikasi sistem saldo akan dikembalikan.

1 0