date:20131029

I'd like to move forward now with this proposal from July.

I've updated the EOL page here to say that OOo 3.3.0 and earlier are
no longer supported.  That page also explains what this means.

http://www.openoffice.org/development/releases/eol.html

I'll start to do the other 3 items now.  I'll coordinate with Oliver
on the update notifications.

Of course, help on any of these items is welcome.

Regards,

-Rob


On Sun, Jul 21, 2013 at 11:28 PM, Shenfeng Liu liush...@gmail.com wrote:
 2013/7/19 Rob Weir robw...@apache.org

 We currently have this link from the download page,from 2009,
 announcing end-of-life for OpenOffice.org 2.x:

 http://www.openoffice.org/development/releases/eol.html

 I'd like to update that page to also state that 3.x version prior to
 3.4.x are also end-of-life.  Why?  We're unlikely to issue any more
 security patches for 3.3.0 or earlier.

 So the concrete proposal is:

 1) Update the eol.html page to state that OOo 3.3.0 and earlier are no
 longer supported.

 2) Create a new landing page for users of OOo 3.3.0 and before who are
 using a language version that we do not yet have a translation.
 Explain in this page that the earlier versions are no longer
 supported.  List what translations are currently available and where
 they can be downloaded from.  Give information on how they can
 volunteer to help translate AOO into their native language.

 3) Configure the update notification server to OOo 3.3.0 users to this
 new landing page, if their language is not already translated.  (Where
 there is a translation we already point them to the download page)

 4) Blog post/announcement on end-of-life for OOo 3.3.0 and earlier.

 The end result is that:  1) We made it clear what versions are
 supported.  2) We did our due diligence to reach out to users of older
 versions.  3) We encourage new translation volunteers.

 No rush on this.  It does not need to be done at the same time as the
 4.0 announcement.  It can follow a week or so later.

 -Rob



 +1

 - Shenfeng (Simon)





 -
 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: [PROPOSAL] End-of-Life for OpenOffice.org 3.3.0

On Tue, Oct 29, 2013 at 11:51 AM, Rob Weir robw...@apache.org wrote:
 I'd like to move forward now with this proposal from July.

 I've updated the EOL page here to say that OOo 3.3.0 and earlier are
 no longer supported.  That page also explains what this means.

 http://www.openoffice.org/development/releases/eol.html

 I'll start to do the other 3 items now.  I'll coordinate with Oliver
 on the update notifications.


And here is a draft of the landing page we'd send users to who have an
older version of OOo if there is not an AOO version in their language:

http://www.openoffice.org/development/releases/eol-nl.html

Regards,

-Rob

 Of course, help on any of these items is welcome.

 Regards,

 -Rob


 On Sun, Jul 21, 2013 at 11:28 PM, Shenfeng Liu liush...@gmail.com wrote:
 2013/7/19 Rob Weir robw...@apache.org

 We currently have this link from the download page,from 2009,
 announcing end-of-life for OpenOffice.org 2.x:

 http://www.openoffice.org/development/releases/eol.html

 I'd like to update that page to also state that 3.x version prior to
 3.4.x are also end-of-life.  Why?  We're unlikely to issue any more
 security patches for 3.3.0 or earlier.

 So the concrete proposal is:

 1) Update the eol.html page to state that OOo 3.3.0 and earlier are no
 longer supported.

 2) Create a new landing page for users of OOo 3.3.0 and before who are
 using a language version that we do not yet have a translation.
 Explain in this page that the earlier versions are no longer
 supported.  List what translations are currently available and where
 they can be downloaded from.  Give information on how they can
 volunteer to help translate AOO into their native language.

 3) Configure the update notification server to OOo 3.3.0 users to this
 new landing page, if their language is not already translated.  (Where
 there is a translation we already point them to the download page)

 4) Blog post/announcement on end-of-life for OOo 3.3.0 and earlier.

 The end result is that:  1) We made it clear what versions are
 supported.  2) We did our due diligence to reach out to users of older
 versions.  3) We encourage new translation volunteers.

 No rush on this.  It does not need to be done at the same time as the
 4.0 announcement.  It can follow a week or so later.

 -Rob



 +1

 - Shenfeng (Simon)





 -
 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: Submission for consultants page

2013-10-29 Thread Drew Jensen

On Tue, Oct 22, 2013 at 6:33 PM, Rob Weir robw...@apache.org wrote:

 I have no idea.  Should we?



Sorry for the delay.

Well, it rather depends on what you are trying to do - I doubt that in this
instance it would make much sense. Anyhow, it is rather a different subject
from the listing itself, and on that note (the listing) I did not mean to
say I had objection.

Change of Subject - I note, or so it appears, that Symphony is no longer
available or at least not for download. There where a few ancillary
artifacts, some key board shortcut sheets and a few small tutorials which
had been available from the old Symphony site and seems to have no links to
the newer web page - any chance you employer would allow someone to update
those for AOO 4 and make them available on the wiki here? [perhaps I should
of broken that into a separate thread]

Thanks for all your work,

//drew

Re: Submission for consultants page

On Tue, Oct 29, 2013 at 2:14 PM, Drew Jensen drewjensen.in...@gmail.com wrote:
 On Tue, Oct 22, 2013 at 6:33 PM, Rob Weir robw...@apache.org wrote:

 I have no idea.  Should we?



 Sorry for the delay.

 Well, it rather depends on what you are trying to do - I doubt that in this
 instance it would make much sense. Anyhow, it is rather a different subject
 from the listing itself, and on that note (the listing) I did not mean to
 say I had objection.

 Change of Subject - I note, or so it appears, that Symphony is no longer
 available or at least not for download. There where a few ancillary
 artifacts, some key board shortcut sheets and a few small tutorials which
 had been available from the old Symphony site and seems to have no links to
 the newer web page - any chance you employer would allow someone to update
 those for AOO 4 and make them available on the wiki here? [perhaps I should
 of broken that into a separate thread]


Did you see the stuff that was already contributed?

Look inside:  
https://svn.apache.org/repos/asf/openoffice/symphony/trunk/help/com.ibm.symphony.help.en/doc.zip

-Rob


 Thanks for all your work,

 //drew

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

Re: Submission for consultants page

2013-10-29 Thread Drew Jensen

Drat - I'm so far behind *laughing*..

The answer is no. I did just download it however and will look when I get
home.

Thanks again

On Tue, Oct 29, 2013 at 2:28 PM, Rob Weir robw...@apache.org wrote:

On Tue, Oct 29, 2013 at 2:14 PM, Drew Jensen drewjensen.in...@gmail.com
wrote:
On Tue, Oct 22, 2013 at 6:33 PM, Rob Weir robw...@apache.org wrote:

I have no idea. Should we?

Sorry for the delay.

Well, it rather depends on what you are trying to do - I doubt that in
this
instance it would make much sense. Anyhow, it is rather a different
subject
from the listing itself, and on that note (the listing) I did not mean to
say I had objection.

Change of Subject - I note, or so it appears, that Symphony is no longer
available or at least not for download. There where a few ancillary
artifacts, some key board shortcut sheets and a few small tutorials which
had been available from the old Symphony site and seems to have no links
to
the newer web page - any chance you employer would allow someone to
update
those for AOO 4 and make them available on the wiki here? [perhaps I
should
of broken that into a separate thread]

Did you see the stuff that was already contributed?

Look inside:
https://svn.apache.org/repos/asf/openoffice/symphony/trunk/help/com.ibm.symphony.help.en/doc.zip

-Rob

Thanks for all your work,

//drew

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

Re: The crux with 2 open standards for more or less the same thing

On Mon, Oct 28, 2013 at 11:57 AM, Jürgen Schmidt jogischm...@gmail.com wrote:
 Hi,

 The OpenDocument format (ODF) which has it's roots in OpenOffice is a
 good thing and it helped a lot that office productivity becomes a little
 bit more transparent and a step forward to become vendor independent.
 Ideally one standard would have been used and would evolve over time to
 address new requirements, features etc.

 We all know that the reality is different and we have today 2 open
 standards for more or less the same thing, at least from my point of view.


