date:20130722

On Mon, Jul 22, 2013 at 5:07 PM, Kay Schenk  wrote:

>
>
> On Mon, Jul 22, 2013 at 8:49 AM, Kay Schenk  wrote:
>
>>
>>
>> On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir  wrote:
>>
>>> Can we do something like this?
>>>
>>> Two stage:  release and announce.
>>>
>>> Release == put the 4.0 files into production on SourceForge, update
>>> our download web page to serve 4.0 files by default.
>>>
>>> Announce == go live with news on front page, header announcement on
>>> every page (branding.mdtext), announcement email, blog post, social
>>> media, new logo on website, etc.
>>>
>>> For the Release part,  can we do that end-of-day today, say in a
>>> couple of hours?
>>>
>>> For the announcement part, this waits for the ASF press release to go
>>> out tomorrow (Tuesday) at 6am New York time.
>>>
>>> This will give us some time today to:
>>>
>>> 1) verify the downloads are working
>>> 2) add the correct download links to the NL pages.
>>>
>>> -Rob
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>>
>> A sterling idea! and one I was thinking about also! +1 
>>
>> I was just about to suggest holding off on the web site "branding"
>> changes until much later today.  But, this idea is better.
>>
>> Re site branding updates -- later  today (1700 PDT? or suggest something
>> an alternate time)  after 'Release' stage, I will commit/port branding/site
>> changes to staging -- they're not there yet -- so someone else can publish
>> this if need be. I will NOT be available at 0600 EDT -- later like 1100 EDT
>> probably.
>>
>
> Branding changes are now in staging for www.openoffice.org:
>
> http://ooo-site.staging.apache.org/
>
> So, this one is available for publishing, along with all the download
> changes, etc that went in today. A surprisingly quick refresh.
>
> Any problems?
>
> I'm getting error messages on project site that I can only do CHECKOUTs.
>
> Not sure what the problem is. :(
>
> I'll try again in an hour or so and see  if I can get them committed. If I
> can't, I'll file an issue with the files attached and post the issue number
> here.
>
> later...
>

Ok, all good...both sides updated with new branding...

http://openoffice.staging.apache.org/


Hopefully, good to be published...

Sweet dreams, people! :)



>
>
>
>>
>>
>>
>> --
>>
>> -
>> MzK
>>
>> Success is falling nine times and getting up ten."
>>  -- Jon Bon Jovi
>>
>
>
>
> --
>
> -
> MzK
>
> Success is falling nine times and getting up ten."
>  -- Jon Bon Jovi
>



-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 8:49 AM, Kay Schenk  wrote:

>
>
> On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir  wrote:
>
>> Can we do something like this?
>>
>> Two stage:  release and announce.
>>
>> Release == put the 4.0 files into production on SourceForge, update
>> our download web page to serve 4.0 files by default.
>>
>> Announce == go live with news on front page, header announcement on
>> every page (branding.mdtext), announcement email, blog post, social
>> media, new logo on website, etc.
>>
>> For the Release part,  can we do that end-of-day today, say in a
>> couple of hours?
>>
>> For the announcement part, this waits for the ASF press release to go
>> out tomorrow (Tuesday) at 6am New York time.
>>
>> This will give us some time today to:
>>
>> 1) verify the downloads are working
>> 2) add the correct download links to the NL pages.
>>
>> -Rob
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>
> A sterling idea! and one I was thinking about also! +1 
>
> I was just about to suggest holding off on the web site "branding" changes
> until much later today.  But, this idea is better.
>
> Re site branding updates -- later  today (1700 PDT? or suggest something
> an alternate time)  after 'Release' stage, I will commit/port branding/site
> changes to staging -- they're not there yet -- so someone else can publish
> this if need be. I will NOT be available at 0600 EDT -- later like 1100 EDT
> probably.
>

Branding changes are now in staging for www.openoffice.org:

http://ooo-site.staging.apache.org/

So, this one is available for publishing, along with all the download
changes, etc that went in today. A surprisingly quick refresh.

Any problems?

I'm getting error messages on project site that I can only do CHECKOUTs.

Not sure what the problem is. :(

I'll try again in an hour or so and see  if I can get them committed. If I
can't, I'll file an issue with the files attached and post the issue number
here.

later...



>
>
>
> --
>
> -
> MzK
>
> Success is falling nine times and getting up ten."
>  -- Jon Bon Jovi
>



-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: mwiki contact page.

On Mon, Jul 22, 2013 at 6:13 PM, Ricardo Berlasso  wrote:
> 2013/7/22 janI 
>
>> On Jul 22, 2013 11:50 PM, "Marcus (OOo)"  wrote:
>> >
>> > Am 07/22/2013 06:12 PM, schrieb Marcus (OOo):
>> >
>> >> Am 07/22/2013 05:16 PM, schrieb janI:
>> >>>
>> >>> On 22 July 2013 17:09, Rob Weir wrote:
>> >>>
>>  On Mon, Jul 22, 2013 at 3:46 AM, janI wrote:
>> >
>> > On Jul 22, 2013 8:59 AM, "Marcus (OOo)" wrote:
>> >>
>> >>
>> >> Am 07/22/2013 04:46 AM, schrieb Kay Schenk:
>> >>
>> >>> On Jul 20, 2013 11:38 PM, "Andrea Pescetti"
>> 
>>  wrote:
>> 
>> 
>> 
>>  Rob Weir wrote:
>> >
>> >
>> >
>> > Remember, the number of people who have admin-related questions
>> > about
>> > the wiki are very, very, very few in number. They will be best
>> 
>>  served
>> >
>> > by directing them to some variation of a page like the one we
>> > have on
>> > the main website:
>> > http://www.openoffice.org/contact_us.html
>> 
>> 
>> 
>> 
>>  Why not linking directly to it then? It would be enough to add a
>> 
>>  section
>> >>>
>> >>>
>> >>> to
>> 
>> 
>>  http://www.openoffice.org/contact_us.html
>>  like the following:
>> 
>>  * If you have technical problems with one of the OpenOffice
>> 
>>  websites...
>> 
>>  - For problems with the www.openoffice.org site: contact
>> >>>
>> >>>
>> >>> dev@openoffice.apache.org and insert "[Website]" in the subject
>> 
>> 
>>  - For problems with the https://issues.apache.org/ooo/ site:
>> contact
>> >>>
>> >>>
>> >>> aoo-bugzilla-ad...@apache.org
>> 
>> 
>>  - For problems with the wiki.openoffice.org site: contact
>> >>>
>> >>>
>> >>> dev@openoffice.apache.org and insert "[Mwiki]" in the subject
>> 
>> 
>>  - For problems with the https://translate.apache.org/ site:
>> contact
>> >>>
>> >>>
>> >>> l...@openoffice.apache.org and insert "[Pootle]" in the subject
>> 
>> 
>> 
>>  Regards,
>>  Andrea.
>> >>>
>> >>>
>> >>>
>> >>> This suggestion looks very reasonable to me.
>> >>
>> >>
>> >>
>> >> In general also for me reasonable. But I don't want to rely on the
>> >
>> > subject prefix that the users have to insert manually. Rather, I
>> would
>> 
>>  use
>> >
>> > some aliases to see where the mail come from.
>> >>
>> >>
>> >> web-admin@ --> dev@
>> >> wiki-admin@ --> dev@
>> >>
>> >> Marcus
>> >>
>> >
>> > sounds good to me, even though I dont think it will make a huge
>> 
>>  difference'
>> >
>> > having a contact link on wiki will cause trafic, and users pr
>> 
>>  defitinition
>> >
>> > choose the easy road.
>> >
>> 
>>  Yes, users are lazy, but they also know what they want. They only
>>  write to the dev list if there is no other option that sounds closer
>>  to what they were looking for.
>> 
>>  So if we have have a page that gives them the appropriate options for
>>  support, reporting bugs, admin issues, etc., and order these
>>  appropriately on
>>  the page (most commonly needed at top), then we should do OK. The
>>  idea that Dave had was to add these items to an existing contact page
>>  that already has these other options.
>> 
>>  So the issue is that 99.99% of the visitors to a wiki page, if they
>>  have a question, will have a product support question. Some, but very
>>  few, will have an admin-related question. It is OK to tell how to get
>>  admin help, but we need to make sure that we say, in the same place,
>>  how to get product support, and make the product support more
>>  prominent by listing it first. That explains the ordering of
>>  information on the contact page:
>> 
>>  http://www.openoffice.org/contact_us.html
>> 
>>  It is not perfect, but it gets most people closer to where they want
>>  to be.
>> 
>>  which I why I wrote "sounds good to me".
>> >>>
>> >>>
>> >>> Also, to the other idea, an alternative to a set of email aliases is
>> 
>>  to use URL's of the form:
>>  mailto:d...@openoffice.org?subject=[Pootle].
>> 
>> >>> +1 that is a better idea, since we do not need to maintain extra
>> virtual
>> >>> mail adresses
>> >>> (I did not know that trix, thats pretty cool)
>> >>
>> >>
>> >> Yes, with this formatting it's OK.
>> >>
>> >> However, we should extend the "contact_us.html" were needed to point to
>> >> this site from, e.g., Wiki or Forum. No need to create a new page for
>> >> such purpose - ahm, if this was planned. ;-)
>> >
>> >
>> > I updated the webpage and adde

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 3:21 PM, Marcus (OOo)  wrote:

> Am 07/22/2013 09:35 PM, schrieb Marcus (OOo):
>
>  Am 07/22/2013 08:00 PM, schrieb Marcus (OOo):
>>
>>> OK, I've updated the DL webpages.
>>>
>>> After fixing some broken links, I think it's OK and ready for a review:
>>>
>>> http://ooo-site.staging.**apache.org/download/index.html
>>>
>>
>> The last hints are fixed. So, when nothing else comes in we should be
>> ready to go live with the new DL webages.
>>
>> Furthermore, the project's download webpage is also updated, of course
>> until now just staged:
>>
>> http://openoffice.staging.**apache.org/downloads4test.html
>>
>>  Only then I will publish to the live server.
>>>
>>
>> Before the night is coming I can finalize and publish the project's
>> download webpage.
>>
>
> Done.
>
>
>  The main download webpage can be published at any time when you see fit.
>>
>
> The main download webpages are now up-to-date and just need to be put on
> the Live server. So, you can do this when you see the time has come.
>
> Go, Apache OpenOffice 4, go! :-)
>
> Nighty night everyone.
>
>
> Marcus
>

Sleep well knowing you did a great job! :)


>
>
>
>  Am 07/22/2013 07:08 PM, schrieb Kay Schenk:
>>>
 On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)
 wrote:

  Am 07/22/2013 05:49 PM, schrieb Kay Schenk:
>
> On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir wrote:
>
>>
>> Can we do something like this?
>>
>>>
>>> Two stage: release and announce.
>>>
>>>
>>  This was already planned to do.
>
>
> Release == put the 4.0 files into production on SourceForge, update
>
>> our download web page to serve 4.0 files by default.
>>>
>>> Announce == go live with news on front page, header announcement on
>>> every page (branding.mdtext), announcement email, blog post, social
>>> media, new logo on website, etc.
>>>
>>> For the Release part, can we do that end-of-day today, say in a
>>> couple of hours?
>>>
>>>
>>  Hm, in a couple of hours it's bed time in Hamburg, So, I need to
> publish
> the new things earlier. I think in 1 or 2 hours, then I have some
> time to
> correct faulty things.
>


 Yep! Do it! I think this is what Rob meant. We do the bulk of the DL
 stuff
 WITHOUT the rebranding until tomorrow.



> For the announcement part, this waits for the ASF press release to go
>
>> out tomorrow (Tuesday) at 6am New York time.
>>>
>>> This will give us some time today to:
>>>
>>> 1) verify the downloads are working
>>> 2) add the correct download links to the NL pages.
>>>
>>>
>>  Marcus
>
>
>
>
> A sterling idea! and one I was thinking about also! +1 
>
>>
>> I was just about to suggest holding off on the web site "branding"
>> changes
>> until much later today. But, this idea is better.
>>
>> Re site branding updates -- later today (1700 PDT? or suggest
>> something
>> an
>> alternate time) after 'Release' stage, I will commit/port
>> branding/site
>> changes to staging -- they're not there yet -- so someone else can
>> publish
>> this if need be. I will NOT be available at 0600 EDT -- later like
>> 1100
>> EDT
>> probably.
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: Release coordination proposal


Am 07/22/2013 09:35 PM, schrieb Marcus (OOo):

Am 07/22/2013 08:00 PM, schrieb Marcus (OOo):

OK, I've updated the DL webpages.

After fixing some broken links, I think it's OK and ready for a review:

http://ooo-site.staging.apache.org/download/index.html


The last hints are fixed. So, when nothing else comes in we should be
ready to go live with the new DL webages.

Furthermore, the project's download webpage is also updated, of course
until now just staged:

http://openoffice.staging.apache.org/downloads4test.html


Only then I will publish to the live server.


Before the night is coming I can finalize and publish the project's
download webpage.


Done.


The main download webpage can be published at any time when you see fit.


The main download webpages are now up-to-date and just need to be put on 
the Live server. So, you can do this when you see the time has come.


Go, Apache OpenOffice 4, go! :-)

Nighty night everyone.

Marcus




Am 07/22/2013 07:08 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)
wrote:


Am 07/22/2013 05:49 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir wrote:


Can we do something like this?


Two stage: release and announce.




This was already planned to do.


Release == put the 4.0 files into production on SourceForge, update

our download web page to serve 4.0 files by default.

Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part, can we do that end-of-day today, say in a
couple of hours?




Hm, in a couple of hours it's bed time in Hamburg, So, I need to
publish
the new things earlier. I think in 1 or 2 hours, then I have some
time to
correct faulty things.



Yep! Do it! I think this is what Rob meant. We do the bulk of the DL
stuff
WITHOUT the rebranding until tomorrow.




For the announcement part, this waits for the ASF press release to go

out tomorrow (Tuesday) at 6am New York time.

This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.




Marcus




A sterling idea! and one I was thinking about also! +1 


I was just about to suggest holding off on the web site "branding"
changes
until much later today. But, this idea is better.

Re site branding updates -- later today (1700 PDT? or suggest
something
an
alternate time) after 'Release' stage, I will commit/port
branding/site
changes to staging -- they're not there yet -- so someone else can
publish
this if need be. I will NOT be available at 0600 EDT -- later like
1100
EDT
probably.


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

Re: mwiki contact page.

2013-07-22 Thread Ricardo Berlasso

2013/7/22 janI 

