Re: FOSDEM

[Andrea Pescetti]

On 01/02/2019 Andrea Pescetti wrote:

Matthias Seidel wrote:

Am 31.01.19 um 18:27 schrieb Andrea Pescetti:

I will be there, but with a limited attendance this year, only
Saturday afternoon. But I'm looking forward to seeing some of us there!

I see you have a talk at 18:00:
https://fosdem.org/2019/schedule/track/open_document_editors/
I would suggest that we all have a meeting then?

Sure!


Ahem... unfortunately I won't be at my talk. I missed my flight due to 
train delays apparently caused by bad weather. And, as I had planned to 
only attend this afternoon, it doesn't make sense that I reschedule.


I'll miss meeting you! I'll still upload the presentation to the FOSDEM 
site so that not everything is lost.


On the bright side, this means that I will have an unexpected free 
weekend, so I'll be fixing the MWiki issues in queue...


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: FOSDEM

[Matthias Seidel]

Hi Andrea,

Am 02.02.19 um 09:51 schrieb Andrea Pescetti:
> On 01/02/2019 Andrea Pescetti wrote:
>> Matthias Seidel wrote:
>>> Am 31.01.19 um 18:27 schrieb Andrea Pescetti:
 I will be there, but with a limited attendance this year, only
 Saturday afternoon. But I'm looking forward to seeing some of us
 there!
>>> I see you have a talk at 18:00:
>>> https://fosdem.org/2019/schedule/track/open_document_editors/
>>> I would suggest that we all have a meeting then?
>> Sure!
>
> Ahem... unfortunately I won't be at my talk. I missed my flight due to
> train delays apparently caused by bad weather. And, as I had planned
> to only attend this afternoon, it doesn't make sense that I reschedule.
>
> I'll miss meeting you! I'll still upload the presentation to the
> FOSDEM site so that not everything is lost.

"Funny" fact: I also missed my flight and will only be there on
Sunday... :-0
(I will take a bus over night)

>
> On the bright side, this means that I will have an unexpected free
> weekend, so I'll be fixing the MWiki issues in queue...

Yes, there was some add-in missing?
Maybe you can also publish the new graphics...

Regards,

   Matthias

>
> Regards,
>   Andrea.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Query for progress for Issue [Issue 47111] Auto-inserted empty page should honour page layout

[Peter Kovacs]

Hello,

 Better ask for progress on Developer Mailing list then in the bug
itself. There you can get a better discussion. The Issue should focus on
the solution of the issue.

Our main development focus is currently the following (Roughly):

# Updating SDKs

# Improving build environment

# Windows 64 builds

# improving the Language translation process

# prepare our next release 4.2.0, which will come as beta.


Currently all Volunteers are busy. If 47111 is to be done, it needs a
new volunteer or it has to wait longer.


Thanks for your Interest.

All the Best

Peter





-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: FOSDEM

[Mechtilde]

Hello Andrea,

do you have a link to the document?

Kind regards

Am 02.02.19 um 09:51 schrieb Andrea Pescetti:
> On 01/02/2019 Andrea Pescetti wrote:
>> Matthias Seidel wrote:
>>> Am 31.01.19 um 18:27 schrieb Andrea Pescetti:
 I will be there, but with a limited attendance this year, only
 Saturday afternoon. But I'm looking forward to seeing some of us there!
>>> I see you have a talk at 18:00:
>>> https://fosdem.org/2019/schedule/track/open_document_editors/
>>> I would suggest that we all have a meeting then?
>> Sure!
> 
> Ahem... unfortunately I won't be at my talk. I missed my flight due to
> train delays apparently caused by bad weather. And, as I had planned to
> only attend this afternoon, it doesn't make sense that I reschedule.
> 
> I'll miss meeting you! I'll still upload the presentation to the FOSDEM
> site so that not everything is lost.
> 
> On the bright side, this means that I will have an unexpected free
> weekend, so I'll be fixing the MWiki issues in queue...
> 
> Regards,
>   Andrea.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature

Re: Remove main/crashrep?

[Peter Kovacs]

Can someone then open up a bugzilla report and file the action points
what needs to be done?

We have a bunch of bugs that are pointing towards crash the
crashreporter. Should we set those on obsolete and start fresh?


