11–20 of 269 posts
A bit off topic but what’s an easy to use FOSS WYSIWYG text processor for Linux? I’ve tried OpenOffice and I became frustrated.
> we find that whitespace changes are not just part of the commits that Apache Open Office has been receiving, whitespace changes make up a substantial amount of the commits added to the repository. wat.
Why on earth are we advocating for spamming the software foundation with emails about deprecating OpenOffice?
they're looking busy but are actually idle?
this smells like fraud but I ain't cooking so why do I speak of smells?
> we find that whitespace changes are not just part of the commits that Apache Open Office has been receiving, whitespace changes make up a substantial amount of the commits added to the repository. wat.
The trunk branch, the Bugzilla list, the OS/2 support, the user forums, the multi-hour build process, the XHTML 1.0 compliant badge on the https://www.openoffice.org/ homepage .....
Reminds me of the good old days.
I believe that the death blow which lead to the fork LibreOffice was the lack of trust in Oracle commitment to Open Office and open source in general, after Oracle acquired Sun Microsystems.
Sun indeed had largely reduced its involvement in the project in the last years, and there was the "Symphony incident" [1]. The death blow was when Oracle arrived, started the trial with Google over Java/Android, inherited MySQL and almost killed it, inherited OpenOffice and the future did not look bright anymore [2, in German]
[1] https://web.archive.org/web/20130927072255/https://lwn.net/A...
[2] https://web.archive.org/web/20131024094250/http://www.heise....
Surely if you don't like a project rather than writing open letters and whatnot, you fork it? That's the whole point of open source. That's how gcc project governance got fixed - egcs forked and made the improvements they wanted, won the argument and basically became the main branch. Some of the history is here https://softpanorama.org/People/Stallman/history_of_gcc_deve...
What is that supposed to mean?!
Surely if you don't like a project rather than writing open letters and whatnot, you fork it? That's the whole point of open source. That's how gcc project governance got fixed - egcs forked and made the improvements they wanted, won the argument and basically became the main branch. Some of the history is here https://softpanorama.org/People/Stallman/history_of_gcc_deve...
I mean, this happened a long long time ago. LibreOffice inherited approximately 100% of developer effort. The problem is that Apache is effectively lying about OpenOffice still being a thing, and trapping less-savvy users who aren't aware of this context into an office suite frozen in time in 2014.
Oracle just managed to kill a strong FLOSS brand. But, in some way, the LibreOffice fork energized the community.
Why on earth are we advocating for spamming the software foundation with emails about deprecating OpenOffice?
because someone is changing whitepsaces in the source code and pretending to maintain a stable/done piece of software. they're looking busy but are actually idle? this smells like fraud but I ain't cooking so why do I speak of smells?
> we find that whitespace changes are not just part of the commits that Apache Open Office has been receiving, whitespace changes make up a substantial amount of the commits added to the repository. wat.
It appears to be true. https://github.com/apache/openoffice/activity
Don't know if he's really trying to make the project seem active, or trying to score a certain number of commits, or if he's just really passionate about cleaning up that codebase all by himself.