> On Jul 22, 2013 11:50 PM, "Marcus (OOo)"  wrote:
> >
> > Am 07/22/2013 06:12 PM, schrieb Marcus (OOo):
> >
> >> Am 07/22/2013 05:16 PM, schrieb janI:
> >>>
> >>> On 22 July 2013 17:09, Rob Weir wrote:
> >>>
>  On Mon, Jul 22, 2013 at 3:46 AM, janI wrote:
> >
> > On Jul 22, 2013 8:59 AM, "Marcus (OOo)" wrote:
> >>
> >>
> >> Am 07/22/2013 04:46 AM, schrieb Kay Schenk:
> >>
> >>> On Jul 20, 2013 11:38 PM, "Andrea Pescetti"
> 
>  wrote:
> 
> 
> 
>  Rob Weir wrote:
> >
> >
> >
> > Remember, the number of people who have admin-related questions
> > about
> > the wiki are very, very, very few in number. They will be best
> 
>  served
> >
> > by directing them to some variation of a page like the one we
> > have on
> > the main website:
> > http://www.openoffice.org/contact_us.html
> 
> 
> 
> 
>  Why not linking directly to it then? It would be enough to add a
> 
>  section
> >>>
> >>>
> >>> to
> 
> 
>  http://www.openoffice.org/contact_us.html
>  like the following:
> 
>  * If you have technical problems with one of the OpenOffice
> 
>  websites...
> 
>  - For problems with the www.openoffice.org site: contact
> >>>
> >>>
> >>> dev@openoffice.apache.org and insert "[Website]" in the subject
> 
> 
>  - For problems with the https://issues.apache.org/ooo/ site:
> contact
> >>>
> >>>
> >>> aoo-bugzilla-ad...@apache.org
> 
> 
>  - For problems with the wiki.openoffice.org site: contact
> >>>
> >>>
> >>> dev@openoffice.apache.org and insert "[Mwiki]" in the subject
> 
> 
>  - For problems with the https://translate.apache.org/ site:
> contact
> >>>
> >>>
> >>> l...@openoffice.apache.org and insert "[Pootle]" in the subject
> 
> 
> 
>  Regards,
>  Andrea.
> >>>
> >>>
> >>>
> >>> This suggestion looks very reasonable to me.
> >>
> >>
> >>
> >> In general also for me reasonable. But I don't want to rely on the
> >
> > subject prefix that the users have to insert manually. Rather, I
> would
> 
>  use
> >
> > some aliases to see where the mail come from.
> >>
> >>
> >> web-admin@ --> dev@
> >> wiki-admin@ --> dev@
> >>
> >> Marcus
> >>
> >
> > sounds good to me, even though I dont think it will make a huge
> 
>  difference'
> >
> > having a contact link on wiki will cause trafic, and users pr
> 
>  defitinition
> >
> > choose the easy road.
> >
> 
>  Yes, users are lazy, but they also know what they want. They only
>  write to the dev list if there is no other option that sounds closer
>  to what they were looking for.
> 
>  So if we have have a page that gives them the appropriate options for
>  support, reporting bugs, admin issues, etc., and order these
>  appropriately on
>  the page (most commonly needed at top), then we should do OK. The
>  idea that Dave had was to add these items to an existing contact page
>  that already has these other options.
> 
>  So the issue is that 99.99% of the visitors to a wiki page, if they
>  have a question, will have a product support question. Some, but very
>  few, will have an admin-related question. It is OK to tell how to get
>  admin help, but we need to make sure that we say, in the same place,
>  how to get product support, and make the product support more
>  prominent by listing it first. That explains the ordering of
>  information on the contact page:
> 
>  http://www.openoffice.org/contact_us.html
> 
>  It is not perfect, but it gets most people closer to where they want
>  to be.
> 
>  which I why I wrote "sounds good to me".
> >>>
> >>>
> >>> Also, to the other idea, an alternative to a set of email aliases is
> 
>  to use URL's of the form:
>  mailto:d...@openoffice.org?subject=[Pootle].
> 
> >>> +1 that is a better idea, since we do not need to maintain extra
> virtual
> >>> mail adresses
> >>> (I did not know that trix, thats pretty cool)
> >>
> >>
> >> Yes, with this formatting it's OK.
> >>
> >> However, we should extend the "contact_us.html" were needed to point to
> >> this site from, e.g., Wiki or Forum. No need to create a new page for
> >> such purpose - ahm, if this was planned. ;-)
> >
> >
> > I updated the webpage and added some text and links at the end:
> >
> > http://ooo-site.staging.apache.org/contact_us.html
> >
> > Feel free to improve.
>
> Does a user really need to subscribe to dev@ to get e.g. help with wiki
> login ? I dont think th

Re: [RELEASE]: availability of uploads and synchronize SF mirrors


Am 07/23/2013 12:02 AM, schrieb Roberto Galoppini:

2013/7/22 Marcus (OOo)


Am 07/20/2013 07:40 PM, schrieb Roberto Galoppini:


Il giorno sabato 20 luglio 2013, Kay Schenk ha scritto:

  On Sat, Jul 20, 2013 at 3:45 AM, Marcus (OOo)
javascript:;>>

wrote:

  Here a little update what I can see:


1.
https://sourceforge.net/projects/openofficeorg.mirror/
files/4.0.0/binaries/<


https://sourceforge.net/**projects/openofficeorg.mirror/**
files/4.0.0/binaries/




The builds seem to be completely received on SourceForge. So, for me
it's
done.





We used 'staged' directories, as discussed before, Think we are ready to
turn them on when it's time.



I've now deleted the staged status from the new "4.0.0" directory.

I expect that this attribute change has to be distributed to all mirrors.
So, we should have enough time until tomorrow.



The files are all already propagated, unstaging happens exactly when you
delete the status.


OK, good to know.

Maybe a general problem, a little hint for fixing: ;-)

I've unchecked the box and hit on [Save] several times. But the hint 
"staged" remained behind the folder name. Then I have reloaded the 
complete webpage and now it was removed.


Marcus




  2.

http://www.apache.org/dist/



yeah, I saw this also just nowh

this one, where SF pulls from --

   
http://www.apache.org/dist/**externaldist/

is in good shape.


  No "openoffice" directory and therefore no binary and source builds.

Maybe Juergen and Infra are still working on this. I'll look again today
evening/tomorrow morning (European timezone).

Marcus




Am 07/19/2013 05:16 PM, schrieb Jürgen Schmidt:

  The vote closed successful and I have once again uploaded the files in


the dist are on the people server.

/www/www.apache.org/dist/openoffice/4.0.0
<


http://www.apache.org/dist/**openoffice/4.0.0






The relevant files for SF are under
/www/www.apache.org/dist/extgernaldist/openoffice/4.0.0
**<


http://www.apache.org/dist/**extgernaldist/openoffice/4.0.0

**>





I hope the rsync url works now, if not please contact the infra people
directly.

rsync Url: rsync.apache.org::apache-dist-external


A complete file list can you find here

  http://people.apache.org/~jsc/aoo4.0_files_dist-**

openoffice-**4.0.0.txt
<
http://people.apache.org/~jsc/**aoo4.0_files_dist-openoffice-**4.0.0.txt





http://people.apache.org/~jsc/aoo4.0_files_dist-**

externaldist-openoffice-4.0.0.txt<


http://people.apache.org/~jsc/**aoo4.0_files_dist-**

externaldist-openoffice-4.0.0.**txt





As I mentioned earlier I will be not available until next week
Thursday.
But I hope I can follow the release a little bit to have some fun with
you all together ;-)

Juergen


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

Re: [RELEASE]: availability of uploads and synchronize SF mirrors

2013/7/22 Marcus (OOo) 

> Am 07/20/2013 07:40 PM, schrieb Roberto Galoppini:
>
>> Il giorno sabato 20 luglio 2013, Kay Schenk ha scritto:
>>
>>  On Sat, Jul 20, 2013 at 3:45 AM, Marcus (OOo)>> javascript:;>>
>>>
>>> wrote:
>>>
>>>  Here a little update what I can see:

 1.
 https://sourceforge.net/projects/openofficeorg.mirror/
 files/4.0.0/binaries/<

>>> https://sourceforge.net/**projects/openofficeorg.mirror/**
>>> files/4.0.0/binaries/
>>>


 The builds seem to be completely received on SourceForge. So, for me
 it's
 done.

>>>
>>
>> We used 'staged' directories, as discussed before, Think we are ready to
>> turn them on when it's time.
>>
>
> I've now deleted the staged status from the new "4.0.0" directory.
>
> I expect that this attribute change has to be distributed to all mirrors.
> So, we should have enough time until tomorrow.
>

The files are all already propagated, unstaging happens exactly when you
delete the status.

Roberto



>
> Marcus
>
>
>
>
>  2.
 http://www.apache.org/dist/


>>> yeah, I saw this also just nowh
>>>
>>> this one, where SF pulls from --
>>>
>>>   
>>> http://www.apache.org/dist/**externaldist/
>>>
>>> is in good shape.
>>>
>>>
>>>  No "openoffice" directory and therefore no binary and source builds.
 Maybe Juergen and Infra are still working on this. I'll look again today
 evening/tomorrow morning (European timezone).

 Marcus




 Am 07/19/2013 05:16 PM, schrieb Jürgen Schmidt:

  The vote closed successful and I have once again uploaded the files in
>
> the dist are on the people server.
>
> /www/www.apache.org/dist/openoffice/4.0.0
> <
>
 http://www.apache.org/dist/**openoffice/4.0.0
>>> >
>>>

> The relevant files for SF are under
> /www/www.apache.org/dist/extgernaldist/openoffice/4.0.0
> **<
>
 http://www.apache.org/dist/**extgernaldist/openoffice/4.0.0
>>> **>
>>>

>
> I hope the rsync url works now, if not please contact the infra people
> directly.
>
> rsync Url: rsync.apache.org::apache-dist-external
>
>
> A complete file list can you find here
>
>  http://people.apache.org/~jsc/aoo4.0_files_dist-**
>>> openoffice-**4.0.0.txt
>>> <
>>> http://people.apache.org/~jsc/**aoo4.0_files_dist-openoffice-**4.0.0.txt
>>> >
>>>
 http://people.apache.org/~jsc/aoo4.0_files_dist-**
> externaldist-openoffice-4.0.0.txt<
>
 http://people.apache.org/~jsc/**aoo4.0_files_dist-**
>>> externaldist-openoffice-4.0.0.**txt
>>>


> As I mentioned earlier I will be not available until next week
> Thursday.
> But I hope I can follow the release a little bit to have some fun with
> you all together ;-)
>
> Juergen
>

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

Re: mwiki contact page.

On Jul 22, 2013 11:50 PM, "Marcus (OOo)"  wrote:
>
> Am 07/22/2013 06:12 PM, schrieb Marcus (OOo):
>
>> Am 07/22/2013 05:16 PM, schrieb janI:
>>>
>>> On 22 July 2013 17:09, Rob Weir wrote:
>>>
 On Mon, Jul 22, 2013 at 3:46 AM, janI wrote:
>
> On Jul 22, 2013 8:59 AM, "Marcus (OOo)" wrote:
>>
>>
>> Am 07/22/2013 04:46 AM, schrieb Kay Schenk:
>>
>>> On Jul 20, 2013 11:38 PM, "Andrea Pescetti"

 wrote:

 Rob Weir wrote:
>
>
>
> Remember, the number of people who have admin-related questions
> about
> the wiki are very, very, very few in number. They will be best

 served
>
> by directing them to some variation of a page like the one we
> have on
> the main website:
> http://www.openoffice.org/contact_us.html

 Why not linking directly to it then? It would be enough to add a

 section
>>>
>>>
>>> to

 http://www.openoffice.org/contact_us.html
 like the following:

 * If you have technical problems with one of the OpenOffice

 websites...

 - For problems with the www.openoffice.org site: contact
>>>
>>>
>>> dev@openoffice.apache.org and insert "[Website]" in the subject

 - For problems with the https://issues.apache.org/ooo/ site:
contact
>>>
>>>
>>> aoo-bugzilla-ad...@apache.org

 - For problems with the wiki.openoffice.org site: contact
>>>
>>>
>>> dev@openoffice.apache.org and insert "[Mwiki]" in the subject

 - For problems with the https://translate.apache.org/ site: contact
>>>
>>>
>>> l...@openoffice.apache.org and insert "[Pootle]" in the subject

 Regards,
 Andrea.
>>>
>>>
>>>
>>> This suggestion looks very reasonable to me.
>>
>>
>>
>> In general also for me reasonable. But I don't want to rely on the
>
> subject prefix that the users have to insert manually. Rather, I would

 use
>
> some aliases to see where the mail come from.
>>
>>
>> web-admin@ --> dev@
>> wiki-admin@ --> dev@
>>
>> Marcus
>>
>
> sounds good to me, even though I dont think it will make a huge

 difference'
>
> having a contact link on wiki will cause trafic, and users pr

 defitinition
>
> choose the easy road.
>

 Yes, users are lazy, but they also know what they want. They only
 write to the dev list if there is no other option that sounds closer
 to what they were looking for.

 So if we have have a page that gives them the appropriate options for
 support, reporting bugs, admin issues, etc., and order these
 appropriately on
 the page (most commonly needed at top), then we should do OK. The
 idea that Dave had was to add these items to an existing contact page
 that already has these other options.

 So the issue is that 99.99% of the visitors to a wiki page, if they
 have a question, will have a product support question. Some, but very
 few, will have an admin-related question. It is OK to tell how to get
 admin help, but we need to make sure that we say, in the same place,
 how to get product support, and make the product support more
 prominent by listing it first. That explains the ordering of
 information on the contact page:

 http://www.openoffice.org/contact_us.html

 It is not perfect, but it gets most people closer to where they want
 to be.

 which I why I wrote "sounds good to me".
>>>
>>>
>>> Also, to the other idea, an alternative to a set of email aliases is

 to use URL's of the form:
 mailto:d...@openoffice.org?subject=[Pootle].

>>> +1 that is a better idea, since we do not need to maintain extra virtual
>>> mail adresses
>>> (I did not know that trix, thats pretty cool)
>>
>>
>> Yes, with this formatting it's OK.
>>
>> However, we should extend the "contact_us.html" were needed to point to
>> this site from, e.g., Wiki or Forum. No need to create a new page for
>> such purpose - ahm, if this was planned. ;-)
>
>
> I updated the webpage and added some text and links at the end:
>
> http://ooo-site.staging.apache.org/contact_us.html
>
> Feel free to improve.

Does a user really need to subscribe to dev@ to get e.g. help with wiki
login ? I dont think that is very user friendly.

rgds
jan I
>
>
> Marcus
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

Re: [WWW]Forum landing page

On Jul 22, 2013 11:31 PM, "Andrea Pescetti"  wrote:
>
> janI wrote:
>
>> On 22 July 2013 22:59, Hagar Delest wrote:
>>>
>>> Le 21/07/2013 20:00, janI a écrit :

 I am not sure who is actively administrating phpBB. The phpBB group
only
 contains imacat and terrye.
>>>
>>> Terry left so imacat is the only one.
>>
>> I suspected that, but was not sure if andrea also had access.
>
>
> I have access to both the forum (meaning that I have an account for web
login there) and the machine hosting it (SSH access), but in both cases I
have normal user privileges, so I cannot administer either the forum or the
machine hosting it.

you should also have karma to reboot and/or restart the form, which is all
you need for a quick problem solving. when the vm_team was started we got a
mail with allowed commands from gncdonald (I might have copied the
commands). I dont have access to my old mails.

so we are down to imacat (at least for the moment) for changing backup
strategy.