We always had to support at least two document formats:  our native
format for OpenOffice and the native format for Microsoft Office.
This has been true from the start.

Although many of us would have preferred to see a single widespread
open standard in use, it is progress that we have detailed
specifications for two formats now, along with patent assurances that
came with the standardization process.  This helps OpenOffice.

As you know, when OpenOffice first started the Microsoft file format
had to be reverse engineered.  Now we have 7000+ pages of
specification.

 We have ODF which is an OASIS and ISO standard (ISO/IEC 26300:2006), see
 [1] and [2]. And we have OOXML which is an Ecma and ISO standard
 (ISO/IEC 29500-1:2008), see [3] and [4].

 We can now argue why do we have 2 standards and can discuss the pros and
 cons. But does it help? I don't think so and I believe we have to live
 with the current situation.


As before, we always have had two formats to support.  The main
difference is now they are both standardized and have better
documentation.

 But this means that we have to take into account that OOXML is an
 important file format that becomes more and more important over time.
 And that we should think about a strategy to support this format better
 in AOO.

 We see growing demand for better interoperability with OOXML and I
 believe we can't ignore this anymore. We have OOXML import which have to
 be improved and we don't have an export yet. I think it was a strategic
 decision from Sun/Oracle to focus on an import only. I believe the goal
 was to push ODF and an ODF eco system which was not a bad idea. But
 again the reality seems to be different today and the demand for OOXML
 is growing.

 That is the reason why we will start to investigate in a better OOXML
 support for AOO and you will probably notice some more activity in the
 future going in this direction. We have already started to analyze what
 we have and how we can push things forward. One thing is of course the
 missing export and the other thing an improved import. For the import we
 are thinking about a bigger change to consolidate 3 different approaches
 in 3 applications that we have today and we plan to start a new
 framework. Something cleaner and better structured as what we have today
 and that will give us further opportunities to use it for analyzing of
 documents and used features, tracking of our coverage and in the end to
 become more efficient.


This sounds like a good approach.

 Of course this does not mean that we support ODF any less. We remain
 strong supporters of ODF and aim to be the reference implementation for
 the standard. AOO committers like Regina, Oliver and Rob work directly
 on the ODF standard in OASIS.

And if we have any OOXML questions, I have some friendly contacts at
Microsoft that might be able to answer questions.

 And it is not really about choosing one standard over another. The point
 is to preserve the MS interop capabilities that OOo always had, and
 update it to work with the latest formats used by MSO.

 Anyway this will be a major task but I believe a necessary and important
 one for AOO to continue to be the best free open source office suite.


It is worth thinking as well as better support for non-WYSIWYG
formats.   For example, I get a lot of requests for a clean,
structurally accurate unformatted (X)HTML output.  So not trying to
mimic the appearance of the document, but getting the structure right.
 If we can get good HTML output it is an attractive intermediate
format for transforming to other similar XML-based formats like EPUB
and DITA.

Regards,

-Rob



 Juergen


 [1] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office

 [2]
 http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=43485

 [3] http://www.ecma-international.org/publications/standards/Ecma-376.htm

 [4] http://www.iso.org/iso/catalogue_detail?csnumber=51463

 -
 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: Submission for consultants page

On Mon, Oct 28, 2013 at 1:00 PM, Kay Schenk kay.sch...@gmail.com wrote:
 On Sat, Oct 26, 2013 at 6:56 PM, Rob Weir robw...@apache.org wrote:

 On Sat, Oct 26, 2013 at 5:57 PM, Kay Schenk kay.sch...@gmail.com wrote:
  On Sat, Oct 26, 2013 at 1:24 PM, Rob Weir robw...@apache.org wrote:
 
  On Sat, Oct 26, 2013 at 1:35 PM, Kay Schenk kay.sch...@gmail.com
 wrote:
   On Sat, Oct 26, 2013 at 5:21 AM, Jörg Schmidt joe...@j-m-schmidt.de
  wrote:
  
   Hello *,
  
  
From: Kay Schenk [mailto:kay.sch...@gmail.com]
  
So...this thread does not meet lazy consensus but are we ready to
implement this addition, without further changes, anyway?
I'll be happy to
take care of this either later today or tomorrow if we are.
  
   Can you please summarize what the solution should look like?
  
   The thread is long and I have somewhat lost track as point # 4
 should
  be
   changed.
   Should he ever be changed or what says:
  
... Can be eased a bit as it is clear enough did the
Items are with and for our project, respectively. product.
  
  
   In particular, it would be important for me to know whether I can
 change
   my website (http://www.jm-schmidt.de/inhalt.html) or must.
  
  
  
   Greetings,
   Jörg
  
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
   For additional commands, e-mail: dev-h...@openoffice.apache.org
  
  
   My take on this discussion so far  (and I am certainly NOT the
 definitive
   judge on this):
  
   * there is the listing on the consultants page itself:
   http://www.openoffice.org/bizdev/consultants.html
  
 
  I wrote that page, so it might not be too presumptuous if I say what I
  meant when I wrote it ;-)
 
  The guideline is that the 3rd party pages must respect ASF
  Trademarks.  This is vague, but intentionally so.   I think we'll all
  be more accurate judges of what is wrong when we see it than we are
  predictors of all things that could possibly be wrong.  So the
  discretion is given to the PMC to take this on a case-by-case basis.
  We should be looking at each submission and their linked websites as a
  whole.
 
  The kinds of abuses I had in mind were mainly pages that implied that
  the services were endorsed or affiliated with the ASF.   This is much
  more than technicalities of whether or not a (TM) symbol is used.  For
  example, a page that calls itself Apache OpenOffice (TM) Consulting
  Group would *not* be OK. We don't want our trademarks used as
  adjectives, since that suggests an affiliation.
 
  I also had in mind that we might need to correct names where they are
  misstated, e.g., Apache Open Office, Apache Openoffice,
  OpenOffice.org, etc.
 
  Regards,
 
  -Rob
 
 
  OK -- I think we should go ahead with this. Unfortunately, testing with
 my
  private web area on my box, my server is balking at the .xsl page that
  goes with this...so...
 

 The command line should look something like:

 xsltproc -o consultants.html --stringparam locale en to-html.xsl
 consultants.xml

 You can switch locales by setting different values via stringparam
 parameter.

 Other XSLT engines should work, but the command line would be different.


 ok, that's not what I was using...this seems to work and not complain about
 the stylesheet being invalid.



  Rob, since you have always taken care of this in the past, I would be
 fine
  and dandy with you committing this change -- wearing your Apache hat
  instead of your IBM one of course. ;)
 

 Sure, I can do it next week when I am at my desk.

 Regards,

 -Rob


 Anyway, I was just about to do this when I see that there is no contact
 info -- e-mail, phone etc. -- supplied with this listing as with the
 others. I see there's a phone number supplied on the website, so maybe just
 include that?


If you include the phone number you would also want to include the
priority code that is on the webpage.   Or don't have a phone
number.

-Rob




  So sorry about this -- I guess it's time for more of us to give this
 area a
  bit more attention.
 
 
 
   concerning the actual content we are discussing. This does not have a
  (TM)
   after Apache OpenOffice. I thought this was the original cause of
  objection.
  
   And, we can see from the listings on the consultants page that we did
 not
   enforce a (TM) after Apache OpenOffice on the consultants page.
  
   * there are the actual websites of the consultants, like yours, and
 this
   submitted one up for consideration.
  
   It seems there is  more concern to enforce a (TM) symbol after Apache
   OpenOffice for these third party websites.  However, this is not
  something
   required by Apache.
  
   See:
  
   http://www.apache.org/foundation/marks/faq/#attribution
  
   The important factor is referencing OpenOffice as Apache OpenOffice,
  and
   not the use the of the (TM) after the name.
  
   The website, http://www.jm-schmidt.de/inhalt.html, seems to have all

Re: Websites headers (forum, wiki, main site, ...)

2013-10-29 Thread FR web forum

