I use USB passthrough with my KVM guests fine on Fedora 19
Have Windows (XP and 7) VMs with full virtio drivers installed along with the SPICE agent etc etc
But did any version of MS Office actually use the ISO/IEC 29500:2008 standard in the end?
There was so much hand waving and so on - especially given the Office spec this was based on used the ECMA standard - and a few ethereal promises later on
But did they ever (so far as was possible given the appalling state of the spec) actually get to implementing what was agreed on?
This appears to be SOP for him throughout the comments...
It's sad really - seems a different Rob Weir from several years back and the OOXML ISO saga
I'm rapidly mentally filing him under the same categories I keep the likes of Florian Muller and Miguel de Icaza in...
If the LibreOffice guys were smart, they'd be contributing as many of their changes as possible to the upstream project,
Can we please get past calling AOO the upstream project of LO? This is like calling gorillas the upstream project of humans...
Yes they share a common ancestry but that is it at this point... sure some stuff can be transplanted from one to the other but there is no upstream/downstream relationship that one would usually understand that term as in the FOSS world (eg Fedora -> RHEL).
*blink*
Seriously Rob - go back up and check the comment thread
I will reiterate I am not the anonymous coward who made the 5% comment - I was never part of that argument or discussion
My comment in this chain of comments was merely replying to the first 'Palestrina' comment I saw going down the page to ask for your view on the negative light from that blog and for curiosity on why you use such a different nick here than elsewhere
I understand you are feeling under pressure and that there is a general negative stance towards Apache Open Office for many reasons but there is no need to be on such an offensive posture
So before you accuse me of changing the subject for a third time let me remind you I am not that anonymous coward
Oh and I had a look at ohloh in more detail and I do see it hitting trunk
Rob I think you have lost track of who your are replying to and why
There was no ad hominem attack on my side just a curiosity as to why you choose a nick that is so far different from your usual (reddit, lwn, etc) given this is another social network and if you had balance to bring that blog post which paints a rather negative light...
I never made that 5% claim - that was an anonymous coward and I stay logged in here... Incidentally I disagree with your position that no one ever benefits from the small commits... just as DNA changes very slowly over generations those do add up to larger changes and a clean code base being nicer to work on and get started with means a feasibly larger contribution from people in future.
Also does it definitely only count 'trunk' over ah ohloh? It says there are 23 million LOC in AOO but only 7 million in LO
Rob why do you go by the nick Palestrina here rather than the usual rcweir you use elsewhere?
Interesting blog post I came across just now - care to comment?
The point is that without the Apache guys there wouldn't be a sidebar in either project. LibreOffice has done a lot of stuff but none if it is as visible as the Apache guys have done.
This is nonsense... The sidebar stuff wasn't written by anyone in Apache - it was IBM code from the symphony project/fork donated to Apache that was then merged into AOO and merged (with small improvements like resizing) into LO as well...
As for the not visible bit have a look through the new features and fixes in 4.0 and 4.1.
There's a lot of nice new content with visible useful features such as chart import and export as both ODC and images in calc, presentation mode in Impress, visio import in Draw (that was LO 3.5), huge reduction of java dependencies, refactor how calc views cells internally for much faster performance on large spreadsheets, MS Publisher import, and the list goes on
As for letting the code speak for itself
Too bad users use the product and don't gain direct productivity merely from looking at Ohloh stats.
But the stats do paint the picture of the direct benefit to the users...
See all those deleted lines? That's code clean up that is... That means less bugs and easier to maintain and also easier for new people to help with when they get an itch they need to scratch.
It shows that the average AOO contributor makes twice the number of commits as the average LO contributor. And the average AOO commit is far more significant, touching twice the number of files as the average LO commit. Net it out and the average AOO contributor is 4x as productive compared to the average LO contributor!
Way to twist the statistics...
In a way what you say is absolutely true but then that misses the mark but quite an impressive amount. It's almost to the point I feel a need to call you out on this as being literally true so no one can call you a liar but that truth being represented in such a way as to mask the real situation.
The recent libreoffice blog post covers the the growth of committers and includes a brief discussion of "the long tail" with a large number of people in the community submitting small fixes here and there because they can and to scratch a small itch... this is not happening on the AOO code base.
To me that shows a healthier development community of in the LO camp.
Put it this way if a project has 100 people each committing to 2 files over a code base and another project which had 2 people committing to 100 files over another fork which would you say was "more productive" and would you equate that with project healthiness?
Well since they laud the new sidebar so much for better use of widescreen monitors they should love the fact that LibreOffice will have it within a few days...
4.1 is due in a matter of days which has an improved sidebar that's resizeable and not just a static part of the screen.
I really question what the point of AOO is at this juncture given that LO is clearly the more active project and has two years of code clean up and development over AOO due to the way Oracle let it stagnate for so long.
If you want to try 4.1 now it is on the pre-releases page and it's the final RC there
Never test for an error condition you don't know how to handle. -- Steinbach