rgds
jan i.

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

Re: mwiki contact page.


Am 07/22/2013 06:12 PM, schrieb Marcus (OOo):

Am 07/22/2013 05:16 PM, schrieb janI:

On 22 July 2013 17:09, Rob Weir wrote:


On Mon, Jul 22, 2013 at 3:46 AM, janI wrote:

On Jul 22, 2013 8:59 AM, "Marcus (OOo)" wrote:


Am 07/22/2013 04:46 AM, schrieb Kay Schenk:


On Jul 20, 2013 11:38 PM, "Andrea Pescetti"

wrote:



Rob Weir wrote:



Remember, the number of people who have admin-related questions
about
the wiki are very, very, very few in number. They will be best

served

by directing them to some variation of a page like the one we
have on
the main website:
http://www.openoffice.org/contact_us.html




Why not linking directly to it then? It would be enough to add a

section


to


http://www.openoffice.org/contact_us.html
like the following:

* If you have technical problems with one of the OpenOffice

websites...

- For problems with the www.openoffice.org site: contact


dev@openoffice.apache.org and insert "[Website]" in the subject


- For problems with the https://issues.apache.org/ooo/ site: contact


aoo-bugzilla-ad...@apache.org


- For problems with the wiki.openoffice.org site: contact


dev@openoffice.apache.org and insert "[Mwiki]" in the subject


- For problems with the https://translate.apache.org/ site: contact


l...@openoffice.apache.org and insert "[Pootle]" in the subject



Regards,
Andrea.



This suggestion looks very reasonable to me.



In general also for me reasonable. But I don't want to rely on the

subject prefix that the users have to insert manually. Rather, I would

use

some aliases to see where the mail come from.


web-admin@ --> dev@
wiki-admin@ --> dev@

Marcus



sounds good to me, even though I dont think it will make a huge

difference'

having a contact link on wiki will cause trafic, and users pr

defitinition

choose the easy road.



Yes, users are lazy, but they also know what they want. They only
write to the dev list if there is no other option that sounds closer
to what they were looking for.

So if we have have a page that gives them the appropriate options for
support, reporting bugs, admin issues, etc., and order these
appropriately on
the page (most commonly needed at top), then we should do OK. The
idea that Dave had was to add these items to an existing contact page
that already has these other options.

So the issue is that 99.99% of the visitors to a wiki page, if they
have a question, will have a product support question. Some, but very
few, will have an admin-related question. It is OK to tell how to get
admin help, but we need to make sure that we say, in the same place,
how to get product support, and make the product support more
prominent by listing it first. That explains the ordering of
information on the contact page:

http://www.openoffice.org/contact_us.html

It is not perfect, but it gets most people closer to where they want
to be.

which I why I wrote "sounds good to me".


Also, to the other idea, an alternative to a set of email aliases is

to use URL's of the form:
mailto:d...@openoffice.org?subject=[Pootle].


+1 that is a better idea, since we do not need to maintain extra virtual
mail adresses
(I did not know that trix, thats pretty cool)


Yes, with this formatting it's OK.

However, we should extend the "contact_us.html" were needed to point to
this site from, e.g., Wiki or Forum. No need to create a new page for
such purpose - ahm, if this was planned. ;-)


I updated the webpage and added some text and links at the end:

http://ooo-site.staging.apache.org/contact_us.html

Feel free to improve.

Marcus


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

Re: Release coordination proposal


Am 07/22/2013 11:40 PM, schrieb Donald Whytock:

On Mon, Jul 22, 2013 at 3:55 PM, Marcus (OOo)  wrote:


Am 07/22/2013 09:45 PM, schrieb Rob Weir:

  2) What should the "legacy" link go to now?  Is 3.3.0 still "legacy"?

If so, what is "3.4.1"?   We might need to reword and restructure that
destination page, but I think it is OK for now.



In this context I understand "legacy release" as a release from a former
instance - here Sun/Oracle. With the planned EOL for 3.4 this can be
cleaned-up, too.



Thought the planned EOL was for 3.3.  Not that an EOL for 3.4 doesn't make
sense, given 3.4.1...


Ups, you are right. I meant of course the planned EOL of 3.3.0.

Marcus


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

Re: Release coordination proposal

2013-07-22 Thread Donald Whytock

On Mon, Jul 22, 2013 at 3:55 PM, Marcus (OOo)  wrote:

> Am 07/22/2013 09:45 PM, schrieb Rob Weir:
>
>  2) What should the "legacy" link go to now?  Is 3.3.0 still "legacy"?
>> If so, what is "3.4.1"?   We might need to reword and restructure that
>> destination page, but I think it is OK for now.
>>
>
> In this context I understand "legacy release" as a release from a former
> instance - here Sun/Oracle. With the planned EOL for 3.4 this can be
> cleaned-up, too.
>
>
Thought the planned EOL was for 3.3.  Not that an EOL for 3.4 doesn't make
sense, given 3.4.1...

Don

Re: [WWW]Forum landing page

2013-07-22 Thread Andrea Pescetti


janI wrote:

On 22 July 2013 22:59, Hagar Delest wrote:

Le 21/07/2013 20:00, janI a écrit :

I am not sure who is actively administrating phpBB. The phpBB group only
contains imacat and terrye.

Terry left so imacat is the only one.

I suspected that, but was not sure if andrea also had access.


I have access to both the forum (meaning that I have an account for web 
login there) and the machine hosting it (SSH access), but in both cases 
I have normal user privileges, so I cannot administer either the forum 
or the machine hosting it.


Regards,
  Andrea.

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

Re: wiki "sysops" link not working...

On Mon, Jul 22, 2013 at 2:16 PM, janI  wrote:

> On 22 July 2013 22:59, Kay Schenk  wrote:
>
> > I don't know if this is related to previous discussions on the removal of
> > contact items from MWiki--
> >
> > I'm at:
> >
> > http://wiki.openoffice.org/wiki/Help:Administration
> >
> > the link to "sysops" is no longer working.
> >
>
> no this cannot have worked since the upgrade. it was just a matter of
> editing the page and adding the correct link.
>
> Its corrected now.
>
> have a nice evening (if that fits with your TZ),
>
> rgds
> jan I.
>

thank you! all good now...


>
>
> >
> >
> >
> > --
> >
> >
> -
> > MzK
> >
> > Success is falling nine times and getting up ten."
> >  -- Jon Bon Jovi
> >
>



-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: [WWW]Forum landing page

On 22 July 2013 22:59, Hagar Delest  wrote:

> Le 21/07/2013 20:00, janI a écrit :
>
>> I am not sure who is actively administrating phpBB. The phpBB group only
>> contains imacat and terrye.
>>
>
> Terry left so imacat is the only one.
>

I suspected that, but was not sure if andrea also had access.

imacat told me earlier that she is busy until end of this month, so I take
it will have to wait.

We should however have a discussion again, about server support, the team
we setup does not really work (at least seen from my POW).

rgds
jan I.

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

Re: wiki "sysops" link not working...

On 22 July 2013 22:59, Kay Schenk  wrote:

> I don't know if this is related to previous discussions on the removal of
> contact items from MWiki--
>
> I'm at:
>
> http://wiki.openoffice.org/wiki/Help:Administration
>
> the link to "sysops" is no longer working.
>

no this cannot have worked since the upgrade. it was just a matter of
editing the page and adding the correct link.

Its corrected now.

have a nice evening (if that fits with your TZ),

rgds
jan I.


>
>
>
> --
>
> -
> MzK
>
> Success is falling nine times and getting up ten."
>  -- Jon Bon Jovi
>

Re: [WWW]Forum landing page

2013-07-22 Thread Hagar Delest


Le 21/07/2013 20:00, janI a écrit :

I am not sure who is actively administrating phpBB. The phpBB group only
contains imacat and terrye.


Terry left so imacat is the only one.

Hagar

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

wiki "sysops" link not working...

I don't know if this is related to previous discussions on the removal of
contact items from MWiki--

I'm at:

http://wiki.openoffice.org/wiki/Help:Administration

the link to "sysops" is no longer working.



-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: Release coordination proposal


Am 07/22/2013 10:03 PM, schrieb Andrea Pescetti:

Il 22/07/2013 Marcus (OOo) wrote:

Am 07/22/2013 08:00 PM, schrieb Marcus (OOo):

After fixing some broken links, I think it's OK and ready for a review:
http://ooo-site.staging.apache.org/download/index.html

The last hints are fixed. So, when nothing else comes in we should be
ready to go live with the new DL webages.


Everything looks nice, thanks! (just, maybe in other_tables.html the
checksum links could be made in a smaller font size than "exe").


OK, will keep in mind.


There is still one small issue to correct, but I'm not sure whether this
is something Marcus can modify, so CCing Roberto.


I don't see a section to edit the links in the "Please contribute!" box. 
So yes, this is for Roberto.



After I start the download (so, I am already on the SF page) I see:

Thanks for downloading Apache OpenOffice, the free and open productivity
suite. We invite you to learn more about how to enhance your experience
with OpenOffice; sign up to receive important notifications and learn
how you can contribute to make the next version of OpenOffice even better.

This text is OK, but it has two links that should be updated:
ooo-announce-subscr...@incubator.apache.org
-> announce-subscr...@openoffice.apache.org
http://incubator.apache.org/openofficeorg/get-involved.html
-> http://openoffice.apache.org/get-involved.html


Marcus


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

Re: Release coordination proposal

2013-07-22 Thread Andrea Pescetti


Il 22/07/2013 Marcus (OOo) wrote:

Am 07/22/2013 08:00 PM, schrieb Marcus (OOo):

After fixing some broken links, I think it's OK and ready for a review:
http://ooo-site.staging.apache.org/download/index.html

The last hints are fixed. So, when nothing else comes in we should be
ready to go live with the new DL webages.


Everything looks nice, thanks! (just, maybe in other_tables.html the 
checksum links could be made in a smaller font size than "exe").


There is still one small issue to correct, but I'm not sure whether this 
is something Marcus can modify, so CCing Roberto.


After I start the download (so, I am already on the SF page) I see:

Thanks for downloading Apache OpenOffice, the free and open productivity 
suite. We invite you to learn more about how to enhance your experience 
with OpenOffice; sign up to receive important notifications and learn 
how you can contribute to make the next version of OpenOffice even better.


This text is OK, but it has two links that should be updated:
ooo-announce-subscr...@incubator.apache.org
-> announce-subscr...@openoffice.apache.org
http://incubator.apache.org/openofficeorg/get-involved.html
-> http://openoffice.apache.org/get-involved.html

Regards,
  Andrea.

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

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 12:35 PM, Marcus (OOo)  wrote:

> Am 07/22/2013 08:00 PM, schrieb Marcus (OOo):
>
>  OK, I've updated the DL webpages.
>>
>> After fixing some broken links, I think it's OK and ready for a review:
>>
>> http://ooo-site.staging.**apache.org/download/index.html
>>
>
> The last hints are fixed. So, when nothing else comes in we should be
> ready to go live with the new DL webages.
>
> Furthermore, the project's download webpage is also updated, of course
> until now just staged:
>
> http://openoffice.staging.**apache.org/downloads4test.html
>
>
>  Only then I will publish to the live server.
>>
>
> Before the night is coming I can finalize and publish the project's
> download webpage.
>

sounds good to me!


>
> The main download webpage can be published at any time when you see fit.
>
>
> Marcus
>
>
>
>  Am 07/22/2013 07:08 PM, schrieb Kay Schenk:
>>
>>> On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)
>>> wrote:
>>>
>>>  Am 07/22/2013 05:49 PM, schrieb Kay Schenk:

 On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir wrote:

>
> Can we do something like this?
>
>>
>> Two stage: release and announce.
>>
>>
>  This was already planned to do.


 Release == put the 4.0 files into production on SourceForge, update

> our download web page to serve 4.0 files by default.
>>
>> Announce == go live with news on front page, header announcement on
>> every page (branding.mdtext), announcement email, blog post, social
>> media, new logo on website, etc.
>>
>> For the Release part, can we do that end-of-day today, say in a
>> couple of hours?
>>
>>
>  Hm, in a couple of hours it's bed time in Hamburg, So, I need to
 publish
 the new things earlier. I think in 1 or 2 hours, then I have some
 time to
 correct faulty things.

>>>
>>>
>>> Yep! Do it! I think this is what Rob meant. We do the bulk of the DL
>>> stuff
>>> WITHOUT the rebranding until tomorrow.
>>>
>>>
>>>
 For the announcement part, this waits for the ASF press release to go

> out tomorrow (Tuesday) at 6am New York time.
>>
>> This will give us some time today to:
>>
>> 1) verify the downloads are working
>> 2) add the correct download links to the NL pages.
>>
>>
>  Marcus




 A sterling idea! and one I was thinking about also! +1 

>
> I was just about to suggest holding off on the web site "branding"
> changes
> until much later today. But, this idea is better.
>
> Re site branding updates -- later today (1700 PDT? or suggest something
> an
> alternate time) after 'Release' stage, I will commit/port branding/site
> changes to staging -- they're not there yet -- so someone else can
> publish
> this if need be. I will NOT be available at 0600 EDT -- later like 1100
> EDT
> probably.
>

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


-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: Release coordination proposal


Am 07/22/2013 09:45 PM, schrieb Rob Weir:

On Mon, Jul 22, 2013 at 2:00 PM, Marcus (OOo)  wrote:

OK, I've updated the DL webpages.

After fixing some broken links, I think it's OK and ready for a review:

http://ooo-site.staging.apache.org/download/index.html



The small print under the download box has two lines for me:

Get all platforms, languages, language packs | Source Code tarballs and SDK |

and

Signatures and Hashes: ASC , MD5 , SHA256 | Release Notes | Legacy Version


1) Is the first line supposed to end with a '|' character?


Yes, a kind of intended line-break. Formerly it was a one-liner but the 
line-break was never appropriate.



2) What should the "legacy" link go to now?  Is 3.3.0 still "legacy"?
If so, what is "3.4.1"?   We might need to reword and restructure that
destination page, but I think it is OK for now.


In this context I understand "legacy release" as a release from a former 
instance - here Sun/Oracle. With the planned EOL for 3.4 this can be 
cleaned-up, too.



Only then I will publish to the live server.



I verified download of the binaries, source and hash files, from a
Windows 7 machine running Firefox.  It looks good, Marcus!


Thanks

Marcus




Am 07/22/2013 07:08 PM, schrieb Kay Schenk:


On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)
wrote:


Am 07/22/2013 05:49 PM, schrieb Kay Schenk:

   On Mon, Jul 22, 2013 at 8:16 AM, Rob Weirwrote:



   Can we do something like this?



Two stage:  release and announce.




This was already planned to do.


   Release == put the 4.0 files into production on SourceForge, update


our download web page to serve 4.0 files by default.

Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part,  can we do that end-of-day today, say in a
couple of hours?




Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish
the new things earlier. I think in 1 or 2 hours, then I have some time to
correct faulty things.




Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL
stuff
WITHOUT the rebranding until tomorrow.




   For the announcement part, this waits for the ASF press release to go


out tomorrow (Tuesday) at 6am New York time.