-1
Forum is not a universal word.
Many NL forums don't use it like Asia area.

- Mail original -
De: Andrea Pescetti pesce...@apache.org
À: dev@openoffice.apache.org
Envoyé: Dimanche 27 Octobre 2013 21:53:07
Objet: Re: Websites headers (forum, wiki, main site, ...)

Ricardo Berlasso wrote:
 My best attempt is on this Draw file ...
 http://people.apache.org/~rgb-es/Forum-Header-2.odg
 there is agreement on the forum header design and on changing the
 download icon. Which are the steps needed to implement this change on all
 NL forums?

Changing the download icon is easy since we already have the updated 
graphics.

Changing header, if what we have so far is your Draw file, needs some 
adaptation work to the forum CSS. I've already done it for another 
candidate header and, unless somebody else is going to do it, I can try 
producing a CSS implementation for this one too, even though this one is 
harder since backgrounds need to be adapted.

The last step will be materially putting the new files online, but this 
is not particularly problematic.

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

Re: The crux with 2 open standards for more or less the same thing

2013-10-29 Thread Andrew Rist



On 10/28/2013 12:38 PM, Jörg Schmidt wrote:

Hello,


From: Andrea Pescetti [mailto:pesce...@apache.org]

That is the reason why we will start to investigate in a

better OOXML

support for AOO and you will probably notice some more

activity in the

future going in this direction.

Excellent. A better Microsoft compatibility is what our users
set as #1
priority in the user survey and improving OOXML import (and
export!) is
surely part of that.

This is a pragmatic way, also a necessary way, but I fear it will be in the long
run, even the death of the current ODF.

No user of MS Office will move more of OOXML to ODF, if the compatibility of 
OOXML
in AOO will be similar as well of *.doc.

It is not wrong to improve compatibility with OOXML, but that will unfortunately
be the side effect. I think that you should see clearly.

We must also see that the need to improve the compatibility with OOXML,
unfortunately, also an expression of the fact that market dominance continues to
have MS Office .

I look at what happens at the ISO, where they talked some time ago by the 
merging
of the two standards ( ODF and OOXML), and take statements from experts 
seriously,
it seems to me the path mapped out, there will be a new standard in the future,
even if no one likes to hear.

http://xkcd.com/927/


We should all prepare ourselves to it and work on it that it prevents the MS 
this
standard does not dominate. That's what we should see as a long term goal.
I am thinking there must be cooperation between _all_ the OSS projects will use
the ODF.


Greetings,
Jörg



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




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

Re: Websites headers (forum, wiki, main site, ...)

2013-10-29 Thread Alexandro Colorado

The issue here is that there is not a hackable instance of the forum, so is
hard to do any commiting. you can look at my private header template for
the main site:
http://people.apache.org/~jza/index.html

I could produce one for the forum, but this could only be hackable by
myself, making development quite slow. I could have a svn instance (or
git) but again, not sure if that many people will do the commiting or even
know how to commit. From my experience with the community many people don't
know how to work with DSCM and make their own clones as opposed to dealing
with merges.

On Sun, Oct 27, 2013 at 2:53 PM, Andrea Pescetti pesce...@apache.orgwrote:

Ricardo Berlasso wrote:

My best attempt is on this Draw file ...
http://people.apache.org/~rgb-**es/Forum-Header-2.odghttp://people.apache.org/%7Ergb-es/Forum-Header-2.odg

there is agreement on the forum header design and on changing the
download icon. Which are the steps needed to implement this change on all
NL forums?

Changing the download icon is easy since we already have the updated
graphics.

Changing header, if what we have so far is your Draw file, needs some
adaptation work to the forum CSS. I've already done it for another
candidate header and, unless somebody else is going to do it, I can try
producing a CSS implementation for this one too, even though this one is
harder since backgrounds need to be adapted.

The last step will be materially putting the new files online, but this is
not particularly problematic.

Regards,
Andrea.

--**--**-
To unsubscribe, e-mail:
dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org

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

--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614

Re: Websites headers (forum, wiki, main site, ...)

2013-10-29 Thread Ricardo Berlasso

2013/10/29 FR web forum ooofo...@free.fr

 -1
 Forum is not a universal word.
 Many NL forums don't use it like Asia area.


No problem with that: a translation for the word forum on each language
will be enough.

Regards,
Ricardo




 - Mail original -
 De: Andrea Pescetti pesce...@apache.org
 À: dev@openoffice.apache.org
 Envoyé: Dimanche 27 Octobre 2013 21:53:07
 Objet: Re: Websites headers (forum, wiki, main site, ...)

 Ricardo Berlasso wrote:
  My best attempt is on this Draw file ...
  http://people.apache.org/~rgb-es/Forum-Header-2.odg
  there is agreement on the forum header design and on changing the
  download icon. Which are the steps needed to implement this change on all
  NL forums?

 Changing the download icon is easy since we already have the updated
 graphics.

 Changing header, if what we have so far is your Draw file, needs some
 adaptation work to the forum CSS. I've already done it for another
 candidate header and, unless somebody else is going to do it, I can try
 producing a CSS implementation for this one too, even though this one is
 harder since backgrounds need to be adapted.

 The last step will be materially putting the new files online, but this
 is not particularly problematic.

 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

Re: [PROPOSAL] End-of-Life for OpenOffice.org 3.3.0

2013-10-29 Thread Keith N. McKenna

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rob Weir wrote:
 On Tue, Oct 29, 2013 at 11:51 AM, Rob Weir robw...@apache.org
 wrote:
 I'd like to move forward now with this proposal from July.
 
 I've updated the EOL page here to say that OOo 3.3.0 and earlier
 are no longer supported.  That page also explains what this
 means.
 
 http://www.openoffice.org/development/releases/eol.html
 
 I'll start to do the other 3 items now.  I'll coordinate with
 Oliver on the update notifications.
 
 
 And here is a draft of the landing page we'd send users to who have
 an older version of OOo if there is not an AOO version in their
 language:
 
 http://www.openoffice.org/development/releases/eol-nl.html
 
 Regards,
 
 -Rob
 

Rob;
I would suggest that you re-order the list of alternatives such that
the non-recommended item is the last entry such as below:


Download Apache OpenOffice 4.0.1 in another language that you are
familiar with.

Sign up for our announcements mailing list so you will be notified of
new languages and releases when they become available.

Volunteer to help translate OpenOffice into your native language.

(Not Recommended) Continue running an unsupported version of OpenOffice

This puts the non-recommended option further from the initial line of
sight of the reader thus (hopefully) lessening the likelihood they
will grab onto it as the preferred alternative.

Regards
Keith

 Of course, help on any of these items is welcome.
 
 Regards,
 
 -Rob
 
 
 On Sun, Jul 21, 2013 at 11:28 PM, Shenfeng Liu
 liush...@gmail.com wrote:
 2013/7/19 Rob Weir robw...@apache.org
 
 We currently have this link from the download page,from
 2009, announcing end-of-life for OpenOffice.org 2.x:
 
 http://www.openoffice.org/development/releases/eol.html
 
 I'd like to update that page to also state that 3.x version
 prior to 3.4.x are also end-of-life.  Why?  We're unlikely to
 issue any more security patches for 3.3.0 or earlier.
 
 So the concrete proposal is:
 
 1) Update the eol.html page to state that OOo 3.3.0 and
 earlier are no longer supported.
 
 2) Create a new landing page for users of OOo 3.3.0 and
 before who are using a language version that we do not yet
 have a translation. Explain in this page that the earlier
 versions are no longer supported.  List what translations are
 currently available and where they can be downloaded from.
 Give information on how they can volunteer to help translate
 AOO into their native language.
 
 3) Configure the update notification server to OOo 3.3.0
 users to this new landing page, if their language is not
 already translated.  (Where there is a translation we already
 point them to the download page)
 
 4) Blog post/announcement on end-of-life for OOo 3.3.0 and
 earlier.
 
 The end result is that:  1) We made it clear what versions
 are supported.  2) We did our due diligence to reach out to
 users of older versions.  3) We encourage new translation
 volunteers.
 
 No rush on this.  It does not need to be done at the same
 time as the 4.0 announcement.  It can follow a week or so
 later.
 
 -Rob
 
 
 
 +1
 
 - Shenfeng (Simon)
 
 
 
 
 
 -

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJScDi2AAoJEH0fu5UhGmBCBWgIAKBTlZUBr7pzUr+AztM6dRRF
8lpQsYTUuOgXuyRNCoPXc+gW/A7UC4r2OgVNWdS2jRgs5S2IjgAaR3bfv/ncojIX
x4HrXL5dDnW8v9rshBwewfgj+x6gDuFiP4ARkiq6Kz7XiztL4Knt57/Jo0xMEkzL
DjPvTewEprqZOWSEIar6haMMP4gV1LgFmG4wCwcwCFMSZerCbAlsZa44C37gIUcp
/PLzblxuYqDYYWEDzgvcqQHOwBSX/oZW4Wwc+es5LuLcZqUOhoDxrVciQoUcw61i
fkZGvg64RL5qG/Qf3jxoIKFUqbBSVHR1BbNHThbj+KWO5InYZIIFODKMFEJwZyY=
=gMXI
-END PGP SIGNATURE-


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

