Re: Official code signing certificate

2013-05-26 Thread Mechtilde 
Hello Andrea,

Am 26.05.2013 00:07, schrieb Andrea Pescetti:
> janI wrote:
>> in all fairness jsc and rob have worked with this for over a
>> year, so it would be more fair to have them do it, and I do not want to
>> come "in between".
> 
> This is a good summary written by Juergen:
> http://wiki.apache.org/general/ASFCodeSigning
> 
> Note that at FOSDEM we were (inconclusively) discussing with Cacert an
> SSL certificate (to be used for serving HTTPS traffic), not a
> code-signing certificate (to be used for signing released files).

This can be done with the same Certificat.

Kind regards

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




signature.asc
Description: OpenPGP digital signature

Re: Official code signing certificate

2013-05-26 Thread janI 
On 26 May 2013 09:53, Mechtilde  wrote:

> Hello Andrea,
>
> Am 26.05.2013 00:07, schrieb Andrea Pescetti:
> > janI wrote:
> >> in all fairness jsc and rob have worked with this for over a
> >> year, so it would be more fair to have them do it, and I do not want to
> >> come "in between".
> >
> > This is a good summary written by Juergen:
> > http://wiki.apache.org/general/ASFCodeSigning
> >
> > Note that at FOSDEM we were (inconclusively) discussing with Cacert an
> > SSL certificate (to be used for serving HTTPS traffic), not a
> > code-signing certificate (to be used for signing released files).
>
> This can be done with the same Certificat.
>

Technically it could be the same certificate but SSL certificates are
handled by infra, and codesigning might be (still a discussion) be handled
by the projects, making it impractical and less secure to have a single
certificate.

Work on the SSL certificate is ongoing. Code signing certificate seems to
be a longer discussion, where the technical part is the least of the
discussion.

rgds
jan I.

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

Re: Find a better name for "sidebar"?

2013-05-26 Thread Regina Henschel 

Hi,

Shari Smith schrieb:

How about User Box or User Panel? UP Box (User Panel Box; UP the side)


A user cannot customize the sidebar beyond disabling a deck. Therefor 
_User_ Box might arouse expectations that cannot be answered.


Kind regards
Regina




On Sat, May 25, 2013 at 9:36 AM, Jörg Schmidt  wrote:


Hello,


From: Andre Fischer [mailto:awf@gmail.com]



I am quite aware of the difference between a generic name and a
marketable "brand" name.  I just don't think that the sidebar
deserves
this honor.


That may be, just may be the criterion that if you want success?

It proverb says:
It does not matter what color the cat is, the main thing it catches mice.

Therefore, it may be so that the sidebar does not deserve a separate name,
just say "no need" not "not allowed".



Hm, I think that we should be careful about our claims.  The
sidebar in
itself is a me-too feature, not the first of its kind.  If we want to
market it then we have to find the aspects of the sidebar that are
unique or better than in other applications.  If we already
have them,
great.  If not then we should work for 4.1 to get them. It
appears that
the sidebar now gets attention from a lot of people in this
community.
It would be great if we could turn this attention into a list of new
ideas for improvements and new features of the sidebar.


Yes, that's right.

I think if you look for improvements, you should see who can help as a
multiplier.

In the sidebar that are e.g. the macro developer that could use the
sidebar in their applications.
My inquiry to a few months ago but unfortunately had little resonance.

This here would be an area where we could greatly advance AOO, that if we
increase the opportunities for macro programmers, whether. In the Basic
DIE, or with respect to the simple usability of the sidebar in macros

Look at MS Office, a large part of its success is owed o the applications
the macro developer, based on this, to end users, program.



Greetings,
Jörg


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







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

Re: Find a better name for "sidebar"?

2013-05-26 Thread Anton Meixome 
I would propose

Panoply from pan (all) + oply (arms)=toolbars

«Because a panoply is a complete set of diverse components, the word
panoply has come to refer to any complete or impressive collection,
especially one of weaponry or where it is displayed, thus an arsenal
or armory.»

It's widely translatable, and for marketing point of view powerfull :-)

de. Panoplie
es., pl., it.  Panoplia
pt. Panóplia
ru. Паноплия
...

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

Re: Moderated messages not reaching the original poster

2013-05-26 Thread Peter Junge 

On 2013年05月16日 05:07, Andrea Pescetti wrote:

On 14/05/2013 janI wrote:

I have, during my time with infra, learned that asking is a good way to
start an issue and get imidiate feedback, and then create a jira.


The feedback hasn't arrived yet, but I have now created a JIRA issue:
https://issues.apache.org/jira/browse/INFRA-6282


Thanks a lot.

Peter

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

Re: Proofing Tool GUI V1.0 - alpha 1- build 7 - 23.May.2013

2013-05-26 Thread Andrea Pescetti 

On 23/05/2013 Marco A.G.Pinto wrote:

Today I have spent several hours improving my tool and decided to
release an alpha version just for people to feel how it works.


