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
- Amused to see the unconvincing Do Apache projects come
with too much overhead?
rebuttal. My view is based only on the perception that the OO.o
project is strongly influenced by Apache - and, on that basis the answer
would be an unequivocal yes. All this tremendous startup costs
in establishing community roles & governance policies is IMHO
just junk. The excessive-legal-perscriptive view that trust, relationship
and coding are an insufficient basis for 'community' and that instead
formalised written process, with assigned 'roles' is the basis is IMHO
comical. No start-up charity would freeze it's org chart before
it hires anyone. The real communities I've been privileged to work
with are not measured in statutes & governance process, but great
inter-developer relationships, a lack of artificial boundaries, and
actual code production. I fear this stifling beaurocratic approach to
'community' development is unhelpful & unhealthy, will cause bogus
'communities' to be instantiated, and create disillusionment with companies
testing out OpenSource. This heavy governance system may work well for a
10 year old project like Apache - but foisting that on start-ups
[ as some for-hire 'community' consultancies would recommend ] seems
unhelpful in the extreme. If you have community-development money to
spend far better to spend it on flights & beer, get contributors
together, build trust, relationship, co-operation, excitement among the
developers that do real work instead; and that requires hiring no special
consultants either.
- Poked at E-mail; apparently the KDE lists use the Reply-To:
mangling & love it acording to Lubos; - possibly not as clear cut
as I thought; still questing for some vestigal merit in this approach
though.
- More -Bdirect stuff - generating nice .direct sections using
the stored/imported linkonce data, poking at the executable foo.
- Out for a run in the evening, while the babes watched a DVD,
dinner with the wife. Poked at this & that - J. out to cell group.
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)