Re: easy task

If you would like to do an actual html mockup -- compatible licensed
graphics -- that we could committ and critique further -- that would be
great.

Graphics I took from Gallery of AOO (Symbols and Financial. So, I think
that we can freely using this graphics.
About making new page, I would love to do that, but the problem is with my
poor skills. In next Monday starts my education as PHP programmer, and
maybe after that I can totally redesign our site :) but now, I need some
help. Who is interested for making a little team?

Regards,
Wlada


2013/10/29 Kay Schenk kay.sch...@gmail.com

 On Wed, Oct 23, 2013 at 4:09 PM, Vladislav Stevanovic 
 stevanovicvladis...@gmail.com wrote:

  It can be better, with maybe better texts, but main idea is to put
  something what we can named as Master page for developer area. Purpose
 of
  this page is to give the most important links on one place, to save time
  and keep visitors patience, to ensure easier way to reach information.
  So, everyone are invited to give comments and proposals how to improve
 this
  page.
 
  Regards,
  Wlada
 

 If you would like to do an actual html mockup -- compatible licensed
 graphics -- that we could committ and critique further -- that would be
 great.

 You can use the CMS bookmarklet described at:

 http://openoffice.apache.org/developer-faqs.html#im_not_a_committer

 to do this...upload a completely new file.

 I would suggest for now to navigate to :

 http://www.openoffice.org/test/

 and add a new page there.

 Thanks again for this suggestion!

 
 
  2013/10/23 Rob Weir robw...@apache.org
 
   On Tue, Oct 22, 2013 at 8:49 PM, Vladislav Stevanovic
   stevanovicvladis...@gmail.com wrote:
Ok, I made some rough version. The file (see attachment) shows how
 will
looks like web page after you click Develop (on top level menu on
 AOO
website).
So, when you open this file, press F5 (also you can using links on
  second
slide (blue colored words)).
   
  
   I like this design a lot.
  
   -Rob
  
Regards,
Wlada
   
   
2013/10/22 Rob Weir robw...@apache.org
   
On Sun, Oct 20, 2013 at 1:38 AM, Glenn Harvey Liwanag
glennharveyliwa...@gmail.com wrote:
 Another +1 here. I'm actually just reading the e-mails ever since
 I
   got
 here to see if I can get something from those.

 I checked
  https://issues.apache.org/ooo/query.cgi?format=report-table
 and
 https://issues.apache.org/ooo/describecomponents.cgi

 Maybe adding some hot links to common bug lists would help
 everyone
  a
 lot
 and so that the search is not limited by product category. Links
 to
 stuff
 like: Easy, Intermediate, Difficult, Popular,. Giving new ones
 like
   us a
 big list of things that we think can handle, I think, is much
   efficient
 that just us looking for things to work on by category. It's just
 a
 suggestion at best though.

   
The Introduction to Development page has links to BZ views that list
the easy (27 bugs) and simple (16 bugs) categories.
   
http://openoffice.apache.org/orientation/intro-development.html
   
Generally, these bugs are a good start, as a next step after
downloading the code and successfully building.
   
Regards,
   
-Rob
   
 On Sun, Oct 20, 2013 at 12:41 PM, akshika akalanka 
 akshikaakala...@gmail.com wrote:

 I would +1 that idea Wlada, you are really thoughtful. It would
 definitely
 help new developers like us. Thank you. :-)
  On Oct 20, 2013 7:40 AM, Vladislav Stevanovic 
 stevanovicvladis...@gmail.com wrote:

  It seems it's a bit hidden
 
  It is a bit hidden, indeed! And my impression of  this page is
  distant,
  cold tone. No emotions, no pictures to show where is problem,
  there
  is no
  directly approach to the potential developers.  Also, I can not
  see
  list
 of
  features what we want to see in AOO in near future, or maybe
 this
  list
  existed on other place. These features we can split on easy
  task,
  moderate and heavy task. Maybe
  We must improved this. If this is not a problem, I have a  good
   will
  to
 try
  something in that area with some ideas. Is it OK?
 
  Regards,
  Wlada
 
 
 
  2013/10/19 Andrea Pescetti pesce...@apache.org
 
   Vladislav Stevanovic wrote:
  
   Does exist some list of easy tasks that some potential
  developer
   for
 AOO
   can see? Idea is that this sort of  list MUST exist, if we
  want
   to
   see
   here
   new developers...
  
  
   It seems it's a bit hidden, but we've had it for months.
  
   Usually we point new developers to
  
  
  
   http://openoffice.apache.org/**orientation/intro-development.**html
 
 http://openoffice.apache.org/orientation/intro-development.html
  
   that has a chapter named Finding Easy Tasks

Re: Apache

2013-10-29 Thread Keith N. McKenna

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Michael Humpherys wrote:
 Hi,
 
 My name is Mike and I'm interested in getting involved with the
 Apache Foundation projects. I'm currently leaving in eastern Iowa.
 I've got some experience in C++ and I'm interested in doing some
 work in programming and documentation. I'm just trying to figure my
 way around the website to see where and how I can contribute.
 Thanks!
 
 ~Mike Humpherys
 
Greetings Mike;

Welcome to the Apache OpenOffice community. For more information on
contributing to our project you can go to our orientation pages at
http://openoffice.apache.org/orientation/index.html. There you will
find both general information about the project and how it operates
and introductory information geared to different areas such as
documentation, development etc.

I would strongly suggest that you subscribe to this mailing list so as
not to miss any other replies. To subscribe send a blank email to
mailto:dev-subscr...@openoffice.apache.org and then follow the
instructions in the follow-up e-mail you will receive.

Regards
Keith McKenna
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJScEF7AAoJEH0fu5UhGmBCguAH/R31HGygrzxCIxdcrJVzTmGK
rPj/Rw8x1hGcqtJTTsfyFzxcX8rNhHTTGef+89AgPAgUuoyCd2r5gZl9xen/zmc+
RgqPs6CJDOiBJHyeewtOpPwyjb7xyJkaCvgnc30CbaO44Ska3beV+oZxbevez1sQ
gruvKYvaPIsOZcs9pHW77/3Ac1TiDWhl5TNNGu3MS0cYbYNRb7yvlCZ3O8wjUMgQ
Q27eRQUS9f19vXj0YKLSpJN8hN5oT9WnlRAeKVzWP0TO+Xo1QMwvO48tjQErv7K/
NXJFSH8vQ0xwPGlRBMYTY2BwmdDXoTQk2p8ZkqNdlNrpM1bLnySRmhF0L24mCvo=
=avgR
-END PGP SIGNATURE-


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

Re: Extensions

