Matthias Seidel wrote:
I think it would be a good idea to upgrade Serf in our builds.
What about the others (real developers)? ;-)
Years ago, we had to avoid upgrading Serf in 4.1.x as Serf had started
to require SCons for the build and we didn't want to introduce yet
another build system
This is not necessarily a bug, but I'd like to check on this: on
Linux-64 (I haven't tried on other systems), if you are editing a file
in Writer you'll get two different toolbar icons in 4.1.5 and 4.1.6.
Comparison screenshot: https://imgur.com/a/wtNhT9k
In short:
- 4.1.5 (left): the Writer
Peter Kovacs wrote:
I am just saying a 4.1.7 release has nothing to do with the efforts we
have to organize for 4.2.0.
OK, got it! Let's work together on finishing 4.1.6 and then we will have
plenty of time for discussing about the next releases.
Regards,
Andrea.
Mechtilde wrote:
as already wrote, I try to work on translation update.
Now I could get an actual *.sdf file from source code.
Thanks, Mechtilde! Could you please start from my notes at
https://s.apache.org/Dukc and copy them to a wiki page (or, if you don't
like wiki, to a text file to be
Peter Kovacs wrote:
I do not see your issue. Our release team works much faster then the dev
team progresses on 4.2.0.
There is a major difference between a 4.1.x and a new release like
4.2.0: for 4.2.0 we need the entire community, not only what you call
the "release team" and developers
On 12/11/2018 Matthias Seidel wrote:
Just to be clear, I wasn't thinking about taking the dictionary directly
from Opentaal.org but rather how we get the updated dictionary uploaded
to SourceForge.
Yes, this was clear. We simply mirror it on the Extensions site (not
SourceForge per se, as we
On 12/11/2018 Patricia Shanahan wrote:
The way I see it, we should be keeping 4.1.x for security fixes that
cannot wait until 4.2.0. As such, we may need to decide to release 4.1.7
at any time.
Sure, this is obvious. Thanks for pointing it out and of course I agree
with it. I was commenting
On 11/11/2018 Peter Kovacs wrote:
I suggest that we start right away with an Parallel development of 4.1.7
Release branch.
First, we'll have to officially release and announce 4.1.6.
Then energy should really go to 4.2.0. Only if there are any outstanding
bugs or regressions we should
Matthias Seidel wrote:
https://extensions.openoffice.org/en/project/dutch-spelling-and-hyphenation-dictionary
version 200g was also taken from Opentaal.org and uploaded to SourceForge.
Since users complain about problems with this version I would really
like to bundle the updated dictionary in
Mechtilde wrote:
My first problem is to extract an actual SDF Template ...
I followed the intructions in the wiki and the slides from FOSDEM 2018.
Please find more comprehensive information here:
https://s.apache.org/Dukc
This is a set of messages I sent to the dev list with everything I
Peter Kovacs wrote:
openoffice.org3.4-freedesktop-menus-3.4-9593.noarch.rpm
openoffice.org3.4-redhat-menus-3.4-9593.noarch.rpm
openoffice.org3.4-mandriva-menus-3.4-9593.noarch.rpm
openoffice.org3.4-suse-menus-3.4-9593.noarch.rpm
These are highly experimental test versions. Even when we agreed
Matthias Seidel wrote:
There is already an (empty) update feed for 4.1.6. AOO 4.1.6 should just
report it is "up to date" (like 4.2.0 does).
Yes, but unless we can monitor it on the server side this is only
partial information: I mean, if 4.1.6-RC1 was set, by some mistake, to
use the same
On 29/10/2018 Matthias Seidel wrote:
Am 28.10.18 um 22:53 schrieb Andrea Pescetti:
https://bz.apache.org/ooo/show_bug.cgi?id=127789 ...
As I wrote in the issue, this could be an issue just with the ASF
network configuration and it may not require a fix at all.
This is also my guess.
Just
Peter Kovacs wrote:
I extend the deadline until Saturday Morning CET.
Thanks! I've completed my tests tonight.
The Release Candidate 1 for 4.1.6 has passed my tests.
[X] yes / +1 (binding)
I have tested
Linux Release 64 bit
[X] source / binding
[X] binary
Further details: I've
On 06/11/2018 Marcus wrote:
Why no own builds?
At the moment I'm very busy with my day job and just recently I got back
a repaired laptop. So, had not yet the time to update my build system
Since I see that we don't have many people who built from source yet and
the vote deadline is
Peter Kovacs wrote:
So now the rules state I should sign all artifacts. Others may
concatenate their signature if they want. Do we follow this?
No, you need to sign only three files, the three source files. And you
should remove the existing three corresponding .asc files since multiple
Keith N. McKenna wrote:
I just checked the user list on the pootle server and indeed there was
no e-mail address associated with your account. I added your @apache.org
e-mail address to the account. This should allow you to log in with your
committer credentials. If you still have problems
Mechtilde wrote:
for doing some Improvments to translations I started with a login to
https://translate.apache.org.
then I choose "Reset my password" with the apache E-Mail adress and with
my normal E-Mail adress. With both adresses I get the message, "this
E-Mail adress isn't asigned to a user
Keith N. McKenna wrote:
In his second vote announcement Peter also specified that to cast a
non-binding vote one still had to download and compile the source on
ones own machine and then test that binary. This is far over and above
anything that has ever been required for a non-binding vote.
On 31/10/2018 Marcus wrote:
To make it an official vote I miss the following information:
- What exactly do we vote for (link to the source and binaries)?
Yes please, let's try to be reasonably serious about releases: due to
legal implications (among other things), there are some formalities
I've taken a look at the few 4.1.6 accepted blockers that are still
open. Don already discussed the ones affecting libraries.
I'm especially interested in this one (server error when looking for
updates)
https://bz.apache.org/ooo/show_bug.cgi?id=127789
that should be investigated properly
Jim Jagielski wrote:
I went ahead and tagged AOO-4.1.6RC1. If it passes then we can copy that tag to
the GA.
We don't tag RCs normally, only releases (and we thus do it AFTER the
vote has passed). No problem, it just means that if the vote passes the
tag will be renamed (moved instead of
Marcus wrote:
Am 25.10.2018 um 12:48 schrieb Peter kovacs:
All I can add it is fields to enter on the booth registration.
hm, OK.
For the social media link, our project page could be helpful - as
Matthias stated:
https://openoffice.apache.org/social.html
I assume the form we are talking
On 23/10/2018 Matthias Seidel wrote:
Am 23.10.18 um 13:06 schrieb Jim Jagielski:
r1844555 was the SVN version of HEAD at the time of the email.
Yes, and it increases by the time of writing...
So it gives no information about what revision the RC should be build upon?
This has always been an
Matthias Seidel wrote:
Am 20.10.18 um 22:18 schrieb Andrea Pescetti:
The Release Candidate will have to be called by Peter, but it looks
like we are not far...
Next week Marco Pinto will probably update the English dictionary.
Maybe we are ready until then?
We never depended on a dictionary
Jim Jagielski wrote:
Which langs would people like? I'll upload to my Apache people space.
Italian please. And thanks to both you and Matthias for providing the
builds.
The Release Candidate will have to be called by Peter, but it looks like
we are not far...
Regards,
Andrea.
Pedro Lino wrote:
I could try to build on Linux. My SSD has 76GB free. Is this space enough?
Sure it is. With 60GB you can build all languages. For a test build
(English only) you won't need more than 10GB.
How long will it take to build AOO on a Intel® Core™ i5-2520M CPU @ 2.50GHz × 4
Howard Cary Morris wrote:
I want the HTML5 look identical to printed code. I will have additional
references to understand the code.
I see many mixed ideas in this conversations. Let me give you some
pointers, and sorry for being late at this.
Start here:
On 06/09/2018 Peter kovacs wrote:
Hi Andrea,
Can you specify at least one task? So Sandro can make a plan.
It took a while, but here I am with a task.
One of the many things that would be nice to have is a new skin (i.e.,
graphical theme) for our MWiki
On 11/10/2018 Andrea Pescetti wrote:
While I haven't received any feedback from FOSDEM organizers yet (the
two contact addresses I had given were mine and Peter's), I am not
seeing the Open Document Editors devroom listed at
https://fosdem.org/2019/schedule/
The organizers confirmed
orm you accordingly via
email.
Title: Apache OpenOffice [or: joint "ODF Editors" devroom]
Coordinator: Andrea Pescetti
Coordinator email: pescetti@...
Secondary contact: Peter Kovacs
Secondary email: petko@...
Description:
Apache OpenOffice, formerly known as OpenOffice.org, is one o
Peter Kovacs wrote:
Well it turns out the Apache CMS system we use for our download side is
unmaintained and unsupported. ...
It is something we should address mid term.
For the main openoffice.org site we could simply go back to static HTML
(plus SSI for the limited usage we are making of
Peter kovacs wrote:
If you see something on our wiki-pages.
You can decide on yourself. There is no real command structure here.
If you need a user for editing the wiki, just write a request here.
Right. Sandro, if we haven't created a MWiki account for you yet, please
ask here. Otherwise,
On 09/09/2018 Matthias Seidel wrote:
But I know that Andrea wanted to ask for a blocker, but we hadn't
enabled the flag at that time.
It worked now: https://bz.apache.org/ooo/show_bug.cgi?id=127712
Regards,
Andrea.
-
To
Matthias Seidel wrote:
How about this one:
https://bz.apache.org/ooo/show_bug.cgi?id=126736
It fixes a typo in the build process.
This one has zero impact for users and, if 4.1.6 was just a maintenance
release and we had regular 4.x major releases, it wouldn't make sense to
include fixes
Pedro Lino wrote:
So this means that the correct Distro information needs to be extracted from
somewhere else.
All we have is the user agent. And a user agent like your example:
"Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0"
bears no indication of the distribution,
Peter kovacs wrote:
Doh! *facepalm* Where did I take that from, ...
Okay, Drupal is still PHP.
The PHP applications we, as a project, have are:
1. http://forum.openoffice.org/ phpBB
2. http://wiki.openoffice.org/ MediaWiki
3. http://extensions.openoffice.org/ (and Templates) Drupal
For #1
On 28/08/2018 FR web forum wrote:
https://bz.apache.org/ooo/show_bug.cgi?id=9392
This patch could be embedded in this release?
I'm not the release manager, so this is just a personal opinion. The
patch swaps the behaviour of two keys (Backspace and Del) and thus
shouldn't be applied to a
Matthias Seidel wrote:
Dictionary updates are no problem and done routinely in every release.
Sure, no problem.
But I have yet to find the script that updates the version number. ;-)
Here it is:
https://bz.apache.org/ooo/show_bug.cgi?id=127639
And its destination if of course somewhere
Matthias Seidel wrote:
I could try to create the branch. Just to make sure:
svn copy https://svn.apache.org/repos/asf/openoffice/branches/AOO415/
https://svn.apache.org/repos/asf/openoffice/branches/AOO416/ -m "Branch
off 4.1.6 from HEAD of 4.1.5"
is enough? Or is -r HEAD needed?
Yes, that
Matthias Seidel wrote:
Am 19.08.2018 um 15:13 schrieb Andrea Pescetti:
It does not create branches. So one would, for example, create the
AOO416 branch with an svn copy operation form AOO415, then run the
script locally to update constants and other settings.
Is there a planned date to create
Peter kovacs wrote:
Maybe in fisheye (don't have the link at hand) the history can be looked up?
Why? The icon Donald sent is our current one, right?
I mean, it's the orb icon (blu circle, white gulls) as shown in
http://www.openoffice.org/images/AOO_logos/AOO4_website_logo.png
and it is our
Peter Kovacs wrote:
However I am not able to access the svn. I can do that with my password
right or do I need to use a passkey?
Password authentication is fine. It's unlikely that your user is banned:
often you will be able to reset your password at id.apache.org
The KEYS file is described
Matthias Seidel wrote:
Just for better understanding:
Does the script create a new branch incl. all needed changes or do we
have to branch first and then run the script?
It does not create branches. So one would, for example, create the
AOO416 branch with an svn copy operation form AOO415,
Matthias Seidel ha scritto:
Am 17.08.2018 um 07:51 schrieb Peter kovacs:
I have managed to make time on the next weekend's. So I volunteer for Release
Manager. Hope it helps to get this from the table.
If there would be a role as Co-Release Manager, I would volunteer for it.
That said, I
On 10/08/2018 Matthias Seidel wrote:
Am 10.08.2018 um 00:13 schrieb Keith N. McKenna:
On 8/9/2018 11:55 AM, Matthias Seidel wrote:
I am wondering if we could include it in OpenOffice?
[1] https://www.ibm.com/plex/
My question would be like Marcus's; What purpose are we serving by
adding it
Jörg Schmidt wrote:
But I was surprised that apparently not even a single mirror mirrors the
üpenoffice/ directory. In the past there were many mirors offering OOo, I guess
at least 20.
In theory we have a mechanism for it:
http://www.apache.org/dyn/aoo-closer.cgi
but I don't think this is
On 21/07/2018 Jörg Schmidt wrote:
Is there currently any alternative to Sourceforge for downloading?
(Because: The Apache mirror should not be used.)
ASF mirrors, with their current capabilities, should not be used for
downloads of the latest release due to disk space and bandwidth issues:
Pedro Lino wrote:
I have a login for site https://cwiki.apache.org but the pages there seem
really empty
https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home
On the other hand the cwiki login data won't work on the wikitest.
This is expected.
CWiki =
Yakov Reztsov wrote:
I think that error creating thumbnail is problem of setup new MediaWiki server
for path to ImageMagic or path to thumbnail folder.
Possibly. Or it could be that Aleksey's images are relatively new. The
setup process took several weeks, so not all components are
Алексей Евгеньевич Харламенков wrote:
Where can I continue to work: on a test wiki or in an old wiki?
Work can continue normally on the "old" MWiki at
https://wiki.openoffice.org ; at a certain point, when we schedule
migration, we will announce a 1-2 days "freeze" for the MWiki while we
Our MWiki needs to be moved to a new server since Infra is replacing old
hardware. It took some work and some help from Infra, but a test
instance is now available on a new server at
https://wikitest.openoffice.org
Please test it as follows:
- if you don't have an account, just browse the
On 03/07/2018 Jim Jagielski wrote:
+1. I'll start on a CentOS7 VM.
Makes sense to me. So our indication for the Release Notes would be
something like "OpenOffice 4.2.0 is built on CentOS 7 and is expected to
run on Linux-based systems released in YEAR or later (CentOS 7, Ubuntu
XYZ...)".
Hagar Delest wrote:
The Chinese forum was removed 2 years ago and the link is still on the
landing page (https://forum.openoffice.org/), leading to a 404 error.
Could someone either remove the link or change the page to something
saying the forum is closed?
Done. Removed from
On 01/06/2018 Lukas Häusermann wrote:
The System is a KVM VM running on Ubuntu 16:04.
Specs:
1x vCPU
4GB RAM
60GB Diskspace
Does this help so far?
Thanks, this gives us some useful data in case we want to replace the
service.
Just in case, would the VM disk image be available in case we
On 30/05/2018 Lukas Häusermann wrote:
I would like to inform you that we (Adfinis SyGroup AG) plan to
shutdown the opengrok system (http://opengrok.adfinis-sygroup.org/sourc
e) as we cannot afford to maintain the the system further.
Shutdown will be on 2018-06-20.
Thanks for maintaining it so
Matthias Seidel wrote:
Am 01.05.2018 um 00:17 schrieb Dave Brondsema:
SourceForge has Drupal admin login credentials for historical reasons, so
earlier when you sent this mail I checked that extension and it wasn't
"published".
Whatever happened... First the page was accessible, then access
Peter Kovacs wrote:> Currently you have to download the extention in
order to see the license.
With OO 3.3 I have seen that you have to add the license in the extention
description.
You have to distinguish between an extension and a release. The same
extension can have different releases
Matthias Seidel wrote:
Am 23.04.2018 um 00:15 schrieb Andrea Pescetti:
Correct. Jim's builds (not only releases) are done with CentOS 6, so
they will work on CentOS 6 too, and Kay can try with the latest link
you gave. Only buildbots builds won't.
And that's the problem, even Jim's build won't
Matthias Seidel wrote:
The problem may be that the buildbot is running on Ubuntu 14.04.
Normally we build releases on CentOS (5 for 4.1.x, 6 for 4.2.x).
That's the issue indeed. CentOS 6 has glibc 2.12, Ubuntu 12.04 has 2.15,
Ubuntu 14.04 has 2.19.
Your errors show that glibc >= 2.15 is
Jim Jagielski wrote:
We then svn copy trunk to a AOO420 branch and
start focusing on getting a 4.2.0 GA release out.
On my side, this looks OK but localization is still lagging behind.
Unless we deem it acceptable to get 4.2.0 out in English only (or with a
significant percentage of English
On 31/03/2018 Marcus wrote:
Am 30.03.2018 um 18:45 schrieb Matthias Seidel:
My question is, what impact does it have on Pootle synchronization if
I also delete the unused string from:
/main/instsetoo_native/inc_openoffice/windows/msi_languages
I've no clue what will happen with Pootle. Maybe
Kay Schenk wrote:
This particular requirement is a source of confusion for me.
I'm pretty sure glib 2.5, is some internal RedHat (CentOS5) version
numbering scheme. This is really glibc, and we need to accurately
specify the minimal version we will be requiring.
No they are two different
Rory O'Farrell wrote:
Centos may be a good distro for building OO, but it is hardly the most widely
used for daily work
How popular a system is is not very relevant.
What matters is: we build OpenOffice on an "old" system since this makes
it compatible with more recent systems. If we built
Dave Brondsema wrote:
On 3/15/18 6:57 PM, Andrea Pescetti wrote:
For example, https://t.co/sZTK7wwASJ and https://t.co/HV0HdhJLGR (listed there)
are still broken. And others from that list are broken too. But I guess it's
just a matter of moving them to the right place now.
The other
Dave Fisher wrote:
We have a record here: https://www.openhub.net/p?query=openoffice=users
Please have a look as I think we should make some changes.
The page https://www.openhub.net/p/openoffice is full of inaccuracies
and shows that they are not even able to maintain data: they report our
Dave Brondsema wrote:
On 3/14/18 6:08 PM, Andrea Pescetti wrote:
Currently, downloads of recent releases of the extensions (not only the English
dictionary, even if it is the most prominent) are broken. ...
https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice
Damjan Jovanovic wrote:
GStreamer 1.0.0 requires glib 2.32.0.
CentOS 6 ships with glib (package name: glib2) 2.28 as per
http://mirror.centos.org/centos/6/os/x86_64/Packages/
So this is indeed an issue: we would need a distribution that ships with
glib >= 2.32 (without considering other
Martin Groenescheij wrote:
I forward your mail to the developers list:
Error message from Sourceforge: The
"/17102/39/dict-en-20..dict-en-20180301.oxt" file could not be found or
is not available. Please select another file.
This has already been discussed, for example, here (link to dev
Jim Jagielski wrote:
Either we make gstreamer 1.0 an external download dependency,
so we can continue to build on CentOS6, or else we decide that
we switch to Ubuntu as our "official" build platform for our
community releases.
Can we define the problem better?
I assume the gstreamer license
Matthias Seidel wrote:
Just for the record, the release/tag for AOO 4.1.5 is missing on GitHub:
https://github.com/apache/openoffice/releases
@Jim: Can you add it like you did for 4.1.4?
We shouldn't tag in Github. Github does not exist as an official repository.
Tags go here:
Peter Kovacs wrote:
We could always write what has happend in the Project. I think the
different perspective could help a little the cause.
For the first Community Report we could start off with the 4.2.0 beta
plan, and what we want to do. What we hope for and talk about some
highlights like
Peter Kovacs wrote:
can someone delete the page
https://cwiki.apache.org/confluence/display/OOOUSERS/new+multimedia+Backend
Now you can. I've just given you permission to delete pages.
Wouldn't a blog post at https://blogs.apache.org/OOo/ with the good news
be more useful (at the present
On 08/03/2018 Marcus wrote:
However, for me "Beta" sounds like from the 1990s. Maybe we can find
another term and try to be a bit more modern with "Preview Release",
"Early Access" or something else.
I'm not much interested in how outdated the name "Beta" looks, but it
looks wrong.
Andrea Pescetti wrote:
Thanks! Sites are indeed back and pages are shown correctly. Still,
users are reporting that they cannot download extensions so I guess this
is not fixed yet, right? I mean, the pages are displayed but the files
are not available for download yet.
Answering myself
Dave Brondsema wrote:
https://templates.openoffice.org/ and https://extensions.openoffice.org/ are
back up. Thanks for your patience.
Thanks! Sites are indeed back and pages are shown correctly. Still,
users are reporting that they cannot download extensions so I guess this
is not fixed
As discussed in https://s.apache.org/sHGE we can't do a clean build
while SourceForge is down, to to the fact that oooextras.mirror (where
we keep some libraries) is unreachable.
I've created a temporary mirror with the files I had locally and with
some more files (especially extensions) that
Hagar Delest wrote:
For the record, there is a google custom search field on the forum
landing page: https://forum.openoffice.org/
It now returns:
Unauthorized access to internal API. Please refer to
https://support.google.com/customsearch/answer/4542055
->
Matthias Seidel wrote:
Am 03.03.2018 um 18:00 schrieb Andrea Pescetti:
I'm trying to do a clean build of trunk and I'm stuck too (I do have a
local cache, but it has the AOO415 dependencies only). Does anyone
have a copy of ext_sources for trunk configured with --enable-category-b?
I can send
On 02/03/2018 Matthias Seidel wrote:
The buildbots are unable to do their work because SourceForge is
unreachable...
I'm trying to do a clean build of trunk and I'm stuck too (I do have a
local cache, but it has the AOO415 dependencies only). Does anyone have
a copy of ext_sources for trunk
Dave Brondsema wrote:
On 3/1/18 12:08 PM, Andrea Pescetti wrote:
I currently get this on https://extensions.openoffice.org/ for the record:
"Sourceforge project sites are currently under maintenance. Please check back
later. We thank you for your patience."
Correct. We will be pr
FR web forum wrote:
Unable to connect :-(
http://status.apache.org says that all is ok
Extensions is not hosted at Apache. It is hosted by SourceForge, and
apparently they are having issues:
https://twitter.com/sfnet_ops
I currently get this on https://extensions.openoffice.org/ for the
Matthias Seidel wrote:
Lately here have been some posts about AOO "Check for Updates..."
showing an error (Checking for an update failed).
Normally the second attempt is successful. (Indeed it is *every* second
attempt for me)
I can't make it fail within OpenOffice. From my network I always
CCing Dave since it is clear that SourceForge is having some issues with
the OpenOffice downloads.
I didn't manage to reproduce the problem (I made some attempts with
different files and downloads always started correctly for me), but we
are seeing a regular stream of reports from users who
Peter Kovacs wrote:
We had a discussion about special small update versions for Windows,
some time ago.
We had experimented with patches some years ago, but never released them
officially. Everything is documented at
A bug has been reported on the Italian mailing list but I'd like to get
verification by a Mac user.
To reproduce:
1. Be on High Sierra (but it would be useful to check with other
versions too; the reporter says everything worked correctly, with
OpenOffice 4.1.5, before upgrading to High
On 12/02/2018 Peter Kovacs wrote:
Steve here is volunteering to help. See below.
Can someone guide him further?
Sure. For documentation see here: https://s.apache.org/bCco - help
welcome, and refer to Keith's mail there for some pointers.
Also I am not sure about what the exact situation
Marcus wrote:
@all:
What do you think is the first topic we should start with?
I think the only reasonable way forward is that Peter chooses one of the
many available tasks (digital signatures? Java 9 support? MSVC update?
.docx export? you name it) and experiments the workflow limited to
On 11/02/2018 Pedro Lino wrote:
dpkg: error processing archive openoffice-core01_4.2.0-1_amd64.deb (--install):
trying to overwrite '/opt/openoffice4/program/gconfbe1.uno.so', which is also
in package openoffice-gnome-integration 4.1.5-1
Errors were encountered while processing:
Peter Kovacs wrote:
I would like to propose that we apply Agile development methods as
much as we can.
Well, "as much as we can" is the key here. OpenOffice is as agile as an
elephant. A lot of us use Agile in their daily work activities, and
maybe they even like it, but it's a totally
Stephan Bergmann wrote:
Peter, I'm a bit puzzled that you got hold of that email directed at me,
and forwarded it here including the review link.
I've already explained this to Peter off-list yesterday. Peter wasn't
familiar with the video review process. As a co-organizer of the devroom
Matthias Seidel wrote:
I can see the video both on the website linked above and on YouTube
I refer to the entire set of videos (the entire devroom day), not this
specific talk. Each video is processed individually.
Regards,
Andrea.
Matthias Seidel:
https://fosdem.org/2018/schedule/event/ode_localization/
You will still need some patience... Mike Saunders, co-organizer of the
devroom and employees at The Document Foundation, is taking care of
preparing and cutting all videos and making them available (a lengthy
job and
Patricia Shanahan wrote:
My cough has got worse, so I am going back to London today, skipping the rest
of the conference.
Get well, Patricia! And thanks for the talks yesterday... I think it
will take a few days before we can report it properly, but besides the
all-day technical talks
I know that several of us will be at FOSDEM in Brussels this weekend,
and I guess most will spend time at the ASF booth or at the Open
Document Editors devroom:
https://fosdem.org/2018/schedule/track/open_document_editors/
The devroom runs all day, without a lunch break, but is it OK if we
I know that several of us will be at FOSDEM this weekend, and I guess
most will spend time at the ASF booth or at the Open Document Editors
devroom: https://fosdem.org/2018/schedule/track/open_document_editors/
The devroom runs all day, without a lunch break, but is it OK if we meet
at 13:00,
Juan Florez wrote:
I'm writing to report a problem that surfaced after trying to download a
relatively big number of bug reports from this project's bugzilla. In
short, any domain at apache.org started rejecting connections
You have likely been blacklisted. You need to contact ASF Infra. See
On 24/01/2018 Ash Blade wrote:
I have been working on a script to help increase the version of OO in certain
files before a release.
Thank you Ash! Noted in https://bz.apache.org/ooo/show_bug.cgi?id=127639
My issue is this: the version is currently set up in the form of x.x.x, but
this is
Matthias Seidel wrote:
When I look at the installed DEB packages on my Ubuntu system (e.g. with
"dpkg -s openoffice") I see "Copyright: 2012 by The Apache Software
Foundation".
Looking at [1] and how it was handled at OpenOffice.org I think it
should be "2012-2018" now.
I would commit it to
FR web forum wrote:
provided as office suite in Linux repositories.
It's their choice, driven by commercial interests in some cases.
Since they won't do the work, we take care of it (we actually always
did) by providing RPMs and DEBs that will run on most distributions.
One could make a
201 - 300 of 2585 matches
Mail list logo
