As I've had a few new followers, by way of #introduction:
- I'm a free and open source software developer
- I contribute to #gnome, typically in the core platform libraries
- I mostly toot about my History of the GNOME project podcast (every week, on Thursday) and about my #gundam plastic models
- I try to keep my software development ranting to the bird site, but it may end up spilling over here
Embloggeration happened: https://www.bassi.io/articles/2021/08/01/documenting-gnome-for-developers/ — In which I explain what's up with http://developer.gnome.org
The documentation for GTK3 and GLib is not designed for gi-docgen, so it'll take a little bit to get decent result without an outright port—which isn't planned, at the moment.
So, a little bit of patience goes a long way.
The GTK3 and GLib API references are now available on docs.gtk.org, alongside GTK4, Pango, and GdkPixbuf.
Once all of that is done, maybe I'll try to work on world peace. It'll likely be easier.
Additionally, I'm working on a CI template for libraries hosted on gitlab.gnome.org, to allow them to build and publish their API reference as part of their CI pipeline.
Separately, I'm looking into being able to install and browse locally the documentation of different versions of the #gnome SDK using Devhelp: https://gitlab.gnome.org/GNOME/devhelp/-/issues/48
The remaining task is publishing the API references for the libraries in the #gnome SDK—which we're already building for the org.gnome.Sdk.Docs run time extension: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/178
After fighting against library-web for a couple of months, I ended up switching to Sphinx for the new developer.gnome.org website—following the work done by the #gnome design team for the new HIG. Turns out it was a very good choice, because now we have a decent developer documentation website that we can easily improve, instead of an opaque Django monstrosity that we can't even test locally.
Day 4 of #GUADEC2021 is here and we’re starting the day with Lightning Talks! Join us in Track 1 at 15:00 UTC.
GUADEC starts today! Take a look at the full schedule and plan your day: https://events.gnome.org/event/9/timetable/#20210721
Make sure to register and check your email for the track links and access codes: https://events.gnome.org/event/9/registrations/34/
We’ll see you for the Welcome in Track 1 at 14:50 UTC!
Our #GUADEC2021 welcome party starts in just a few minutes in Track 1. Make sure to check your registration email for the access code - see you there!
Asking for financial help
Hey folks, it feels a bit rude to ask again, but I’m still struggling to find work right now and don’t have much money left. I don’t have enough to pay rent or bills right now. If you can spare it, I would really appreciate if you could help me out.
This summer I'm implementing the cool new screenshot UI in GNOME Shell. Here's my blog post about what I've done so far: https://imolodetskikh.wordpress.com/2021/06/29/gsoc-2021-gnome-shell-screenshot-ui/
If you cannot use Linux and you have to keep using Windows because of the accessibility stack, then it's sad, but you gotta do what you gotta do.
What you don't get to do is whine, and shit on somebody else's work just because people haven't figured out how to make things appear out of thin air without having to worry about food.
You don't get to be a child, throwing a temper tantrum because you didn't get what you want for free.
I guess I'm more appreciative of the people who filed bugs, who went through the guts of the screen reader to understand the undocumented behaviours it encodes, who submitted code, and helped out with the design. A lot of those who helped out are also users of the accessibility stack, by the way.
Geek, husband, lover, software developer, Londoner. Not necessarily in that order. | he/him | Opinions are my own
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!