I've managed to open the Italian thesaurus from
http://extensions.openoffice.org/en/project/dict-it
and, while the import mostly worked:
- something went wrong on some words (if you try, look around "calamita")
- character encoding is not respected (this might also be a font problem)
- import is really slow, it took extremely long (30+ minutes) to open 
the thesaurus so I couldn't actually try editing entries.



On later releases I want to edit the speller and hyphenation.


I'm not sure that this is a good approach to edit the spell checker 
entries. At least, make sure you properly use the .aff rules (well, I've 
already sent you the relevant links for this and other).


Regards,
  Andrea.

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

Re: Update of pages oo.o credits

2013-05-26 Thread Andrea Pescetti 

On 20/05/2013 Claudio Filho wrote:

 http://www.openoffice.org/welcome/credits.html

IMHO, I think that the best is put a "cut line" and to restart this
list, e.g., preserve this as a old page and in this new page putting a
link to it.


I see that Kay has now updated the page with an "outdated" notice, 
saying that current information is reachable from

http://openoffice.apache.org/people.html

This is good. It only leaves one problem: the current link we place in 
OpenOffice is to http://www.openoffice.org/welcome/credits.html and it 
doesn't look nice that OpenOffice 4.0 points to a page that says "This 
page is outdated".


I see two solutions:

1) Preserve the link, move 
http://www.openoffice.org/welcome/credits.html to 
http://www.openoffice.org/welcome/credits-ooo33.html and move/copy 
http://openoffice.apache.org/people.html to 
http://www.openoffice.org/welcome/credits.html


2) Change the link in OpenOffice (and all translations) so that it 
points to http://openoffice.apache.org/people.html


I think one of the two should be implemented. Solution #1 is heavier on 
the website side, solution #2 would be easier if we weren't in 
translation phase (even though it can probably be automatically done on 
all languages).


Regards,
  Andrea.

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

Re: Update of pages oo.o credits

2013-05-26 Thread RGB ES 
2013/5/26 Andrea Pescetti 

> On 20/05/2013 Claudio Filho wrote:
>
>>  
>> http://www.openoffice.org/**welcome/credits.html
>
 IMHO, I think that the best is put a "cut line" and to restart this
>> list, e.g., preserve this as a old page and in this new page putting a
>> link to it.
>>
>
> I see that Kay has now updated the page with an "outdated" notice, saying
> that current information is reachable from
> http://openoffice.apache.org/**people.html
>
> This is good. It only leaves one problem: the current link we place in
> OpenOffice is to 
> http://www.openoffice.org/**welcome/credits.htmland
>  it doesn't look nice that OpenOffice 4.0 points to a page that says
> "This page is outdated".
>
> I see two solutions:
>
> 1) Preserve the link, move http://www.openoffice.org/**
> welcome/credits.html  to
> http://www.openoffice.org/**welcome/credits-ooo33.htmland
>  move/copy
> http://openoffice.apache.org/**people.htmlto
> http://www.openoffice.org/**welcome/credits.html
>
> 2) Change the link in OpenOffice (and all translations) so that it points
> to 
> http://openoffice.apache.org/**people.html
>
> I think one of the two should be implemented. Solution #1 is heavier on
> the website side, solution #2 would be easier if we weren't in translation
> phase (even though it can probably be automatically done on all languages).
>

About option 2, changing this is a matter of five seconds on pootle, so it
is not a problem. But I think #1 is a better solution considering that we
are talking about a page on the main site: maintaining everything up to
date there, moving outdated material to a dedicated page is better, IMO.

Regards
Ricardo


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

[Bugzilla]Documentation component?

2013-05-26 Thread RGB ES 
Recently, an user on the EN forum raised a valid question: which is the
best way to report a bug not on how the program works but on the
documentation? For example, Math have only two components, "code" and "UI",
but what happens if someone find an error on the bundled help? I
recommended to use "code" and write a tag on the summary like [Help] or
[Documentation], but I'm not sure if this is the better approach.

Note, under "infrastructure" product there is a "documentation" component,
but everything on the infrastructure product points to the website, so
almost nobody arrives there.

Regards
Ricardo

Re: [Bugzilla]Documentation component?

2013-05-26 Thread Ariel Constenla-Haile 
On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote:
> Recently, an user on the EN forum raised a valid question: which is the
> best way to report a bug not on how the program works but on the
> documentation? For example, Math have only two components, "code" and "UI",
> but what happens if someone find an error on the bundled help?

This used to be Product: documentation, Component: Online Help, as in
https://issues.apache.org/ooo/show_bug.cgi?id=120194


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpvZXFcUfbcb.pgp
Description: PGP signature

Re: [Bugzilla]Documentation component?

2013-05-26 Thread RGB ES 
2013/5/26 Ariel Constenla-Haile 

> On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote:
> > Recently, an user on the EN forum raised a valid question: which is the
> > best way to report a bug not on how the program works but on the
> > documentation? For example, Math have only two components, "code" and
> "UI",
> > but what happens if someone find an error on the bundled help?
>
> This used to be Product: documentation, Component: Online Help, as in
> https://issues.apache.org/ooo/show_bug.cgi?id=120194
>
>
Yes, but if you click on "New" to create a new issue the product
"documentation" is missing. The available products are

