Hi Jim,
Am 24.10.23 um 14:44 schrieb Jim Jagielski:
Yep. macOS and Linux 32 and 64 bit builds (as source) are uploaded to dist/dev
Windows builds are also uploaded now.
Regards,
Matthias
On Oct 24, 2023, at 5:52 AM, Matthias Seidel wrote:
Hi Jim,
Am 23.10.23 um 14:34 schrieb Jim
Yep. macOS and Linux 32 and 64 bit builds (as source) are uploaded to dist/dev
> On Oct 24, 2023, at 5:52 AM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 23.10.23 um 14:34 schrieb Jim Jagielski:
>> I'll start some dev builds for 0a12a2c1
>
> So this is already RC1?
>
> Regards,
>
>
Hi Jim,
Am 23.10.23 um 14:34 schrieb Jim Jagielski:
I'll start some dev builds for 0a12a2c1
So this is already RC1?
Regards,
Matthias
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional
I have now started Test builds for Windows (0a12a2c1).
Am 23.10.23 um 14:34 schrieb Jim Jagielski:
I'll start some dev builds for 0a12a2c1
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional
I'll start some dev builds for 0a12a2c1
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
16:52 schrieb Matthias Seidel:
Am 05.10.23 um 16:50 schrieb Keith N. McKenna:
Matthias Seidel wrote:
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in good condition, but
personally I would like to have the "
>>>> I would like to collect ideas for some kind of roadmap for AOO:
>>>>
>>>> - Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in good
>>>> condition, but personally I would like to have the "ugly UI" fixed on some
>&
Am 17.10.23 um 16:52 schrieb Matthias Seidel:
Am 05.10.23 um 16:50 schrieb Keith N. McKenna:
Matthias Seidel wrote:
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in
good condition, but personally I would like
Hi All,
Am 05.10.23 um 16:50 schrieb Keith N. McKenna:
Matthias Seidel wrote:
Hi All,
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in
good condition, but personally I would like to have the "ugly UI&qu
Hello,
On Fri, Oct 06, 2023 at 11:14:41PM +0200, Marcus wrote:
[...]
> @All:
> Please have a look if that psart of text is OK or what should be written in
> another way.
Fixed on the wiki:
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.15+Release+Notes
Best regards,
--
Arrigo
Am 06.10.23 um 22:07 schrieb Arrigo Marchiori:
On Fri, Oct 06, 2023 at 07:18:37PM +0200, Marcus wrote:
Am 06.10.23 um 18:39 schrieb Rory O'Farrell:
On Fri, 6 Oct 2023 18:31:01 +0200
Marcus wrote:
Am 06.10.23 um 18:02 schrieb Pedro Lino:
Hi Matthias
On 10/06/2023 3:44 PM WEST Matthias
Hello All,
On Fri, Oct 06, 2023 at 07:18:37PM +0200, Marcus wrote:
> Am 06.10.23 um 18:39 schrieb Rory O'Farrell:
> > On Fri, 6 Oct 2023 18:31:01 +0200
> > Marcus wrote:
> >
> > > Am 06.10.23 um 18:02 schrieb Pedro Lino:
> > > > Hi Matthias
> > > >
> > > > > On 10/06/2023 3:44 PM WEST
Am 06.10.23 um 18:39 schrieb Rory O'Farrell:
On Fri, 6 Oct 2023 18:31:01 +0200
Marcus wrote:
Am 06.10.23 um 18:02 schrieb Pedro Lino:
Hi Matthias
On 10/06/2023 3:44 PM WEST Matthias Seidel wrote:
Funny, I *thought* I already did that...
But yes, that solves the problem. Thank you!
On Fri, 6 Oct 2023 18:31:01 +0200
Marcus wrote:
> Am 06.10.23 um 18:02 schrieb Pedro Lino:
> > Hi Matthias
> >
> >> On 10/06/2023 3:44 PM WEST Matthias Seidel
> >> wrote:
> >
> >> Funny, I *thought* I already did that...
> >> But yes, that solves the problem. Thank you!
> >
> > Maybe I
Am 06.10.23 um 18:02 schrieb Pedro Lino:
Hi Matthias
On 10/06/2023 3:44 PM WEST Matthias Seidel wrote:
Funny, I *thought* I already did that...
But yes, that solves the problem. Thank you!
Maybe I missed your previous solution. Sorry!
Does it mean we need to include this library in
Hi Pedro,
Am 06.10.23 um 18:02 schrieb Pedro Lino:
Hi Matthias
On 10/06/2023 3:44 PM WEST Matthias Seidel wrote:
Funny, I *thought* I already did that...
But yes, that solves the problem. Thank you!
Maybe I missed your previous solution. Sorry!
No, you didn't miss anything!
I was
Hi Matthias
> On 10/06/2023 3:44 PM WEST Matthias Seidel wrote:
> Funny, I *thought* I already did that...
> But yes, that solves the problem. Thank you!
Maybe I missed your previous solution. Sorry!
> > Does it mean we need to include this library in the installer?
>
> Either bundle it
On Fri, Oct 6, 2023 at 10:57 AM Pedro Lino
wrote:
> Hi Arrigo, all
>
> This does solve the UI problem.
>
> Does it mean we need to include this library in the installer?
>
>
The licence is LGPL-2+, so we can't ship it, right?
Regards
Damjan
:25 schrieb Matthias Seidel:
Am 05.10.23 um 21:06 schrieb Marcus:
Am 05.10.23 um 15:23 schrieb Matthias Seidel:
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch
AOO41X is in good condition, but personally I would like
to have
23:17 schrieb Marcus:
Am 05.10.23 um 21:25 schrieb Matthias Seidel:
Am 05.10.23 um 21:06 schrieb Marcus:
Am 05.10.23 um 15:23 schrieb Matthias Seidel:
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch
AOO41X is in good
> > Am 05.10.23 um 15:23 schrieb Matthias Seidel:
> > > > > > > I would like to collect ideas for some kind of roadmap for AOO:
> > > > > > >
> > > > > > > - Release AOO 4.1.15 before the end of 2023. Branch
> > > > >
Hi Damjan, all
I just installed AOO 4.1.14 in my Ubuntu 22.04.3 USB drive in Persistence mode
and can see the "ugly" Windows 3.x interface Matthias showed.
> On 10/06/2023 5:27 AM CEST Damjan Jovanovic wrote:
> Actually as per main/vcl/unx/generic/desktopdetect/desktopdetector.cxx:
> Try
0.23 um 21:06 schrieb Marcus:
> > > > > Am 05.10.23 um 15:23 schrieb Matthias Seidel:
> > > > > > I would like to collect ideas for some kind of roadmap for AOO:
> > > > > >
> > > > > > - Release AOO 4.1.15 before the end of 202
arcus:
> >>>> Am 05.10.23 um 15:23 schrieb Matthias Seidel:
> >>>>> I would like to collect ideas for some kind of roadmap for AOO:
> >>>>>
> >>>>> - Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in
>
arcus:
> >>>> Am 05.10.23 um 15:23 schrieb Matthias Seidel:
> >>>>> I would like to collect ideas for some kind of roadmap for AOO:
> >>>>>
> >>>>> - Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in
>
Am 05.10.23 um 23:25 schrieb Matthias Seidel:
Hi Marcus,
Am 05.10.23 um 23:17 schrieb Marcus:
Am 05.10.23 um 21:25 schrieb Matthias Seidel:
Am 05.10.23 um 21:06 schrieb Marcus:
Am 05.10.23 um 15:23 schrieb Matthias Seidel:
I would like to collect ideas for some kind of roadmap for AOO
Hi Marcus,
Am 05.10.23 um 23:17 schrieb Marcus:
Am 05.10.23 um 21:25 schrieb Matthias Seidel:
Am 05.10.23 um 21:06 schrieb Marcus:
Am 05.10.23 um 15:23 schrieb Matthias Seidel:
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023
Am 05.10.23 um 21:25 schrieb Matthias Seidel:
Am 05.10.23 um 21:06 schrieb Marcus:
Am 05.10.23 um 15:23 schrieb Matthias Seidel:
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in
good condition, but personally I
Hi Marcus,
Am 05.10.23 um 21:06 schrieb Marcus:
Am 05.10.23 um 15:23 schrieb Matthias Seidel:
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in
good condition, but personally I would like to have the "ug
Am 05.10.23 um 15:23 schrieb Matthias Seidel:
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in good
condition, but personally I would like to have the "ugly UI" fixed on
some Linux distributi
Sent from my iPhone
> On Oct 5, 2023, at 8:12 AM, Matthias Seidel
> wrote:
>
> Hi Pedro,
>
>> Am 05.10.23 um 16:32 schrieb Pedro Lino:
>> Hi Matthias, all
>>
On 10/05/2023 2:23 PM WEST Matthias Seidel
wrote:
>>> - Release AOO 4.1.15 before the end of 2023. Branch AOO41X is
Hi,
Am 05.10.23 um 18:25 schrieb Damjan Jovanovic:
On Thu, Oct 5, 2023 at 1:24 PM Matthias Seidel
wrote:
Hi All,
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in good
condition, but personally I would like
On Thu, Oct 5, 2023 at 1:24 PM Matthias Seidel
wrote:
> Hi All,
>
> I would like to collect ideas for some kind of roadmap for AOO:
>
> - Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in good
> condition, but personally I would like to have the "ugly UI
Hi Pedro,
Am 05.10.23 um 16:32 schrieb Pedro Lino:
Hi Matthias, all
On 10/05/2023 2:23 PM WEST Matthias Seidel wrote:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in good
condition, but personally I would like to have the "ugly UI" fixed on
some Linux distribution.
Matthias Seidel wrote:
Hi All,
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in good
condition, but personally I would like to have the "ugly UI" fixed on
some Linux distribution.
- Start o
Hi Matthias, all
> On 10/05/2023 2:23 PM WEST Matthias Seidel wrote:
> - Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in good
> condition, but personally I would like to have the "ugly UI" fixed on
> some Linux distribution.
Agree. What ugly UI issues does 4.1.15 fix?
>
Hi All,
I would like to collect ideas for some kind of roadmap for AOO:
- Release AOO 4.1.15 before the end of 2023. Branch AOO41X is in good
condition, but personally I would like to have the "ugly UI" fixed on
some Linux distribution.
- Start on removing the blocker for
On 12/5/2016 12:35 PM, Peter Kovacs wrote:
...
# Concerning 12h period. (did not find who brought this up :) )
What I mean is that it would be great if we could devide all activities
in good estimate able chunks. Agile methology claims everything that an
experienced developer estimates beyond
On 12/06/2016 01:39 AM, Peter Kovacs wrote:
I have created a page on the Confluence Wiki
https://cwiki.apache.org/confluence/display/OOOUSERS/Roadmap
I made a start, with Points that came into my mind without haveing to
check on something. I thought we have in the upper Region our Release
Peter Kovacs wrote:
Also there are lots of document that describe old processes in Planing
and so forth. We should Archive them too. However I can not move things
to an appropriate Folder.
So I left the Link to avoid unlinked pages.
Can we maybe add a Open Office.org Archieve and move all the
Am 12/06/2016 07:39 AM, schrieb Peter Kovacs:
I have created a page on the Confluence Wiki
https://cwiki.apache.org/confluence/display/OOOUSERS/Roadmap
I made a start, with Points that came into my mind without haveing to
check on something. I thought we have in the upper Region our Release
I have now Archieved the Roadmap on the Mediawiki. It is now in a
subpage features/Archieve/OOo 3.3
And put a note out that the new Roadmap is to be found on the Confluence
Wiki.
But I have not delivered any link. Should I add it?
Also there are lots of document that describe old processes
I have created a page on the Confluence Wiki
https://cwiki.apache.org/confluence/display/OOOUSERS/Roadmap
I made a start, with Points that came into my mind without haveing to
check on something. I thought we have in the upper Region our Release
Plan and the a Backlog where we simply collect
. The meritocratic workbase is
not affected by this. If people do not agree, on a single common goal,
then this is as okay as we agree on one vision how Open Office will change.
it's not pro or contra regarding a product roadmap. It's just where to
document this. Maybe this was not clearly enough
On 12/4/2016 2:13 PM, toki wrote:
>
>
> On 03/12/16 12:21, Peter Kovacs wrote:
>
>> But then wrote nothing more. I think if you come here, with the
>> will to fight alone through all the mess, you will give up fast because
>> you have no Idea what your next step is.
>
>
Yes, we could use our cWiki for that...
Apart from that, it would be a good idea to give our users a small
overview of what is planned for the future.
Maybe combined with a Christmas greeting? ;-)
regards, Matthias
Am 04.12.2016 um 15:11 schrieb Marcus:
> Am 12/03/2016 01:21 PM, schrieb Peter
and
then delays for some reasons, while other Topics having a drive.
Plans will have to constantly be revised and changed. On the other hand
you are right. To get started again Wiki is as good as any other approach.
@Patricia
In my opinion the building tool is part of our Roadmap. Not only that we
need
then estimated 12h to accomplish.
If we manage to chop tasks into small pieces like this It is easy to
wor through the tasks.
I believe 12h task is unrealistic
What do you think? Is this nuts? What are your thoughts?
I think if we have such a roadmap, we can go also on public and have
something to talk
On 03/12/16 12:21, Peter Kovacs wrote:
> But then wrote nothing more. I think if you come here, with the
> will to fight alone through all the mess, you will give up fast because
> you have no Idea what your next step is.
https://wiki.openoffice.org/wiki/Features
Am 12/03/2016 01:21 PM, schrieb Peter Kovacs:
So I suggest to keep Bugzilla as Bugtracker, and use Jira as a Todo
backlog List type. I love Agile methology. Never came to use it thought,
because companies can not deal well if there is no timeframe. But I
think for us its perfect.
we have
ent
> ## Test system
>
> Some thing like this. Maybe a bit more detailed, best Idea
> would be that
> no task takes more then estimated 12h to accomplish.
> If we manage to chop tasks into small pieces like this It is
> easy to wor
> through the tasks.
>
> What
+1 for a roadmap!
regards, Matthias
Am 03.12.2016 um 13:21 schrieb Peter Kovacs:
> Hello all,
>
> I thought a little. There were some people claiming that they want to
> help. But then wrote nothing more. I think if you come here, with the
> will to fight alone through al
? Is this nuts? What are your thoughts?
I think if we have such a roadmap, we can go also on public and have
something to talk about. I think it would make our Project a lot more
lovely.
All the best
Peter
-
To unsubscribe, e-mail: dev
this It is easy to wor
through the tasks.
What do you think? Is this nuts? What are your thoughts?
I think if we have such a roadmap, we can go also on public and have
something to talk about. I think it would make our Project a lot more
lovely.
All the best
Peter
On 08/06/2013 RGB ES wrote:
At this point, I think we all agree that we have a bit of a license mess
that needs to be fixed in order to clarify the documentation project. So
here is one possible idea:
1- Move the current /Documentation page to /Documentation-OLD or
/Documentation-LEGACY(1),
2013/6/9 Andrea Pescetti pesce...@apache.org
On 08/06/2013 RGB ES wrote:
At this point, I think we all agree that we have a bit of a license mess
that needs to be fixed in order to clarify the documentation project. So
here is one possible idea:
1- Move the current /Documentation page to
(or not) localized wiki sites
[was: Fwd: [UserGuide]My roadmap]
On Wed, Jun 5, 2013 at 4:12 PM, Dennis E. Hamilton orc...@apache.org
wrote:
+1
I prepared my response before I saw this one.
There is still need to be careful around this:
However, when we create new material, including
Hi
2013/6/3 RGB ES rgb.m...@gmail.com:
2013/6/3 Andrea Pescetti pesce...@apache.org
On 02/06/2013 RGB ES wrote:
Do we want to clone, for example, the documentation section on all the
localized sites, just translating it? On Sun times that was the idea, with
sub sites (portals) like
On Wed, Jun 5, 2013 at 12:02 PM, janI j...@apache.org wrote:
On 5 June 2013 16:36, Claudio Filho filh...@gmail.com wrote:
Hi
2013/6/3 RGB ES rgb.m...@gmail.com:
2013/6/3 Andrea Pescetti pesce...@apache.org
On 02/06/2013 RGB ES wrote:
Do we want to clone, for example, the
...@openoffice.apache.org
Subject: Re: [Discuss][Wiki]Synchronizing (or not) localized wiki sites [was:
Fwd: [UserGuide]My roadmap]
[ ... ]
PDL is a sort of copyleft license.
This is a excelent question. I ask to my self how the TDF did about
(more) this question. Can we do like them? Simply overwrite
roadmap]
[ ... ]
All those portal pages are under PDL license (look at the categories at
the bottom of those pages). If we want to promote new wiki content under
Apache license, this means a problem. If I read this page right
http://www.openoffice.org/licenses/PDL.html
PDL is a sort
...@openoffice.apache.org; d...@openoffice.apache.org
Subject: Re: [Discuss][Wiki]Synchronizing (or not) localized wiki sites
[was: Fwd: [UserGuide]My roadmap]
[ ... ]
All those portal pages are under PDL license (look at the categories at
the bottom of those pages). If we want to promote new wiki content
(or not) localized wiki sites [was:
Fwd: [UserGuide]My roadmap]
On Wed, Jun 5, 2013 at 4:12 PM, Dennis E. Hamilton orc...@apache.org wrote:
+1
I prepared my response before I saw this one.
There is still need to be careful around this:
However, when we create new material, including
On 02/06/2013 RGB ES wrote:
(Top posting, CC to dev, doc and l10n, not sure on which one it is better
to continue the discussion)
Do we want to clone, for example, the documentation section on all the
localized sites, just translating it? On Sun times that was the idea, with
sub sites (portals)
Ops! I forgot to add dev and doc as CC...
-- Forwarded message --
From: RGB ES rgb.m...@gmail.com
Date: 2013/6/3
Subject: Re: [Discuss][Wiki]Synchronizing (or not) localized wiki sites
[was: Fwd: [UserGuide]My roadmap]
To: l...@openoffice.apache.org
2013/6/3 Andrea Pescetti
on the new one here.
I think this was briefly discussed before on the dev list (with no clear
output), but I cannot find the original thread now.
Regards
Ricardo
-- Forwarded message --
From: Alexandro Colorado j...@oooes.org
Date: 2013/6/1
Subject: Re: [UserGuide]My roadmap
66 matches
Mail list logo
