glad to hear from you! :)
We noticed that the runner went offline like two weeks ago, but it was
certainly not inactive. While we’re shifting CI towards GitLab’s fleet,
I’d still put our MacStadium resources to good use. If there are any
left, that is :/
If you have any kind of emails or contact info, please send it my way.
Because MacStadium’s open source pages can only be found via Google
and all their links regarding their open source program are defunct.
To me it looks like they have shut it down, there is no way to register
at this time. I have already sent them an email about this, but the
email address they provided is a very general one and I’m not sure if
I’ll ever get a response that way. I hope I can salvage something.
Thank you for your time - for now, eMail is sufficient, but I’ll
reach out via chat if things get complicated.
> Am 27.10.2023 um 21:44 schrieb Patrick Storz <eduard.braun2(a)gmx.de>:
> Hi René,
> I'm fine, thanks for asking! Hope you're doing fine these days as well!
> I'm more than happy to share the credentials for MacStadium and (if you
> can make use of them) the scripts I used to set-up our runner instance.
> I'm afraid however that our server might already have been shut down due
> to inactivity (tbh I had assumed the project had long shifted to
> something else since I did not hear anything in a long time and
> therefore did not make an effort to reach out when MacStadium sent some
> mails recently), so maybe the easiest way is to re-register a FOSS account?
> Either way just let me know what you need from my end and I'm happy to
> help where I can (by mail is fine, but Chat works too, if you want to
> discuss synchronously at some point!)
> Am 22.10.2023 um 13:39 schrieb René de Hesselle:
>> Hi Patrick,
>> I hope you are well!
>> You are the single point of contact for MacStadium and our Windows runner and
>> we need to shift these responsibilities to someone who is more active in the
>> project. I hope you understand that this is by no means a personal critique
>> but just „business as usual“ that we need to take care of our resources.
>> I am taking over these responsibilities, so I need the MacStadium contact info
>> and credentials from you. With these I’m going to contact MacStadium and inform
>> them of the handover and have your personal info exchanged with mine where
>> I do not have encrypted email, I suggest that you put all the info and credentials
>> into a KeePass database (e.g. https://keepassxc.org/) and I’ll provide you my
>> mobile number where you can text me the password.
>> This initial email goes to the board list so people are informed, but do not
>> send your reply there (even if password protected, I do not feel comfortable with
>> this kind of exchange over a mailing list).
>> Looking forward to hearing from you,
I hope you are well!
You are the single point of contact for MacStadium and our Windows runner and
we need to shift these responsibilities to someone who is more active in the
project. I hope you understand that this is by no means a personal critique
but just „business as usual“ that we need to take care of our resources.
I am taking over these responsibilities, so I need the MacStadium contact info
and credentials from you. With these I’m going to contact MacStadium and inform
them of the handover and have your personal info exchanged with mine where
I do not have encrypted email, I suggest that you put all the info and credentials
into a KeePass database (e.g. https://keepassxc.org/) and I’ll provide you my
mobile number where you can text me the password.
This initial email goes to the board list so people are informed, but do not
send your reply there (even if password protected, I do not feel comfortable with
this kind of exchange over a mailing list).
Looking forward to hearing from you,
Dear Inkscape Community,
Here are the meeting notes from today's developer meeting:
Present: S.Ouchene, Martin, Tav, Marc, Krlr17, MikeKov, Jabier,
Next Meeting: October 28th
Tav has been working on the File Fialogs. When investigating the code
there appear to be so many classes which at first seem like it's too
many, but it's actually a permutation of open, save, windows, gtk. The
real problem is the mixed up way they're written. The new Gtk4 dialogs
all return Gio::File objects, and we should be using these more within
our own code to avoid the conversions between std::string and
Issues with the filter drop-down, keeping things in sync. Probably get
rid of the win32 dialogs. Martin suggests not spending too much time
trying to keep functionality which we will probably have to redesign
anyway or that would take a ton of work to support. Especially if it
involves hacking the Gtk widget tree in the dialog which is prone to
# Building and Infrastructure
Marc asked Rene why the macstatium runner doesn't any more, it's
blocking the 1.3.x branch. Rene wasn't aware of any issues, but to cope
with it we can migrate it to the normal windows runners. There are some
permissions issues to work out between Rene and Patrick to make sure
the machines are accessible by more people as Rene doesn't have access
to the machine
Checking out CI minutes. We're ok, but cutting it close with the amount
of spare minutes.
Marc wanted to ask about a specific merge request related to building
and CI. A short explanation about windows docker. Although this is
probably not available to GitLab, but worth checking out as downloads
of depedencies take the longest time in our builds and cutting this
part out would be very good.
Rene has been working on dependency updates. Looking into Gtk3 and 4
deps. Especially regarding libadwaita which is complicated to build
with deps that don't build yet on macOS. Working through the depedency
stack, for example cairo has made all their symbols private like
poppler. This is worth keeping in mind when we use private symbols.
Brief talk about the use of font config and freetype uses in inkscape.
Libjpeg-turbo claims to be much faster than regular jpeg library. It's
supposed to be compatible and more capable. Rene is interested because
jpeg is built really early. Mike says it has asembler instructions for
intel and wonders if this would work on macOS. Rene will make a test to
try it out.
# Next Version (1.3)
Martin talked about his 1.3.x backporting work, some basic requests for
how to tag merge requests for the backport and the target dates. All
work should be completed by the end of the month giving people enough
time to test 1.3.1rc1 (or similar).
Jabier has finished helping with the fixes for LPE crashes and offers
to help with the backporting process. But he has some worries about
possible regressions from his fixes in the LPE code and asks for help
testing the LPEs. Marc provides a crash issue and asks about if it's
# Color Refactoring
Martin has been working on doing the color refactoring. There are two
main ideas, the first is to make sure colors that use profiles are tied
to their profiles using a URIHandler, so we can see what objects are in
use and clean them up. We can also use this to make a list of used
colors for the palettes.
The second is to support different spaces and not convert everything to
sRGB in order to store the numbers in our code. An icc profile is not
required to specify a different color space, and we should be able to
output css4 like colors (for example hsl(...))
Marc shared an older merge request with his work on refactoring and
Martin said this would be useful to compare it all.
Mike asked for a location for color profiles and we talked breifly
about color profile data.
# Other Business
Mikekov has been helping with merge requests.
Jonthan has been waiting on feedback for the grants proposal. We'll be
meeting with pono on Monday after a two week gap in SFC meetings for
Big thanks to everyone who came to today's meeting.
You don't have to dress up to attend next week's developer meeting.
It's a Saturday and attendance is lower, so we might just have a social
or may just talk about 1.3, depending on the crowd.
Best Regards, Martin Owens
this is a vote to extend Daniel Boles' contract for another two months
(320 hours) and allocate additional budget at the request of the
- Daniel was originally hired for the GTK4 migration. This is making
good progress: as of now, the development team estimates that a first
version of Inkscape that builds with GTK4 will be available around the
time his current contract ends.
- By all accounts, the progress has been very steady, also including
general code cleanups which however did not distract him from his main
task. We were impressed by his knowledge, speed, and contribution
quality. By now, Daniel has 174 MRs merged.
- However, there are will be no more hours to spend for debugging,
fixing regressions, and upstream bugs. Daniel now has in-depth knowledge
of Inkscape's codebase as well as his GTK4 expertise. He would be a very
valuable asset going forward, so we feel it would be great to have him
available for some additional time.
- He has expressed interest to take on a permanent position somewhere
and in that case would finish the contract part-time. This might be an
even better deal for us, as he can take on a "consultant / technical
support" role, on an as-needed basis, e.g. fixing difficult bugs and
helping other contributors to move their work to GTK4. This is possible
under the terms of his (current) contract: it allows to submit invoices
over the course of a year, for a total of 320 hours. The same model
would apply to the extension of his contract.
- If he - which we currently don't expect - runs out of work related to
GTK4, there's enough other technical debt that he can work on.
a) Extend Daniel Boles' contract for another two months (320 hours)
under the same conditions as his previous contracts; the work items will
be (ordered by priority, as time permits)
- finishing the GTK4 migration,
- fix regressions in the GTK4 build of Inkscape, including upstream work,
- assist other contributors in updating their work for GTK4 if requested,
- work on other technical debt in the Inkscape codebase
and allocate $16,000 for his compensation.
b) Don't extend Daniel Boles' contract.
c) Other: ______
Thanks to those who were able to make today's develop meeting
Attending: Alezzacreative, Jonathan, Marc, Martin, Krlr17, Ishaan, Tav
Next Meeting: 12th October 2023
FOSSDem call for dev rooms. We need to decide if we're going to team up
with another project, the room is mostly focused on presentation and on
technical and development side. So we expect technical presentations
and would need to be able to fill the room for at least half a day.
Martin asked Marc to head up organing the effort so we have a main
person who can act as the driver and ask other projects.
Marc has some packaging stuff to take care of for Linux; a bunch of
issues to look at in the coming week.
Martin wanted to know about the backports task, Jonathan suggested to
do the testing for each of the issues to make sure it's all working.
One month to go before the release and is still the plan, Martin will
tell vectors so they have time.
Krlr17 reports that the windows builds are not available on the website
currently. Marc knows about the issue.
# Grant Prooposal
Jonathan reports back his meeting with pono about the grants funding
project; he has found that we wouldn't ever be able to a hybrid system
of allowing users to donate towards specific projects. But without that
part of the proposal it would still be possible to attract donations
for the global fund.
# Gtk4 Migration
Tav has been doing more Gtk4 stuff, trying to deal with some filename
issues. It's much more particular about conversing std string and
Glib::ustring classes. It's a bit tough as it's a windows specific
issue because filenames are stored on windows as UTF16 but UTF8 on
linux and mac.
Tav is working on a script to make Images Gtk4 compatible.
Daniel has been progressing on small items, still working on both his
Gtk4 branch and bringing things into master when they can be.
We reviewed the Gtk4 contract progress, the amount of money we're
spending down and the type of work being done within the terms of the
Martin has talked about the merge conflicts that are happening, mostly
he's holding onto large feature merge requests. Other developers might
be waiting for the Gtk4 work to complete before developing new things.
# Color Management System
Martin gave a talk about his CMS work, the user interface, color
picking the kinds of assumptions and workflows. And how to use color
seperation. Other developers were very helpful in confirming if these
designs and approaches are correct.
Thanks for reading!
Best Regards, Martin Owens
We have our monthly PLC status meeting this week at the regular time. Friday Oct 6th at 10am PST.
Unfortunately I'm going to be traveling out to see my son, and our schedule is up in the air, so I'm not sure I can lead it. Is there someone who could lead the meeting in my absence?