This is update of proposal:
1) Mark all unmaintained extensions on our site (With appropriate mark, and
with button with link to the page where exist new, compatilble version of
extension. Note: button will be added if exist new version. Marks and
buttons will be on preview page, as result of search engeen)
2) Send mail to authors of extensions with request to make appropriate
changes (in some short period)
3) If author does not answer on our mail, or does not update his
extension, we will make this changes inside extension (if licence of
extension permit) and make new web page on site Extensions for this
new version.
4) If an end-user try to download an extension that has not been
updated a pop-up might ask him/her if they're looking for an extension
compatible with AOO 4.x or older version. If they ask for AOO 4.x
they'll be redirected to the new extension page, otherwise they'll get
the 3.x compatible extension.

It is now this proposal good?

Regards,
Wlada


2013/10/29 Roberto Galoppini roberto.galopp...@gmail.com

 2013/10/28 Vladislav Stevanovic stevanovicvladis...@gmail.com:
 Why should we mark them?
 
  If there is some  warning mark, visually you will in easier way to
  know that this extension is not compatible with AOO4.0. We can even
  more.  We can (near that mark) add button for link to the version
  which can run on AOO4.0. Where we can add this marks, buttons?Before
  you actual go inside some of extension's page, you have page where is
  some kind list of extensions, what serve as preview.  I think that this
  page with list of extensions, given by search engine, is not page of
  authors of extensions, so I think that we can freely add this helpful
  marks, buttons etc. Purpose of this is to save time for end-user when
  he/she want to find appropriate extension. But, if somebody miss to
  see marks or he/she using direct link to the author's page of
  extension, your idea to having pop-ups will solve the potential
  problem. With this  pop-up dialog we will get good warnings and solver
  system for end-users.

 You got the gist, right.


 Who's going to do those changes?
 
  That is next step of this discussion. If we have consensus about this
  basic steps (how we want to manage this problem) than next step is to
  see who want to take responsibility for that area. Who have skills,
  time and good will to make changes on site Extensions, and who want
  to made corrections inside extensions (if licence of extensions permit
  that).

 In other words we can provide a platform doing the magic, but we need
 people to take care of updating those Extensions. We might want to run
 in parallel those two processes, though.

 Roberto


 
  Regards,
  Wlada
 
  -
  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

[CWiki] Account Whitelisting

2013-10-29 Thread Michael Humpherys

I have signed up on CWiki under the username: mhumpher and real name:
Michael Humpherys. Thanks!

Mike

Re: Extensions

On Tue, Oct 29, 2013 at 1:16 PM, Vladislav Stevanovic 
stevanovicvladis...@gmail.com wrote:

 This is update of proposal:
 1) Mark all unmaintained extensions on our site (With appropriate mark, and
 with button with link to the page where exist new, compatilble version of
 extension. Note: button will be added if exist new version. Marks and
 buttons will be on preview page, as result of search engeen)
 2) Send mail to authors of extensions with request to make appropriate
 changes (in some short period)
 3) If author does not answer on our mail, or does not update his
 extension, we will make this changes inside extension (if licence of
 extension permit) and make new web page on site Extensions for this
 new version.
 4) If an end-user try to download an extension that has not been
 updated a pop-up might ask him/her if they're looking for an extension
 compatible with AOO 4.x or older version. If they ask for AOO 4.x
 they'll be redirected to the new extension page, otherwise they'll get
 the 3.x compatible extension.

 It is now this proposal good?

 Regards,
 Wlada


Well...I apologize for not keeping up with this conversation earlier, by
here's my take on some of this.

* @Roberto -- it looks like MANY extensions (the ones I've checked anyway)
have version compatibility information. Can this be set-up as a search
filter like OS, etc.? And, perhpas make it the FIRST filter group?

* If this could be done, we wouldn't need to do anything much with
contacting authors, much less changing any code in the extensions. Users
would be able to find extensions for the version they're using without much
trouble.

Again, I apologize for not partaking in this conversations sooner. I'm just
thinking letting users find the appropriate extension themselves might be
easier than taking a more aggressive approach with this.





 2013/10/29 Roberto Galoppini roberto.galopp...@gmail.com

  2013/10/28 Vladislav Stevanovic stevanovicvladis...@gmail.com:
  Why should we mark them?
  
   If there is some  warning mark, visually you will in easier way to
   know that this extension is not compatible with AOO4.0. We can even
   more.  We can (near that mark) add button for link to the version
   which can run on AOO4.0. Where we can add this marks, buttons?Before
   you actual go inside some of extension's page, you have page where is
   some kind list of extensions, what serve as preview.  I think that this
   page with list of extensions, given by search engine, is not page of
   authors of extensions, so I think that we can freely add this helpful
   marks, buttons etc. Purpose of this is to save time for end-user when
   he/she want to find appropriate extension. But, if somebody miss to
   see marks or he/she using direct link to the author's page of
   extension, your idea to having pop-ups will solve the potential
   problem. With this  pop-up dialog we will get good warnings and solver
   system for end-users.
 
  You got the gist, right.
 
 
  Who's going to do those changes?
  
   That is next step of this discussion. If we have consensus about this
   basic steps (how we want to manage this problem) than next step is to
   see who want to take responsibility for that area. Who have skills,
   time and good will to make changes on site Extensions, and who want
   to made corrections inside extensions (if licence of extensions permit
   that).
 
  In other words we can provide a platform doing the magic, but we need
  people to take care of updating those Extensions. We might want to run
  in parallel those two processes, though.
 
  Roberto
 
 
  
   Regards,
   Wlada
  
   -
   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

“Unless someone like you cares a whole awful lot,
 Nothing is going to get better. It's not.”
  -- Dr. Seuss, The Lorax

Re: easy task

On Tue, Oct 29, 2013 at 12:41 PM, Vladislav Stevanovic 
stevanovicvladis...@gmail.com wrote:

 If you would like to do an actual html mockup -- compatible licensed
 graphics -- that we could committ and critique further -- that would be
 great.

 Graphics I took from Gallery of AOO (Symbols and Financial. So, I think
 that we can freely using this graphics.
 About making new page, I would love to do that, but the problem is with my
 poor skills. In next Monday starts my education as PHP programmer, and
 maybe after that I can totally redesign our site :) but now, I need some
 help. Who is interested for making a little team?

 Regards,
 Wlada


OK, I understand...since you gave me a hint about the graphics...maybe I
will try to do a mockup of your idea in the next few days.

Good luck with your PHP programming class. :)

 re new site suggestion...you probably should start a new thread on this.
Folks on the marketing list will likely be interested as well.



 2013/10/29 Kay Schenk kay.sch...@gmail.com

  On Wed, Oct 23, 2013 at 4:09 PM, Vladislav Stevanovic 
  stevanovicvladis...@gmail.com wrote:
 
   It can be better, with maybe better texts, but main idea is to put
   something what we can named as Master page for developer area.
 Purpose
  of
   this page is to give the most important links on one place, to save
 time
   and keep visitors patience, to ensure easier way to reach information.
   So, everyone are invited to give comments and proposals how to improve
  this
   page.
  
   Regards,
   Wlada
  
 
  If you would like to do an actual html mockup -- compatible licensed
  graphics -- that we could committ and critique further -- that would be
  great.
 
  You can use the CMS bookmarklet described at:
 
  http://openoffice.apache.org/developer-faqs.html#im_not_a_committer
 
  to do this...upload a completely new file.
 
  I would suggest for now to navigate to :
 
  http://www.openoffice.org/test/
 
  and add a new page there.
 
  Thanks again for this suggestion!
 
  
  
   2013/10/23 Rob Weir robw...@apache.org
  
On Tue, Oct 22, 2013 at 8:49 PM, Vladislav Stevanovic
stevanovicvladis...@gmail.com wrote:
 Ok, I made some rough version. The file (see attachment) shows how
  will
 looks like web page after you click Develop (on top level menu on
  AOO
 website).
 So, when you open this file, press F5 (also you can using links on
   second
 slide (blue colored words)).

   
I like this design a lot.
   