This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.




Marcus




   A sterling idea! and one I was thinking about also! +1 



I was just about to suggest holding off on the web site "branding"
changes
until much later today.  But, this idea is better.

Re site branding updates -- later  today (1700 PDT? or suggest something
an
alternate time)  after 'Release' stage, I will commit/port branding/site
changes to staging -- they're not there yet -- so someone else can
publish
this if need be. I will NOT be available at 0600 EDT -- later like 1100
EDT
probably.


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

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 2:00 PM, Marcus (OOo)  wrote:
> OK, I've updated the DL webpages.
>
> After fixing some broken links, I think it's OK and ready for a review:
>
> http://ooo-site.staging.apache.org/download/index.html
>

The small print under the download box has two lines for me:

Get all platforms, languages, language packs | Source Code tarballs and SDK |

and

Signatures and Hashes: ASC , MD5 , SHA256 | Release Notes | Legacy Version


1) Is the first line supposed to end with a '|' character?

2) What should the "legacy" link go to now?  Is 3.3.0 still "legacy"?
If so, what is "3.4.1"?   We might need to reword and restructure that
destination page, but I think it is OK for now.

> Only then I will publish to the live server.
>

I verified download of the binaries, source and hash files, from a
Windows 7 machine running Firefox.  It looks good, Marcus!

-Rob



> Marcus
>
>
>
> Am 07/22/2013 07:08 PM, schrieb Kay Schenk:
>
>> On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)
>> wrote:
>>
>>> Am 07/22/2013 05:49 PM, schrieb Kay Schenk:
>>>
>>>   On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir   wrote:


   Can we do something like this?
>
>
> Two stage:  release and announce.
>

>>> This was already planned to do.
>>>
>>>
>>>   Release == put the 4.0 files into production on SourceForge, update
>
> our download web page to serve 4.0 files by default.
>
> Announce == go live with news on front page, header announcement on
> every page (branding.mdtext), announcement email, blog post, social
> media, new logo on website, etc.
>
> For the Release part,  can we do that end-of-day today, say in a
> couple of hours?
>

>>> Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish
>>> the new things earlier. I think in 1 or 2 hours, then I have some time to
>>> correct faulty things.
>>
>>
>>
>> Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL
>> stuff
>> WITHOUT the rebranding until tomorrow.
>>
>>
>>>
>>>   For the announcement part, this waits for the ASF press release to go
>
> out tomorrow (Tuesday) at 6am New York time.
>
> This will give us some time today to:
>
> 1) verify the downloads are working
> 2) add the correct download links to the NL pages.
>

>>> Marcus
>>>
>>>
>>>
>>>
>>>   A sterling idea! and one I was thinking about also! +1 


 I was just about to suggest holding off on the web site "branding"
 changes
 until much later today.  But, this idea is better.

 Re site branding updates -- later  today (1700 PDT? or suggest something
 an
 alternate time)  after 'Release' stage, I will commit/port branding/site
 changes to staging -- they're not there yet -- so someone else can
 publish
 this if need be. I will NOT be available at 0600 EDT -- later like 1100
 EDT
 probably.
>
>
> -
> 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: Release coordination proposal


Am 07/22/2013 08:00 PM, schrieb Marcus (OOo):

OK, I've updated the DL webpages.

After fixing some broken links, I think it's OK and ready for a review:

http://ooo-site.staging.apache.org/download/index.html


The last hints are fixed. So, when nothing else comes in we should be 
ready to go live with the new DL webages.


Furthermore, the project's download webpage is also updated, of course 
until now just staged:


http://openoffice.staging.apache.org/downloads4test.html


Only then I will publish to the live server.


Before the night is coming I can finalize and publish the project's 
download webpage.


The main download webpage can be published at any time when you see fit.

Marcus




Am 07/22/2013 07:08 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)
wrote:


Am 07/22/2013 05:49 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir wrote:


Can we do something like this?


Two stage: release and announce.




This was already planned to do.


Release == put the 4.0 files into production on SourceForge, update

our download web page to serve 4.0 files by default.

Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part, can we do that end-of-day today, say in a
couple of hours?




Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish
the new things earlier. I think in 1 or 2 hours, then I have some
time to
correct faulty things.



Yep! Do it! I think this is what Rob meant. We do the bulk of the DL
stuff
WITHOUT the rebranding until tomorrow.




For the announcement part, this waits for the ASF press release to go

out tomorrow (Tuesday) at 6am New York time.

This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.




Marcus




A sterling idea! and one I was thinking about also! +1 


I was just about to suggest holding off on the web site "branding"
changes
until much later today. But, this idea is better.

Re site branding updates -- later today (1700 PDT? or suggest something
an
alternate time) after 'Release' stage, I will commit/port branding/site
changes to staging -- they're not there yet -- so someone else can
publish
this if need be. I will NOT be available at 0600 EDT -- later like 1100
EDT
probably.


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

[SourceForge] New defaults for AOO 4.0.0 release


https://sourceforge.net/projects/openofficeorg.mirror/

SourceForge has a nice feature that the green download button provides 
you with the respective build for your (or better: recognized) OS.


Up to now it's AOO 3.4.1.

I'll update this for AOO 4.0.0.

Marcus

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

Re: Release coordination proposal


Am 07/22/2013 09:17 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 11:59 AM, Marcus (OOo)  wrote:


Am 07/22/2013 08:28 PM, schrieb Kay Schenk:


On Mon, Jul 22, 2013 at 11:00 AM, Marcus (OOo)
  wrote:

  OK, I've updated the DL webpages.


After fixing some broken links, I think it's OK and ready for a review:

http://ooo-site.staging.**apac**he.org/download/index.html
http://ooo-site.staging.apache.org/download/index.html>





Only then I will publish to the live server.

Marcus



So far, all I found was the checksums  link in the right hand column goes
to checksums for 3.4.1.



Yes, I've commented it out for the moment.

@All:
I've re-designed the "other.html", so that all checksums are offered
together with the binary in a single table cell (depending for the
respective OS and language). See here:

http://ooo-site.staging.**apache.org/download/test/**other_tables.html

With this we a) don't need a separate webpage just for checksums and b)
have all links in a single place.

PS:
The URLs do not work yet but you can see the design and the intented way
how it should work.

Marcus



Assuming a link can be found for the user,  they can use the links at the
bottom of the green DL box to get the checksum appropriate to their
selection.

  So the problem is for folks who can NOT find an acceptable DL.

I would say if you can get the incorrect URL situation fixed quickly, we
should go with the new "other" page. Or, leave things as they are now, and
maybe wait until after main release to work on this.


I think I can finalize this until next weekend.

Marcus




  Am 07/22/2013 07:08 PM, schrieb Kay Schenk:


   On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)


   wrote:

   Am 07/22/2013 05:49 PM, schrieb Kay Schenk:



On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir
  wrote:



Can we do something like this?



Two stage:  release and announce.


This was already planned to do.





Release == put the 4.0 files into production on SourceForge, update

  our download web page to serve 4.0 files by default.




Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part,  can we do that end-of-day today, say in a
couple of hours?


Hm, in a couple of hours it's bed time in Hamburg, So, I need to



publish
the new things earlier. I think in 1 or 2 hours, then I have some time
to
correct faulty things.




Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL
stuff
WITHOUT the rebranding until tomorrow.



 For the announcement part, this waits for the ASF press release to

go

  out tomorrow (Tuesday) at 6am New York time.




This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.


Marcus







A sterling idea! and one I was thinking about also! +1 



I was just about to suggest holding off on the web site "branding"
changes
until much later today.  But, this idea is better.

Re site branding updates -- later  today (1700 PDT? or suggest
something
an
alternate time)  after 'Release' stage, I will commit/port
branding/site
changes to staging -- they're not there yet -- so someone else can
publish
this if need be. I will NOT be available at 0600 EDT -- later like
1100
EDT
probably.


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

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 11:59 AM, Marcus (OOo)  wrote:

> Am 07/22/2013 08:28 PM, schrieb Kay Schenk:
>
>> On Mon, Jul 22, 2013 at 11:00 AM, Marcus (OOo)
>>  wrote:
>>
>>  OK, I've updated the DL webpages.
>>>
>>> After fixing some broken links, I think it's OK and ready for a review:
>>>
>>> http://ooo-site.staging.**apac**he.org/download/index.html
>>> http://ooo-site.staging.apache.org/download/index.html>
>>> >
>>>
>>>
>>> Only then I will publish to the live server.
>>>
>>> Marcus
>>>
>>>
>> So far, all I found was the checksums  link in the right hand column goes
>> to checksums for 3.4.1.
>>
>
> Yes, I've commented it out for the moment.
>
> @All:
> I've re-designed the "other.html", so that all checksums are offered
> together with the binary in a single table cell (depending for the
> respective OS and language). See here:
>
> http://ooo-site.staging.**apache.org/download/test/**other_tables.html
>
> With this we a) don't need a separate webpage just for checksums and b)
> have all links in a single place.
>
> PS:
> The URLs do not work yet but you can see the design and the intented way
> how it should work.
>
> Marcus


Assuming a link can be found for the user,  they can use the links at the
bottom of the green DL box to get the checksum appropriate to their
selection.

 So the problem is for folks who can NOT find an acceptable DL.

I would say if you can get the incorrect URL situation fixed quickly, we
should go with the new "other" page. Or, leave things as they are now, and
maybe wait until after main release to work on this.


>
>
>
>  Am 07/22/2013 07:08 PM, schrieb Kay Schenk:
>>>
>>>   On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)
>>>
   wrote:

   Am 07/22/2013 05:49 PM, schrieb Kay Schenk:

>
>On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir
>  wrote:
>
>
>>Can we do something like this?
>>
>>
>>> Two stage:  release and announce.
>>>
>>>
>>>This was already planned to do.
>>
>
>
>Release == put the 4.0 files into production on SourceForge, update
>
>  our download web page to serve 4.0 files by default.
>>
>>>
>>> Announce == go live with news on front page, header announcement on
>>> every page (branding.mdtext), announcement email, blog post, social
>>> media, new logo on website, etc.
>>>
>>> For the Release part,  can we do that end-of-day today, say in a
>>> couple of hours?
>>>
>>>
>>>Hm, in a couple of hours it's bed time in Hamburg, So, I need to
>>
> publish
> the new things earlier. I think in 1 or 2 hours, then I have some time
> to
> correct faulty things.
>
>

 Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL
 stuff
 WITHOUT the rebranding until tomorrow.



 For the announcement part, this waits for the ASF press release to
> go
>
>  out tomorrow (Tuesday) at 6am New York time.
>>
>>>
>>> This will give us some time today to:
>>>
>>> 1) verify the downloads are working
>>> 2) add the correct download links to the NL pages.
>>>
>>>
>>>Marcus
>>
>
>
>
>
>A sterling idea! and one I was thinking about also! +1 
>
>
>> I was just about to suggest holding off on the web site "branding"
>> changes
>> until much later today.  But, this idea is better.
>>
>> Re site branding updates -- later  today (1700 PDT? or suggest
>> something
>> an
>> alternate time)  after 'Release' stage, I will commit/port
>> branding/site
>> changes to staging -- they're not there yet -- so someone else can
>> publish
>> this if need be. I will NOT be available at 0600 EDT -- later like
>> 1100
>> EDT
>> probably.
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: Release coordination proposal

Am 07/22/2013 08:24 PM, schrieb Manuel del Valle:

Date: Mon, 22 Jul 2013 20:00:21 +0200
From: marcus.m...@wtnet.de
To: dev@openoffice.apache.org
Subject: Re: Release coordination proposal

OK, I've updated the DL webpages.

After fixing some broken links, I think it's OK and ready for a review:

http://ooo-site.staging.apache.org/download/index.html

Only then I will publish to the live server.

Marcus

I noticed just two little details:

- When I hover over the "Download Apache Open Office 4.0.0" string, I get a caption 
"Version - Milestone - Build - SVN rNº"
When I hover over the "Click here [...] Windows (EXE) and Español" string, I get a 
caption "http://sourceforge.net";
Is that difference intended?

Ah, good catch. I've fixed it.

- The "Release Notes" link links (yes, that's what it does;) to the editable version of 
the cwiki Release Notes, instead of the "fixed" HTML. Is that correct?

Hm, I like it as it is better formatted.

Marcus

Am 07/22/2013 07:08 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)   wrote:

Am 07/22/2013 05:49 PM, schrieb Kay Schenk:

   On Mon, Jul 22, 2013 at 8:16 AM, Rob Weirwrote:

   Can we do something like this?

Two stage:  release and announce.

This was already planned to do.

   Release == put the 4.0 files into production on SourceForge, update

our download web page to serve 4.0 files by default.

Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part,  can we do that end-of-day today, say in a
couple of hours?

Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish
the new things earlier. I think in 1 or 2 hours, then I have some time to
correct faulty things.

Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL stuff
WITHOUT the rebranding until tomorrow.

   For the announcement part, this waits for the ASF press release to go

out tomorrow (Tuesday) at 6am New York time.

This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.

Marcus

   A sterling idea! and one I was thinking about also! +1 

I was just about to suggest holding off on the web site "branding" changes
until much later today.  But, this idea is better.

Re site branding updates -- later  today (1700 PDT? or suggest something
an
alternate time)  after 'Release' stage, I will commit/port branding/site
changes to staging -- they're not there yet -- so someone else can publish
this if need be. I will NOT be available at 0600 EDT -- later like 1100
EDT
probably.

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

Re: Release coordination proposal


Am 07/22/2013 08:28 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 11:00 AM, Marcus (OOo)  wrote:


OK, I've updated the DL webpages.

After fixing some broken links, I think it's OK and ready for a review:

http://ooo-site.staging.**apache.org/download/index.html

Only then I will publish to the live server.

Marcus



So far, all I found was the checksums  link in the right hand column goes
to checksums for 3.4.1.


Yes, I've commented it out for the moment.

@All:
I've re-designed the "other.html", so that all checksums are offered 
together with the binary in a single table cell (depending for the 
respective OS and language). See here:


http://ooo-site.staging.apache.org/download/test/other_tables.html

With this we a) don't need a separate webpage just for checksums and b) 
have all links in a single place.


PS:
The URLs do not work yet but you can see the design and the intented way 
how it should work.


Marcus




Am 07/22/2013 07:08 PM, schrieb Kay Schenk:

  On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)

  wrote:

  Am 07/22/2013 05:49 PM, schrieb Kay Schenk:


   On Mon, Jul 22, 2013 at 8:16 AM, Rob Weirwrote:



   Can we do something like this?



Two stage:  release and announce.



  This was already planned to do.



   Release == put the 4.0 files into production on SourceForge, update


our download web page to serve 4.0 files by default.


Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part,  can we do that end-of-day today, say in a
couple of hours?



  Hm, in a couple of hours it's bed time in Hamburg, So, I need to

publish
the new things earlier. I think in 1 or 2 hours, then I have some time to
correct faulty things.




Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL
stuff
WITHOUT the rebranding until tomorrow.




   For the announcement part, this waits for the ASF press release to go


out tomorrow (Tuesday) at 6am New York time.


