Stuff Michael Meeks is doing
|
|
This is my (in)activity log. You might like to visit
Collabora
Productivity a subsidiary of Collabora focusing on LibreOffice support and
services for whom I work.
Also if you have the time to read this sort of stuff you could enlighten
yourself by going to Unraveling Wittgenstein's net or if
you are feeling objectionable perhaps here.
Failing that, there are all manner of interesting things to read on
the LibreOffice Planet news
feed.
Older items:
2023: (
J
F
M
A
M
J
),
2022: (
J
F
M
A
M
J
J
A
S
O
N
D
),
2021,
2019,
2018,
2017,
2016,
2015,
2014,
2013,
2012,
2011,
2010,
2009,
2009,
2008,
2007,
2006,
2005,
2004,
2003,
2002,
2001,
2000,
1999,
legacy html
- Up early, sucked mail, off to London, hacked
on the train. Found the evil bonobo-activation bug
breaking gnome-meeting, down to the way gtk+ does
threading, again.
- Lunch, interesting meeting with the NetProject
people and some other guys. Off to the pub afterwards. Train
to Hove, to see the parents.
- Release team meeting as soon as I arrived home.
Tried to address the issue of the Gtk+ team not branching
and deep freezing for 2+ weeks before Gnome 2.0.0 like
everyone else is. Absolutely no contrition for promising a
new release, with only a single day of testing, having just
crammed a load of fixes from bugzilla in. Tragic that we
havn't carried the Gtk+ team with us and communicated our
strategy for producing a bug-free release.
- Lots of amusing arguments as to why gtk+
shouldn't co-operate:
- It's always been that way -
look out for this argument in the Women's
emancipation debate.
- We havn't had any problems yet -
ergo the Gtk+ team are somehow infallible in
a way the Gnome hackers are not. Consider whence
the delay of Gnome 2.0 stems.
- Gtk+ just has a different, but equally
good release process - which seems to involve
by admission, cramming misc. fixes in before
release, and a single day of testing.
- Just because gtk+ doesn't hard freeze, it
doesn't mean it's pointless Gnome doing it -
well true, we can hopefully be confidant that
the bugs will be in gtk+ not say eog, but that
helps precicely not at all to the end user whose
eog crashed.
- Just really, really irritated that the Gtk+ team
vacillate between being Gnome guys and not, as it suits them.
The irony is that gtk+ people typically wander around telling
people that gtk+ is the only useable, stable etc. bit, and
discouraging people from using / adopting Gnome.
- J' arrived, substantially better. Had a nice meal
in the evening, good to see the parents, bed early.
My content in this blog and associated images / data under
images/ and data/ directories are (usually)
created by me and (unless obviously labelled otherwise) are licensed under
the public domain, and/or if that doesn't float your boat a CC0
license. I encourage linking back (of course) to help people decide for
themselves, in context, in the battle for ideas, and I love fixes /
improvements / corrections by private mail.
In case it's not painfully obvious: the reflections reflected here are my
own; mine, all mine ! and don't reflect the views of Collabora, SUSE,
Novell, The Document Foundation, Spaghetti Hurlers (International),
or anyone else.
It's also important to realise that I'm not in on the Swedish Conspiracy.
Occasionally people ask for formal photos for conferences
or fun.
Michael Meeks (michael.meeks@collabora.com)