-Rob
   
 Regards,
 Wlada


 2013/10/22 Rob Weir robw...@apache.org

 On Sun, Oct 20, 2013 at 1:38 AM, Glenn Harvey Liwanag
 glennharveyliwa...@gmail.com wrote:
  Another +1 here. I'm actually just reading the e-mails ever
 since
  I
got
  here to see if I can get something from those.
 
  I checked
   https://issues.apache.org/ooo/query.cgi?format=report-table
  and
  https://issues.apache.org/ooo/describecomponents.cgi
 
  Maybe adding some hot links to common bug lists would help
  everyone
   a
  lot
  and so that the search is not limited by product category. Links
  to
  stuff
  like: Easy, Intermediate, Difficult, Popular,. Giving new ones
  like
us a
  big list of things that we think can handle, I think, is much
efficient
  that just us looking for things to work on by category. It's
 just
  a
  suggestion at best though.
 

 The Introduction to Development page has links to BZ views that
 list
 the easy (27 bugs) and simple (16 bugs) categories.

 http://openoffice.apache.org/orientation/intro-development.html

 Generally, these bugs are a good start, as a next step after
 downloading the code and successfully building.

 Regards,

 -Rob

  On Sun, Oct 20, 2013 at 12:41 PM, akshika akalanka 
  akshikaakala...@gmail.com wrote:
 
  I would +1 that idea Wlada, you are really thoughtful. It would
  definitely
  help new developers like us. Thank you. :-)
   On Oct 20, 2013 7:40 AM, Vladislav Stevanovic 
  stevanovicvladis...@gmail.com wrote:
 
   It seems it's a bit hidden
  
   It is a bit hidden, indeed! And my impression of  this page
 is
   distant,
   cold tone. No emotions, no pictures to show where is problem,
   there
   is no
   directly approach to the potential developers.  Also, I can
 not
   see
   list
  of
   features what we want to see in AOO in near future, or maybe
  this
   list
   existed on other place. These features we can split on easy
   task,
   moderate and heavy task. Maybe
   We must improved this. If this is not a problem, I have a
  good
will
   to
  try
   something in that area with some ideas. Is it OK?
  
   Regards,
   Wlada
  
  
  
   2013/10/19 Andrea Pescetti pesce...@apache.org
  
Vladislav Stevanovic wrote:

Re: [PROPOSAL] End-of-Life for OpenOffice.org 3.3.0

On Tue, Oct 29, 2013 at 9:22 AM, Rob Weir robw...@apache.org wrote:

 On Tue, Oct 29, 2013 at 11:51 AM, Rob Weir robw...@apache.org wrote:
  I'd like to move forward now with this proposal from July.
 
  I've updated the EOL page here to say that OOo 3.3.0 and earlier are
  no longer supported.  That page also explains what this means.
 
  http://www.openoffice.org/development/releases/eol.html
 
  I'll start to do the other 3 items now.  I'll coordinate with Oliver
  on the update notifications.
 

 And here is a draft of the landing page we'd send users to who have an
 older version of OOo if there is not an AOO version in their language:

 http://www.openoffice.org/development/releases/eol-nl.html

 Regards,

 -Rob


+1

both look good to me



  Of course, help on any of these items is welcome.
 
  Regards,
 
  -Rob
 
 
  On Sun, Jul 21, 2013 at 11:28 PM, Shenfeng Liu liush...@gmail.com
 wrote:
  2013/7/19 Rob Weir robw...@apache.org
 
  We currently have this link from the download page,from 2009,
  announcing end-of-life for OpenOffice.org 2.x:
 
  http://www.openoffice.org/development/releases/eol.html
 
  I'd like to update that page to also state that 3.x version prior to
  3.4.x are also end-of-life.  Why?  We're unlikely to issue any more
  security patches for 3.3.0 or earlier.
 
  So the concrete proposal is:
 
  1) Update the eol.html page to state that OOo 3.3.0 and earlier are no
  longer supported.
 
  2) Create a new landing page for users of OOo 3.3.0 and before who are
  using a language version that we do not yet have a translation.
  Explain in this page that the earlier versions are no longer
  supported.  List what translations are currently available and where
  they can be downloaded from.  Give information on how they can
  volunteer to help translate AOO into their native language.
 
  3) Configure the update notification server to OOo 3.3.0 users to this
  new landing page, if their language is not already translated.  (Where
  there is a translation we already point them to the download page)
 
  4) Blog post/announcement on end-of-life for OOo 3.3.0 and earlier.
 
  The end result is that:  1) We made it clear what versions are
  supported.  2) We did our due diligence to reach out to users of older
  versions.  3) We encourage new translation volunteers.
 
  No rush on this.  It does not need to be done at the same time as the
  4.0 announcement.  It can follow a week or so later.
 
  -Rob
 
 
 
  +1
 
  - Shenfeng (Simon)
 
 
 
 
 
  -
  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

“Unless someone like you cares a whole awful lot,
 Nothing is going to get better. It's not.”
  -- Dr. Seuss, The Lorax

Re: easy task

maybe I will try to do a mockup of your idea in the next few days.

Be my guest :)

I will be happy if you sent me your version, or link, to see how it looks
like, for further suggestions.

Good luck with your PHP programming class. :)
Thanks!

Regards,
Wlada


2013/10/29 Kay Schenk kay.sch...@gmail.com

 On Tue, Oct 29, 2013 at 12:41 PM, Vladislav Stevanovic 
 stevanovicvladis...@gmail.com wrote:

  If you would like to do an actual html mockup -- compatible licensed
  graphics -- that we could committ and critique further -- that would be
  great.
 
  Graphics I took from Gallery of AOO (Symbols and Financial. So, I
 think
  that we can freely using this graphics.
  About making new page, I would love to do that, but the problem is with
 my
  poor skills. In next Monday starts my education as PHP programmer, and
  maybe after that I can totally redesign our site :) but now, I need some
  help. Who is interested for making a little team?
 
  Regards,
  Wlada
 

 OK, I understand...since you gave me a hint about the graphics...maybe I
 will try to do a mockup of your idea in the next few days.

 Good luck with your PHP programming class. :)

  re new site suggestion...you probably should start a new thread on this.
 Folks on the marketing list will likely be interested as well.


 
  2013/10/29 Kay Schenk kay.sch...@gmail.com
 
   On Wed, Oct 23, 2013 at 4:09 PM, Vladislav Stevanovic 
   stevanovicvladis...@gmail.com wrote:
  
It can be better, with maybe better texts, but main idea is to put
something what we can named as Master page for developer area.
  Purpose
   of
this page is to give the most important links on one place, to save
  time
and keep visitors patience, to ensure easier way to reach
 information.
So, everyone are invited to give comments and proposals how to
 improve
   this
page.
   
Regards,
Wlada
   
  
   If you would like to do an actual html mockup -- compatible licensed
   graphics -- that we could committ and critique further -- that would be
   great.
  
   You can use the CMS bookmarklet described at:
  
   http://openoffice.apache.org/developer-faqs.html#im_not_a_committer
  
   to do this...upload a completely new file.
  
   I would suggest for now to navigate to :
  
   http://www.openoffice.org/test/
  
   and add a new page there.
  
   Thanks again for this suggestion!
  
   
   
2013/10/23 Rob Weir robw...@apache.org
   
 On Tue, Oct 22, 2013 at 8:49 PM, Vladislav Stevanovic
 stevanovicvladis...@gmail.com wrote:
  Ok, I made some rough version. The file (see attachment) shows
 how
   will
  looks like web page after you click Develop (on top level menu
 on
   AOO
  website).
  So, when you open this file, press F5 (also you can using links
 on
second
  slide (blue colored words)).
 

 I like this design a lot.

 -Rob

  Regards,
  Wlada
 
 
  2013/10/22 Rob Weir robw...@apache.org
 
  On Sun, Oct 20, 2013 at 1:38 AM, Glenn Harvey Liwanag
  glennharveyliwa...@gmail.com wrote:
   Another +1 here. I'm actually just reading the e-mails ever
  since
   I
 got
   here to see if I can get something from those.
  
   I checked