This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.



  Marcus





   A sterling idea! and one I was thinking about also! +1 



I was just about to suggest holding off on the web site "branding"
changes
until much later today.  But, this idea is better.

Re site branding updates -- later  today (1700 PDT? or suggest something
an
alternate time)  after 'Release' stage, I will commit/port branding/site
changes to staging -- they're not there yet -- so someone else can
publish
this if need be. I will NOT be available at 0600 EDT -- later like 1100
EDT
probably.


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

Re: Release coordination proposal

Am 07/22/2013 08:30 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 11:24 AM, Manuel del Valle  wrote:

Date: Mon, 22 Jul 2013 20:00:21 +0200
From: marcus.m...@wtnet.de
To: dev@openoffice.apache.org
Subject: Re: Release coordination proposal

OK, I've updated the DL webpages.

After fixing some broken links, I think it's OK and ready for a review:

http://ooo-site.staging.apache.org/download/index.html

Only then I will publish to the live server.

Marcus

I noticed just two little details:

- When I hover over the "Download Apache Open Office 4.0.0" string, I get
a caption "Version - Milestone - Build - SVN rNº"
When I hover over the "Click here [...] Windows (EXE) and Español" string,
I get a caption "http://sourceforge.net";
Is that difference intended?

I think these may be "new" features! :) I like this!

Yes, I thought it would be more infomative to show some version 
information about the downloadable installation file instead of showing 
the download link to SourceForge as it is shown anyway when finally 
clicking.

Marcus

- The "Release Notes" link links (yes, that's what it does;) to the
editable version of the cwiki Release Notes, instead of the "fixed" HTML.
Is that correct?

Yes, this is correct.

HTH

Cheers!

Am 07/22/2013 07:08 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)

  wrote:

Am 07/22/2013 05:49 PM, schrieb Kay Schenk:

   On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir

wrote:

   Can we do something like this?

Two stage:  release and announce.

This was already planned to do.

   Release == put the 4.0 files into production on SourceForge, update

our download web page to serve 4.0 files by default.

Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part,  can we do that end-of-day today, say in a
couple of hours?

Hm, in a couple of hours it's bed time in Hamburg, So, I need to

publish

the new things earlier. I think in 1 or 2 hours, then I have some time

to

correct faulty things.

Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL

stuff

WITHOUT the rebranding until tomorrow.

   For the announcement part, this waits for the ASF press release to go

out tomorrow (Tuesday) at 6am New York time.

This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.

Marcus

   A sterling idea! and one I was thinking about also! +1 

I was just about to suggest holding off on the web site "branding"

changes

until much later today.  But, this idea is better.

Re site branding updates -- later  today (1700 PDT? or suggest

something

an
alternate time)  after 'Release' stage, I will commit/port

branding/site

changes to staging -- they're not there yet -- so someone else can

publish

this if need be. I will NOT be available at 0600 EDT -- later like

1100

EDT
probably.

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

Extension Options Page

2013-07-22 Thread Rajath Shashidhara

Hello,

The wikipage:
http://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/Saving_and_Reading_Data_for_the_Options_Page
contains
example code which listens to "external_event". When is this
"external_event" triggered? How do I link events to actions like mouse
click, etc?

-- 
Rajath S,
M.Sc(Hons.) Physics,
Birla Institute of Technology and Science - Pilani,
Pilani

Re: [RESULT][VOTE]: Release OpenOffice 4.0 (RC2)

2013-07-22 Thread imacat

On 2013/07/20 06:26, Juergen Schmidt said:
> Am Freitag, 19. Juli 2013 um 19:46 schrieb Andrea Pescetti:
>> Dave Fisher wrote:
>>> On Jul 19, 2013, at 9:09 AM, janI wrote:
 It is in principle no good, that a single person decides if a vote is valid
 or not, it sort of invalidates the idea of voting.

Hmm... ^^;  I did not notice this following discussion.

I suppose we are counting the votes, not the comments after the
votes.  That is, whether I comment as "for the release blocker #" or
"for missing the Traditional Chinese version" or "bc'z I'm krazzzy"
is irrelevant to my vote.  The interpretation of the comments belong to
the [DISCUSS] thread, not to this [VOTE] thread.

So please still count me as -1, although this does not affect the
result of the votes.  I have to present my position as a member of our
local community.

Nevertheless, this release is great!  It's really pity for me not
able to involve in the process of this release.  Thanks to Juergen and
everybody on your hard work on this release.

>>>
>>> imacat's VOTE was not a Veto as you cannot veto a release.
>>>
>>
>>
>> Enough misunderstandings here (I think that Jan was saying: Juergen 
>> cannot decide by himself whether a -1 is valid...).
>>
>> Anyway, let's update the tally to 24 "+1" votes (14 binding) and 1 "-1" 
>> vote (imacat, binding) and move on.
>>
>> As Juergen already wrote, we remain committed to make the traditional 
>> Chinese version available at the earliest occasion, it is already at 
>> 100% but it simply came too late to build/include it. In the meantime, 
>> it will be available as snapshot build.
>>
>>
> 
> do whatever you want, from my point of view imacat voted on something that 
> wasn't part of the vote. It remains an invalid vote for me.
> 
> Juergen
>>
>> Regards,
>> Andrea.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>
> 
> 
> 

-- 
Best regards,
imacat ^_*' 
PGP Key http://www.imacat.idv.tw/me/pgpkey.asc

<> News: http://www.wov.idv.tw/
Tavern IMACAT's http://www.imacat.idv.tw/
Woman in FOSS in Taiwan http://wofoss.blogspot.com/
OpenOffice http://www.openoffice.org/
EducOO/OOo4Kids Taiwan http://www.educoo.tw/
Greenfoot Taiwan http://greenfoot.westart.tw/

signature.asc
Description: OpenPGP digital signature

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 11:24 AM, Manuel del Valle  wrote:

> > Date: Mon, 22 Jul 2013 20:00:21 +0200
> > From: marcus.m...@wtnet.de
> > To: dev@openoffice.apache.org
> > Subject: Re: Release coordination proposal
> >
> > OK, I've updated the DL webpages.
> >
> > After fixing some broken links, I think it's OK and ready for a review:
> >
> > http://ooo-site.staging.apache.org/download/index.html
> >
> > Only then I will publish to the live server.
> >
> > Marcus
> >
>
>
> I noticed just two little details:
>
> - When I hover over the "Download Apache Open Office 4.0.0" string, I get
> a caption "Version - Milestone - Build - SVN rNº"
> When I hover over the "Click here [...] Windows (EXE) and Español" string,
> I get a caption "http://sourceforge.net";
> Is that difference intended?
>

I think these may be "new" features! :) I like this!


>
> - The "Release Notes" link links (yes, that's what it does;) to the
> editable version of the cwiki Release Notes, instead of the "fixed" HTML.
> Is that correct?
>

Yes, this is correct.


>
> HTH
>
> Cheers!
>
>
> >
> >
> > Am 07/22/2013 07:08 PM, schrieb Kay Schenk:
> >> On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)
>  wrote:
> >>
> >>> Am 07/22/2013 05:49 PM, schrieb Kay Schenk:
> >>>
> >>>   On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir
> wrote:
> 
>    Can we do something like this?
> >
> > Two stage:  release and announce.
> >
> 
> >>> This was already planned to do.
> >>>
> >>>
> >>>   Release == put the 4.0 files into production on SourceForge, update
> > our download web page to serve 4.0 files by default.
> >
> > Announce == go live with news on front page, header announcement on
> > every page (branding.mdtext), announcement email, blog post, social
> > media, new logo on website, etc.
> >
> > For the Release part,  can we do that end-of-day today, say in a
> > couple of hours?
> >
> 
> >>> Hm, in a couple of hours it's bed time in Hamburg, So, I need to
> publish
> >>> the new things earlier. I think in 1 or 2 hours, then I have some time
> to
> >>> correct faulty things.
> >>
> >>
> >> Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL
> stuff
> >> WITHOUT the rebranding until tomorrow.
> >>
> >>
> >>>
> >>>   For the announcement part, this waits for the ASF press release to go
> > out tomorrow (Tuesday) at 6am New York time.
> >
> > This will give us some time today to:
> >
> > 1) verify the downloads are working
> > 2) add the correct download links to the NL pages.
> >
> 
> >>> Marcus
> >>>
> >>>
> >>>
> >>>
> >>>   A sterling idea! and one I was thinking about also! +1 
> 
>  I was just about to suggest holding off on the web site "branding"
> changes
>  until much later today.  But, this idea is better.
> 
>  Re site branding updates -- later  today (1700 PDT? or suggest
> something
>  an
>  alternate time)  after 'Release' stage, I will commit/port
> branding/site
>  changes to staging -- they're not there yet -- so someone else can
> publish
>  this if need be. I will NOT be available at 0600 EDT -- later like
> 1100
>  EDT
>  probably.
> >
> > -
> > 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
>
>


-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 11:00 AM, Marcus (OOo)  wrote:

> OK, I've updated the DL webpages.
>
> After fixing some broken links, I think it's OK and ready for a review:
>
> http://ooo-site.staging.**apache.org/download/index.html
>
> Only then I will publish to the live server.
>
> Marcus
>

So far, all I found was the checksums  link in the right hand column goes
to checksums for 3.4.1.





>
>
> Am 07/22/2013 07:08 PM, schrieb Kay Schenk:
>
>  On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)
>>  wrote:
>>
>>  Am 07/22/2013 05:49 PM, schrieb Kay Schenk:
>>>
>>>   On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir   wrote:
>>>

   Can we do something like this?

>
> Two stage:  release and announce.
>
>
  This was already planned to do.
>>>
>>>
>>>   Release == put the 4.0 files into production on SourceForge, update
>>>
 our download web page to serve 4.0 files by default.
>
> Announce == go live with news on front page, header announcement on
> every page (branding.mdtext), announcement email, blog post, social
> media, new logo on website, etc.
>
> For the Release part,  can we do that end-of-day today, say in a
> couple of hours?
>
>
  Hm, in a couple of hours it's bed time in Hamburg, So, I need to
>>> publish
>>> the new things earlier. I think in 1 or 2 hours, then I have some time to
>>> correct faulty things.
>>>
>>
>>
>> Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL
>> stuff
>> WITHOUT the rebranding until tomorrow.
>>
>>
>>
>>>   For the announcement part, this waits for the ASF press release to go
>>>
 out tomorrow (Tuesday) at 6am New York time.
>
> This will give us some time today to:
>
> 1) verify the downloads are working
> 2) add the correct download links to the NL pages.
>
>
  Marcus
>>>
>>>
>>>
>>>
>>>   A sterling idea! and one I was thinking about also! +1 
>>>

 I was just about to suggest holding off on the web site "branding"
 changes
 until much later today.  But, this idea is better.

 Re site branding updates -- later  today (1700 PDT? or suggest something
 an
 alternate time)  after 'Release' stage, I will commit/port branding/site
 changes to staging -- they're not there yet -- so someone else can
 publish
 this if need be. I will NOT be available at 0600 EDT -- later like 1100
 EDT
 probably.

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


-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

RE: Release coordination proposal

2013-07-22 Thread Manuel del Valle

> Date: Mon, 22 Jul 2013 20:00:21 +0200
> From: marcus.m...@wtnet.de
> To: dev@openoffice.apache.org
> Subject: Re: Release coordination proposal
> 
> OK, I've updated the DL webpages.
> 
> After fixing some broken links, I think it's OK and ready for a review:
> 
> http://ooo-site.staging.apache.org/download/index.html
> 
> Only then I will publish to the live server.
> 
> Marcus
> 


I noticed just two little details:

- When I hover over the "Download Apache Open Office 4.0.0" string, I get a 
caption "Version - Milestone - Build - SVN rNº"
When I hover over the "Click here [...] Windows (EXE) and Español" string, I 
get a caption "http://sourceforge.net";
Is that difference intended?

- The "Release Notes" link links (yes, that's what it does;) to the editable 
version of the cwiki Release Notes, instead of the "fixed" HTML. Is that 
correct?

HTH

Cheers!


> 
> 
> Am 07/22/2013 07:08 PM, schrieb Kay Schenk:
>> On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)  wrote:
>>
>>> Am 07/22/2013 05:49 PM, schrieb Kay Schenk:
>>>
>>>   On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir   wrote:

   Can we do something like this?
>
> Two stage:  release and announce.
>

>>> This was already planned to do.
>>>
>>>
>>>   Release == put the 4.0 files into production on SourceForge, update
> our download web page to serve 4.0 files by default.
>
> Announce == go live with news on front page, header announcement on
> every page (branding.mdtext), announcement email, blog post, social
> media, new logo on website, etc.
>
> For the Release part,  can we do that end-of-day today, say in a
> couple of hours?
>

>>> Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish
>>> the new things earlier. I think in 1 or 2 hours, then I have some time to
>>> correct faulty things.
>>
>>
>> Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL stuff
>> WITHOUT the rebranding until tomorrow.
>>
>>
>>>
>>>   For the announcement part, this waits for the ASF press release to go
> out tomorrow (Tuesday) at 6am New York time.
>
> This will give us some time today to:
>
> 1) verify the downloads are working
> 2) add the correct download links to the NL pages.
>

>>> Marcus
>>>
>>>
>>>
>>>
>>>   A sterling idea! and one I was thinking about also! +1 

 I was just about to suggest holding off on the web site "branding" changes
 until much later today.  But, this idea is better.

 Re site branding updates -- later  today (1700 PDT? or suggest something
 an
 alternate time)  after 'Release' stage, I will commit/port branding/site
 changes to staging -- they're not there yet -- so someone else can publish
 this if need be. I will NOT be available at 0600 EDT -- later like 1100
 EDT
 probably.
> 
> -
> 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: Release coordination proposal


OK, I've updated the DL webpages.

After fixing some broken links, I think it's OK and ready for a review:

http://ooo-site.staging.apache.org/download/index.html

Only then I will publish to the live server.

Marcus



Am 07/22/2013 07:08 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)  wrote:


Am 07/22/2013 05:49 PM, schrieb Kay Schenk:

  On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir   wrote:


  Can we do something like this?


Two stage:  release and announce.




This was already planned to do.


  Release == put the 4.0 files into production on SourceForge, update

our download web page to serve 4.0 files by default.

Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part,  can we do that end-of-day today, say in a
couple of hours?




Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish
the new things earlier. I think in 1 or 2 hours, then I have some time to
correct faulty things.



Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL stuff
WITHOUT the rebranding until tomorrow.




  For the announcement part, this waits for the ASF press release to go

out tomorrow (Tuesday) at 6am New York time.

This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.




Marcus




  A sterling idea! and one I was thinking about also! +1 


I was just about to suggest holding off on the web site "branding" changes
until much later today.  But, this idea is better.

Re site branding updates -- later  today (1700 PDT? or suggest something
an
alternate time)  after 'Release' stage, I will commit/port branding/site
changes to staging -- they're not there yet -- so someone else can publish
this if need be. I will NOT be available at 0600 EDT -- later like 1100
EDT
probably.


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

Re: [DISCUSS] New localization requirements policy needed for releases

