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
- As I was heading to bed last night, I discovered
some wise advice from my (6 week) old daughter Myriam:
Lets hope she lives to see her patch get up-stream.
- Up, poked mail. Set about disabling the quick-start
feature in the up-stream build because it doesn't meet the
demanding standards of beaurocratic process; at least if it's
disabled, people can easily get / ship it, and we don't
apparently have a fork, and Sun gets to write the spec. /
suffer their own pain.
- Relieved on returning to my desk to find the result
of my query to the StarDivision library, a critical document
(note the much-thumbed aspect). Since there is a bug in some
OO.o printing interaction, it'll be good to read up on some of
the background rational, work out if the behavior is already
specified, where to adjust the specification, take some new
screenshots and so on.
Some may call this process unnecessary - but without
this specification (including pictures & big print) how
could User Experience, or QA understand what the feature
should do ? Or worse - imagine coming back to this area, and
not knowing if a bug was even a bug, and whether to fix it.
Remember: there is no process so effective that it
can't be improved by adding steps and stakeholders, and there
is nothing too trivial to be fully specified.
- Got on with some real hacking for once, fixed a
number of issues, cwsaddtask'd them, pasted the number &
description into the commit message (dutifully). If we add
enough process barriers, and consensus generation stages to
the OO.o development process, perhaps we will (eventually)
end up with something
easy to use.
- Fixed several other quick-starter issues, it
starts to look rather polished, marked CWS 'Ready for QA'.
Out to hire a dinner jacket for next week.
- Got an encouraging mail, from a pro-active Sun
employee that cares about improving this relationship -
wonderful. Call with Intel.
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)