https://issues.apache.org/ooo/query.cgi?format=report-table
   and
   https://issues.apache.org/ooo/describecomponents.cgi
  
   Maybe adding some hot links to common bug lists would help
   everyone
a
   lot
   and so that the search is not limited by product category.
 Links
   to
   stuff
   like: Easy, Intermediate, Difficult, Popular,. Giving new ones
   like
 us a
   big list of things that we think can handle, I think, is much
 efficient
   that just us looking for things to work on by category. It's
  just
   a
   suggestion at best though.
  
 
  The Introduction to Development page has links to BZ views that
  list
  the easy (27 bugs) and simple (16 bugs) categories.
 
  http://openoffice.apache.org/orientation/intro-development.html
 
  Generally, these bugs are a good start, as a next step after
  downloading the code and successfully building.
 
  Regards,
 
  -Rob
 
   On Sun, Oct 20, 2013 at 12:41 PM, akshika akalanka 
   akshikaakala...@gmail.com wrote:
  
   I would +1 that idea Wlada, you are really thoughtful. It
 would
   definitely
   help new developers like us. Thank you. :-)
On Oct 20, 2013 7:40 AM, Vladislav Stevanovic 
   stevanovicvladis...@gmail.com wrote:
  
It seems it's a bit hidden
   
It is a bit hidden, indeed! And my impression of  this page
  is
distant,
cold tone. No emotions, no pictures to show where is
 problem,
there
is no
directly approach to the potential developers.  Also, I can
  not
see
list
   of
features what we want to see in AOO in

Re: Submission for consultants page

On Tue, Oct 29, 2013 at 11:41 AM, Rob Weir robw...@apache.org wrote:

 On Mon, Oct 28, 2013 at 1:00 PM, Kay Schenk kay.sch...@gmail.com wrote:
  On Sat, Oct 26, 2013 at 6:56 PM, Rob Weir robw...@apache.org wrote:
 
  On Sat, Oct 26, 2013 at 5:57 PM, Kay Schenk kay.sch...@gmail.com
 wrote:
   On Sat, Oct 26, 2013 at 1:24 PM, Rob Weir robw...@apache.org wrote:
  
   On Sat, Oct 26, 2013 at 1:35 PM, Kay Schenk kay.sch...@gmail.com
  wrote:
On Sat, Oct 26, 2013 at 5:21 AM, Jörg Schmidt 
 joe...@j-m-schmidt.de
   wrote:
   
Hello *,
   
   
 From: Kay Schenk [mailto:kay.sch...@gmail.com]
   
 So...this thread does not meet lazy consensus but are we
 ready to
 implement this addition, without further changes, anyway?
 I'll be happy to
 take care of this either later today or tomorrow if we are.
   
Can you please summarize what the solution should look like?
   
The thread is long and I have somewhat lost track as point # 4
  should
   be
changed.
Should he ever be changed or what says:
   
 ... Can be eased a bit as it is clear enough did the
 Items are with and for our project, respectively. product.
   
   
In particular, it would be important for me to know whether I can
  change
my website (http://www.jm-schmidt.de/inhalt.html) or must.
   
   
   
Greetings,
Jörg
   
   
   
 -
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
   
   
My take on this discussion so far  (and I am certainly NOT the
  definitive
judge on this):
   
* there is the listing on the consultants page itself:
http://www.openoffice.org/bizdev/consultants.html
   
  
   I wrote that page, so it might not be too presumptuous if I say what
 I
   meant when I wrote it ;-)
  
   The guideline is that the 3rd party pages must respect ASF
   Trademarks.  This is vague, but intentionally so.   I think we'll
 all
   be more accurate judges of what is wrong when we see it than we are
   predictors of all things that could possibly be wrong.  So the
   discretion is given to the PMC to take this on a case-by-case basis.
   We should be looking at each submission and their linked websites as
 a
   whole.
  
   The kinds of abuses I had in mind were mainly pages that implied that
   the services were endorsed or affiliated with the ASF.   This is much
   more than technicalities of whether or not a (TM) symbol is used.
  For
   example, a page that calls itself Apache OpenOffice (TM) Consulting
   Group would *not* be OK. We don't want our trademarks used as
   adjectives, since that suggests an affiliation.
  
   I also had in mind that we might need to correct names where they are
   misstated, e.g., Apache Open Office, Apache Openoffice,
   OpenOffice.org, etc.
  
   Regards,
  
   -Rob
  
  
   OK -- I think we should go ahead with this. Unfortunately, testing
 with
  my
   private web area on my box, my server is balking at the .xsl page
 that
   goes with this...so...
  
 
  The command line should look something like:
 
  xsltproc -o consultants.html --stringparam locale en to-html.xsl
  consultants.xml
 
  You can switch locales by setting different values via stringparam
  parameter.
 
  Other XSLT engines should work, but the command line would be different.
 
 
  ok, that's not what I was using...this seems to work and not complain
 about
  the stylesheet being invalid.
 
 
 
   Rob, since you have always taken care of this in the past, I would be
  fine
   and dandy with you committing this change -- wearing your Apache hat
   instead of your IBM one of course. ;)
  
 
  Sure, I can do it next week when I am at my desk.
 
  Regards,
 
  -Rob
 
 
  Anyway, I was just about to do this when I see that there is no contact
  info -- e-mail, phone etc. -- supplied with this listing as with the
  others. I see there's a phone number supplied on the website, so maybe
 just
  include that?
 

 If you include the phone number you would also want to include the
 priority code that is on the webpage.   Or don't have a phone
 number.

 -Rob


I felt odd about suggesting this at all -- but it just looked a bit out of
place with the other listings we have without some contact information.

So,  with your OK, I will add the phone number and priority code and get on
with this. Of course, it can always be changed.




 
 
   So sorry about this -- I guess it's time for more of us to give this
  area a
   bit more attention.
  
  
  
concerning the actual content we are discussing. This does not
 have a
   (TM)
after Apache OpenOffice. I thought this was the original cause of
   objection.
   
And, we can see from the listings on the consultants page that we
 did
  not
enforce a (TM) after Apache OpenOffice on the consultants page.
   
* there are the actual websites of the consultants, like yours,

Re: Link to Windows SDK 4.0.1 is broken

2013-10-29 Thread Andrea Pescetti


On 18/10/2013 Polk, Henry wrote:

Yes. The install package for Office is ok, it's just SDK package was giving me 
an error.
This is exact error from web server:
The requested URL 
/dist/externaldist/openoffice/4.0.1/binaries/SDK/Apache_OpenOffice-SDK_4.0.1_Win_x86_install_en-US.exe
 was not found on this server.
I have tried download this from two different locations and got same result.


Thank you, links in
http://openoffice.apache.org/downloads.html
have now been corrected as suggested by Rob.

Regards,
  Andrea.

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

Re: Extensions

2013-10-29 Thread Roberto Galoppini