2013-07-22 Thread Andrew Rist



On 7/20/2013 1:19 PM, Andrea Pescetti wrote:

On 15/07/2013 Herbert Duerr wrote:

Currently the Windows buildbot of the SNAPSHOT tag does a weekly full
build of all languages:
http://ci.apache.org/projects/openoffice/#winsnap
Is any fully translated language missing from that list?


Yes, ast.


Should semi-translated languages be built too?


The following have less than 20.000 words left (means, 75%+ done, more 
or less) and should ideally be built too:

ca eu he hi id lt pl sv th tr

ok - I committed this change.


Regards,
  Andrea.

-
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

Extension toolbar compatibility and 4.0, again

2013-07-22 Thread Simon Kornblith

Hi,

I'm a developer with Zotero. We currently distribute a
LibreOffice/OpenOffice.org plugin for our software that provides rich citation
functionality in OpenOffice/LibreOffice/NeoOffice, as well as plugins for Word
for Mac and Word for Windows.

I've read through the previous thread on changes to the toolbar in 4.0
(http://mail-archives.apache.org/mod_mbox/openoffice-dev/201302.mbox/%3C51195E5E.304%40laposte.net%3E),
but I'd like to emphasize that the changes to toolbar functionality in AOO 4
are quite problematic for us, not because the change to Addons.xcu is hard, but
because having a separate extension for AOO 4 is somewhat of a nightmare from a
support and distribution perspective.

To give some background, users don't install our extension manually. Instead,
it is installed either by an optional Firefox extension (in Zotero for Firefox)
or automatically when our software is opened (in Zotero Standalone). At the
moment, the same extension works with NeoOffice 3.0+, OpenOffice.org 3.0-3.3,
AOO 3.4, LibreOffice 3.4-4.1.

Unless there's a way to create a single extension that works with AOO 4 and
LibreOffice or earlier versions of OOo, supporting AOO 4 would appear to
require the following changes:

1. Adapt the extension to work with Apache OpenOffice. This is actually the
easiest part.
2. Bundle two extensions with the LibreOffice plugin and Zotero Standalone (2MB
more download size) or modify the extension locally on install to use a
separate Addons.xcu file for AOO 4.
3. Detect AOO 4 and install a different extension there than we do in
LibreOffice, AOO 3.4, and OOo.
4. Find a way to make the extension fix itself when AOO is upgraded (is this
possible?), or at least present a dialog telling the user to reinstall the
extension from within Zotero.

While I realize that this is somewhat late in your release process, it would
make us much happier if AOO 4 could use an alternative Addons.xcu file
(Addons4.xcu?) if it exists. That way we wouldn't have to distribute multiple
extensions, and our toolbar wouldn't break for our users when they upgrade to
AOO 4. If this isn't a possibility, perhaps someone has a better suggestion for
how we should handle this?

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

Re: Pasting HTML not possible in AOO 4.0?

2013-07-22 Thread David Gerard

On 22 July 2013 15:10, Ricardo Berlasso  wrote:

> Copy-paste from web work without problems on native Linux binaries. Note
> that Linux clipboard works different from windows clipboard: I think that
> if you copy from a win firefox running on wine to the win AOO running on
> wine you'll have no problem, but copying from a Linux app and pasting to a
> win app running atop of wine... well, that's wine's problem/bug.


Specifically, this bug: http://bugs.winehq.org/show_bug.cgi?id=7372


- d.

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

Re: staged web server -- can we publish what's there now?


Am 07/22/2013 07:05 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 10:01 AM, Marcus (OOo)  wrote:


Am 07/22/2013 06:38 PM, schrieb Rob Weir:

  On Mon, Jul 22, 2013 at 12:21 PM, Marcus (OOo)

  wrote:


Am 07/22/2013 04:52 PM, schrieb Kay Schenk:

  Please see:


https://cms.apache.org/ooo-**site/publish?diff=1

Can we publish what is here?




IMHO yes.

The very most is from me. I've tried to fix many HTML errors from the view
point of the W3C Validator.

I've verified the commits on the staged webpages and they look still OK.


  Hm, I cannot login.


Maybe it's because of the current LDAP issue (see the today's mail to all
committers) but I cannot login.



Same happened to me.  But I was able to reset my id via
http://id.apache.org using the  "Forgot your password?" link.



Wow, great.

Now I can access Kay's link and do commits again.

Thanks a lot!


Marcus


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



ok -- done! a backlog of stuff some of which are needed to do anything
further...

@Marcus -- I won't be doing anything else until the main DL stuff is in.


OK, I will then go on in the other mail thread.

Marcus


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

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)  wrote:

> Am 07/22/2013 05:49 PM, schrieb Kay Schenk:
>
>  On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir  wrote:
>>
>>  Can we do something like this?
>>>
>>> Two stage:  release and announce.
>>>
>>
> This was already planned to do.
>
>
>  Release == put the 4.0 files into production on SourceForge, update
>>> our download web page to serve 4.0 files by default.
>>>
>>> Announce == go live with news on front page, header announcement on
>>> every page (branding.mdtext), announcement email, blog post, social
>>> media, new logo on website, etc.
>>>
>>> For the Release part,  can we do that end-of-day today, say in a
>>> couple of hours?
>>>
>>
> Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish
> the new things earlier. I think in 1 or 2 hours, then I have some time to
> correct faulty things.


Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL stuff
WITHOUT the rebranding until tomorrow.


>
>  For the announcement part, this waits for the ASF press release to go
>>> out tomorrow (Tuesday) at 6am New York time.
>>>
>>> This will give us some time today to:
>>>
>>> 1) verify the downloads are working
>>> 2) add the correct download links to the NL pages.
>>>
>>
> Marcus
>
>
>
>
>  A sterling idea! and one I was thinking about also! +1 
>>
>> I was just about to suggest holding off on the web site "branding" changes
>> until much later today.  But, this idea is better.
>>
>> Re site branding updates -- later  today (1700 PDT? or suggest something
>> an
>> alternate time)  after 'Release' stage, I will commit/port branding/site
>> changes to staging -- they're not there yet -- so someone else can publish
>> this if need be. I will NOT be available at 0600 EDT -- later like 1100
>> EDT
>> probably.
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: Pasting HTML not possible in AOO 4.0?

2013-07-22 Thread David Gerard

On 22 July 2013 15:10, Ricardo Berlasso  wrote:
> 2013/7/22 David Gerard 

>> Is this actually supposed to happen - no ability to c'n'p from a web
>> page - or will it be a weirdness of my setup? Admittedly I'm running
>> the Windows binary under Wine ...

> That's the answer... ;)
> Copy-paste from web work without problems on native Linux binaries. Note
> that Linux clipboard works different from windows clipboard: I think that
> if you copy from a win firefox running on wine to the win AOO running on
> wine you'll have no problem, but copying from a Linux app and pasting to a
> win app running atop of wine... well, that's wine's problem/bug.


Yeah, I just got Windows LO to do the same :-) Sorry to trouble the list!


- d.

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

Re: staged web server -- can we publish what's there now?

On Mon, Jul 22, 2013 at 10:01 AM, Marcus (OOo)  wrote:

> Am 07/22/2013 06:38 PM, schrieb Rob Weir:
>
>  On Mon, Jul 22, 2013 at 12:21 PM, Marcus (OOo)
>>  wrote:
>>
>>> Am 07/22/2013 04:52 PM, schrieb Kay Schenk:
>>>
>>>  Please see:

 https://cms.apache.org/ooo-**site/publish?diff=1

 Can we publish what is here?

>>>
> IMHO yes.
>
> The very most is from me. I've tried to fix many HTML errors from the view
> point of the W3C Validator.
>
> I've verified the commits on the staged webpages and they look still OK.
>
>
>  Hm, I cannot login.
>>>
>>> Maybe it's because of the current LDAP issue (see the today's mail to all
>>> committers) but I cannot login.
>>>
>>>
>> Same happened to me.  But I was able to reset my id via
>> http://id.apache.org using the  "Forgot your password?" link.
>>
>
> Wow, great.
>
> Now I can access Kay's link and do commits again.
>
> Thanks a lot!
>
>
> Marcus
>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
ok -- done! a backlog of stuff some of which are needed to do anything
further...

@Marcus -- I won't be doing anything else until the main DL stuff is in.


-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 11:49 AM, Kay Schenk  wrote:
> On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir  wrote:
>
>> Can we do something like this?
>>
>> Two stage:  release and announce.
>>
>> Release == put the 4.0 files into production on SourceForge, update
>> our download web page to serve 4.0 files by default.
>>
>> Announce == go live with news on front page, header announcement on
>> every page (branding.mdtext), announcement email, blog post, social
>> media, new logo on website, etc.
>>
>> For the Release part,  can we do that end-of-day today, say in a
>> couple of hours?
>>
>> For the announcement part, this waits for the ASF press release to go
>> out tomorrow (Tuesday) at 6am New York time.
>>
>> This will give us some time today to:
>>
>> 1) verify the downloads are working
>> 2) add the correct download links to the NL pages.
>>
>> -Rob
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>
> A sterling idea! and one I was thinking about also! +1 
>
> I was just about to suggest holding off on the web site "branding" changes
> until much later today.  But, this idea is better.
>
> Re site branding updates -- later  today (1700 PDT? or suggest something an
> alternate time)  after 'Release' stage, I will commit/port branding/site
> changes to staging -- they're not there yet -- so someone else can publish
> this if need be. I will NOT be available at 0600 EDT -- later like 1100 EDT
> probably.
>

That sounds good.   I'll set my alarm so I am up for 6am, but if
someone in Europe pushes this first then I'll just enjoy my coffee.

-Rob

>
>
> --
> -
> MzK
>
> Success is falling nine times and getting up ten."
>  -- Jon Bon Jovi

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

Re: staged web server -- can we publish what's there now?


Am 07/22/2013 06:38 PM, schrieb Rob Weir:

On Mon, Jul 22, 2013 at 12:21 PM, Marcus (OOo)  wrote:

Am 07/22/2013 04:52 PM, schrieb Kay Schenk:


Please see:

https://cms.apache.org/ooo-site/publish?diff=1

Can we publish what is here?


IMHO yes.

The very most is from me. I've tried to fix many HTML errors from the 
view point of the W3C Validator.


I've verified the commits on the staged webpages and they look still OK.


Hm, I cannot login.

Maybe it's because of the current LDAP issue (see the today's mail to all
committers) but I cannot login.



Same happened to me.  But I was able to reset my id via
http://id.apache.org using the  "Forgot your password?" link.


Wow, great.

Now I can access Kay's link and do commits again.

Thanks a lot!

Marcus


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

Release coordination proposal

Can we do something like this?

Two stage:  release and announce.

Release == put the 4.0 files into production on SourceForge, update
our download web page to serve 4.0 files by default.

Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part,  can we do that end-of-day today, say in a
couple of hours?

For the announcement part, this waits for the ASF press release to go
out tomorrow (Tuesday) at 6am New York time.

This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.

-Rob

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

Re: mwiki contact page.

On 22 July 2013 17:09, Rob Weir  wrote:

> On Mon, Jul 22, 2013 at 3:46 AM, janI  wrote:
> > On Jul 22, 2013 8:59 AM, "Marcus (OOo)"  wrote:
> >>
> >> Am 07/22/2013 04:46 AM, schrieb Kay Schenk:
> >>
> >>> On Jul 20, 2013 11:38 PM, "Andrea Pescetti"
>  wrote:
> 
> 
>  Rob Weir wrote:
> >
> >
> > Remember, the number of people who have admin-related questions about
> > the wiki are very, very, very few in number.  They will be best
> served
> > by directing them to some variation of a page like the one we have on
> > the main website:
> > http://www.openoffice.org/contact_us.html
> 
> 
> 
>  Why not linking directly to it then? It would be enough to add a
> section
> >>>
> >>> to
> 
>  http://www.openoffice.org/contact_us.html
>  like the following:
> 
>  * If you have technical problems with one of the OpenOffice
> websites...
>  - For problems with the www.openoffice.org site: contact
> >>>
> >>> dev@openoffice.apache.org and insert "[Website]" in the subject
> 
>  - For problems with the https://issues.apache.org/ooo/ site: contact
> >>>
> >>> aoo-bugzilla-ad...@apache.org
> 
>  - For problems with the wiki.openoffice.org site: contact
> >>>
> >>> dev@openoffice.apache.org and insert "[Mwiki]" in the subject
> 
>  - For problems with the https://translate.apache.org/ site: contact
> >>>
> >>> l...@openoffice.apache.org and insert "[Pootle]" in the subject
> 
> 
>  Regards,
> Andrea.
> >>>
> >>>
> >>> This suggestion looks very reasonable to me.
> >>
> >>
> >> In general also for me reasonable. But I don't want to rely on the
> > subject prefix that the users have to insert manually. Rather, I would
> use
> > some aliases to see where the mail come from.
> >>
> >> web-admin@ --> dev@
> >> wiki-admin@ --> dev@
> >>
> >> Marcus
> >>
> >
> > sounds good to me, even though I dont think it will make a huge
> difference'
> > having a contact link on wiki will cause trafic, and users pr
> defitinition
> > choose the easy road.
> >
>
> Yes, users are lazy, but they also know what they want.  They only
> write to the dev list if there is no other option that sounds closer
> to what they were looking for.
>
> So if we have have a page that gives them the appropriate options for
> support, reporting bugs, admin issues, etc., and order these
> appropriately on
> the page (most commonly needed at top), then we should do OK.  The
> idea that Dave had was to add these items to an existing contact page
> that already has these other options.
>
> So the issue is that 99.99% of the visitors to a wiki page, if they
> have a question, will have a product support question.  Some, but very
> few, will have an admin-related question.  It is OK to tell how to get
> admin help, but we need to make sure that we say, in the same place,
> how to get product support, and make the product support more
> prominent by listing it first.  That explains the ordering of
> information on the contact page:
>
> http://www.openoffice.org/contact_us.html
>
> It is not perfect, but it gets most people closer to where they want to be.
>
> which I why I wrote "sounds good to me".

Also, to the other idea, an alternative to a set of email aliases is
> to use URL's of the form:
> mailto:d...@openoffice.org?subject=[Pootle].
>
+1 that is a better idea, since we do not need to maintain extra virtual
mail adresses
(I did not know that trix, thats pretty cool)

rgds
jan I.


> Regards,
>
> -Rob
>
>
> > rgds
> > jan i
> >>
> >>
> >> -
> >> 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
>
>

apache-rat-incubating-0.8-bin.tar.bz2

Hi

apache-rat-incubating-0.8-bin.tar.bz2 is still referenced by configure
(trunk) that does not seem correct ?

I have filed BZ:


https://issues.apache.org/ooo/show_bug.cgi?id=122797

rgds
jan I.

Re: Release coordination proposal