On 31.01.19 18:58, Matthias Seidel wrote:
> Hi Damjan,
>
> Am 31.01.19 um 18:36 schrieb Damjan Jovanovic:
>> On Tue, Jan 29, 2019 at 12:54 AM Matthias Seidel 
>> wrote:
>>
>>> Hi all,
>>>
>>> The crash report tool was abandoned some years ago. Help files were
>>> removed in 2014:
>>> https://bz.apache.org/ooo/show_bug.cgi?id=125696
>>>
>>> Now I simply removed the directory main/crashrep from my build tree
>>> (AOO42X) and still could build successfully.
>>>
>>> So my question is, can it be safely removed? That would free some space
>>> and remove unused strings for translation.
>>>
>>>
>> My vote would be: ABSOLUTELY NOT!
>>
>> This is C++, there is no Exception.printStackTrace() when things go wrong,
>> there is no cross-platform remote debugging. What are we going to do when
>> users come back to us crying how "it crashed"? With a stack trace, we know
>> where to look, and even if there are no debug symbols, we at least know
>> which module crashed. Without a stack trace, the best we can hope for is to
>> reproduce the problem ourselves while running in a debugger.
>>
>> We absolutely need a user-friendly crash reporter, especially after so many
>> changes, with the upcoming Win64 port, with the port to newer MSVC, and
>> many other changes that will destabilize the codebase further.
> I see your point.
>> Yes the crashreporter tool wasn't great, it didn't work on Mac, it required
>> some webservice to submit reports to, but so what? It's just code. We could
>> just make it print a textual report that users can copy and paste into
>> Bugzilla.
> Then let's get it functional again. Indeed a simple text file would
> really be helpful for bug reports.
>
> Later, we can update/re-enable the help pages again.
>
> Regards,
>
>    Matthias
>
>> That crashreporter stands between us and chaos.
>>
>>
>> Prior threads discussing it:
>>
>> 29 May 2012
>> “How to enable crash log for AOO3.4?”
>> http://mail-archives.apache.org/mod_mbox/openoffice-dev/201205.mbox/%3cCAGSaLEqZaw12nYE089iDRJY=bb0axqujepnadvg25vrw0ln...@mail.gmail.com%3e
>>
>> 22 October 2014
>> “crash reporter -- can someone supply commit information on this?”
>> http://mail-archives.apache.org/mod_mbox/openoffice-dev/201410.mbox/%3C544838E3.6050600%40gmail.com%3E
>>
>>
>> Regards
>> Damjan
>>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Google+ going away on April 2, 2019

[Kay Schenk]

I'm assuming most of you know that Google+ is going away April 2. 2019. 
I am one of the moderators for the AOO group. Here is information I just 
received. I know MANY are disappointed by this decision, and we need to 
discuss what to do with the current AOO information.


___

*You've received this email because you have a consumer (personal) 
Google+ account or you manage a Google+ page.*


In December 2018, we announced 
 
our decision to shut down Google+ for consumers in April 2019 due to low 
usage and challenges involved in maintaining a successful product that 
meets consumers' expectations. We want to thank you for being part of 
Google+ and provide next steps, including how to download your photos 
and other content.


*On April 2nd, your Google+ account and any Google+ pages you created 
will be shut down and we will begin deleting content from consumer 
Google+ accounts*. Photos and videos from Google+ in your Album Archive 
and your Google+ pages will also be deleted. You can download and save 
 your content, just make 
sure to do so before April. Note that photos and videos backed up in 
Google Photos will not be deleted.


The process of deleting content from consumer Google+ accounts, Google+ 
Pages, and Album Archive will take a few months, and content may remain 
through this time. For example, users may still see parts of their 
Google+ account via activity log and some consumer Google+ content may 
remain visible to G Suite users until consumer Google+ is deleted.


*As early as February 4th, you will no longer be able to create new 
Google+ profiles, pages, communities or events.*


See the full FAQ  for 
more details and updates leading up to the shutdown.


*If you're a Google+ Community owner or moderator*, you may download and 
save  your data for your 
Google+ Community. Starting early March 2019, additional data will be 
available for download, including author, body, and photos for every 
community post in a public community. Learn more 



*If you sign in to sites and apps using the Google+ Sign-in button*, 
these buttons will stop working in the coming weeks but in some cases 
may be replaced by a Google Sign-in button. You'll still be able to sign 
in with your Google Account wherever you see Google Sign-in buttons. 
Learn more 


*If you've used Google+ for comments on your own or other sites*, this 
feature will be removed from Blogger by February 4th and other sites by 
March 7th. All your Google+ comments on all sites will be deleted 
starting April 2, 2019. Learn more 



*If you're a G Suite customer*, Google+ for your G Suite account should 
remain active. Contact your G Suite administrator 
 for more details. You can 
also expect a new look and new features soon. Learn more 



*If you're a developer* using Google+ APIs or Google+ Sign-in, click 
here  to see how this will 
impact you.


From all of us on the Google+ team, thank you for making Google+ such a 
special place. We are grateful for the talented group of artists, 
community builders, and thought leaders who made Google+ their home. It 
would not have been the same without your passion and dedication.


Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043

You have received this mandatory email service announcement to update 
you about important changes to your Google+ Page, product or account.


--
--
MzK

Re: Google+ going away on April 2, 2019

[Keith N. McKenna]

On 2/2/2019 1:00 PM, Kay Schenk wrote:
> I'm assuming most of you know that Google+ is going away April 2. 2019.
> I am one of the moderators for the AOO group. Here is information I just
> received. I know MANY are disappointed by this decision, and we need to
> discuss what to do with the current AOO information.
> 
Hi Kay;

Yes we should definitely make an archive of Google+ pages, just not sure
where the best place for them to be stored would be.

Regards
Keith



signature.asc
Description: OpenPGP digital signature

Re: FOSDEM

[Andrea Pescetti]

Mechtilde wrote:

do you have a link to the document?


There's a technical issue since of course, before writing here about my 
absence, I had informed the devroom contact asking to be replaced. The 
talk was then replaced but it looks like this made my (canceled) talk 
page inaccessible, so I won't be able to upload anything there.


If the issue remains, I'll keep materials for some other occasions where 
they can actually be presented, or for the OpenOffice blog that we never 
use.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Issues with EPS is this a printer related or more filter related?

[Peter Kovacs]

Hello all,

As you know I  sort and Order Issues we have in our databes in order to
get a better feeling where to plan changes in the code.

I do not know how to deal with Issues around the EPS Export. Is this
more a Filter issue or is this more in terms of Printing? What would you
say? Or some other connect?

Thanks for any insights.


All the best

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org