2013/10/29 Kay Schenk kay.sch...@gmail.com:
 On Tue, Oct 29, 2013 at 1:16 PM, Vladislav Stevanovic 
 stevanovicvladis...@gmail.com wrote:

 This is update of proposal:
 1) Mark all unmaintained extensions on our site (With appropriate mark, and
 with button with link to the page where exist new, compatilble version of
 extension. Note: button will be added if exist new version. Marks and
 buttons will be on preview page, as result of search engeen)
 2) Send mail to authors of extensions with request to make appropriate
 changes (in some short period)
 3) If author does not answer on our mail, or does not update his
 extension, we will make this changes inside extension (if licence of
 extension permit) and make new web page on site Extensions for this
 new version.
 4) If an end-user try to download an extension that has not been
 updated a pop-up might ask him/her if they're looking for an extension
 compatible with AOO 4.x or older version. If they ask for AOO 4.x
 they'll be redirected to the new extension page, otherwise they'll get
 the 3.x compatible extension.

 It is now this proposal good?

 Regards,
 Wlada


 Well...I apologize for not keeping up with this conversation earlier, by
 here's my take on some of this.

 * @Roberto -- it looks like MANY extensions (the ones I've checked anyway)
 have version compatibility information. Can this be set-up as a search
 filter like OS, etc.? And, perhpas make it the FIRST filter group?

 * If this could be done, we wouldn't need to do anything much with
 contacting authors, much less changing any code in the extensions. Users
 would be able to find extensions for the version they're using without much
 trouble.

 Again, I apologize for not partaking in this conversations sooner. I'm just
 thinking letting users find the appropriate extension themselves might be
 easier than taking a more aggressive approach with this.

Great idea Kay!
+1
I'll look into what it takes to make it in the very next days, stay tuned!









 2013/10/29 Roberto Galoppini roberto.galopp...@gmail.com

  2013/10/28 Vladislav Stevanovic stevanovicvladis...@gmail.com:
  Why should we mark them?
  
   If there is some  warning mark, visually you will in easier way to
   know that this extension is not compatible with AOO4.0. We can even
   more.  We can (near that mark) add button for link to the version
   which can run on AOO4.0. Where we can add this marks, buttons?Before
   you actual go inside some of extension's page, you have page where is
   some kind list of extensions, what serve as preview.  I think that this
   page with list of extensions, given by search engine, is not page of
   authors of extensions, so I think that we can freely add this helpful
   marks, buttons etc. Purpose of this is to save time for end-user when
   he/she want to find appropriate extension. But, if somebody miss to
   see marks or he/she using direct link to the author's page of
   extension, your idea to having pop-ups will solve the potential
   problem. With this  pop-up dialog we will get good warnings and solver
   system for end-users.
 
  You got the gist, right.
 
 
  Who's going to do those changes?
  
   That is next step of this discussion. If we have consensus about this
   basic steps (how we want to manage this problem) than next step is to
   see who want to take responsibility for that area. Who have skills,
   time and good will to make changes on site Extensions, and who want
   to made corrections inside extensions (if licence of extensions permit
   that).
 
  In other words we can provide a platform doing the magic, but we need
  people to take care of updating those Extensions. We might want to run
  in parallel those two processes, though.
 
  Roberto
 
 
  
   Regards,
   Wlada
  
   -
   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

 “Unless someone like you cares a whole awful lot,
  Nothing is going to get better. It's not.”
   -- Dr. Seuss, The Lorax

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

Re: The crux with 2 open standards for more or less the same thing

On Tue, Oct 29, 2013 at 12:05 PM, Andrew Rist andrew.r...@oracle.comwrote:


 On 10/28/2013 12:38 PM, Jörg Schmidt wrote:

 Hello,

  From: Andrea Pescetti [mailto:pesce...@apache.org]

 That is the reason why we will start to investigate in a

 better OOXML

 support for AOO and you will probably notice some more

 activity in the

 future going in this direction.

 Excellent. A better Microsoft compatibility is what our users
 set as #1
 priority in the user survey and improving OOXML import (and
 export!) is
 surely part of that.

 This is a pragmatic way, also a necessary way, but I fear it will be in
 the long
 run, even the death of the current ODF.

 No user of MS Office will move more of OOXML to ODF, if the compatibility
 of OOXML
 in AOO will be similar as well of *.doc.

 It is not wrong to improve compatibility with OOXML, but that will
 unfortunately
 be the side effect. I think that you should see clearly.

 We must also see that the need to improve the compatibility with OOXML,
 unfortunately, also an expression of the fact that market dominance
 continues to
 have MS Office .

 I look at what happens at the ISO, where they talked some time ago by the
 merging
 of the two standards ( ODF and OOXML), and take statements from experts
 seriously,
 it seems to me the path mapped out, there will be a new standard in the
 future,
 even if no one likes to hear.

 http://xkcd.com/927/


LOL! yep! :)





 We should all prepare ourselves to it and work on it that it prevents the
 MS this
 standard does not dominate. That's what we should see as a long term goal.
 I am thinking there must be cooperation between _all_ the OSS projects
 will use
 the ODF.


 Greetings,
 Jörg



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



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




-- 
-
MzK

“Unless someone like you cares a whole awful lot,
 Nothing is going to get better. It's not.”
  -- Dr. Seuss, The Lorax

Re: Extensions

@Kay: In my earlier mail of this discussion:  Also, Filter option on
site Extension need to has option for what version of AOO you want to
find extension.
I do not know how I droped this from my Proposals.


Regards,
Wlada


2013/10/29 Roberto Galoppini roberto.galopp...@gmail.com

 2013/10/29 Kay Schenk kay.sch...@gmail.com:
  On Tue, Oct 29, 2013 at 1:16 PM, Vladislav Stevanovic 
  stevanovicvladis...@gmail.com wrote:
 
  This is update of proposal:
  1) Mark all unmaintained extensions on our site (With appropriate mark,
 and
  with button with link to the page where exist new, compatilble version
 of
  extension. Note: button will be added if exist new version. Marks and
  buttons will be on preview page, as result of search engeen)
  2) Send mail to authors of extensions with request to make appropriate
  changes (in some short period)
  3) If author does not answer on our mail, or does not update his
  extension, we will make this changes inside extension (if licence of
  extension permit) and make new web page on site Extensions for this
  new version.
  4) If an end-user try to download an extension that has not been
  updated a pop-up might ask him/her if they're looking for an extension
  compatible with AOO 4.x or older version. If they ask for AOO 4.x
  they'll be redirected to the new extension page, otherwise they'll get
  the 3.x compatible extension.
 
  It is now this proposal good?
 
  Regards,
  Wlada
 
 
  Well...I apologize for not keeping up with this conversation earlier, by
  here's my take on some of this.
 
  * @Roberto -- it looks like MANY extensions (the ones I've checked
 anyway)
  have version compatibility information. Can this be set-up as a search
  filter like OS, etc.? And, perhpas make it the FIRST filter group?
 
  * If this could be done, we wouldn't need to do anything much with
  contacting authors, much less changing any code in the extensions. Users
  would be able to find extensions for the version they're using without
 much
  trouble.
 
  Again, I apologize for not partaking in this conversations sooner. I'm
 just
  thinking letting users find the appropriate extension themselves might be
  easier than taking a more aggressive approach with this.

 Great idea Kay!
 +1
 I'll look into what it takes to make it in the very next days, stay tuned!




 
 
 
 
 
  2013/10/29 Roberto Galoppini roberto.galopp...@gmail.com
 
   2013/10/28 Vladislav Stevanovic stevanovicvladis...@gmail.com:
   Why should we mark them?
   
If there is some  warning mark, visually you will in easier way to
know that this extension is not compatible with AOO4.0. We can even
more.  We can (near that mark) add button for link to the version
which can run on AOO4.0. Where we can add this marks, buttons?Before
you actual go inside some of extension's page, you have page where
 is
some kind list of extensions, what serve as preview.  I think that
 this
page with list of extensions, given by search engine, is not page of
authors of extensions, so I think that we can freely add this
 helpful
marks, buttons etc. Purpose of this is to save time for end-user
 when
he/she want to find appropriate extension. But, if somebody miss to
see marks or he/she using direct link to the author's page of
extension, your idea to having pop-ups will solve the potential
problem. With this  pop-up dialog we will get good warnings and
 solver
system for end-users.
  
   You got the gist, right.
  
  
   Who's going to do those changes?
   
That is next step of this discussion. If we have consensus about
 this
basic steps (how we want to manage this problem) than next step is
 to
see who want to take responsibility for that area. Who have skills,
time and good will to make changes on site Extensions, and who
 want
to made corrections inside extensions (if licence of extensions
 permit
that).
  
   In other words we can provide a platform doing the magic, but we need
   people to take care of updating those Extensions. We might want to run
   in parallel those two processes, though.
  
   Roberto
  
  
   
Regards,
Wlada
   
   
 -
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
 
  “Unless someone like you cares a whole awful lot,
   Nothing is going to get better. It's not.”
-- Dr. Seuss, The Lorax

 -
 To unsubscribe, e-mail:

Re: Extensions