On Mon, Jul 22, 2013 at 12:18 PM, Marcus (OOo)  wrote:
> Am 07/22/2013 05:49 PM, schrieb Kay Schenk:
>
>> On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir  wrote:
>>
>>> Can we do something like this?
>>>
>>> Two stage:  release and announce.
>
>
> This was already planned to do.
>
>
>>> Release == put the 4.0 files into production on SourceForge, update
>>> our download web page to serve 4.0 files by default.
>>>
>>> Announce == go live with news on front page, header announcement on
>>> every page (branding.mdtext), announcement email, blog post, social
>>> media, new logo on website, etc.
>>>
>>> For the Release part,  can we do that end-of-day today, say in a
>>> couple of hours?
>
>
> Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish the
> new things earlier. I think in 1 or 2 hours, then I have some time to
> correct faulty things.
>

Well, I did send that note an hour ago ;-)

-Rob

>
>>> For the announcement part, this waits for the ASF press release to go
>>> out tomorrow (Tuesday) at 6am New York time.
>>>
>>> This will give us some time today to:
>>>
>>> 1) verify the downloads are working
>>> 2) add the correct download links to the NL pages.
>
>
> Marcus
>
>
>
>
>> A sterling idea! and one I was thinking about also! +1 
>>
>> I was just about to suggest holding off on the web site "branding" changes
>> until much later today.  But, this idea is better.
>>
>> Re site branding updates -- later  today (1700 PDT? or suggest something
>> an
>> alternate time)  after 'Release' stage, I will commit/port branding/site
>> changes to staging -- they're not there yet -- so someone else can publish
>> this if need be. I will NOT be available at 0600 EDT -- later like 1100
>> EDT
>> probably.
>
>
> -
> 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: mwiki contact page.


Am 07/22/2013 05:16 PM, schrieb janI:

On 22 July 2013 17:09, Rob Weir  wrote:


On Mon, Jul 22, 2013 at 3:46 AM, janI  wrote:

On Jul 22, 2013 8:59 AM, "Marcus (OOo)"  wrote:


Am 07/22/2013 04:46 AM, schrieb Kay Schenk:


On Jul 20, 2013 11:38 PM, "Andrea Pescetti"

  wrote:



Rob Weir wrote:



Remember, the number of people who have admin-related questions about
the wiki are very, very, very few in number.  They will be best

served

by directing them to some variation of a page like the one we have on
the main website:
http://www.openoffice.org/contact_us.html




Why not linking directly to it then? It would be enough to add a

section


to


http://www.openoffice.org/contact_us.html
like the following:

* If you have technical problems with one of the OpenOffice

websites...

- For problems with the www.openoffice.org site: contact


dev@openoffice.apache.org and insert "[Website]" in the subject


- For problems with the https://issues.apache.org/ooo/ site: contact


aoo-bugzilla-ad...@apache.org


- For problems with the wiki.openoffice.org site: contact


dev@openoffice.apache.org and insert "[Mwiki]" in the subject


- For problems with the https://translate.apache.org/ site: contact


l...@openoffice.apache.org and insert "[Pootle]" in the subject



Regards,
Andrea.



This suggestion looks very reasonable to me.



In general also for me reasonable. But I don't want to rely on the

subject prefix that the users have to insert manually. Rather, I would

use

some aliases to see where the mail come from.


web-admin@ -->  dev@
wiki-admin@ -->  dev@

Marcus



sounds good to me, even though I dont think it will make a huge

difference'

having a contact link on wiki will cause trafic, and users pr

defitinition

choose the easy road.



Yes, users are lazy, but they also know what they want.  They only
write to the dev list if there is no other option that sounds closer
to what they were looking for.

So if we have have a page that gives them the appropriate options for
support, reporting bugs, admin issues, etc., and order these
appropriately on
the page (most commonly needed at top), then we should do OK.  The
idea that Dave had was to add these items to an existing contact page
that already has these other options.

So the issue is that 99.99% of the visitors to a wiki page, if they
have a question, will have a product support question.  Some, but very
few, will have an admin-related question.  It is OK to tell how to get
admin help, but we need to make sure that we say, in the same place,
how to get product support, and make the product support more
prominent by listing it first.  That explains the ordering of
information on the contact page:

http://www.openoffice.org/contact_us.html

It is not perfect, but it gets most people closer to where they want to be.

which I why I wrote "sounds good to me".


Also, to the other idea, an alternative to a set of email aliases is

to use URL's of the form:
mailto:d...@openoffice.org?subject=[Pootle].


+1 that is a better idea, since we do not need to maintain extra virtual
mail adresses
 (I did not know that trix, thats pretty cool)


Yes, with this formatting it's OK.

However, we should extend the "contact_us.html" were needed to point to 
this site from, e.g., Wiki or Forum. No need to create a new page for 
such purpose - ahm, if this was planned. ;-)


Marcus


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

Re: staged web server -- can we publish what's there now?

On Mon, Jul 22, 2013 at 12:21 PM, Marcus (OOo)  wrote:
> Am 07/22/2013 04:52 PM, schrieb Kay Schenk:
>
>> Please see:
>>
>> https://cms.apache.org/ooo-site/publish?diff=1
>>
>> Can we publish what is here?
>>
>> Thanks.
>
>
> Hm, I cannot login.
>
> Maybe it's because of the current LDAP issue (see the today's mail to all
> committers) but I cannot login.
>

Same happened to me.  But I was able to reset my id via
http://id.apache.org using the  "Forgot your password?" link.

-Rob


> Marcus
>
> -
> 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: staged web server -- can we publish what's there now?


Am 07/22/2013 04:52 PM, schrieb Kay Schenk:

Please see:

https://cms.apache.org/ooo-site/publish?diff=1

Can we publish what is here?

Thanks.


Hm, I cannot login.

Maybe it's because of the current LDAP issue (see the today's mail to 
all committers) but I cannot login.


Marcus

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

Re: Release coordination proposal


Am 07/22/2013 05:49 PM, schrieb Kay Schenk:

On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir  wrote:


Can we do something like this?

Two stage:  release and announce.


This was already planned to do.


Release == put the 4.0 files into production on SourceForge, update
our download web page to serve 4.0 files by default.

Announce == go live with news on front page, header announcement on
every page (branding.mdtext), announcement email, blog post, social
media, new logo on website, etc.

For the Release part,  can we do that end-of-day today, say in a
couple of hours?


Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish 
the new things earlier. I think in 1 or 2 hours, then I have some time 
to correct faulty things.



For the announcement part, this waits for the ASF press release to go
out tomorrow (Tuesday) at 6am New York time.

This will give us some time today to:

1) verify the downloads are working
2) add the correct download links to the NL pages.


Marcus




A sterling idea! and one I was thinking about also! +1 

I was just about to suggest holding off on the web site "branding" changes
until much later today.  But, this idea is better.

Re site branding updates -- later  today (1700 PDT? or suggest something an
alternate time)  after 'Release' stage, I will commit/port branding/site
changes to staging -- they're not there yet -- so someone else can publish
this if need be. I will NOT be available at 0600 EDT -- later like 1100 EDT
probably.


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

Re: mwiki contact page.

On Mon, Jul 22, 2013 at 3:46 AM, janI  wrote:
> On Jul 22, 2013 8:59 AM, "Marcus (OOo)"  wrote:
>>
>> Am 07/22/2013 04:46 AM, schrieb Kay Schenk:
>>
>>> On Jul 20, 2013 11:38 PM, "Andrea Pescetti"  wrote:

 Rob Weir wrote:
>
>
> Remember, the number of people who have admin-related questions about
> the wiki are very, very, very few in number.  They will be best served
> by directing them to some variation of a page like the one we have on
> the main website:
> http://www.openoffice.org/contact_us.html

 Why not linking directly to it then? It would be enough to add a section
>>>
>>> to

 http://www.openoffice.org/contact_us.html
 like the following:

 * If you have technical problems with one of the OpenOffice websites...
 - For problems with the www.openoffice.org site: contact
>>>
>>> dev@openoffice.apache.org and insert "[Website]" in the subject

 - For problems with the https://issues.apache.org/ooo/ site: contact
>>>
>>> aoo-bugzilla-ad...@apache.org

 - For problems with the wiki.openoffice.org site: contact
>>>
>>> dev@openoffice.apache.org and insert "[Mwiki]" in the subject

 - For problems with the https://translate.apache.org/ site: contact
>>>
>>> l...@openoffice.apache.org and insert "[Pootle]" in the subject

 Regards,
Andrea.
>>>
>>>
>>> This suggestion looks very reasonable to me.
>>
>>
>> In general also for me reasonable. But I don't want to rely on the
> subject prefix that the users have to insert manually. Rather, I would use
> some aliases to see where the mail come from.
>>
>> web-admin@ --> dev@
>> wiki-admin@ --> dev@
>>
>> Marcus
>>
>
> sounds good to me, even though I dont think it will make a huge difference'
> having a contact link on wiki will cause trafic, and users pr defitinition
> choose the easy road.
>

Yes, users are lazy, but they also know what they want.  They only
write to the dev list if there is no other option that sounds closer
to what they were looking for.

So if we have have a page that gives them the appropriate options for
support, reporting bugs, admin issues, etc., and order these
appropriately on
the page (most commonly needed at top), then we should do OK.  The
idea that Dave had was to add these items to an existing contact page
that already has these other options.

So the issue is that 99.99% of the visitors to a wiki page, if they
have a question, will have a product support question.  Some, but very
few, will have an admin-related question.  It is OK to tell how to get
admin help, but we need to make sure that we say, in the same place,
how to get product support, and make the product support more
prominent by listing it first.  That explains the ordering of
information on the contact page:

http://www.openoffice.org/contact_us.html

It is not perfect, but it gets most people closer to where they want to be.

Also, to the other idea, an alternative to a set of email aliases is
to use URL's of the form:
mailto:d...@openoffice.org?subject=[Pootle].

Regards,

-Rob

> rgds
> jan i
>>
>>
>> -
>> 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: Release coordination proposal

On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir  wrote:

> Can we do something like this?
>
> Two stage:  release and announce.
>
> Release == put the 4.0 files into production on SourceForge, update
> our download web page to serve 4.0 files by default.
>
> Announce == go live with news on front page, header announcement on
> every page (branding.mdtext), announcement email, blog post, social
> media, new logo on website, etc.
>
> For the Release part,  can we do that end-of-day today, say in a
> couple of hours?
>
> For the announcement part, this waits for the ASF press release to go
> out tomorrow (Tuesday) at 6am New York time.
>
> This will give us some time today to:
>
> 1) verify the downloads are working
> 2) add the correct download links to the NL pages.
>
> -Rob
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
A sterling idea! and one I was thinking about also! +1 

I was just about to suggest holding off on the web site "branding" changes
until much later today.  But, this idea is better.

Re site branding updates -- later  today (1700 PDT? or suggest something an
alternate time)  after 'Release' stage, I will commit/port branding/site
changes to staging -- they're not there yet -- so someone else can publish
this if need be. I will NOT be available at 0600 EDT -- later like 1100 EDT
probably.

-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: Building the PDF Import extension

2013-07-22 Thread Max Merbald


Hello,

when I wrote about the pdf import addon not working on AOO4 / Win 8 I 
overlooked Regina's mail. The new extension works perfectly well on AOO4 
running on Windows 8. Sorry for my complaint!


Max


Am 21.07.2013 15:43, schrieb Regina Henschel:

Hi Andrea,

Andrea Pescetti schrieb:

OpenOffice 4 (like all previous versions) does not include the PDF
Import extension. But, while in OpenOffice 3.4.x it was enough to
download it from the Extensions site, Ariel wrote that he expects that a
PDF Import Extension built for OpenOffice 3.x won't work except on
64-bit Linux, due to the stlport changes.

PDF Import is by far the most popular extension, so I'd like that we are
prepared if we receive questions. Due to a GPL dependency, it's not
shipped with OpenOffice, but questions will come here so...

I tried downloading the extension from
http://extensions.openoffice.org/en/node/874/ and it works nicely, but
I'm in the exceptional case (I tested on 64-bit Linux, the only platform
where the old extension is expected to work). Do people who use other
operating systems have problems?


This is tracked in issue 122733.

Ariel has build the extension newly. Find it in 
http://people.apache.org/~arielch/extensions/aoo-pdf-import/


I have tested the version aoo-pdf-import-0.0.1-windows-x86.oxt on 
Windows7. It works fine.


Kind regards
Regina



-
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: release media files

On Sun, Jul 21, 2013 at 2:21 PM, Drew Jensen wrote:

> The SVG files for the logo certainly make a trick ;_)
>
> You'll see I've made a few other changes and I kind of like where this is
> at.
>
> One item to note, I did, even with the admonition attached to the logo
> images, stick with the AOO_w_4 logo in the opening frames. That just makes
> sense to me specific to the purpose here - I did however switch to the
> numberless logo for the closing frames.
>
> OK - so, I pulled down the file from the other day and put up the results
> of the changes here:
>
> https://docs.google.com/file/d/0Bx7ZNEXlmR0ITkdtcnQwOEp3cm8/edit?usp=sharing
>
>
> Second note - the license CC-BY-NC-SA - that's just because of the little 7
> second blurb of music, I must use the NC license for that, if that is a
> problem with anyone I don't mind avoiding that.
>
> Otherwise, I'll follow up with mail about a second video (with features
> highlights) in a separate mail thread.
>
> As I said earlier, I'm not connected to the internet regularly, so I've not
> (and wouldn't able to again before Wed.) posted to any media sites, if this
> looks acceptable and you folks can make use of it, in any way, please do.
>
> Thanks,
>
> //drew
>

nice! I really like the way you did the fade-in...


>
>
>
>
> On Sat, Jul 20, 2013 at 3:36 PM, Dave Fisher 
> wrote:
>
> > Hi Drew,
> >
> > This looks really great, but as a note I had to run the mp4 through a
> > convertor program to play it on my MacOSX 10.6.8.
> >
> > Regards,
> > Dave
> >
> > On Jul 20, 2013, at 11:26 AM, Drew Jensen wrote:
> >
> > > Thanks for links - I grabbed all the files.
> > >
> > > So - I'll give another throw and post what happens tomorrow..
> > >
> > >
> > > On Sat, Jul 20, 2013 at 8:43 AM, Andrea Pescetti  > >wrote:
> > >
> > >> Drew Jensen wrote:
> > >>
> > >>> I took the liberty of spinning up a very brief such item, which you
> can
> > >>> find here:
> > >>> https://docs.google.com/file/**d/**0Bx7ZNEXlmR0IUTY1YzFhR1VLQU0/**
> > >>> edit?usp=sharing<
> >
> https://docs.google.com/file/d/0Bx7ZNEXlmR0IUTY1YzFhR1VLQU0/edit?usp=sharing
> > >
> > >>> [unzip the a4.mp4 video file from the uploaded zip container]
> > >>>
> > >>
> > >> Nice! (and welcome back Drew, by the way). The new logo colors appear
> a
> > >> bit too bright at the end, but see below for vector sources, that may
> > help
> > >> with this.
> > >>
> > >>
> > >> was not able to quickly find a vector graphic of what I take if the
> new
> > >>> logo, only - I did what I could using the PNG image I found on the
> > wiki,
> > >>> but I'm sure there is a better image available.
> > >>>
> > >>
> > >> You can find all versions, including PDF and SVG, at
> > >> https://svn.apache.org/repos/**asf/openoffice/ooo-site/trunk/**
> > >> content/marketing/art/**galleries/logos/aoo-working/<
> >
> https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/marketing/art/galleries/logos/aoo-working/
> > >
> > >> (warning: this is meant to be a temporary location)
> > >>
> > >>
> > >> I would also like to offer, and have started, a second video. Longer,
> > 45 -
> > >>> 90 sec. range, with a quick summary of new features. A little
> different
> > >>> audiance from the shorty here, I suppose. To start that I've
> downloaded
> > >>> all
> > >>> the information from the release notes page on the wiki, have used
> > this to
> > >>> generate some raw screen video catpure for the GUI changes and will
> > use,
> > >>> with your permission If I may, the graphics from the wiki for some of
> > the
> > >>> file fidelity enhancements.
> > >>>
> > >>
> > >> This would be very good to have. I don't know of anyone else working
> on
> > >> this, and obviously you can feel free to use images from the Release
> > Notes
> > >> page.
> > >>
> > >> Regards,
> > >>  Andrea.
> > >>
> > >>
> > >>
> > --**--**-
> > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<
> > 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
> >
> >
>



-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: New Extensions website goes live!

2013/7/13 Tsutomu Uchino 

> Hi,
>
> Thank you for gread features.
>
> When I added new release as "Host on this site", it got wrong version
> number of the package [1].
> The package contains  but 4.0 is shown.
> It seems minimal-version was used for the package version.
>

This bug has been fixed, thanks for heads up.

Roberto



>
> [1]
> http://extensions.services.openoffice.org/en/projectrelease/mersenne-twister-random-number-generator-add-40
>
> Regards
> - Tsutomu
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: final look at website test page...and slightly smaller logo

On Sun, Jul 21, 2013 at 11:08 PM, Dave Fisher  wrote:

>
> On Jul 21, 2013, at 4:35 PM, Kay Schenk wrote:
>
> > On Sun, Jul 21, 2013 at 3:28 PM, Marcus (OOo) 
> wrote:
> >
> >> Am 07/21/2013 10:01 PM, schrieb Kay Schenk:
> >>
> >> Well I thought the VERY BIG logo didn't look so good after all --
> here's a
> >>> slightly smaller version
> >>>
> >>> http://ooo-site.staging.**apache.org/test/<
> http://ooo-site.staging.apache.org/test/>
> >>>
> >>
> >> Looks also good. However, it's the main entry page for users. IMHO it is
> >> OK to use the bigger one.
> >
> >
> > Thanks. maybe for now, we use the same logo on both websites -- this new
> > one.
>
> I like your slightly smaller version. It looks great!
>
> Regards,
> Dave
>

Thanks... :)


>
> >
> >
> >>
> >>
> >> Committed, but not published since LOTS of DL stuff pending.
> >>>
> >>> So, we will go with this one I think.
> >>>
> >>> Another odd thing -- the LARGE earlier logo I rendered:
> >>>
> >>> http://www.openoffice.org/**images/AOO_logos/AOO4_logo_**cropped.png<
> http://www.openoffice.org/images/AOO_logos/AOO4_logo_cropped.png>
> >>>
> >>> I was able to render with transparent background -- this was from Chris
> >>> R's
> >>> original svg. The new ones in:
> >>>
> >>>
> http://www.openoffice.org/**marketing/art/galleries/logos/**aoo-working/<
> http://www.openoffice.org/marketing/art/galleries/logos/aoo-working/>
> >>>
> >>
> >> After the release we should definitely clean-up the logos in the
> different
> >> locations.
> >>
> >
> > That and more... ;}
> >
> >
> >>
> >> Marcus
> >>
> >>
> >>
> >>
> >> I don't seem to be able to render new svgs as transparent. So???
> >>> Either svg has changed or Gimp (new version) is broken.
> >>>
> >>> So, for right now -- logo has white background.
> >>>
> >>
> >>
> --**--**-
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<
> dev-unsubscr...@openoffice.apache.org>
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >>
> >
> >
> > --
> >
> -
> > MzK
> >
> > Success is falling nine times and getting up ten."
> > -- Jon Bon Jovi
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: New Extensions website goes live!

2013/7/19 Ariel Constenla-Haile 

> On Sat, Jul 13, 2013 at 12:01:12PM -0300, Ariel Constenla-Haile wrote:
> > The download buttons for externally hosted extensions (or at least for
> > this one:
> >
> http://extensions.openoffice.org/en/project/mysql-driver-apache-openoffice
> )
> > give an "Access denied" error page.
>
> Confirmed also with
> http://extensions.openoffice.org/en/project/eurooffice-nonlinear-solver
>

We are fixing a number of issues like that. I can tell we didn't loose any
download information in the process, but some projects were using the
'thank you link' to actually serve downloads and we are working to recover
those as well.

Roberto

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

l10n branch.

HI.

I have deleted branches/l10n and created branches/l10n40

This was done to secure, that I work with a copy of our trunk at the time
of release. Merging the trunk to the old l10n looked too error prone.

Work will now commence on l10n40. As suggested by jsc, I will test and
integrate genLang in the branch only, and then "release" it for general
testing.


Plan is to have genLang available at the time where translation for 4.1
starts.

any thoughts ?

rgds
jan I.

staged web server -- can we publish what's there now?

Please see:

https://cms.apache.org/ooo-site/publish?diff=1

Can we publish what is here?

Thanks.
-- 
-
MzK

Success is falling nine times and getting up ten."
 -- Jon Bon Jovi

Re: New Extensions website goes live!

2013/7/13 Ricardo Berlasso 

> 2013/7/13 Roberto Galoppini 
>
> > 2013/7/9 Roberto Galoppini 
> >
> > >
> > >
> > >
> > > 2013/7/8 Rob Weir 
> > >
> > >> On Sat, Jul 6, 2013 at 4:18 PM, Roberto Galoppini
> > >>  wrote:
> > >> > We are updating http://extensions.openoffice.org to tturn on all
> > >> > enhancements previously made available at the test website.
> > >> >
> > >>
> > >> This is great news, Roberto!
> > >>
> > >
> > > Indeed!
> > >
> > >
> > >> Are you planning a blog post related to this at SourceForge?  Or
> > >> should we plan something for the AOO blog?  (Or both?)
> > >>
> > >
> > > I'll cover that at the SF blog as usual, open to do something that
> makes
> > > sense for AOO blog too, sure.
> > >
> > > Give me a day or two, I want to finalize the migration before.
> > >
> >
> > AOOE has been successfully migrated, below a concise list of
> improvements,
> > a blog post on SF will follow next week (possibly coordinating  that with
> > the new AOO release).
> >
> > 1. The whole platform has been upgraded to a web 2.0ish style. Adding
> more
> > content, serve developers' needs as well as scale with end-users' growth
> is
> > easier now.
> >
> > 2. The look&feel has been updated and aligned with the new AOO 4 look. We
> > put the word 'beta' in the header, to be removed once the new release
> will
> > go out.
> >
> > 3.  The search has been improved and it provides the autocomplete
> > functionality (try it out writing 'dr' for example).
> >
> > 4. The auto-update for Extensions has been reactivated.
> >
> > 5. A new feature allows devs to report AOO 4.0 compatibility for their
> > extensions, and by default we set all to 'unknown'. Have a look at
> >
> http://extensions.openoffice.org/upgrade/400/abcdef+754758+df418f+a81383to
> > get an example.
> >
> > Note that to take full advantage of this new feature we need authors to
> set
> > properly the compatibility field, and to crack a new Extension to check
> > extensions compatibility or changes (it should check which extensions are
> > installed, e.g. A, B, C and then call
> > http://extensions.openoffice.org/upgrade/400/A+B+C). Maybe we can
> discuss
> > further option once AOO 4 will be released.
> >
> > 6. Finally Extensions authors have full control over comments and spam.
> >
> > Roberto
> >
>
> Great!
>
> A quick question for the future: will the site be translated into more
> languages?
>

Sure! We upgraded to Drupal 7 that has a nice multi-lingual support, but we
do not have yet the files we use for OpenOffice (Pootle).

We might need to talk to Jurgen once is back and see how to move on.

Roberto


>
> Anyway, thanks for this new site! It looks gorgeous!
>
> Regards
> Ricardo
>
>
> >
> >
> >
> >
> > >
> > > Roberto
> > >
> > >
> > >>
> > >> Do you have a list of changes that we can reference?
> > >>
> > >> Regards,
> > >>
> > >> -Rob
> > >>
> > >>
> > >> > All users accounts will be migrated, along with associated passwords
> > and
> > >> > users content.
> > >> >
> > >> >  http://extensions.openoffice.org may be temporarily unavailable or
> > >> slow
> > >> > down.
> > >> >
> > >> > Once the migration will be completed "update notifications" will be
> > >> > activated.
> > >> >
> > >> > Roberto
> > >>
> > >
> > >
> >
>

Re: Pasting HTML not possible in AOO 4.0?

2013-07-22 Thread Ricardo Berlasso

2013/7/22 David Gerard 

> Just preparing to update the Wikipedia article, and tried pasting from
> a web page into AOO 4.0.0 Writer. It gives "Requested clipboard format
> not available." (The paste works fine in LO 4.0 and is formatted as
> one would expect it to just work.)
>
> Is this actually supposed to happen - no ability to c'n'p from a web
> page - or will it be a weirdness of my setup? Admittedly I'm running
> the Windows binary under Wine ...
>

That's the answer... ;)

Copy-paste from web work without problems on native Linux binaries. Note
that Linux clipboard works different from windows clipboard: I think that
if you copy from a win firefox running on wine to the win AOO running on
wine you'll have no problem, but copying from a Linux app and pasting to a
win app running atop of wine... well, that's wine's problem/bug.

Regards
Ricardo



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

Pasting HTML not possible in AOO 4.0?

2013-07-22 Thread David Gerard

Just preparing to update the Wikipedia article, and tried pasting from
a web page into AOO 4.0.0 Writer. It gives "Requested clipboard format
not available." (The paste works fine in LO 4.0 and is formatted as
one would expect it to just work.)

Is this actually supposed to happen - no ability to c'n'p from a web
page - or will it be a weirdness of my setup? Admittedly I'm running
the Windows binary under Wine ...


- d.

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

Re: release media files

On 22 July 2013 10:55, Rony G. Flatscher (Apache)  wrote:

>
> On 21.07.2013 23:21, Drew Jensen wrote:
> > The SVG files for the logo certainly make a trick ;_)
> >
> > You'll see I've made a few other changes and I kind of like where this is
> > at.
> >
> > One item to note, I did, even with the admonition attached to the logo
> > images, stick with the AOO_w_4 logo in the opening frames. That just
> makes
> > sense to me specific to the purpose here - I did however switch to the
> > numberless logo for the closing frames.
> >
> > OK - so, I pulled down the file from the other day and put up the results
> > of the changes here:
> >
> https://docs.google.com/file/d/0Bx7ZNEXlmR0ITkdtcnQwOEp3cm8/edit?usp=sharing
> The new logo with the transparent background really improves the video a
> lot, very well done!
>
> Impressive work, well done.

rgds
jan I.


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

Re: release media files

2013-07-22 Thread Rony G. Flatscher (Apache)


On 21.07.2013 23:21, Drew Jensen wrote:
> The SVG files for the logo certainly make a trick ;_)
>
> You'll see I've made a few other changes and I kind of like where this is
> at.
>
> One item to note, I did, even with the admonition attached to the logo
> images, stick with the AOO_w_4 logo in the opening frames. That just makes
> sense to me specific to the purpose here - I did however switch to the
> numberless logo for the closing frames.
>
> OK - so, I pulled down the file from the other day and put up the results
> of the changes here:
> https://docs.google.com/file/d/0Bx7ZNEXlmR0ITkdtcnQwOEp3cm8/edit?usp=sharing
The new logo with the transparent background really improves the video a lot, 
very well done!

---rony


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

Starting Introduction to Contributing to Apache OpenOffice Module

2013-07-22 Thread Prince Soni

Hi, my name is Prince Soni, 3rd Year CSE from India.

 

I know J2se and J2EE. I want to strong my grip in both these fields. 

 

Since this one would be my 1st open source project I have no Idea how to take 
part or contribute in open source.

 

I am looking for a simple and popular project in these two field for now. Once 
I became comfortable I may take difficult one

 

Thanx for your time

Re: User Guides

2013-07-22 Thread Shenfeng Liu

2013/7/18 Rob Weir 

> On Thu, Jul 18, 2013 at 7:05 AM, Shenfeng Liu  wrote:
> > Hi, all,
> >   I just noticed that the latest user guides we have is for
> OpenOffice.org
> > 3.3, as below:
> >
> > http://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides
> >
> >   I wonder if any one is willing to help to update the user guides for
> AOO
> > 4.0?
> >
>
> We have a separate doc mailing list and volunteers who have been
> working on the wiki here:
>
> http://wiki.openoffice.org/wiki/Documentation/UserGuide
>
> -Rob
>

Thanks for the information, Rob!

- Shenfeng (Simon)



>
>
> >   Thanks!
> >
> > - Shenfeng (Simon)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: mwiki contact page.

On Jul 22, 2013 8:59 AM, "Marcus (OOo)"  wrote:
>
> Am 07/22/2013 04:46 AM, schrieb Kay Schenk:
>
>> On Jul 20, 2013 11:38 PM, "Andrea Pescetti"  wrote:
>>>
>>>
>>> Rob Weir wrote:


 Remember, the number of people who have admin-related questions about
 the wiki are very, very, very few in number.  They will be best served
 by directing them to some variation of a page like the one we have on
 the main website:
 http://www.openoffice.org/contact_us.html
>>>
>>>
>>>
>>> Why not linking directly to it then? It would be enough to add a section
>>
>> to
>>>
>>> http://www.openoffice.org/contact_us.html
>>> like the following:
>>>
>>> * If you have technical problems with one of the OpenOffice websites...
>>> - For problems with the www.openoffice.org site: contact
>>
>> dev@openoffice.apache.org and insert "[Website]" in the subject
>>>
>>> - For problems with the https://issues.apache.org/ooo/ site: contact
>>
>> aoo-bugzilla-ad...@apache.org
>>>
>>> - For problems with the wiki.openoffice.org site: contact
>>
>> dev@openoffice.apache.org and insert "[Mwiki]" in the subject
>>>
>>> - For problems with the https://translate.apache.org/ site: contact
>>
>> l...@openoffice.apache.org and insert "[Pootle]" in the subject
>>>
>>>
>>> Regards,
>>>Andrea.
>>
>>
>> This suggestion looks very reasonable to me.
>
>
> In general also for me reasonable. But I don't want to rely on the
subject prefix that the users have to insert manually. Rather, I would use
some aliases to see where the mail come from.
>
> web-admin@ --> dev@
> wiki-admin@ --> dev@
>
> Marcus
>

sounds good to me, even though I dont think it will make a huge difference'
having a contact link on wiki will cause trafic, and users pr defitinition
choose the easy road.

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

Re: [RELEASE]: availability of uploads and synchronize SF mirrors