App Dev
Base
Build Tools
Calc
Draw
General
Impress
Infrastructure
Installation
Internationalization
Math
Native-Lang
Writer

Regards
Ricardo


>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina
>

Re: [Bugzilla]Documentation component?

2013-05-26 Thread Ariel Constenla-Haile 
On Sun, May 26, 2013 at 10:04:57PM +0200, RGB ES wrote:
> 2013/5/26 Ariel Constenla-Haile 
> 
> > On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote:
> > > Recently, an user on the EN forum raised a valid question: which is the
> > > best way to report a bug not on how the program works but on the
> > > documentation? For example, Math have only two components, "code" and
> > "UI",
> > > but what happens if someone find an error on the bundled help?
> >
> > This used to be Product: documentation, Component: Online Help, as in
> > https://issues.apache.org/ooo/show_bug.cgi?id=120194
> >
> >
> Yes, but if you click on "New" to create a new issue the product
> "documentation" is missing. 

Yes, that's why the "used to be" ;)
The option is also missing if you try to edit the product once created
the bug. The category clean-up narrowed it too much, most of the bugs
I submit end up in General - code.


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpgWyK0XjG1H.pgp
Description: PGP signature

Re: [Bugzilla]Documentation component?

2013-05-26 Thread Kay Schenk 
On Sun, May 26, 2013 at 1:13 PM, Ariel Constenla-Haile
wrote:

> On Sun, May 26, 2013 at 10:04:57PM +0200, RGB ES wrote:
> > 2013/5/26 Ariel Constenla-Haile 
> >
> > > On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote:
> > > > Recently, an user on the EN forum raised a valid question: which is
> the
> > > > best way to report a bug not on how the program works but on the
> > > > documentation? For example, Math have only two components, "code" and
> > > "UI",
> > > > but what happens if someone find an error on the bundled help?
> > >
> > > This used to be Product: documentation, Component: Online Help, as in
> > > https://issues.apache.org/ooo/show_bug.cgi?id=120194
> > >
> > >
> > Yes, but if you click on "New" to create a new issue the product
> > "documentation" is missing.
>
> Yes, that's why the "used to be" ;)
> The option is also missing if you try to edit the product once created
> the bug. The category clean-up narrowed it too much, most of the bugs
> I submit end up in General - code.
>
>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina
>

Is there no way to add "Documentation" back into the component list?

-- 

MzK

"You can't believe one thing and do another.
 What you believe and what you do are the same thing."
 -- Leonard Peltier

Re: Update of pages oo.o credits

2013-05-26 Thread Kay Schenk 
On Sun, May 26, 2013 at 10:16 AM, Andrea Pescetti wrote:

> On 20/05/2013 Claudio Filho wrote:
>
>>  
>> http://www.openoffice.org/**welcome/credits.html
>
 IMHO, I think that the best is put a "cut line" and to restart this
>> list, e.g., preserve this as a old page and in this new page putting a
>> link to it.
>>
>
> I see that Kay has now updated the page with an "outdated" notice, saying
> that current information is reachable from
> http://openoffice.apache.org/**people.html
>
> This is good. It only leaves one problem: the current link we place in
> OpenOffice is to 
> http://www.openoffice.org/**welcome/credits.htmland
>  it doesn't look nice that OpenOffice 4.0 points to a page that says
> "This page is outdated".
>
> I see two solutions:
>
> 1) Preserve the link, move http://www.openoffice.org/**
> welcome/credits.html  to
> http://www.openoffice.org/**welcome/credits-ooo33.htmland
>  move/copy
> http://openoffice.apache.org/**people.htmlto
> http://www.openoffice.org/**welcome/credits.html
>
> 2) Change the link in OpenOffice (and all translations) so that it points
> to 
> http://openoffice.apache.org/**people.html
>
> I think one of the two should be implemented. Solution #1 is heavier on
> the website side, solution #2 would be easier if we weren't in translation
> phase (even though it can probably be automatically done on all languages).
>
> Regards,
>   Andrea.
>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
>From a historical perspective, solution #1 is a good choice. However,  I'm
not sure it would have the same impact as what is presented now in the
"legacy" page with the list of names, but, that's OK I guess. I would
certainly want to keep the wiki "self post" aspect.

If we moved the information from:

http://openoffice.apache.org/people.html

over to the website on a new "/welcome/credits.html", I think I would keep
this statement (well even that needs to be changed) with its link to
"about" which could also use some also use some changes and link back to
the project site.

*"OpenOffice.org  acknowledges all
community members, especially those mentioned here.* If your name is not
listed, please contact your project lead."

-- 

MzK

"You can't believe one thing and do another.
 What you believe and what you do are the same thing."
 -- Leonard Peltier

Re: Update of pages oo.o credits

2013-05-26 Thread Albino B Neto 
2013/5/26 Andrea Pescetti :
> 1) Preserve the link, move http://www.openoffice.org/welcome/credits.html to
> http://www.openoffice.org/welcome/credits-ooo33.html and move/copy
> http://openoffice.apache.org/people.html to
> http://www.openoffice.org/welcome/credits.html

+1

No more.

Albino

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