Re: ia2 Buildbot needs attention

2013-11-12 Thread Herbert Duerr

On 11.11.2013 11:12, Steve Yin wrote:

Based on Herbert suggestion, I will synchronize the branch with the latest
trunk. And the build issue will go away. :)


Thanks for synchronizing with trunk! That solved the problem, the ia2 
builds are successful again and the install packages are available [1].


[1] http://ci.apache.org/projects/openoffice/#w7ia2

Herbert

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



How can I know that this file effects save/export feature ?

2013-11-12 Thread Vivek Rai
I want to especially be part of developement activity in save/export. for
that matter, i've been reading QA bugs on bugzilla but what i want to know
(for ease) that how can i know that which file or which part of file
effects save/export features in svn ?
If anyone can give hint, please provide.

Thanks

Vivek Rai


Re: Time to think about a Language Update release?

2013-11-12 Thread Jürgen Schmidt
On 11/12/13 4:48 AM, Kay Schenk wrote:
 On Nov 11, 2013 6:37 AM, Jürgen Schmidt jogischm...@gmail.com wrote:

 On 11/10/13 8:06 PM, Kay Schenk wrote:
 On Sun, Nov 3, 2013 at 11:05 AM, Ricardo Berlasso
 rgb.m...@gmail.comwrote:

 2013/11/3 Keith N. McKenna keith.mcke...@comcast.net

 Andrea Pescetti wrote:
 Comparing http://www.openoffice.org/download/other.html
 and https://translate.apache.org/projects/aoo40/ I see that
 we have: - Two unreleased languages that are now 100%
 translated (Bulgarian and Danish) - One language with only
 about 1000 words left and activity in the last week
 (Norwegian Bokmal) - Three languages with about 4000 words
 left and activity in the last week (Thai, Uighur, Hebrew;
 Indonesian and Icelandic are in the same group, but less
 active)

 Would it make sense to schedule a language update 4.0.1
 release for late November? I mean something like: announce
 a translation deadline on the l10n list, produce SDF files
 for the languages that reach 100% (which of course already
 include Bulgarian and Danish, and hopefully some of the
 other languages listed above), building only those
 languages and releasing an updated source package and
 binaries for those languages.

 Yes I believe that it would make sense and would add to our
 reputation for actively supporting native languages.


 Indeed. +1 from my part for a language update to 4.0.1.

 Regards, Ricardo


 +1

 I also think this would be a good idea...hopefully our Release
 Manager will comment soon.

 In general I am always a fan of having further languages available as
 soon as possible. But we are still in the situation that our builds
 and releases take some time. We have no Mac build bot and we don't
 have Linux systems that can build against our currently existing
 baseline.
 
 I know we don't have a Mac buildbot but what is meant by the Linux comment.
 The last I saw 32-bit nightly was OK. 64-bit success seems intermittent. Is
 this what you mean?

as far as I know the build bots are based on newer systems (Ubuntu 12.04
for 32 bit and 10.04 for 64bit). We build on an older CentOS 5.10 system
which is comaptible to RedHat Enterprise Linux 5. This ensures that our
builds can be used on more different Linux systems.

Juergen

 
 All this should be taken into account and even a language
 update requires some time and we should think careful if we want to do
 it for 2 languages only.

 I we can complete at least 5 languages until end of Nov. we can make
 language update only. Means we will release only this new languages on
 the AOO401 branch + a new source release. The same as we did for 3.4.1
 where we released 12 new languages.

 And this is only a time limiting factor because many other things are
 to do and we already started thinking about a 4.1 release.

 But I am open and in the end I won't be the limiting element here even
 if I ave to do major parts of such a release

 Juergen










 It would make more snse
 So this would work like we did for 3.4.1 when we added new
 languages. Why not call it 4.0.2? Well, we already
 discussed it, but the main reasons would be: for the
 languages already released in 4.0.1, 4.0.2 would be
 identical (example: 4.0.1 in French would be identical to
 4.0.2 in French) since all commits in the meantime have
 been done to trunk; a new 4.0.2 release takes a much
 larger effort than a 4.0.1 language update, so it is harder
 to find volunteers and this is worth doing only if we have
 some important bugfixes for 4.0.1 to include (and I don't
 see any at the moment).

 It would make more sense for it to be 4.0.1 unless there were
 critical bug fixes that would justify a 4.0.2. The only potential
 glitch that I see is handling the release notes. I have a couple of
 ideas that I will lay out in a separate thread if we decide to go
 ahead with a language only release.

 Regards Keith
 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

 


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



Re: Call for Automation BVT volunteer for AOO4.1

2013-11-12 Thread Liu Ping
Hi,all

Because Build update for synchronize ia2 branch with the latest trunk , So
make BVT for  410m1(Build:9750) (en-US) Rev
1540658https://fisheye6.atlassian.com/changelog/~br=trunk/ooo/?showid=1540658


BVT  result :

All 22 testcases , Pass 22,  Fail 0, Error 0 , Ignored 0

The detailed information ,please refer capture.png and  http://wiki.
openoffice.org/wiki/QA/BVT_Report,




On Fri, Nov 8, 2013 at 2:41 PM, Liu Ping doneyours...@gmail.com wrote:

 Hi, Sandhya

 Ia2 branch builds is ready, focus on BTV Automatic testing on Windows
 Plaform
 The ia2 branch builds are on the daily Buildbot, current is rev 1539225
 http://ci.apache.org/projects/openoffice/install/w7ia2/Apache_OpenOffice
 _4.1.0_Win_x86_install_en-US.exe_1539225.exe

 You can post the BVT result on, thanks
 http://wiki.openoffice.org/wiki/QA/BVT_Report,

 And we need more volunteers on multi-platform(Linux 64bit and Mac 10.8 and
 Mac 10.9 ) to support continuing testing ,please reply this letter and post
 your name/email and your platform

 Thanks




 On Wed, Nov 6, 2013 at 6:37 AM, Kay Schenk kay.sch...@gmail.com wrote:

 On Tue, Nov 5, 2013 at 1:41 PM, Andrew Rist andrew.r...@oracle.com
 wrote:

 
  On 11/5/2013 10:32 AM, Kay Schenk wrote:
 
  On Mon, Nov 4, 2013 at 10:15 AM, Alexandro Colorado j...@oooes.org
  wrote:
 
   I reported this a while back:
  http://markmail.org/message/x2plcngb6xczxbch
 
   yes...we have NIGHTLY 32 bit RPMS buildt from trunk  but not
  snapshot
  builds -- those built from the snapshot trunk -- at the moment.
 
 
  I believe the rpm was failing on the snapshot, and I did not have the
 time
  to sort that.  I'll try with the rpms, and if it succeeds we'll leave
 that
  running.
 
  A.
 
 
 
 OK, thanks -- I didn't know if the linux-32 snapshot was just setup to
 output debs or ??? so thanks for this note.


 
 
 
 
  On Mon, Nov 4, 2013 at 12:00 PM, Kay Schenk kay.sch...@gmail.com
  wrote:
 
  On Sun, Nov 3, 2013 at 9:18 PM, Liu Ping doneyours...@gmail.com
  wrote:
 
   Hi ,Kay
  Maybe you can get RPM packs for 32-bit Linux snapshot. from
  http://ci.apache.org/projects/openoffice/
 
   Hi. These snapshot packs are all deb format, not rpm. I don't
 know
 
  what
 
  the decisions were concerning these setups.
 
  OK. I will see what I can find out about this. There ARE nightly
  Linux-32
  rpm packs but not from the SNAPSHOT trunk.
 
 
 
  On Sun, Nov 3, 2013 at 1:16 AM, Kay Schenk kay.sch...@gmail.com
 
  wrote:
 
  On Fri, Oct 25, 2013 at 1:09 AM, Liu Ping doneyours...@gmail.com
 
  wrote:
 
  Hi, all.
 
  BVT(Build Verification Testing)  is a set of tests that run on new
 
  build
 
  to
 
  verify that whether the build is testable or not,  which play an
 
  important
 
  role in software quality
 
  Encourage more efforts in community to engage in automation BVT
 
for
 
  AOO
 
  4.1 (refer item 5 in AOO 4.1 Test Arrangement)
 
(1)First, Welcome volunteers familiar with BVT according by the
 
  guidence
 
  http://wiki.openoffice.org/wiki/QA/BVT
 
   Hi --
 
  Currently, there are no RPM packs for 32-bit Linux snapshot.
  Does anyone know why?
 
 
  Below are prerequisites:
 
  1) 1)Environment tool: SVN Client, JDK, Ant
 
  2) 2)Soft Skills:
 
  · a.Basic skills about Windows Command line,
  Linux/Mac Terminal
 
  · b.Basic knowledge of Java
 
  If have some problems, please put forward issues that block you. I
 
  will
 
  help to resolve it.
 
  (2)Second, Notice new build and collect volunteers’ BTV result.
 
  Please post your name/email and your platform , When new build is
 
  ready
 
I
 
  will notice by email.
 
  Volunteer  post your result on
  http://wiki.openoffice.org/wiki/QA/BVT_Report, thx.
 
 
 
  --
 
 
   
  -
 
  MzK
 
  “Unless someone like you cares a whole awful lot,
Nothing is going to get better. It's not.”
 -- Dr. Seuss, The Lorax
 
 
 
  --
 
   
  -
 
  MzK
 
  “Unless someone like you cares a whole awful lot,
Nothing is going to get better. It's not.”
 -- Dr. Seuss, The Lorax
 
 
 
 
  --
  Alexandro Colorado
  Apache OpenOffice Contributor
  http://www.openoffice.org
  882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614
 
  -
  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,
  

Re: Build braker in rejuvenate01 cppu

2013-11-12 Thread Herbert Dürr

Hi Raphael,

On 11.11.2013 10:47, Raphael Bircher wrote:

I run in a build breaker in the rejuvenate01 branche

dmake:  Error: -- `uno_purpenvhelpers5abi.map' not found, and can't be made


I just committed r1540968 to add the missing file by renaming its older 
cousin.



Has someone a idea what happend here, and what's wrong?


The rejuvenate01 branch had its UNO bridge renamed. UNO bridges are 
named after the calling convention supported by them. C++ calling 
conventions used to be very specific to the compiler/platform/etc. but 
things have settled and became standardized.


With the rejuvenate branch we are using the standard C++ tool chain on 
the OSX platform (XCode4/5) and build for the standard C++ calling 
conventions [1]. So the name I originally chose (cxx) emphasized the 
fact that the new UNO bridge was for the standard C++ ABI on the target 
platform.


[1] 
https://developer.apple.com/library/mac/documentation/developertools/conceptual/LowLevelABI/000-Introduction/introduction.html


Other developers disagreed with naming it cxx (for C++) as that name 
is quite generic. So I mentioned the fully qualified ABI name of the 
standard C++ ABI on this platform which is System V Application Binary 
Interface [for the] AMD64 Architecture and Jürgen abbreviated it as 
s5abi.


Thanks for looking into the rejuvenate01 branch. With the renaming and 
the recent major update from trunk it has become a construction site 
though. After the RmMoz work I can now focus on getting the branch round 
again and make it a viable port. So stay tuned, in a few days it will 
build+run out of the box again and it will have gained an important 
feature it missed so far: support for password protected documents!


Herbert

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



Re: [Accessibility] IA2 Integration proposal

2013-11-12 Thread MENGUAL Jean-Philippe

Hi,

I use Windows XP Pro, and now I am working on r1540658.

regsvr2.exe /U UAccCOM.dl says: module not found.

How should I register


oleacc.dll and oleaut32.dll? Is it relevant on XP (the bug you mention seems to 
be on W7).

Regards,


 


Le 11/11/2013 14:43, V Stuart Foote a écrit :

Jean-Phillipe,

Removal of earlier revisions of the ia2 branch may have corrupted the MSAA
libraries.

Have you unregistered UAccCOM.dll with a regsvr2.exe /U command, and  have
you tried re-registering the oleacc.dll and oleaut32.dll?

Additional notes in issue  aoo#123640




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

Stuart




--
View this message in context: 
http://openoffice.2283327.n4.nabble.com/Accessibility-IA2-Integration-proposal-tp4655454p460.html
Sent from the Development mailing list archive at Nabble.com.

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





--

Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: te...@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu


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



Re: Time to start 4.1 planning?

2013-11-12 Thread Shenfeng Liu
2013/11/12 Rob Weir robw...@apache.org

 On Mon, Nov 11, 2013 at 3:21 PM, Marcus (OOo) marcus.m...@wtnet.de
 wrote:
  Am 11/11/2013 04:12 PM, schrieb Jürgen Schmidt:
 
  On 11/11/13 3:59 PM, Rob Weir wrote:
 
  On Mon, Nov 11, 2013 at 3:32 AM, Shenfeng Liuliush...@gmail.com
  wrote:
 
  Hi, all,
 It was one month since 4.0.1 release. And I noticed some some great
  works
  are going to be delivered soon. e.g. the IA2 framework from Steve, the
  Mac
  64-bit support from Herbert, and Windows Patch mechanism from Andre.
 
 So I'm thinking, is it a good time to start the 4.1 plan now? We
  should
  deliver those great value to our users through a formal release ASAP!
  And
  IMO, even only the 3 items above can be enough for a release to be
  called
  4.1. We also want to do OOXML improvement by integrating OSBA patches,
  and
  enhance user experience like in-place Input Field, and many other
  things...
  While, I think we can keep the continuous improvement across releases.
  From
  the record breaking download number since 4.0 and 4.0.1, I feel that
  keeping regular release is very important to response to our users,
  attract
  more new comers, and bring this product to success.
 
 So I suggest we start the 4.1 plan now, and set a target date.
 Since
  4.0
  was in July, 4.0.1 was in Oct, I feel some time in 1Q will be a good
  time
  for 4.1.
 
 
  Hi Simon,
 
  Something to think about:   After 4.0.0 we discussed having a public
  beta with out next major release.  If we think this is worth doing,
  then we should plan on two dates:  1) A public beta data, and 2) a
  final release date.   For the beta to be useful I think we would want
  it to last 3-4 weeks, enough time to process any new bug reports,
  identify any critical regressions, and fix them.
 
 
  4 weeks between both is a minimum form my pov
 
  But having a beta is of course the route we should take.
 
 
  What about taking into account to keep the possibility to release a
 second
  Beta version? It can include fixes for the most nasty and prominent bugs.
 

 Well, hopefully we do some amount of testing before we have a beta.
 So the goal should be for the beta to have no nasty and prominent
 bugs.  The beta is a form of insurance and a way of setting
 expectations.

 For example, I think these two scenarios are technically equivalent:

 a) release 4.1.0 after normal testing

 b) release 4.1.1 to fix major bugs that we missed in 4.1.0 testing.

 and

 a') release 4.1.0 beta after normal testing

 b') release 4.1.0 GA after fixing important bugs found in beta

 These are technically the same, and take approximately the same amount
 of time.  The difference is in user expectations.  A beta
 designation tells the cautious user to avoid it.  It encourages users
 who are willing to take more risk and help us by giving feedback.  It
 also helps preserve the brand reputation by ensuring that the actual
 GA releases are high quality.

 (If we're not careful the users will develop a sense to avoid all
 x.y.0 releases, believing them to be low quality.  Other products have
 run into that problem, even with x.y.1 and x.y.2 releases.  I think it
 is better if we can avoid having that kind of reputation.)

 A 2nd beta might be necessary in some rare cases, but I think in most
 cases we fix the critical bugs found in the beta and just do normal
 re-testing of those areas in a Release Candidate.


Hi, Rob,
  I think a public beta is a good idea!
  After the 4.1 feature development and related FVT completed, I think we
kick off a beta testing which cover the major function areas, then announce
the 4.1 beta.
  Then we run the Full Regression Test and monitor the beta feedback, from
4.0 experience the Full Regression Test will take at least 4 weeks, depends
on the number of volunteers. Then the end game critical fix and RC build
testing for 4.1.

- Shenfeng (Simon)



 Regards,

 -Rob



  If we agree on that, we should expand the timeframe to 6 or more weeks.
 
  My 2 ct.
 
  Marcus
 
 
 
 
 I suggest to update the 4.1 planning wiki[1] and:
  (1) Set the target date.
  (2) Clean up the planning list, starting from leaving only the active
  items, and moving the rest to project backlog[2].
 
 Any suggestion/comments?
 
 
  [1]
 
 
 https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Planning
  [2] https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Blog
 
 
  - 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: Fwd: Re: Re : [Call For QA Volunteers][Accessibility] AOO IAccessible2 testing work

2013-11-12 Thread MENGUAL Jean-Philippe

Hi,

My experience with bugs trackers and Windows world isn't very big, so I 
submit you my situation to see if everything is good.
Now I have an account on the bug tracker. Is it enough or should I add 
myself to something? How can I do this while logged in?


Thanks for your answer.

Regards,


Le 09/11/2013 15:11, MENGUAL Jean-Philippe a écrit :




 Message original 
Sujet: 	Re: Re : [Call For QA Volunteers][Accessibility] AOO 
IAccessible2 testing work

Date :  Wed, 6 Nov 2013 20:53:21 -0800 (PST)
De :V Stuart Foote vstuart.fo...@utsa.edu
Répondre à :dev@openoffice.apache.org
Pour :  ooo-...@incubator.apache.org



@Jean-Philippe

The ia2 branch builds are on the daily Buildbot, current is  rev 1539225
http://ci.apache.org/projects/openoffice/install/w7ia2/Apache_OpenOffice_4.1.0_Win_x86_install_en-US.exe_1539225.exe  
.


Issues are being recorded and worked withing AOO Bugzilla and for the branch
are being tagged with an [ia2] in the subject line. We have a META  bug
121767https://issues.apache.org/ooo/show_bug.cgi?id=121767open to link
the QA and testing efforts both now and as the branch is merged into trunk
for the 4.1.0 release.  I could not locate you BZ account, so please add
yourself to the META bug--you'll receive notification of any issues linked
to it.

Thanks for helping.





--
View this message in 
context:http://openoffice.2283327.n4.nabble.com/Call-For-QA-Volunteers-Accessibility-AOO-IAccessible2-testing-work-tp4654497p4655408.html
Sent from the Development mailing list archive at Nabble.com.

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







--

Jean-Philippe MENGUAL

accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels

Mail: te...@accelibreinfo.eu

Site Web: http://www.accelibreinfo.eu



Request For improvement

2013-11-12 Thread Rizwan Mohammed
Hi 
my name is Mohammed Rizwan 
This email is concerning the Open Office
I am currently studying in the University of Bolton and I have chosen this 
software to have a look at
Their is one problem which I realized when I was using this software which is 
that when a large file is opened the software will crash.
  

Re: [OS2] gcc 4.7.3, CPPULIB now required for some modules

2013-11-12 Thread Yuri Dario
Hi Herbert,

 Did you change the linker too? When linux distributions switched from 
 the bfd to the gold linker there where problems that libraries that 
 were only linked indirectly had to be mentioned directly [1]

OS/2 does not use ld to link object files. But this seems not the 
problem I see. 

I'm thinking that these functions were inlined in previous gcc 
releases or that now code generates some new kind of reference to 
them, thus requiring the linker to satisfy the dependancy. OS/2 
linkers needs to resolve all symbols like Windows, we do not have lazy
loading enabled by default.

thanks,


-- 
Bye,

Yuri Dario

/*
 * OS/2 open source software
 * http://web.os2power.com/yuri
 * http://www.netlabs.org
*/



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



Re: [OS2] gcc 4.7.3, CPPULIB now required for some modules

2013-11-12 Thread Herbert Duerr

Hi Yuri,

On 12.11.2013 12:37, Yuri Dario wrote:

Did you change the linker too? When linux distributions switched from
the bfd to the gold linker there where problems that libraries that
were only linked indirectly had to be mentioned directly [1]


OS/2 does not use ld to link object files. But this seems not the
problem I see.

I'm thinking that these functions were inlined in previous gcc
releases or that now code generates some new kind of reference to
them, thus requiring the linker to satisfy the dependancy.


I had thought about that too, but seeing that the missing functions are 
declared in main/cppu/source/uno/any.cxx and not in an exported header 
file convinced me that this cannot happen.


But maybe there really are new uses of cssu::Any in the modules you 
mentioned. Do the error messages say which object files need these 
methods that were missing without the CPPULIB dependency?



OS/2
linkers needs to resolve all symbols like Windows, we do not have lazy
loading enabled by default.


The direct/indirect linking (in the build phase) I referred to is 
orthogonal to eager/lazy loading (in the run phase).


Herbert

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



XML files are binary?

2013-11-12 Thread Andre Fischer
I just checked in some files for creating Windows patches (no, the work 
is not yet finished) and saw that the .xml files are flagged as binary.  
Checking their properties revealed that their mime type is correctly set 
to application/xml.  Does anybody know why they are still flagged as binary?


By the way, what became of our attempt to replace SVN with GIT? For 
getting the mime type I first tried svn info filename which shows a 
lot of information but not the properties.  Then I tried svn proplist 
filename which only shows the names of the properties but not their 
values.  I really needed a third call svn propget svn:mime-type 
filename to see the value.  Can we please change to GIT? Life would 
be so much easier.


Regards,
Andre


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



Re: XML files are binary?

2013-11-12 Thread Oliver-Rainer Wittmann

Hi,

On 12.11.2013 14:59, Andre Fischer wrote:

I just checked in some files for creating Windows patches (no, the work
is not yet finished) and saw that the .xml files are flagged as binary.
Checking their properties revealed that their mime type is correctly set
to application/xml.  Does anybody know why they are still flagged as
binary?


I do not know, but I was also hit by this SVN feature when working on 
the application XML update feeds.




By the way, what became of our attempt to replace SVN with GIT? For
getting the mime type I first tried svn info filename which shows a
lot of information but not the properties.  Then I tried svn proplist
filename which only shows the names of the properties but not their
values.  I really needed a third call svn propget svn:mime-type
filename to see the value.  Can we please change to GIT? Life would
be so much easier.



+1


Best regards, Oliver.

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



Re: Request For improvement

2013-11-12 Thread Vladislav Stevanovic
Hi Rizwan Mohammed,
If you have a good will, that will be great!

 Also, next problem is present when open some big file: it takes to long.


Regards,
Wlada


2013/11/12 Rizwan Mohammed king...@live.co.uk

 Hi
 my name is Mohammed Rizwan
 This email is concerning the Open Office
 I am currently studying in the University of Bolton and I have chosen this
 software to have a look at
 Their is one problem which I realized when I was using this software which
 is that when a large file is opened the software will crash.



Re: XML files are binary?

2013-11-12 Thread Jürgen Schmidt
On 11/12/13 2:59 PM, Andre Fischer wrote:
 I just checked in some files for creating Windows patches (no, the work
 is not yet finished) and saw that the .xml files are flagged as binary. 
 Checking their properties revealed that their mime type is correctly set
 to application/xml.  Does anybody know why they are still flagged as
 binary?
 
 By the way, what became of our attempt to replace SVN with GIT? For
 getting the mime type I first tried svn info filename which shows a
 lot of information but not the properties.  Then I tried svn proplist
 filename which only shows the names of the properties but not their
 values.  I really needed a third call svn propget svn:mime-type
 filename to see the value.  Can we please change to GIT? Life would
 be so much easier.

+1

Juergen

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



Re: XML files are binary?

2013-11-12 Thread Rob Weir
On Tue, Nov 12, 2013 at 8:59 AM, Andre Fischer awf@gmail.com wrote:
 I just checked in some files for creating Windows patches (no, the work is
 not yet finished) and saw that the .xml files are flagged as binary.
 Checking their properties revealed that their mime type is correctly set to
 application/xml.  Does anybody know why they are still flagged as binary?


Do you have svn:eol-style set?

-Rob


 By the way, what became of our attempt to replace SVN with GIT? For getting
 the mime type I first tried svn info filename which shows a lot of
 information but not the properties.  Then I tried svn proplist filename
 which only shows the names of the properties but not their values.  I really
 needed a third call svn propget svn:mime-type filename to see the value.
 Can we please change to GIT? Life would be so much easier.

 Regards,
 Andre


 -
 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: XML files are binary?

2013-11-12 Thread Andre Fischer

On 12.11.2013 15:19, Rob Weir wrote:

On Tue, Nov 12, 2013 at 8:59 AM, Andre Fischer awf@gmail.com wrote:

I just checked in some files for creating Windows patches (no, the work is
not yet finished) and saw that the .xml files are flagged as binary.
Checking their properties revealed that their mime type is correctly set to
application/xml.  Does anybody know why they are still flagged as binary?


Do you have svn:eol-style set?


No, svn:mime-type is the only property that was (automatically) set.

Maybe its value should be text/xml instead of application/xml.

-Andre



-Rob



By the way, what became of our attempt to replace SVN with GIT? For getting
the mime type I first tried svn info filename which shows a lot of
information but not the properties.  Then I tried svn proplist filename
which only shows the names of the properties but not their values.  I really
needed a third call svn propget svn:mime-type filename to see the value.
Can we please change to GIT? Life would be so much easier.

Regards,
Andre


-
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




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



Re: Interested in a technical cross-platform mailing?

2013-11-12 Thread Donald Whytock
...Does that bottom part mean this mailing list is subscribed to his
mailing list?

Don


On Mon, Nov 11, 2013 at 4:54 PM, MENGUAL Jean-Philippe 
mengualjean...@free.fr wrote:

 Hi, We have just founded a group, called liberte0 (Freedom 0). Its purpose
 is to promote the accessibility for everybody, so that a high variety of
 users know the free software in accessibility matter, and to let a place so
 that people can have info on accessibility. This group is French, so our
 core mailing is in French, but it is about our actions with users and some
 support to french-speaking users (feedbacks, etc.). But in parallel we
 opened a multilingual website, whose purpose is to speak mainly in English.
 This is a technical mailing list. 2 purposes: 1. enabling to new dev who
 want to work in accessibility technologies or to make thir free software
 accessible to have a place to ask questions, have feedbacks, with technical
 devs, so that they can understand that accessibility is not so hard, but
 it's especially an approach, and not a big effort. It's useful because we
 meet often devs 7who are interested but who don't know where to begin,
 where to have doc about the widgets, the at-spi, assistive technologies,
 etc. Typically I wasn't good to answer to openbox's dev who wanted to do
 efforts about a11y of her WM, I'm sure you could gi(e her basics to
 proceed. And maybe it would give ideas to some people to contribute to
 accessibility so that it is in progress. 2. I feel today one who want to
 have a global technical approach of the accessibility, in particular in GUI
 matter, needs to be subscribed to various lists. I think, even if I know
 most devs are subscribed to all lists, that it'd be useful to have a
 platform where all devs and power-users could have technical exchanges, if
 they work for Qt, GTK, distros, oriented or not, at-spi/qt-at-spi, etc. I
 think this mailing can gather on a single place all the a11y devs, that
 will enable to everybody to have the same info immediately, to discuss it,
 to speak together, to exchange their experiences, and so to make proceed
 accessibility in general, regardless the platform where a dev works (Qt,
 LibreOffice, OOo, Qt, Mozilla, etc.). If such a project is of interest for
 you, subsc!ibe to tech AT liberte0 DOT org. Don't hesitate to forward the
 address. You can subscribe sending a message to sympa AT liberte0 DOT org
 with subject: subscribe tech. I hope the project, in particular this
 technical, can be considered as useful and that a full community of
 accessibility will have a common place to speak regardless the origin of
 everyone, technically and nationally. Don't hesitate if you have questions
 about this group, here or on the tech mailing list. We'll answer as much as
 we can. Regards, Jean-Philippe MENGUAL accelibreinfo, votre partenaire en
 informatique adaptée aux déficients visuels Mail: texou@accelibreinfo.euSite 
 Web:
 http://www.accelibreinfo.eu -- -- You received this message because you
 are subscribed to the Vinux Support mailing list. To unsubscribe from this
 group, email vinux-support+unsubscr...@googlegroups.com Our website:
 www.vinuxproject.org



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




Re: XML files are binary?

2013-11-12 Thread Herbert Dürr

On 12.11.2013 15:34, Andre Fischer wrote:

On 12.11.2013 15:19, Rob Weir wrote:

On Tue, Nov 12, 2013 at 8:59 AM, Andre Fischer awf@gmail.com wrote:

I just checked in some files for creating Windows patches (no, the
work is
not yet finished) and saw that the .xml files are flagged as binary.
Checking their properties revealed that their mime type is correctly
set to
application/xml.  Does anybody know why they are still flagged as
binary?


Do you have svn:eol-style set?


No, svn:mime-type is the only property that was (automatically) set.

Maybe its value should be text/xml instead of application/xml.


Thats also what http://www.apache.org/dev/svn-eol-style.txt
recommends:

Please do not use svn:mime-type=application/xml for xml files as that 
causes SVN to treat them as binary - use text/xml or omit the setting 
entirely.


Now if svn's automatic property setting mechanism agreed with this too 
all would be fine.


Herbert

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



Re: XML files are binary?

2013-11-12 Thread Herbert Duerr

On 12.11.2013 14:59, Andre Fischer wrote:

I just checked in some files for creating Windows patches (no, the work
is not yet finished) and saw that the .xml files are flagged as binary.
Checking their properties revealed that their mime type is correctly set
to application/xml.  Does anybody know why they are still flagged as
binary?

By the way, what became of our attempt to replace SVN with GIT? [...]

 Can we please change to GIT? Life would be so much easier.

Please see the closed JIRA issue [1] and my mail in [2] where I 
suggested to reopen it when we have consensus on
[...] whether we want to have a read-only git-mirror of our svn 
repository or to whether we want to fully switch to git (read-write).


I'm for a read-only git-mirror for a start.

[1] https://issues.apache.org/jira/browse/INFRA-5590
[2] http://markmail.org/message/5cx4yyb5z5qb6sdz

Herbert

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



Re: XML files are binary?

2013-11-12 Thread Andre Fischer

On 12.11.2013 15:54, Herbert Duerr wrote:

On 12.11.2013 14:59, Andre Fischer wrote:

I just checked in some files for creating Windows patches (no, the work
is not yet finished) and saw that the .xml files are flagged as binary.
Checking their properties revealed that their mime type is correctly set
to application/xml.  Does anybody know why they are still flagged as
binary?

By the way, what became of our attempt to replace SVN with GIT? [...]

 Can we please change to GIT? Life would be so much easier.

Please see the closed JIRA issue [1] and my mail in [2] where I 
suggested to reopen it when we have consensus on
[...] whether we want to have a read-only git-mirror of our svn 
repository or to whether we want to fully switch to git (read-write).


I'm for a read-only git-mirror for a start.


I already have a read-only git mirror on my local machine and prefer a 
switch to git completely.


-Andre



[1] https://issues.apache.org/jira/browse/INFRA-5590
[2] http://markmail.org/message/5cx4yyb5z5qb6sdz

Herbert

-
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: XML files are binary?

2013-11-12 Thread janI
On 12 November 2013 14:59, Andre Fischer awf@gmail.com wrote:

 I just checked in some files for creating Windows patches (no, the work is
 not yet finished) and saw that the .xml files are flagged as binary.
  Checking their properties revealed that their mime type is correctly set
 to application/xml.  Does anybody know why they are still flagged as binary?

 By the way, what became of our attempt to replace SVN with GIT? For
 getting the mime type I first tried svn info filename which shows a lot
 of information but not the properties.  Then I tried svn proplist
 filename which only shows the names of the properties but not their
 values.  I really needed a third call svn propget svn:mime-type
 filename to see the value.  Can we please change to GIT? Life would be
 so much easier.


I tried to find the jira ticket, because it needs some updating to what we
really want (original is was just a RO copy).

If someone has the ticket number then please :-)

Do we want to replace svn with git, have both in common or have git as a RO
mirror ?

rgds
jan I.



 Regards,
 Andre


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




Re: XML files are binary?

2013-11-12 Thread janI
On 12 November 2013 15:54, Herbert Duerr h...@apache.org wrote:

 On 12.11.2013 14:59, Andre Fischer wrote:

 I just checked in some files for creating Windows patches (no, the work
 is not yet finished) and saw that the .xml files are flagged as binary.
 Checking their properties revealed that their mime type is correctly set
 to application/xml.  Does anybody know why they are still flagged as
 binary?

 By the way, what became of our attempt to replace SVN with GIT? [...]

  Can we please change to GIT? Life would be so much easier.

 Please see the closed JIRA issue [1] and my mail in [2] where I suggested
 to reopen it when we have consensus on
 [...] whether we want to have a read-only git-mirror of our svn
 repository or to whether we want to fully switch to git (read-write).

 I'm for a read-only git-mirror for a start.

 [1] https://issues.apache.org/jira/browse/INFRA-5590
 [2] http://markmail.org/message/5cx4yyb5z5qb6sdz


Now I know why I could not find it.

There is an infra committer working hard to get all the git stuff done, so
now would be a nice time to decide and then reopen it.

I would prefer a read/write GIT, so people can work solely in git. Then we
can consider over time to drop svn.

rgds
jan I.



 Herbert


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




[proposal] GIT mirror

2013-11-12 Thread janI
Hi.

based on the discussion in thread XML files are binary and herberts
comments I had a chat with jfarrell (the infra git specialist).

We can have a GIT Read/Only mirror very easy (standard)

We cannot have a GIT Read/write mirror (restriction from infra)

We can switch completely to GIT (which I for one would be against).

I recommend to reopen ticket 5590 with a comment asking for a read/only
mirror. Jfarrell is right now (this week) working through git issues, so if
we can reopen the ticket fast, I can help jfarrell make this happen fast.

@herbert, if nobody objects will you reopen the ticket, or should I ?

rgds
jan I.


Re: [proposal] GIT mirror

2013-11-12 Thread Jürgen Schmidt
On 11/12/13 4:48 PM, janI wrote:
 Hi.
 
 based on the discussion in thread XML files are binary and herberts
 comments I had a chat with jfarrell (the infra git specialist).
 
 We can have a GIT Read/Only mirror very easy (standard)
 
 We cannot have a GIT Read/write mirror (restriction from infra)
 
 We can switch completely to GIT (which I for one would be against).

can you share your thoughts against a complete switch with us. I am at
least interested to learn more about others opinion.

We talk here about trunk our real code repo only. Everything else can
continue to be in svn.

Juergen

 
 I recommend to reopen ticket 5590 with a comment asking for a read/only
 mirror. Jfarrell is right now (this week) working through git issues, so if
 we can reopen the ticket fast, I can help jfarrell make this happen fast.
 
 @herbert, if nobody objects will you reopen the ticket, or should I ?
 
 rgds
 jan I.
 


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



Re: [proposal] GIT mirror

2013-11-12 Thread Rob Weir
On Tue, Nov 12, 2013 at 10:57 AM, Jürgen Schmidt jogischm...@gmail.com wrote:
 On 11/12/13 4:48 PM, janI wrote:
 Hi.

 based on the discussion in thread XML files are binary and herberts
 comments I had a chat with jfarrell (the infra git specialist).

 We can have a GIT Read/Only mirror very easy (standard)

 We cannot have a GIT Read/write mirror (restriction from infra)

 We can switch completely to GIT (which I for one would be against).

 can you share your thoughts against a complete switch with us. I am at
 least interested to learn more about others opinion.

 We talk here about trunk our real code repo only. Everything else can
 continue to be in svn.


If we moved the trunk to git what happens to the existing SVN
branches?   Is there a good way for them to merge into git?

-Rob


 Juergen


 I recommend to reopen ticket 5590 with a comment asking for a read/only
 mirror. Jfarrell is right now (this week) working through git issues, so if
 we can reopen the ticket fast, I can help jfarrell make this happen fast.

 @herbert, if nobody objects will you reopen the ticket, or should I ?

 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: [proposal] GIT mirror

2013-11-12 Thread Herbert Duerr

On 12.11.2013 16:48, janI wrote:

based on the discussion in thread XML files are binary and herberts
comments I had a chat with jfarrell (the infra git specialist).

We can have a GIT Read/Only mirror very easy (standard)

We cannot have a GIT Read/write mirror (restriction from infra)

We can switch completely to GIT (which I for one would be against).

I recommend to reopen ticket 5590 with a comment asking for a read/only
mirror. Jfarrell is right now (this week) working through git issues, so if
we can reopen the ticket fast, I can help jfarrell make this happen fast.


Thanks for this interesting info. This makes it clear that we should act 
ASAP.



@herbert, if nobody objects will you reopen the ticket, or should I ?


I have reopened the JIRA issue and requested a read-only mirror for now.

Herbert


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



Re: [proposal] GIT mirror

2013-11-12 Thread janI
On 12 November 2013 17:02, Rob Weir robw...@apache.org wrote:

 On Tue, Nov 12, 2013 at 10:57 AM, Jürgen Schmidt jogischm...@gmail.com
 wrote:
  On 11/12/13 4:48 PM, janI wrote:
  Hi.
 
  based on the discussion in thread XML files are binary and herberts
  comments I had a chat with jfarrell (the infra git specialist).
 
  We can have a GIT Read/Only mirror very easy (standard)
 
  We cannot have a GIT Read/write mirror (restriction from infra)
 
  We can switch completely to GIT (which I for one would be against).
 
  can you share your thoughts against a complete switch with us. I am at
  least interested to learn more about others opinion.
 
  We talk here about trunk our real code repo only. Everything else can
  continue to be in svn.
 

 If we moved the trunk to git what happens to the existing SVN
 branches?   Is there a good way for them to merge into git?


Normal procedure is to move trunk/branches/tags, so we have all info. BUT
as far as I know it will not have the history.

rgds
jan i.



 -Rob


  Juergen
 
 
  I recommend to reopen ticket 5590 with a comment asking for a read/only
  mirror. Jfarrell is right now (this week) working through git issues,
 so if
  we can reopen the ticket fast, I can help jfarrell make this happen
 fast.
 
  @herbert, if nobody objects will you reopen the ticket, or should I ?
 
  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: [proposal] GIT mirror

2013-11-12 Thread janI
On 12 November 2013 16:57, Jürgen Schmidt jogischm...@gmail.com wrote:

 On 11/12/13 4:48 PM, janI wrote:
  Hi.
 
  based on the discussion in thread XML files are binary and herberts
  comments I had a chat with jfarrell (the infra git specialist).
 
  We can have a GIT Read/Only mirror very easy (standard)
 
  We cannot have a GIT Read/write mirror (restriction from infra)
 
  We can switch completely to GIT (which I for one would be against).

 can you share your thoughts against a complete switch with us. I am at
 least interested to learn more about others opinion.


of course.

I think there are still plenty of svn users out there, and switching
completely away from svn, would be a larger change for them.

At the moment (but this might just be me), branches in GIT works real bad
with our current build system. I have f.x. 3 branches and trunk, all being
build more or less daily. I tried with GIT, where branch switching is
supposed to be very simple. The branch switch itself is simple, but I
always needed a complete build --all, because the GIT do (of course not)
preserve the different unxlngx6.pro dirs.




 We talk here about trunk our real code repo only. Everything else can
 continue to be in svn.


That would be a problem, how will you do merge back ? The merge facility in
both directions is very important.

If we switch to git, svn will be a ReadOnly mirror and we cannot do merge
etc. in svn.

rgds
jan I.



 Juergen

 
  I recommend to reopen ticket 5590 with a comment asking for a read/only
  mirror. Jfarrell is right now (this week) working through git issues, so
 if
  we can reopen the ticket fast, I can help jfarrell make this happen fast.
 
  @herbert, if nobody objects will you reopen the ticket, or should I ?
 
  rgds
  jan I.
 


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




Re: [proposal] GIT mirror

2013-11-12 Thread Jürgen Schmidt
On 11/12/13 5:02 PM, Rob Weir wrote:
 On Tue, Nov 12, 2013 at 10:57 AM, Jürgen Schmidt jogischm...@gmail.com 
 wrote:
 On 11/12/13 4:48 PM, janI wrote:
 Hi.

 based on the discussion in thread XML files are binary and herberts
 comments I had a chat with jfarrell (the infra git specialist).

 We can have a GIT Read/Only mirror very easy (standard)

 We cannot have a GIT Read/write mirror (restriction from infra)

 We can switch completely to GIT (which I for one would be against).

 can you share your thoughts against a complete switch with us. I am at
 least interested to learn more about others opinion.

 We talk here about trunk our real code repo only. Everything else can
 continue to be in svn.

 
 If we moved the trunk to git what happens to the existing SVN
 branches?   Is there a good way for them to merge into git?

sorry for being precise enough I meant of course everything we need for
building the office and this includes the branches, the history and tags.

Juergen

 
 -Rob
 
 
 Juergen


 I recommend to reopen ticket 5590 with a comment asking for a read/only
 mirror. Jfarrell is right now (this week) working through git issues, so if
 we can reopen the ticket fast, I can help jfarrell make this happen fast.

 @herbert, if nobody objects will you reopen the ticket, or should I ?

 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
 


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



Re: [proposal] GIT mirror

2013-11-12 Thread Jürgen Schmidt
On 11/12/13 5:06 PM, Herbert Duerr wrote:
 On 12.11.2013 16:48, janI wrote:
 based on the discussion in thread XML files are binary and herberts
 comments I had a chat with jfarrell (the infra git specialist).

 We can have a GIT Read/Only mirror very easy (standard)

 We cannot have a GIT Read/write mirror (restriction from infra)

 We can switch completely to GIT (which I for one would be against).

 I recommend to reopen ticket 5590 with a comment asking for a read/only
 mirror. Jfarrell is right now (this week) working through git issues,
 so if
 we can reopen the ticket fast, I can help jfarrell make this happen fast.
 
 Thanks for this interesting info. This makes it clear that we should act
 ASAP.
 
 @herbert, if nobody objects will you reopen the ticket, or should I ?
 
 I have reopened the JIRA issue and requested a read-only mirror for now.

I am not sure why should we proceed with a read-only mirror if we decide
to switch completely

Juergen

 
 Herbert
 
 
 -
 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] GIT mirror

2013-11-12 Thread janI
On 12 November 2013 17:18, Jürgen Schmidt jogischm...@gmail.com wrote:

 On 11/12/13 5:06 PM, Herbert Duerr wrote:
  On 12.11.2013 16:48, janI wrote:
  based on the discussion in thread XML files are binary and herberts
  comments I had a chat with jfarrell (the infra git specialist).
 
  We can have a GIT Read/Only mirror very easy (standard)
 
  We cannot have a GIT Read/write mirror (restriction from infra)
 
  We can switch completely to GIT (which I for one would be against).
 
  I recommend to reopen ticket 5590 with a comment asking for a read/only
  mirror. Jfarrell is right now (this week) working through git issues,
  so if
  we can reopen the ticket fast, I can help jfarrell make this happen
 fast.
 
  Thanks for this interesting info. This makes it clear that we should act
  ASAP.
 
  @herbert, if nobody objects will you reopen the ticket, or should I ?
 
  I have reopened the JIRA issue and requested a read-only mirror for now.

 I am not sure why should we proceed with a read-only mirror if we decide
 to switch completely


I think that is a bigger decision. it would also mean that f.x. the pootle
workflow would have to be done differently.

Having a git readonly mirror for a period of time, allows us to see how it
works, change workflows, and see if there are user acceptance.

rgds
jan I.



 Juergen

 
  Herbert
 
 
  -
  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] GIT mirror

2013-11-12 Thread Andre Fischer

On 12.11.2013 17:06, janI wrote:

On 12 November 2013 16:57, Jürgen Schmidt jogischm...@gmail.com wrote:


On 11/12/13 4:48 PM, janI wrote:

Hi.

based on the discussion in thread XML files are binary and herberts
comments I had a chat with jfarrell (the infra git specialist).

We can have a GIT Read/Only mirror very easy (standard)

We cannot have a GIT Read/write mirror (restriction from infra)

We can switch completely to GIT (which I for one would be against).

can you share your thoughts against a complete switch with us. I am at
least interested to learn more about others opinion.


of course.

I think there are still plenty of svn users out there, and switching
completely away from svn, would be a larger change for them.


It was a big change for me to switch TO svn when OpenOffice moved to 
Apache.  I managed.  Others managed.  I think a move to git will be 
manageable, too.




At the moment (but this might just be me), branches in GIT works real bad
with our current build system. I have f.x. 3 branches and trunk, all being
build more or less daily. I tried with GIT, where branch switching is
supposed to be very simple. The branch switch itself is simple, but I
always needed a complete build --all, because the GIT do (of course not)
preserve the different unxlngx6.pro dirs.


I agree, using branches like that work not well with OpenOffice.  I 
don't think that that is necessarily a problem of the build system, but 
caused by the amount of code that has to be recompiled.


But you don't have to work like that.  Instead of creating branches 
(which still works well for little changes, eg test changes of one file 
on its own branch) you can create clones.  That is how I currently 
work.  I have one local git mirror of our svn repository and a couple of 
clones of that git mirror, where I make changes. That works quite well.


-Andre






We talk here about trunk our real code repo only. Everything else can
continue to be in svn.


That would be a problem, how will you do merge back ? The merge facility in
both directions is very important.

If we switch to git, svn will be a ReadOnly mirror and we cannot do merge
etc. in svn.

rgds
jan I.



Juergen


I recommend to reopen ticket 5590 with a comment asking for a read/only
mirror. Jfarrell is right now (this week) working through git issues, so

if

we can reopen the ticket fast, I can help jfarrell make this happen fast.

@herbert, if nobody objects will you reopen the ticket, or should I ?

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: [proposal] GIT mirror

2013-11-12 Thread Jürgen Schmidt
On 11/12/13 5:24 PM, janI wrote:
 On 12 November 2013 17:18, Jürgen Schmidt jogischm...@gmail.com wrote:
 
 On 11/12/13 5:06 PM, Herbert Duerr wrote:
 On 12.11.2013 16:48, janI wrote:
 based on the discussion in thread XML files are binary and herberts
 comments I had a chat with jfarrell (the infra git specialist).

 We can have a GIT Read/Only mirror very easy (standard)

 We cannot have a GIT Read/write mirror (restriction from infra)

 We can switch completely to GIT (which I for one would be against).

 I recommend to reopen ticket 5590 with a comment asking for a read/only
 mirror. Jfarrell is right now (this week) working through git issues,
 so if
 we can reopen the ticket fast, I can help jfarrell make this happen
 fast.

 Thanks for this interesting info. This makes it clear that we should act
 ASAP.

 @herbert, if nobody objects will you reopen the ticket, or should I ?

 I have reopened the JIRA issue and requested a read-only mirror for now.

 I am not sure why should we proceed with a read-only mirror if we decide
 to switch completely

 
 I think that is a bigger decision. it would also mean that f.x. the pootle
 workflow would have to be done differently.
 
 Having a git readonly mirror for a period of time, allows us to see how it
 works, change workflows, and see if there are user acceptance.

I believe the majority of active developers work today with git-svn
already. It would simplify the daily work :-)

Regarding the Pootle workflow I am not sure if I understand it
currently. Would it be a big change to git instead svn? And if yes why
and would it be really a blocker?

Juergen

 
 rgds
 jan I.
 
 

 Juergen


 Herbert


 -
 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


 


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



Re: [proposal] GIT mirror

2013-11-12 Thread janI
On 12 November 2013 17:32, Jürgen Schmidt jogischm...@gmail.com wrote:

 On 11/12/13 5:24 PM, janI wrote:
  On 12 November 2013 17:18, Jürgen Schmidt jogischm...@gmail.com wrote:
 
  On 11/12/13 5:06 PM, Herbert Duerr wrote:
  On 12.11.2013 16:48, janI wrote:
  based on the discussion in thread XML files are binary and herberts
  comments I had a chat with jfarrell (the infra git specialist).
 
  We can have a GIT Read/Only mirror very easy (standard)
 
  We cannot have a GIT Read/write mirror (restriction from infra)
 
  We can switch completely to GIT (which I for one would be against).
 
  I recommend to reopen ticket 5590 with a comment asking for a
 read/only
  mirror. Jfarrell is right now (this week) working through git issues,
  so if
  we can reopen the ticket fast, I can help jfarrell make this happen
  fast.
 
  Thanks for this interesting info. This makes it clear that we should
 act
  ASAP.
 
  @herbert, if nobody objects will you reopen the ticket, or should I ?
 
  I have reopened the JIRA issue and requested a read-only mirror for
 now.
 
  I am not sure why should we proceed with a read-only mirror if we decide
  to switch completely
 
 
  I think that is a bigger decision. it would also mean that f.x. the
 pootle
  workflow would have to be done differently.
 
  Having a git readonly mirror for a period of time, allows us to see how
 it
  works, change workflows, and see if there are user acceptance.

 I believe the majority of active developers work today with git-svn
 already. It would simplify the daily work :-)

 I will not being a show-stopper for a complete switch. I found it more
secure to do it stepwise.

And I am sure with the suggestion from andre, I can manage the switch too
:-)


 Regarding the Pootle workflow I am not sure if I understand it
 currently. Would it be a big change to git instead svn? And if yes why
 and would it be really a blocker?


pootle does not git only svn, meaning we will not be able to commit
directly from pootle.

No this is no blocker just inconvenient for the pootle admins, who then
still need to work on the vm.

rgds
jan I.


 Juergen

 
  rgds
  jan I.
 
 
 
  Juergen
 
 
  Herbert
 
 
  -
  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
 
 
 


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




Re: [proposal] GIT mirror

2013-11-12 Thread Jürgen Schmidt
On 11/12/13 5:37 PM, janI wrote:
 On 12 November 2013 17:32, Jürgen Schmidt jogischm...@gmail.com wrote:
 
 On 11/12/13 5:24 PM, janI wrote:
 On 12 November 2013 17:18, Jürgen Schmidt jogischm...@gmail.com wrote:

 On 11/12/13 5:06 PM, Herbert Duerr wrote:
 On 12.11.2013 16:48, janI wrote:
 based on the discussion in thread XML files are binary and herberts
 comments I had a chat with jfarrell (the infra git specialist).

 We can have a GIT Read/Only mirror very easy (standard)

 We cannot have a GIT Read/write mirror (restriction from infra)

 We can switch completely to GIT (which I for one would be against).

 I recommend to reopen ticket 5590 with a comment asking for a
 read/only
 mirror. Jfarrell is right now (this week) working through git issues,
 so if
 we can reopen the ticket fast, I can help jfarrell make this happen
 fast.

 Thanks for this interesting info. This makes it clear that we should
 act
 ASAP.

 @herbert, if nobody objects will you reopen the ticket, or should I ?

 I have reopened the JIRA issue and requested a read-only mirror for
 now.

 I am not sure why should we proceed with a read-only mirror if we decide
 to switch completely


 I think that is a bigger decision. it would also mean that f.x. the
 pootle
 workflow would have to be done differently.

 Having a git readonly mirror for a period of time, allows us to see how
 it
 works, change workflows, and see if there are user acceptance.

 I believe the majority of active developers work today with git-svn
 already. It would simplify the daily work :-)

 I will not being a show-stopper for a complete switch. I found it more
 secure to do it stepwise.
 
 And I am sure with the suggestion from andre, I can manage the switch too
 :-)
 
 
 Regarding the Pootle workflow I am not sure if I understand it
 currently. Would it be a big change to git instead svn? And if yes why
 and would it be really a blocker?

 
 pootle does not git only svn, meaning we will not be able to commit
 directly from pootle.
 
 No this is no blocker just inconvenient for the pootle admins, who then
 still need to work on the vm.

thinking about a cron job doing it automatic at well defined time slots
or so... just thinking

Juergen

 
 rgds
 jan I.
 
 
 Juergen


 rgds
 jan I.



 Juergen


 Herbert


 -
 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





 -
 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: Time to think about a Language Update release?

2013-11-12 Thread Kay Schenk
On Tue, Nov 12, 2013 at 12:11 AM, Jürgen Schmidt jogischm...@gmail.comwrote:

 On 11/12/13 4:48 AM, Kay Schenk wrote:
  On Nov 11, 2013 6:37 AM, Jürgen Schmidt jogischm...@gmail.com wrote:
 
  On 11/10/13 8:06 PM, Kay Schenk wrote:
  On Sun, Nov 3, 2013 at 11:05 AM, Ricardo Berlasso
  rgb.m...@gmail.comwrote:
 
  2013/11/3 Keith N. McKenna keith.mcke...@comcast.net
 
  Andrea Pescetti wrote:
  Comparing http://www.openoffice.org/download/other.html
  and https://translate.apache.org/projects/aoo40/ I see that
  we have: - Two unreleased languages that are now 100%
  translated (Bulgarian and Danish) - One language with only
  about 1000 words left and activity in the last week
  (Norwegian Bokmal) - Three languages with about 4000 words
  left and activity in the last week (Thai, Uighur, Hebrew;
  Indonesian and Icelandic are in the same group, but less
  active)
 
  Would it make sense to schedule a language update 4.0.1
  release for late November? I mean something like: announce
  a translation deadline on the l10n list, produce SDF files
  for the languages that reach 100% (which of course already
  include Bulgarian and Danish, and hopefully some of the
  other languages listed above), building only those
  languages and releasing an updated source package and
  binaries for those languages.
 
  Yes I believe that it would make sense and would add to our
  reputation for actively supporting native languages.
 
 
  Indeed. +1 from my part for a language update to 4.0.1.
 
  Regards, Ricardo
 
 
  +1
 
  I also think this would be a good idea...hopefully our Release
  Manager will comment soon.
 
  In general I am always a fan of having further languages available as
  soon as possible. But we are still in the situation that our builds
  and releases take some time. We have no Mac build bot and we don't
  have Linux systems that can build against our currently existing
  baseline.
 
  I know we don't have a Mac buildbot but what is meant by the Linux
 comment.
  The last I saw 32-bit nightly was OK. 64-bit success seems intermittent.
 Is
  this what you mean?

 as far as I know the build bots are based on newer systems (Ubuntu 12.04
 for 32 bit and 10.04 for 64bit). We build on an older CentOS 5.10 system
 which is comaptible to RedHat Enterprise Linux 5. This ensures that our
 builds can be used on more different Linux systems.

 Juergen


OK. I think I will start a new thread on Linux builds -- specifically
deliverables. We need to gain clarity on what  is going on here, I think.



 
  All this should be taken into account and even a language
  update requires some time and we should think careful if we want to do
  it for 2 languages only.
 
  I we can complete at least 5 languages until end of Nov. we can make
  language update only. Means we will release only this new languages on
  the AOO401 branch + a new source release. The same as we did for 3.4.1
  where we released 12 new languages.
 
  And this is only a time limiting factor because many other things are
  to do and we already started thinking about a 4.1 release.
 
  But I am open and in the end I won't be the limiting element here even
  if I ave to do major parts of such a release
 
  Juergen
 
 
 
 
 
 
 
 
 
 
  It would make more snse
  So this would work like we did for 3.4.1 when we added new
  languages. Why not call it 4.0.2? Well, we already
  discussed it, but the main reasons would be: for the
  languages already released in 4.0.1, 4.0.2 would be
  identical (example: 4.0.1 in French would be identical to
  4.0.2 in French) since all commits in the meantime have
  been done to trunk; a new 4.0.2 release takes a much
  larger effort than a 4.0.1 language update, so it is harder
  to find volunteers and this is worth doing only if we have
  some important bugfixes for 4.0.1 to include (and I don't
  see any at the moment).
 
  It would make more sense for it to be 4.0.1 unless there were
  critical bug fixes that would justify a 4.0.2. The only potential
  glitch that I see is handling the release notes. I have a couple of
  ideas that I will lay out in a separate thread if we decide to go
  ahead with a language only release.
 
  Regards Keith
  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
 
 


 -
 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 

Re: [proposal] GIT mirror

2013-11-12 Thread Andrea Pescetti

Herbert Duerr wrote:

On 12.11.2013 16:48, janI wrote:

@herbert, if nobody objects will you reopen the ticket, or should I ?

I have reopened the JIRA issue and requested a read-only mirror for now.


And what would be the advantage for real contributors in having a 
read-only GIT mirror? The complaints I've seen so far are mostly in the 
other direction (i.e., committing or applying patches). I'm not talking 
about generic advantages of GIT: everybody here can be assumed to have a 
good working knowledge of both SVN and GIT. What concrete problems does 
a read-only GIT mirror solve in our case?


I'm not at all against it, but I'd just like to make sure that a 
read-only GIT mirror brings enough concrete advantages, since many GIT 
niceties (local commits, proper attribution, quick application of 
patches) are still left out or significantly limited with this approach.


By the way, you can find discussions about GIT everywhere at Apache, 
there's even a Github account https://github.com/apache and lots of 
suggestions like adopting the newly-released Apache Allura (Incubating) 
GIT (and more) hosting environment. As far as I know, there have been 
very significant updates in the GIT support at Apache in the last few 
weeks and I hope that this is soon summarized in a blog post at 
http://blogs.apache.org/infra/ or reflected in the documentation at 
http://www.apache.org/dev/git.html . So this is a good moment to start 
considering GIT again.


Regards,
  Andrea.

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



Re: [proposal] GIT mirror

2013-11-12 Thread Rob Weir
On Tue, Nov 12, 2013 at 2:08 PM, Andrea Pescetti pesce...@apache.org wrote:
 Herbert Duerr wrote:

 On 12.11.2013 16:48, janI wrote:

 @herbert, if nobody objects will you reopen the ticket, or should I ?

 I have reopened the JIRA issue and requested a read-only mirror for now.


 And what would be the advantage for real contributors in having a read-only
 GIT mirror? The complaints I've seen so far are mostly in the other
 direction (i.e., committing or applying patches). I'm not talking about
 generic advantages of GIT: everybody here can be assumed to have a good
 working knowledge of both SVN and GIT. What concrete problems does a
 read-only GIT mirror solve in our case?

 I'm not at all against it, but I'd just like to make sure that a read-only
 GIT mirror brings enough concrete advantages, since many GIT niceties (local
 commits, proper attribution, quick application of patches) are still left
 out or significantly limited with this approach.

 By the way, you can find discussions about GIT everywhere at Apache, there's
 even a Github account https://github.com/apache and lots of suggestions like
 adopting the newly-released Apache Allura (Incubating) GIT (and more)
 hosting environment. As far as I know, there have been very significant
 updates in the GIT support at Apache in the last few weeks and I hope that
 this is soon summarized in a blog post at http://blogs.apache.org/infra/ or
 reflected in the documentation at http://www.apache.org/dev/git.html . So
 this is a good moment to start considering GIT again.


We should consider the website as well.  Does the CMS have hooks that
work with git repositories as well?  Or would we need to keep the
website in SVN?

-Rob


 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: Updated migration guide?

2013-11-12 Thread Rob Weir
On Mon, Nov 11, 2013 at 4:58 PM, Keith N. McKenna
keith.mcke...@comcast.net wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Rob Weir wrote:
 I'm thinking of starting to create an updated migration guide for
 AOO. If you have any thoughts on this, or want to help, let me
 know.

 Target audience includes:

 1) Individual Microsoft Office users, where such users provide
 their own technical support.

 2) IT departments who support users migrating from MS Office to
 OpenOffice

 3) Groups considering moving to AOO and wanting some guidance on
 migration strategy

 Rather than starting from scratch, I looked around to see if there
 is anything close that could be updated.   I saw that we have a few
 older versions of this kind of document:

 1) Migration Guide: A guide to ease your migration to
 OpenOffice.org from other office suites (2004)

 http://www.openoffice.org/documentation/manuals/oooauthors/MigrationGuide.pdf

  2) OpenOffice.org 2.0 Migration Guide (2006)

 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide

  3) OpenOffice.org Migration Guide (2006)

 https://wiki.openoffice.org/w/images/7/79/0600MG-MigrationGuide.pdf

  Does anyone know of anything more recent than the 2006 version?
 Does anyone know where the source for the 2006 PDF is?  Or was it
 generated from the wiki?

 I believe that all the documentation for Version 2 was done on the
 wiki and was then made into PDF's using an add-on.


OK.  If I wanted to start a new revision of the guide, without wiping
out or replacing the old version, is there any way to do this?   For
example, is it possible to make a copy of this page and the subpages?

https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide

I don't see how to do this.  Perhaps it requires admin rights?

-Rob

 Regards
 Keith

 I don't think it would be extremely difficult to update the guide.
 The tasks would be mainly:

 1) Update branding, logos, references to websites, ownership,
 license, etc., of OpenOffice.

 2) Update screenshots to current UI of AOO

 3) Update any technical content that has changed, e.g., platforms
 supported, file filters, etc.

 4) Write content for new migration-relevant features in AOO.

 5) General technical and editorial review of the content.

 Any other ideas?

 Regards,

 -Rob


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

 iQEcBAEBAgAGBQJSgVMHAAoJEH0fu5UhGmBCckAH/iVw3d9/pr10DyDMgxk/Z26c
 tq011s+F/CkV5XbPbkLc/VTvZqiwG07dYdrkzUb1e+WTdVHHanUoyZwK8MJpK6YS
 xxkhJGQlIWuN2ctMxJC7/kQI34J/CpZSXOmj0Y0jhImxdefX7n3+QT6jjk4CDWaZ
 UF/fBcSyjnbi4jHg4lm4vmH4F1ts8FckLfsSLspGDfm5aHVv+CZ1ltAckUu2cbiY
 jEfBJQZnrhcsTVXzROQxv/9Z5AWaKFA4R5+ctfU3j3ytwO7QDrNuwtro6YPGerZT
 H/LhfNxIG62g3KVvox/z5pZreOt5U7kuur67J/B3jelP2kO48SuREmuEgQAyKw4=
 =X7xh
 -END PGP SIGNATURE-


 -
 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] GIT mirror

2013-11-12 Thread janI
On 12 November 2013 20:12, Rob Weir robw...@apache.org wrote:

 On Tue, Nov 12, 2013 at 2:08 PM, Andrea Pescetti pesce...@apache.org
 wrote:
  Herbert Duerr wrote:
 
  On 12.11.2013 16:48, janI wrote:
 
  @herbert, if nobody objects will you reopen the ticket, or should I ?
 
  I have reopened the JIRA issue and requested a read-only mirror for now.
 
 
  And what would be the advantage for real contributors in having a
 read-only
  GIT mirror? The complaints I've seen so far are mostly in the other
  direction (i.e., committing or applying patches). I'm not talking about
  generic advantages of GIT: everybody here can be assumed to have a good
  working knowledge of both SVN and GIT. What concrete problems does a
  read-only GIT mirror solve in our case?
 
  I'm not at all against it, but I'd just like to make sure that a
 read-only
  GIT mirror brings enough concrete advantages, since many GIT niceties
 (local
  commits, proper attribution, quick application of patches) are still left
  out or significantly limited with this approach.


At least if we do it, it should be done with plenty of warning to
contributors can commit any outstanding work.

There is one problem, svn branches are moved to GIT, but merging them back
to trunk can/might be a problem. So if I understand it correct it is
generally suggested to open a new branch in GIT, and copy the work from the
old branch to the new branch.

I see the RO GIT as a step, to allow contributors to get their setup
prepared, before we do the full switch.


 
  By the way, you can find discussions about GIT everywhere at Apache,
 there's
  even a Github account https://github.com/apache and lots of suggestions
 like
  adopting the newly-released Apache Allura (Incubating) GIT (and more)
  hosting environment. As far as I know, there have been very significant
  updates in the GIT support at Apache in the last few weeks and I hope
 that
  this is soon summarized in a blog post at http://blogs.apache.org/infra/or
  reflected in the documentation at http://www.apache.org/dev/git.html .
 So
  this is a good moment to start considering GIT again.
 

 We should consider the website as well.  Does the CMS have hooks that
 work with git repositories as well?  Or would we need to keep the
 website in SVN?


The ones I asked in infra, did not know of such a GIT plugin.

rgds
jan I.



 -Rob


  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: Time to think about a Language Update release?

2013-11-12 Thread Andrea Pescetti

On 11/11/2013 Jürgen Schmidt wrote:

I we can complete at least 5 languages until end of Nov. we can make
language update only. Means we will release only this new languages on
the AOO401 branch + a new source release. The same as we did for 3.4.1
where we released 12 new languages.


Thank you, makes a lot of sense. I posted some more information to the 
l10n list and I volunteer for monitoring progress, sending reminders, 
checking translations status, and in general everything that can help 
with getting some translations completed by the end of November.


Regards,
  Andrea.

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



Re: [proposal] GIT mirror

2013-11-12 Thread Marcus (OOo)

Am 11/12/2013 08:24 PM, schrieb janI:

On 12 November 2013 20:12, Rob Weirrobw...@apache.org  wrote:


On Tue, Nov 12, 2013 at 2:08 PM, Andrea Pescettipesce...@apache.org
wrote:

Herbert Duerr wrote:


On 12.11.2013 16:48, janI wrote:


@herbert, if nobody objects will you reopen the ticket, or should I ?


I have reopened the JIRA issue and requested a read-only mirror for now.



And what would be the advantage for real contributors in having a

read-only

GIT mirror? The complaints I've seen so far are mostly in the other
direction (i.e., committing or applying patches). I'm not talking about
generic advantages of GIT: everybody here can be assumed to have a good
working knowledge of both SVN and GIT. What concrete problems does a
read-only GIT mirror solve in our case?

I'm not at all against it, but I'd just like to make sure that a

read-only

GIT mirror brings enough concrete advantages, since many GIT niceties

(local

commits, proper attribution, quick application of patches) are still left
out or significantly limited with this approach.




At least if we do it, it should be done with plenty of warning to
contributors can commit any outstanding work.

There is one problem, svn branches are moved to GIT, but merging them back
to trunk can/might be a problem. So if I understand it correct it is
generally suggested to open a new branch in GIT, and copy the work from the
old branch to the new branch.

I see the RO GIT as a step, to allow contributors to get their setup
prepared, before we do the full switch.


+1

I'm not a real and full developer. However, it sounds better to do the 
transition part-by-part. Our code repository is the central part o our 
software project. This has to be secured as best as possible.


My 2 ct

Marcus




By the way, you can find discussions about GIT everywhere at Apache,

there's

even a Github account https://github.com/apache and lots of suggestions

like

adopting the newly-released Apache Allura (Incubating) GIT (and more)
hosting environment. As far as I know, there have been very significant
updates in the GIT support at Apache in the last few weeks and I hope

that

this is soon summarized in a blog post at http://blogs.apache.org/infra/or
reflected in the documentation at http://www.apache.org/dev/git.html .

So

this is a good moment to start considering GIT again.



We should consider the website as well.  Does the CMS have hooks that
work with git repositories as well?  Or would we need to keep the
website in SVN?



The ones I asked in infra, did not know of such a GIT plugin.

rgds
jan I.




-Rob



Regards,
   Andrea.


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



Re: Time to start 4.1 planning?

2013-11-12 Thread Marcus (OOo)

Am 11/11/2013 10:33 PM, schrieb Rob Weir:

On Mon, Nov 11, 2013 at 3:21 PM, Marcus (OOo)marcus.m...@wtnet.de  wrote:

Am 11/11/2013 04:12 PM, schrieb Jürgen Schmidt:


On 11/11/13 3:59 PM, Rob Weir wrote:


On Mon, Nov 11, 2013 at 3:32 AM, Shenfeng Liuliush...@gmail.com   wrote:


Hi, all,
It was one month since 4.0.1 release. And I noticed some some great
works
are going to be delivered soon. e.g. the IA2 framework from Steve, the
Mac
64-bit support from Herbert, and Windows Patch mechanism from Andre.

So I'm thinking, is it a good time to start the 4.1 plan now? We
should
deliver those great value to our users through a formal release ASAP!
And
IMO, even only the 3 items above can be enough for a release to be
called
4.1. We also want to do OOXML improvement by integrating OSBA patches,
and
enhance user experience like in-place Input Field, and many other
things...
While, I think we can keep the continuous improvement across releases.
From
the record breaking download number since 4.0 and 4.0.1, I feel that
keeping regular release is very important to response to our users,
attract
more new comers, and bring this product to success.

So I suggest we start the 4.1 plan now, and set a target date. Since
4.0
was in July, 4.0.1 was in Oct, I feel some time in 1Q will be a good
time
for 4.1.



Hi Simon,

Something to think about:   After 4.0.0 we discussed having a public
beta with out next major release.  If we think this is worth doing,
then we should plan on two dates:  1) A public beta data, and 2) a
final release date.   For the beta to be useful I think we would want
it to last 3-4 weeks, enough time to process any new bug reports,
identify any critical regressions, and fix them.



4 weeks between both is a minimum form my pov

But having a beta is of course the route we should take.



What about taking into account to keep the possibility to release a second
Beta version? It can include fixes for the most nasty and prominent bugs.



Well, hopefully we do some amount of testing before we have a beta.
So the goal should be for the beta to have no nasty and prominent
bugs.  The beta is a form of insurance and a way of setting
expectations.

For example, I think these two scenarios are technically equivalent:

a) release 4.1.0 after normal testing

b) release 4.1.1 to fix major bugs that we missed in 4.1.0 testing.

and

a') release 4.1.0 beta after normal testing

b') release 4.1.0 GA after fixing important bugs found in beta


Sure but we want to do a testing phase in public and not just technically.


These are technically the same, and take approximately the same amount
of time.  The difference is in user expectations.  A beta
designation tells the cautious user to avoid it.  It encourages users
who are willing to take more risk and help us by giving feedback.  It
also helps preserve the brand reputation by ensuring that the actual
GA releases are high quality.

(If we're not careful the users will develop a sense to avoid all
x.y.0 releases, believing them to be low quality.  Other products have
run into that problem, even with x.y.1 and x.y.2 releases.  I think it
is better if we can avoid having that kind of reputation.)


Intersting, one can understand your arguments as points to *do* a second 
Beta release. ;-)



A 2nd beta might be necessary in some rare cases, but I think in most
cases we fix the critical bugs found in the beta and just do normal
re-testing of those areas in a Release Candidate.


Still no point not to do a second release.

But before you go on with writting, please understand my suggestion as 
simple suggestion. I don't want to force it. When you deny it with a 
short post, then it's fine. No need to find many arguments that speak 
(maybe) against it. ;-)


Marcus




If we agree on that, we should expand the timeframe to 6 or more weeks.

My 2 ct.

Marcus





I suggest to update the 4.1 planning wiki[1] and:
(1) Set the target date.
(2) Clean up the planning list, starting from leaving only the active
items, and moving the rest to project backlog[2].

Any suggestion/comments?


[1]

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Planning
[2] https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Blog


- Shenfeng (Simon)


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



Re: Time to start 4.1 planning?

2013-11-12 Thread Rob Weir
On Tue, Nov 12, 2013 at 3:51 PM, Marcus (OOo) marcus.m...@wtnet.de wrote:
 Am 11/11/2013 10:33 PM, schrieb Rob Weir:

 On Mon, Nov 11, 2013 at 3:21 PM, Marcus (OOo)marcus.m...@wtnet.de
 wrote:

 Am 11/11/2013 04:12 PM, schrieb Jürgen Schmidt:

 On 11/11/13 3:59 PM, Rob Weir wrote:


 On Mon, Nov 11, 2013 at 3:32 AM, Shenfeng Liuliush...@gmail.com
 wrote:


 Hi, all,
 It was one month since 4.0.1 release. And I noticed some some
 great
 works
 are going to be delivered soon. e.g. the IA2 framework from Steve, the
 Mac
 64-bit support from Herbert, and Windows Patch mechanism from Andre.

 So I'm thinking, is it a good time to start the 4.1 plan now? We
 should
 deliver those great value to our users through a formal release ASAP!
 And
 IMO, even only the 3 items above can be enough for a release to be
 called
 4.1. We also want to do OOXML improvement by integrating OSBA patches,
 and
 enhance user experience like in-place Input Field, and many other
 things...
 While, I think we can keep the continuous improvement across releases.
 From
 the record breaking download number since 4.0 and 4.0.1, I feel that
 keeping regular release is very important to response to our users,
 attract
 more new comers, and bring this product to success.

 So I suggest we start the 4.1 plan now, and set a target date.
 Since
 4.0
 was in July, 4.0.1 was in Oct, I feel some time in 1Q will be a good
 time
 for 4.1.


 Hi Simon,

 Something to think about:   After 4.0.0 we discussed having a public
 beta with out next major release.  If we think this is worth doing,
 then we should plan on two dates:  1) A public beta data, and 2) a
 final release date.   For the beta to be useful I think we would want
 it to last 3-4 weeks, enough time to process any new bug reports,
 identify any critical regressions, and fix them.



 4 weeks between both is a minimum form my pov

 But having a beta is of course the route we should take.



 What about taking into account to keep the possibility to release a
 second
 Beta version? It can include fixes for the most nasty and prominent bugs.


 Well, hopefully we do some amount of testing before we have a beta.
 So the goal should be for the beta to have no nasty and prominent
 bugs.  The beta is a form of insurance and a way of setting
 expectations.

 For example, I think these two scenarios are technically equivalent:

 a) release 4.1.0 after normal testing

 b) release 4.1.1 to fix major bugs that we missed in 4.1.0 testing.

 and

 a') release 4.1.0 beta after normal testing

 b') release 4.1.0 GA after fixing important bugs found in beta


 Sure but we want to do a testing phase in public and not just technically.


 These are technically the same, and take approximately the same amount
 of time.  The difference is in user expectations.  A beta
 designation tells the cautious user to avoid it.  It encourages users
 who are willing to take more risk and help us by giving feedback.  It
 also helps preserve the brand reputation by ensuring that the actual
 GA releases are high quality.

 (If we're not careful the users will develop a sense to avoid all
 x.y.0 releases, believing them to be low quality.  Other products have
 run into that problem, even with x.y.1 and x.y.2 releases.  I think it
 is better if we can avoid having that kind of reputation.)


 Intersting, one can understand your arguments as points to *do* a second
 Beta release. ;-)


 A 2nd beta might be necessary in some rare cases, but I think in most
 cases we fix the critical bugs found in the beta and just do normal
 re-testing of those areas in a Release Candidate.


 Still no point not to do a second release.

 But before you go on with writting, please understand my suggestion as
 simple suggestion. I don't want to force it. When you deny it with a short
 post, then it's fine. No need to find many arguments that speak (maybe)
 against it. ;-)


I'm not necessarily opposed to have 2, or even 3 betas. (Ha!).  But I
say let the facts, not preconceptions, determine what we do.  Let's do
a beta, look at the results, discuss and then determine the next
steps.  I *predict* that only one beta will be needed.  But I'm not
insisting on it.

Regards,

-Rob

 Marcus




 If we agree on that, we should expand the timeframe to 6 or more weeks.

 My 2 ct.

 Marcus




 I suggest to update the 4.1 planning wiki[1] and:
 (1) Set the target date.
 (2) Clean up the planning list, starting from leaving only the active
 items, and moving the rest to project backlog[2].

 Any suggestion/comments?


 [1]


 https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Planning
 [2] https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Blog


 - Shenfeng (Simon)


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



Re: [proposal] GIT mirror

2013-11-12 Thread Rob Weir
On Tue, Nov 12, 2013 at 3:51 PM, Marcus (OOo) marcus.m...@wtnet.de wrote:
 Am 11/12/2013 08:12 PM, schrieb Rob Weir:

 On Tue, Nov 12, 2013 at 2:08 PM, Andrea Pescettipesce...@apache.org
 wrote:

 Herbert Duerr wrote:


 On 12.11.2013 16:48, janI wrote:


 @herbert, if nobody objects will you reopen the ticket, or should I ?


 I have reopened the JIRA issue and requested a read-only mirror for now.



 And what would be the advantage for real contributors in having a
 read-only
 GIT mirror? The complaints I've seen so far are mostly in the other
 direction (i.e., committing or applying patches). I'm not talking about
 generic advantages of GIT: everybody here can be assumed to have a good
 working knowledge of both SVN and GIT. What concrete problems does a
 read-only GIT mirror solve in our case?

 I'm not at all against it, but I'd just like to make sure that a
 read-only
 GIT mirror brings enough concrete advantages, since many GIT niceties
 (local
 commits, proper attribution, quick application of patches) are still left
 out or significantly limited with this approach.

 By the way, you can find discussions about GIT everywhere at Apache,
 there's
 even a Github account https://github.com/apache and lots of suggestions
 like
 adopting the newly-released Apache Allura (Incubating) GIT (and more)
 hosting environment. As far as I know, there have been very significant
 updates in the GIT support at Apache in the last few weeks and I hope
 that
 this is soon summarized in a blog post at http://blogs.apache.org/infra/
 or
 reflected in the documentation at http://www.apache.org/dev/git.html . So
 this is a good moment to start considering GIT again.


 We should consider the website as well.  Does the CMS have hooks that
 work with git repositories as well?  Or would we need to keep the
 website in SVN?


 Good point. This has to be clarified as we don't want to keep our website
 volunteers outside just because the CMS system doesn't support Git. To let
 everybody of them commit via CLI or GUI tools wouldn't be nice.


But if it is an issue then one solution could be to move the product
source to git and keep the websites in SVN.  We're generally not
dealing with multiple complex branches for the website, so the
advantages of git here are less.

-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: [Proposal] Update 'Get It Here' Banner

2013-11-12 Thread Samer Mansour
Hey Everyone,

I want to have Get It Here translated so that I can provide banners for
each language, this will help our fans promote us in their markets in their
own language with little effort on their part.

ie.
/images/get-it-here/en.png
/images/get-it-here/fr.png
/images/get-it-here/de.png
etc etc.

I could leverage our existing translators and their process. But I'm not
familiar with pootle, in https://translate.apache.org/projects/aoo40 could
we create a folder called 'website' with a single po file inside called
'general.po' one entry for now as 'Get It Here'.

Thoughts? Who manages this Pootle instance and can they assist me with
setting this up?

- Samer :D

On Mon, Nov 11, 2013 at 10:04 AM, Rob Weir robw...@apache.org wrote:

 On Sun, Nov 10, 2013 at 12:55 PM, Samer Mansour samer...@gmail.com
 wrote:
  Hey everyone,
 
  Just realized the 'get it here' image is out dated.  So I whipped
 together
  a new banner with a design I've been using with our social media pages.
 
  This is the current banner:
  http://openoffice.apache.org/images/get-it-here/en.png (from
  http://openoffice.apache.org/get-it-here.html)
 
  This is what I'm proposing to replace:
  http://dynomie.com/ext/getithere2.png
 

 This is nice.  Thanks.

 -Rob

  I would replace the current one with the same dimensions so that it
 updates
  nicely on other sites with the existing logo code (if they pointed to our
  hosted image).
 
  Lazy consensus as usual, 72 hours.
 
  Samer Mansour

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




Re: Updated migration guide?

2013-11-12 Thread Graham Lauder
On Tue, Nov 12, 2013 at 9:12 AM, Rob Weir robw...@apache.org wrote:

 I'm thinking of starting to create an updated migration guide for AOO.
  If you have any thoughts on this, or want to help, let me know.


Excellent idea, it's in need of it, especially around network installs and
network wide customisations.

So I'm up for helping out.




 Target audience includes:

 1) Individual Microsoft Office users, where such users provide their
 own technical support.

 2) IT departments who support users migrating from MS Office to OpenOffice

 3) Groups considering moving to AOO and wanting some guidance on
 migration strategy

 Rather than starting from scratch, I looked around to see if there is
 anything close that could be updated.   I saw that we have a few older
 versions of this kind of document:

 1) Migration Guide: A guide to ease your migration to OpenOffice.org
 from other office suites (2004)


 http://www.openoffice.org/documentation/manuals/oooauthors/MigrationGuide.pdf

 2) OpenOffice.org 2.0 Migration Guide (2006)


 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide

 3) OpenOffice.org Migration Guide (2006)

 https://wiki.openoffice.org/w/images/7/79/0600MG-MigrationGuide.pdf

 Does anyone know of anything more recent than the 2006 version?  Does
 anyone know where the source for the 2006 PDF is?  Or was it generated
 from the wiki?



Originally it was generated from ODT files, that came from oooauthors. I
have copies of those, unfortunately this is the latest version I have and
I'm pretty sure nothing came after this.

I also have a PDF of SUN Star Office migration white paper from 2009 which
may be helpful

Cheers
GL




 I don't think it would be extremely difficult to update the guide. The
 tasks would be mainly:

 1) Update branding, logos, references to websites, ownership, license,
 etc., of OpenOffice.

 2) Update screenshots to current UI of AOO

 3) Update any technical content that has changed, e.g., platforms
 supported, file filters, etc.

 4) Write content for new migration-relevant features in AOO.

 5) General technical and editorial review of the content.

 Any other ideas?

 Regards,

 -Rob

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




Re: [Proposal] Update 'Get It Here' Banner

2013-11-12 Thread Rob Weir
On Tue, Nov 12, 2013 at 4:40 PM, Samer Mansour samer...@gmail.com wrote:
 Hey Everyone,

 I want to have Get It Here translated so that I can provide banners for
 each language, this will help our fans promote us in their markets in their
 own language with little effort on their part.

 ie.
 /images/get-it-here/en.png
 /images/get-it-here/fr.png
 /images/get-it-here/de.png
 etc etc.


Since this logo gets copied onto 3rd party websites you might want
more context in the filename itself, like
openoffice-get-it-here-en.png or something like that.  A webmaster
might easily forget what fr.png is for.

 I could leverage our existing translators and their process. But I'm not
 familiar with pootle, in https://translate.apache.org/projects/aoo40 could
 we create a folder called 'website' with a single po file inside called
 'general.po' one entry for now as 'Get It Here'.

 Thoughts? Who manages this Pootle instance and can they assist me with
 setting this up?


I don't know how to set this up on Pootle, but if it is just one
sentence it might be easier to just send an email to the localization
mailing list l...@openoffice.apache.org and do this via email.  Or
create a wiki page for it.

Or do you see this growing to include much more content for translation?

-Rob

 - Samer :D

 On Mon, Nov 11, 2013 at 10:04 AM, Rob Weir robw...@apache.org wrote:

 On Sun, Nov 10, 2013 at 12:55 PM, Samer Mansour samer...@gmail.com
 wrote:
  Hey everyone,
 
  Just realized the 'get it here' image is out dated.  So I whipped
 together
  a new banner with a design I've been using with our social media pages.
 
  This is the current banner:
  http://openoffice.apache.org/images/get-it-here/en.png (from
  http://openoffice.apache.org/get-it-here.html)
 
  This is what I'm proposing to replace:
  http://dynomie.com/ext/getithere2.png
 

 This is nice.  Thanks.

 -Rob

  I would replace the current one with the same dimensions so that it
 updates
  nicely on other sites with the existing logo code (if they pointed to our
  hosted image).
 
  Lazy consensus as usual, 72 hours.
 
  Samer Mansour

 -
 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] Update 'Get It Here' Banner

2013-11-12 Thread Samer Mansour
This will be a one time need, I will contact the L10N list for now. Thanks
that's good advice.

I did have an idea earlier in the summer to incorporate pootle into a oo.o
website design, that is to follow my icon proposal.

The oo.o website is my next priority.  Throwing a date out, I can see it
completed end of April 2014, a possible english version available early
March 2014.  I just started a new job, but some reason I'm getting more
things done these days, maybe just Autumn-fever.

Samer Mansour


On Tue, Nov 12, 2013 at 4:46 PM, Rob Weir robw...@apache.org wrote:

 On Tue, Nov 12, 2013 at 4:40 PM, Samer Mansour samer...@gmail.com wrote:
  Hey Everyone,
 
  I want to have Get It Here translated so that I can provide banners for
  each language, this will help our fans promote us in their markets in
 their
  own language with little effort on their part.
 
  ie.
  /images/get-it-here/en.png
  /images/get-it-here/fr.png
  /images/get-it-here/de.png
  etc etc.
 

 Since this logo gets copied onto 3rd party websites you might want
 more context in the filename itself, like
 openoffice-get-it-here-en.png or something like that.  A webmaster
 might easily forget what fr.png is for.

  I could leverage our existing translators and their process. But I'm not
  familiar with pootle, in https://translate.apache.org/projects/aoo40could
  we create a folder called 'website' with a single po file inside called
  'general.po' one entry for now as 'Get It Here'.
 
  Thoughts? Who manages this Pootle instance and can they assist me with
  setting this up?
 

 I don't know how to set this up on Pootle, but if it is just one
 sentence it might be easier to just send an email to the localization
 mailing list l...@openoffice.apache.org and do this via email.  Or
 create a wiki page for it.

 Or do you see this growing to include much more content for translation?

 -Rob

  - Samer :D
 
  On Mon, Nov 11, 2013 at 10:04 AM, Rob Weir robw...@apache.org wrote:
 
  On Sun, Nov 10, 2013 at 12:55 PM, Samer Mansour samer...@gmail.com
  wrote:
   Hey everyone,
  
   Just realized the 'get it here' image is out dated.  So I whipped
  together
   a new banner with a design I've been using with our social media
 pages.
  
   This is the current banner:
   http://openoffice.apache.org/images/get-it-here/en.png (from
   http://openoffice.apache.org/get-it-here.html)
  
   This is what I'm proposing to replace:
   http://dynomie.com/ext/getithere2.png
  
 
  This is nice.  Thanks.
 
  -Rob
 
   I would replace the current one with the same dimensions so that it
  updates
   nicely on other sites with the existing logo code (if they pointed to
 our
   hosted image).
  
   Lazy consensus as usual, 72 hours.
  
   Samer Mansour
 
  -
  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




Swiss Testing Night

2013-11-12 Thread Raphael Bircher

Hi at all

Tomorrow evening I will attend a QA Event in Zurich (Switzerland) The 
Event is not Open Source specific but byside some interesting talks from 
Microsoft and Google employees about performance it will be a load of 
room for personal talks and networking. The Venue is the famos Google 
Building in Zurich. It will be interesting to see this one time from 
inside ;-)


Greetings Raphael

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



Re: Updated migration guide?

2013-11-12 Thread Graham Lauder
I think that you can do this using the move tab, you can rename that and
the subpages as well although that's not a copy per se.

I'll see what I can do, just may have to revert,  if it all turns to
custard tarts

Cheers
GL


On Wed, Nov 13, 2013 at 8:24 AM, Rob Weir robw...@apache.org wrote:

 On Mon, Nov 11, 2013 at 4:58 PM, Keith N. McKenna
 keith.mcke...@comcast.net wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Rob Weir wrote:
  I'm thinking of starting to create an updated migration guide for
  AOO. If you have any thoughts on this, or want to help, let me
  know.
 
  Target audience includes:
 
  1) Individual Microsoft Office users, where such users provide
  their own technical support.
 
  2) IT departments who support users migrating from MS Office to
  OpenOffice
 
  3) Groups considering moving to AOO and wanting some guidance on
  migration strategy
 
  Rather than starting from scratch, I looked around to see if there
  is anything close that could be updated.   I saw that we have a few
  older versions of this kind of document:
 
  1) Migration Guide: A guide to ease your migration to
  OpenOffice.org from other office suites (2004)
 
 
 http://www.openoffice.org/documentation/manuals/oooauthors/MigrationGuide.pdf
 
   2) OpenOffice.org 2.0 Migration Guide (2006)
 
 
 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide
 
   3) OpenOffice.org Migration Guide (2006)
 
  https://wiki.openoffice.org/w/images/7/79/0600MG-MigrationGuide.pdf
 
   Does anyone know of anything more recent than the 2006 version?
  Does anyone know where the source for the 2006 PDF is?  Or was it
  generated from the wiki?
 
  I believe that all the documentation for Version 2 was done on the
  wiki and was then made into PDF's using an add-on.
 

 OK.  If I wanted to start a new revision of the guide, without wiping
 out or replacing the old version, is there any way to do this?   For
 example, is it possible to make a copy of this page and the subpages?


 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide

 I don't see how to do this.  Perhaps it requires admin rights?

 -Rob


It shouldn't be too difficult,



  Regards
  Keith
 
  I don't think it would be extremely difficult to update the guide.
  The tasks would be mainly:
 
  1) Update branding, logos, references to websites, ownership,
  license, etc., of OpenOffice.
 
  2) Update screenshots to current UI of AOO
 
  3) Update any technical content that has changed, e.g., platforms
  supported, file filters, etc.
 
  4) Write content for new migration-relevant features in AOO.
 
  5) General technical and editorial review of the content.
 
  Any other ideas?
 
  Regards,
 
  -Rob
 
 
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v2.0.22 (MingW32)
  Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
 
  iQEcBAEBAgAGBQJSgVMHAAoJEH0fu5UhGmBCckAH/iVw3d9/pr10DyDMgxk/Z26c
  tq011s+F/CkV5XbPbkLc/VTvZqiwG07dYdrkzUb1e+WTdVHHanUoyZwK8MJpK6YS
  xxkhJGQlIWuN2ctMxJC7/kQI34J/CpZSXOmj0Y0jhImxdefX7n3+QT6jjk4CDWaZ
  UF/fBcSyjnbi4jHg4lm4vmH4F1ts8FckLfsSLspGDfm5aHVv+CZ1ltAckUu2cbiY
  jEfBJQZnrhcsTVXzROQxv/9Z5AWaKFA4R5+ctfU3j3ytwO7QDrNuwtro6YPGerZT
  H/LhfNxIG62g3KVvox/z5pZreOt5U7kuur67J/B3jelP2kO48SuREmuEgQAyKw4=
  =X7xh
  -END PGP SIGNATURE-
 
 
  -
  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: Updated migration guide?

2013-11-12 Thread Graham Lauder
On Wed, Nov 13, 2013 at 8:24 AM, Rob Weir robw...@apache.org wrote:

 On Mon, Nov 11, 2013 at 4:58 PM, Keith N. McKenna
 keith.mcke...@comcast.net wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Rob Weir wrote:
  I'm thinking of starting to create an updated migration guide for
  AOO. If you have any thoughts on this, or want to help, let me
  know.
 
  Target audience includes:
 
  1) Individual Microsoft Office users, where such users provide
  their own technical support.
 
  2) IT departments who support users migrating from MS Office to
  OpenOffice
 
  3) Groups considering moving to AOO and wanting some guidance on
  migration strategy
 
  Rather than starting from scratch, I looked around to see if there
  is anything close that could be updated.   I saw that we have a few
  older versions of this kind of document:
 
  1) Migration Guide: A guide to ease your migration to
  OpenOffice.org from other office suites (2004)
 
 
 http://www.openoffice.org/documentation/manuals/oooauthors/MigrationGuide.pdf
 
   2) OpenOffice.org 2.0 Migration Guide (2006)
 
 
 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide
 
   3) OpenOffice.org Migration Guide (2006)
 
  https://wiki.openoffice.org/w/images/7/79/0600MG-MigrationGuide.pdf
 
   Does anyone know of anything more recent than the 2006 version?
  Does anyone know where the source for the 2006 PDF is?  Or was it
  generated from the wiki?
 
  I believe that all the documentation for Version 2 was done on the
  wiki and was then made into PDF's using an add-on.
 

 OK.  If I wanted to start a new revision of the guide, without wiping
 out or replacing the old version, is there any way to do this?   For
 example, is it possible to make a copy of this page and the subpages?


 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide

 I don't see how to do this.  Perhaps it requires admin rights?

 -Rob


Ack Sorry,  GMail defaults can be a pain... as I was trying to say

It shouldn't be too difficult,  I think that you can do this using the move
tab, you can rename that and the subpages as well although that's not a
copy per se.

I'll see what I can do, just may have to revert,  if it all turns to
custard tarts

Cheers
GL






  Regards
  Keith
 
  I don't think it would be extremely difficult to update the guide.
  The tasks would be mainly:
 
  1) Update branding, logos, references to websites, ownership,
  license, etc., of OpenOffice.
 
  2) Update screenshots to current UI of AOO
 
  3) Update any technical content that has changed, e.g., platforms
  supported, file filters, etc.
 
  4) Write content for new migration-relevant features in AOO.
 
  5) General technical and editorial review of the content.
 
  Any other ideas?
 
  Regards,
 
  -Rob
 
 
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v2.0.22 (MingW32)
  Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
 
  iQEcBAEBAgAGBQJSgVMHAAoJEH0fu5UhGmBCckAH/iVw3d9/pr10DyDMgxk/Z26c
  tq011s+F/CkV5XbPbkLc/VTvZqiwG07dYdrkzUb1e+WTdVHHanUoyZwK8MJpK6YS
  xxkhJGQlIWuN2ctMxJC7/kQI34J/CpZSXOmj0Y0jhImxdefX7n3+QT6jjk4CDWaZ
  UF/fBcSyjnbi4jHg4lm4vmH4F1ts8FckLfsSLspGDfm5aHVv+CZ1ltAckUu2cbiY
  jEfBJQZnrhcsTVXzROQxv/9Z5AWaKFA4R5+ctfU3j3ytwO7QDrNuwtro6YPGerZT
  H/LhfNxIG62g3KVvox/z5pZreOt5U7kuur67J/B3jelP2kO48SuREmuEgQAyKw4=
  =X7xh
  -END PGP SIGNATURE-
 
 
  -
  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: [code] solution for issue 33737 - in-place editing of Input Fields

2013-11-12 Thread Andrea Pescetti

On 07/11/2013 Oliver-Rainer Wittmann wrote:

I am working on a solution for issue 33737 [1] and I am making good
progress.
I have started the documentation of the solution in our wiki - please
have a look at https://wiki.openoffice.org/wiki/Writer/Input_Fields


This is a nice usability improvement, thank you for documenting it very 
clearly.


My only concern is whether it is better to use TAB to travel to the next 
input field and CTRL-TAB to insert a TAB, or just use CTRL-TAB to travel 
to the next input field and allow normal insertions of TAB within the 
field. Would this convention be used only here or do we have a similar 
convention in place to travel, say, between text frames or similar?


Regards,
  Andrea.

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



Re: Updated migration guide?

2013-11-12 Thread Graham Lauder
I'm getting a 502 Proxy error on the mwiki, edits aren't taking


On Wed, Nov 13, 2013 at 11:30 AM, Graham Lauder y...@apache.org wrote:




 On Wed, Nov 13, 2013 at 8:24 AM, Rob Weir robw...@apache.org wrote:

 On Mon, Nov 11, 2013 at 4:58 PM, Keith N. McKenna
 keith.mcke...@comcast.net wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Rob Weir wrote:
  I'm thinking of starting to create an updated migration guide for
  AOO. If you have any thoughts on this, or want to help, let me
  know.
 
  Target audience includes:
 
  1) Individual Microsoft Office users, where such users provide
  their own technical support.
 
  2) IT departments who support users migrating from MS Office to
  OpenOffice
 
  3) Groups considering moving to AOO and wanting some guidance on
  migration strategy
 
  Rather than starting from scratch, I looked around to see if there
  is anything close that could be updated.   I saw that we have a few
  older versions of this kind of document:
 
  1) Migration Guide: A guide to ease your migration to
  OpenOffice.org from other office suites (2004)
 
 
 http://www.openoffice.org/documentation/manuals/oooauthors/MigrationGuide.pdf
 
   2) OpenOffice.org 2.0 Migration Guide (2006)
 
 
 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide
 
   3) OpenOffice.org Migration Guide (2006)
 
  https://wiki.openoffice.org/w/images/7/79/0600MG-MigrationGuide.pdf
 
   Does anyone know of anything more recent than the 2006 version?
  Does anyone know where the source for the 2006 PDF is?  Or was it
  generated from the wiki?
 
  I believe that all the documentation for Version 2 was done on the
  wiki and was then made into PDF's using an add-on.
 

 OK.  If I wanted to start a new revision of the guide, without wiping
 out or replacing the old version, is there any way to do this?   For
 example, is it possible to make a copy of this page and the subpages?


 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide

 I don't see how to do this.  Perhaps it requires admin rights?

 -Rob


 Ack Sorry,  GMail defaults can be a pain... as I was trying to say

 It shouldn't be too difficult,  I think that you can do this using the
 move tab, you can rename that and the subpages as well although that's not
 a copy per se.

 I'll see what I can do, just may have to revert,  if it all turns to
 custard tarts

 Cheers
 GL






  Regards
  Keith
 
  I don't think it would be extremely difficult to update the guide.
  The tasks would be mainly:
 
  1) Update branding, logos, references to websites, ownership,
  license, etc., of OpenOffice.
 
  2) Update screenshots to current UI of AOO
 
  3) Update any technical content that has changed, e.g., platforms
  supported, file filters, etc.
 
  4) Write content for new migration-relevant features in AOO.
 
  5) General technical and editorial review of the content.
 
  Any other ideas?
 
  Regards,
 
  -Rob
 
 
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v2.0.22 (MingW32)
  Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
 
  iQEcBAEBAgAGBQJSgVMHAAoJEH0fu5UhGmBCckAH/iVw3d9/pr10DyDMgxk/Z26c
  tq011s+F/CkV5XbPbkLc/VTvZqiwG07dYdrkzUb1e+WTdVHHanUoyZwK8MJpK6YS
  xxkhJGQlIWuN2ctMxJC7/kQI34J/CpZSXOmj0Y0jhImxdefX7n3+QT6jjk4CDWaZ
  UF/fBcSyjnbi4jHg4lm4vmH4F1ts8FckLfsSLspGDfm5aHVv+CZ1ltAckUu2cbiY
  jEfBJQZnrhcsTVXzROQxv/9Z5AWaKFA4R5+ctfU3j3ytwO7QDrNuwtro6YPGerZT
  H/LhfNxIG62g3KVvox/z5pZreOt5U7kuur67J/B3jelP2kO48SuREmuEgQAyKw4=
  =X7xh
  -END PGP SIGNATURE-
 
 
  -
  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





Media Wiki Proxy Error

2013-11-12 Thread Graham Lauder
I'm having issues editing the Media wiki, I keep getting a 502 error.

Everything works up 'til the submit process.

Error as follows:


Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /w/index.php.

Reason: Error reading from remote server

Does this need an infra@ post or a bugzilla issue?

Cheers
GL


Re: [proposal] GIT mirror

2013-11-12 Thread Kay Schenk
On Tue, Nov 12, 2013 at 1:38 PM, Rob Weir robw...@apache.org wrote:

 On Tue, Nov 12, 2013 at 3:51 PM, Marcus (OOo) marcus.m...@wtnet.de
 wrote:
  Am 11/12/2013 08:12 PM, schrieb Rob Weir:
 
  On Tue, Nov 12, 2013 at 2:08 PM, Andrea Pescettipesce...@apache.org
  wrote:
 
  Herbert Duerr wrote:
 
 
  On 12.11.2013 16:48, janI wrote:
 
 
  @herbert, if nobody objects will you reopen the ticket, or should I ?
 
 
  I have reopened the JIRA issue and requested a read-only mirror for
 now.
 
 
 
  And what would be the advantage for real contributors in having a
  read-only
  GIT mirror? The complaints I've seen so far are mostly in the other
  direction (i.e., committing or applying patches). I'm not talking about
  generic advantages of GIT: everybody here can be assumed to have a good
  working knowledge of both SVN and GIT. What concrete problems does a
  read-only GIT mirror solve in our case?
 
  I'm not at all against it, but I'd just like to make sure that a
  read-only
  GIT mirror brings enough concrete advantages, since many GIT niceties
  (local
  commits, proper attribution, quick application of patches) are still
 left
  out or significantly limited with this approach.
 
  By the way, you can find discussions about GIT everywhere at Apache,
  there's
  even a Github account https://github.com/apache and lots of
 suggestions
  like
  adopting the newly-released Apache Allura (Incubating) GIT (and more)
  hosting environment. As far as I know, there have been very significant
  updates in the GIT support at Apache in the last few weeks and I hope
  that
  this is soon summarized in a blog post at
 http://blogs.apache.org/infra/
  or
  reflected in the documentation at http://www.apache.org/dev/git.html. So
  this is a good moment to start considering GIT again.
 
 
  We should consider the website as well.  Does the CMS have hooks that
  work with git repositories as well?  Or would we need to keep the
  website in SVN?
 
 
  Good point. This has to be clarified as we don't want to keep our website
  volunteers outside just because the CMS system doesn't support Git. To
 let
  everybody of them commit via CLI or GUI tools wouldn't be nice.
 

 But if it is an issue then one solution could be to move the product
 source to git and keep the websites in SVN.  We're generally not
 dealing with multiple complex branches for the website, so the
 advantages of git here are less.

 -Rob


On this latest topic here -- we really should NOT consider switching the
web to git if this doesn't play well with the CMS --GUI or otherwise.

On the rest of it...as someone not busy with active development, maybe I
shouldn't voice an opinion, but... I didn't know svn until this Apache work
-- having used the old CVS prior to this. And, I don't know git or git-svn
at all, but, as been pointed out -- I can learn.

My one question at this point concerns the official Apache repositories --

http://www.apache.org/dev/version-control.html

Are we obligated to use svn for this, or the permanent distribution? Use
git only for some branches but not all?

And, like Andrea, I don't see what supplying a read-only git mirror gets
us, but, I guess we need to learn more about the security considerations.




  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




-- 
-
MzK

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


Re: [proposal] GIT mirror

2013-11-12 Thread Marcus (OOo)

Am 11/12/2013 10:38 PM, schrieb Rob Weir:

On Tue, Nov 12, 2013 at 3:51 PM, Marcus (OOo)marcus.m...@wtnet.de  wrote:

Am 11/12/2013 08:12 PM, schrieb Rob Weir:


On Tue, Nov 12, 2013 at 2:08 PM, Andrea Pescettipesce...@apache.org
wrote:


Herbert Duerr wrote:



On 12.11.2013 16:48, janI wrote:



@herbert, if nobody objects will you reopen the ticket, or should I ?



I have reopened the JIRA issue and requested a read-only mirror for now.




And what would be the advantage for real contributors in having a
read-only
GIT mirror? The complaints I've seen so far are mostly in the other
direction (i.e., committing or applying patches). I'm not talking about
generic advantages of GIT: everybody here can be assumed to have a good
working knowledge of both SVN and GIT. What concrete problems does a
read-only GIT mirror solve in our case?

I'm not at all against it, but I'd just like to make sure that a
read-only
GIT mirror brings enough concrete advantages, since many GIT niceties
(local
commits, proper attribution, quick application of patches) are still left
out or significantly limited with this approach.

By the way, you can find discussions about GIT everywhere at Apache,
there's
even a Github account https://github.com/apache and lots of suggestions
like
adopting the newly-released Apache Allura (Incubating) GIT (and more)
hosting environment. As far as I know, there have been very significant
updates in the GIT support at Apache in the last few weeks and I hope
that
this is soon summarized in a blog post at http://blogs.apache.org/infra/
or
reflected in the documentation at http://www.apache.org/dev/git.html . So
this is a good moment to start considering GIT again.



We should consider the website as well.  Does the CMS have hooks that
work with git repositories as well?  Or would we need to keep the
website in SVN?



Good point. This has to be clarified as we don't want to keep our website
volunteers outside just because the CMS system doesn't support Git. To let
everybody of them commit via CLI or GUI tools wouldn't be nice.



But if it is an issue then one solution could be to move the product
source to git and keep the websites in SVN.  We're generally not
dealing with multiple complex branches for the website, so the
advantages of git here are less.


Sure, to split the things when it makes sense is also an option.

Marcus

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



Re: Time to start 4.1 planning?

2013-11-12 Thread Marcus (OOo)

Am 11/12/2013 10:36 PM, schrieb Rob Weir:

On Tue, Nov 12, 2013 at 3:51 PM, Marcus (OOo)marcus.m...@wtnet.de  wrote:

Am 11/11/2013 10:33 PM, schrieb Rob Weir:


On Mon, Nov 11, 2013 at 3:21 PM, Marcus (OOo)marcus.m...@wtnet.de
wrote:


Am 11/11/2013 04:12 PM, schrieb Jürgen Schmidt:


On 11/11/13 3:59 PM, Rob Weir wrote:



On Mon, Nov 11, 2013 at 3:32 AM, Shenfeng Liuliush...@gmail.com
wrote:



Hi, all,
 It was one month since 4.0.1 release. And I noticed some some
great
works
are going to be delivered soon. e.g. the IA2 framework from Steve, the
Mac
64-bit support from Herbert, and Windows Patch mechanism from Andre.

 So I'm thinking, is it a good time to start the 4.1 plan now? We
should
deliver those great value to our users through a formal release ASAP!
And
IMO, even only the 3 items above can be enough for a release to be
called
4.1. We also want to do OOXML improvement by integrating OSBA patches,
and
enhance user experience like in-place Input Field, and many other
things...
While, I think we can keep the continuous improvement across releases.
From
the record breaking download number since 4.0 and 4.0.1, I feel that
keeping regular release is very important to response to our users,
attract
more new comers, and bring this product to success.

 So I suggest we start the 4.1 plan now, and set a target date.
Since
4.0
was in July, 4.0.1 was in Oct, I feel some time in 1Q will be a good
time
for 4.1.



Hi Simon,

Something to think about:   After 4.0.0 we discussed having a public
beta with out next major release.  If we think this is worth doing,
then we should plan on two dates:  1) A public beta data, and 2) a
final release date.   For the beta to be useful I think we would want
it to last 3-4 weeks, enough time to process any new bug reports,
identify any critical regressions, and fix them.




4 weeks between both is a minimum form my pov

But having a beta is of course the route we should take.




What about taking into account to keep the possibility to release a
second
Beta version? It can include fixes for the most nasty and prominent bugs.



Well, hopefully we do some amount of testing before we have a beta.
So the goal should be for the beta to have no nasty and prominent
bugs.  The beta is a form of insurance and a way of setting
expectations.

For example, I think these two scenarios are technically equivalent:

a) release 4.1.0 after normal testing

b) release 4.1.1 to fix major bugs that we missed in 4.1.0 testing.

and

a') release 4.1.0 beta after normal testing

b') release 4.1.0 GA after fixing important bugs found in beta



Sure but we want to do a testing phase in public and not just technically.



These are technically the same, and take approximately the same amount
of time.  The difference is in user expectations.  A beta
designation tells the cautious user to avoid it.  It encourages users
who are willing to take more risk and help us by giving feedback.  It
also helps preserve the brand reputation by ensuring that the actual
GA releases are high quality.

(If we're not careful the users will develop a sense to avoid all
x.y.0 releases, believing them to be low quality.  Other products have
run into that problem, even with x.y.1 and x.y.2 releases.  I think it
is better if we can avoid having that kind of reputation.)



Intersting, one can understand your arguments as points to *do* a second
Beta release. ;-)



A 2nd beta might be necessary in some rare cases, but I think in most
cases we fix the critical bugs found in the beta and just do normal
re-testing of those areas in a Release Candidate.



Still no point not to do a second release.

But before you go on with writting, please understand my suggestion as
simple suggestion. I don't want to force it. When you deny it with a short
post, then it's fine. No need to find many arguments that speak (maybe)
against it. ;-)



I'm not necessarily opposed to have 2, or even 3 betas. (Ha!).  But I
say let the facts, not preconceptions, determine what we do.  Let's do
a beta, look at the results, discuss and then determine the next


Great, then you have understood what I wanted to say.

Marcus




steps.  I *predict* that only one beta will be needed.  But I'm not
insisting on it.

Regards,

-Rob


Marcus





If we agree on that, we should expand the timeframe to 6 or more weeks.

My 2 ct.

Marcus





 I suggest to update the 4.1 planning wiki[1] and:
(1) Set the target date.
(2) Clean up the planning list, starting from leaving only the active
items, and moving the rest to project backlog[2].

 Any suggestion/comments?


[1]


https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Planning
[2] https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Blog


- Shenfeng (Simon)


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



Re: Updated migration guide?

2013-11-12 Thread Keith N. McKenna
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Graham Lauder wrote:
 On Wed, Nov 13, 2013 at 8:24 AM, Rob Weir robw...@apache.org
 wrote:
 
 On Mon, Nov 11, 2013 at 4:58 PM, Keith N. McKenna 
 keith.mcke...@comcast.net wrote:
 Rob Weir wrote:
 I'm thinking of starting to create an updated migration
 guide for AOO. If you have any thoughts on this, or want to
 help, let me know.
 
 Target audience includes:
 
 1) Individual Microsoft Office users, where such users
 provide their own technical support.
 
 2) IT departments who support users migrating from MS
 Office to OpenOffice
 
 3) Groups considering moving to AOO and wanting some
 guidance on migration strategy
 
 Rather than starting from scratch, I looked around to see
 if there is anything close that could be updated.   I saw
 that we have a few older versions of this kind of
 document:
 
 1) Migration Guide: A guide to ease your migration to 
 OpenOffice.org from other office suites (2004)
 
 
 http://www.openoffice.org/documentation/manuals/oooauthors/MigrationGuide.pdf


 
2) OpenOffice.org 2.0 Migration Guide (2006)
 
 
 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide


 
3) OpenOffice.org Migration Guide (2006)
 
 https://wiki.openoffice.org/w/images/7/79/0600MG-MigrationGuide.pdf


 
Does anyone know of anything more recent than the 2006 version?
 Does anyone know where the source for the 2006 PDF is?  Or
 was it generated from the wiki?
 
 I believe that all the documentation for Version 2 was done on the 
 wiki and was then made into PDF's using an add-on.
 
 
 OK.  If I wanted to start a new revision of the guide, without
 wiping out or replacing the old version, is there any way to do
 this?   For example, is it possible to make a copy of this page
 and the subpages?
 
 
 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide


 
I don't see how to do this.  Perhaps it requires admin rights?
 
 -Rob
 
 
 Ack Sorry,  GMail defaults can be a pain... as I was trying to
 say
 
 It shouldn't be too difficult,  I think that you can do this
 using the move tab, you can rename that and the subpages as well
 although that's not a copy per se.
 
 I'll see what I can do, just may have to revert,  if it all turns
 to custard tarts
 
 Cheers GL
 
 
Graham;

Using the Move command will rename the pages to the new namespace and
set a redirect on the original to the new pages.

One word of caution. Those pages are covered by the CCBY license. The
only way I now to redo those pages under an alv2 license would be to
start over from scratch and not use the prior pages at all. For me it
makes much more sense to just update the pages with current
information and keep the license as is. However I bring it up as some
people have rather strong opinions about using other than the alv2
license.

Regards
Keith
 
 
 
 
 Regards Keith
 
 I don't think it would be extremely difficult to update the
 guide. The tasks would be mainly:
 
 1) Update branding, logos, references to websites,
 ownership, license, etc., of OpenOffice.
 
 2) Update screenshots to current UI of AOO
 
 3) Update any technical content that has changed, e.g.,
 platforms supported, file filters, etc.
 
 4) Write content for new migration-relevant features in
 AOO.
 
 5) General technical and editorial review of the content.
 
 Any other ideas?
 
 Regards,
 
 -Rob
 
 
 
 
 -

 
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
 
 
 

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

iQEcBAEBAgAGBQJSgsCeAAoJEH0fu5UhGmBCPNsH/38LW+DR5OTAENWa6wJCYcOA
ZJMVKOAroBRRVWDtf625v+Le58jHeWpg09MrLMy60JTMYxud8j2R1Ur6PBv3Xxam
GzVUx12XszDF4peb/sGvK8XuIODqQqWLaIZApAIGczCTNmmu9Bopu6leoqMTYFdh
IUAFYPkxmZyJs1I4m0ne2XqZmXSyjvVKEmVovyuiGjROgyb+hiS2NLTw11qAbGfm
Bx4FUfRP5LI57sN2uMpbaXrPyX+6sWRvK9UkoNlfAe4ai4piX4216YPlSfnihG3p
jKscC2DfBMyxWzpl9z2Qv952woX3RhuIL5Gud+9k6wyzWq0YF5P1su19oG97s/E=
=1gc0
-END PGP SIGNATURE-


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



Re: Updated migration guide?

2013-11-12 Thread Rob Weir
On Tue, Nov 12, 2013 at 6:58 PM, Keith N. McKenna
keith.mcke...@comcast.net wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Graham Lauder wrote:
 On Wed, Nov 13, 2013 at 8:24 AM, Rob Weir robw...@apache.org
 wrote:

 On Mon, Nov 11, 2013 at 4:58 PM, Keith N. McKenna
 keith.mcke...@comcast.net wrote:
 Rob Weir wrote:
 I'm thinking of starting to create an updated migration
 guide for AOO. If you have any thoughts on this, or want to
 help, let me know.

 Target audience includes:

 1) Individual Microsoft Office users, where such users
 provide their own technical support.

 2) IT departments who support users migrating from MS
 Office to OpenOffice

 3) Groups considering moving to AOO and wanting some
 guidance on migration strategy

 Rather than starting from scratch, I looked around to see
 if there is anything close that could be updated.   I saw
 that we have a few older versions of this kind of
 document:

 1) Migration Guide: A guide to ease your migration to
 OpenOffice.org from other office suites (2004)


 http://www.openoffice.org/documentation/manuals/oooauthors/MigrationGuide.pdf



 2) OpenOffice.org 2.0 Migration Guide (2006)


 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide



 3) OpenOffice.org Migration Guide (2006)

 https://wiki.openoffice.org/w/images/7/79/0600MG-MigrationGuide.pdf



 Does anyone know of anything more recent than the 2006 version?
 Does anyone know where the source for the 2006 PDF is?  Or
 was it generated from the wiki?

 I believe that all the documentation for Version 2 was done on the
 wiki and was then made into PDF's using an add-on.


 OK.  If I wanted to start a new revision of the guide, without
 wiping out or replacing the old version, is there any way to do
 this?   For example, is it possible to make a copy of this page
 and the subpages?


 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide



 I don't see how to do this.  Perhaps it requires admin rights?

 -Rob


 Ack Sorry,  GMail defaults can be a pain... as I was trying to
 say

 It shouldn't be too difficult,  I think that you can do this
 using the move tab, you can rename that and the subpages as well
 although that's not a copy per se.

 I'll see what I can do, just may have to revert,  if it all turns
 to custard tarts

 Cheers GL


 Graham;

 Using the Move command will rename the pages to the new namespace and
 set a redirect on the original to the new pages.

 One word of caution. Those pages are covered by the CCBY license. The
 only way I now to redo those pages under an alv2 license would be to
 start over from scratch and not use the prior pages at all. For me it
 makes much more sense to just update the pages with current
 information and keep the license as is. However I bring it up as some
 people have rather strong opinions about using other than the alv2
 license.


I don't see a problem building on the existing content, under the
stated license.  We're not including these guides in a release.  The
reason for a copy was to preserve the existing material for users
while a new version is being prepared.  It could take a few weeks to
do the update and it could be messy day-to-day.

-Rob

 Regards
 Keith




 Regards Keith

 I don't think it would be extremely difficult to update the
 guide. The tasks would be mainly:

 1) Update branding, logos, references to websites,
 ownership, license, etc., of OpenOffice.

 2) Update screenshots to current UI of AOO

 3) Update any technical content that has changed, e.g.,
 platforms supported, file filters, etc.

 4) Write content for new migration-relevant features in
 AOO.

 5) General technical and editorial review of the content.

 Any other ideas?

 Regards,

 -Rob




 -


 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




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

 iQEcBAEBAgAGBQJSgsCeAAoJEH0fu5UhGmBCPNsH/38LW+DR5OTAENWa6wJCYcOA
 ZJMVKOAroBRRVWDtf625v+Le58jHeWpg09MrLMy60JTMYxud8j2R1Ur6PBv3Xxam
 GzVUx12XszDF4peb/sGvK8XuIODqQqWLaIZApAIGczCTNmmu9Bopu6leoqMTYFdh
 IUAFYPkxmZyJs1I4m0ne2XqZmXSyjvVKEmVovyuiGjROgyb+hiS2NLTw11qAbGfm
 Bx4FUfRP5LI57sN2uMpbaXrPyX+6sWRvK9UkoNlfAe4ai4piX4216YPlSfnihG3p
 jKscC2DfBMyxWzpl9z2Qv952woX3RhuIL5Gud+9k6wyzWq0YF5P1su19oG97s/E=
 =1gc0
 -END PGP SIGNATURE-


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



Re: Updated migration guide?

2013-11-12 Thread Graham Lauder
On Wed, Nov 13, 2013 at 12:58 PM, Keith N. McKenna 
keith.mcke...@comcast.net wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Graham Lauder wrote:
  On Wed, Nov 13, 2013 at 8:24 AM, Rob Weir robw...@apache.org
  wrote:
 
  On Mon, Nov 11, 2013 at 4:58 PM, Keith N. McKenna
  keith.mcke...@comcast.net wrote:
  Rob Weir wrote:
  I'm thinking of starting to create an updated migration
  guide for AOO. If you have any thoughts on this, or want to
  help, let me know.
 
  Target audience includes:
 
  1) Individual Microsoft Office users, where such users
  provide their own technical support.
 
  2) IT departments who support users migrating from MS
  Office to OpenOffice
 
  3) Groups considering moving to AOO and wanting some
  guidance on migration strategy
 
  Rather than starting from scratch, I looked around to see
  if there is anything close that could be updated.   I saw
  that we have a few older versions of this kind of
  document:
 
  1) Migration Guide: A guide to ease your migration to
  OpenOffice.org from other office suites (2004)
 
 
 
 http://www.openoffice.org/documentation/manuals/oooauthors/MigrationGuide.pdf
 
 
 
 2) OpenOffice.org 2.0 Migration Guide (2006)
 
 
 
 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide
 
 
 
 3) OpenOffice.org Migration Guide (2006)
 
  https://wiki.openoffice.org/w/images/7/79/0600MG-MigrationGuide.pdf
 
 
 
 Does anyone know of anything more recent than the 2006 version?
  Does anyone know where the source for the 2006 PDF is?  Or
  was it generated from the wiki?
 
  I believe that all the documentation for Version 2 was done on the
  wiki and was then made into PDF's using an add-on.
 
 
  OK.  If I wanted to start a new revision of the guide, without
  wiping out or replacing the old version, is there any way to do
  this?   For example, is it possible to make a copy of this page
  and the subpages?
 
 
 
 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide
 
 
 
 I don't see how to do this.  Perhaps it requires admin rights?
 
  -Rob
 
 
  Ack Sorry,  GMail defaults can be a pain... as I was trying to
  say
 
  It shouldn't be too difficult,  I think that you can do this
  using the move tab, you can rename that and the subpages as well
  although that's not a copy per se.
 
  I'll see what I can do, just may have to revert,  if it all turns
  to custard tarts
 
  Cheers GL
 
 
 Graham;

 Using the Move command will rename the pages to the new namespace and
 set a redirect on the original to the new pages.


Ah good I was wondering about that which is what I was trying to test.



 One word of caution. Those pages are covered by the CCBY license. The
 only way I now to redo those pages under an alv2 license would be to
 start over from scratch and not use the prior pages at all. For me it
 makes much more sense to just update the pages with current
 information and keep the license as is. However I bring it up as some
 people have rather strong opinions about using other than the alv2
 license.


That was one of my concerns and I am of the opinion that at some point a
ground up rewrite would be the best in order to adjust the license
position.  However in the short term I agree with you that an updated
Migration Guide under the old license would be the simplest.  As long it's
not released with the software, it shouldn't be too much of an issue right
now.

Cheers
GL




 Regards
 Keith
 
 
 
 
  Regards Keith
 
  I don't think it would be extremely difficult to update the
  guide. The tasks would be mainly:
 
  1) Update branding, logos, references to websites,
  ownership, license, etc., of OpenOffice.
 
  2) Update screenshots to current UI of AOO
 
  3) Update any technical content that has changed, e.g.,
  platforms supported, file filters, etc.
 
  4) Write content for new migration-relevant features in
  AOO.
 
  5) General technical and editorial review of the content.
 
  Any other ideas?
 
  Regards,
 
  -Rob
 
 
 
 
  -
 
 
 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
 
 
 

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

 iQEcBAEBAgAGBQJSgsCeAAoJEH0fu5UhGmBCPNsH/38LW+DR5OTAENWa6wJCYcOA
 ZJMVKOAroBRRVWDtf625v+Le58jHeWpg09MrLMy60JTMYxud8j2R1Ur6PBv3Xxam
 GzVUx12XszDF4peb/sGvK8XuIODqQqWLaIZApAIGczCTNmmu9Bopu6leoqMTYFdh
 IUAFYPkxmZyJs1I4m0ne2XqZmXSyjvVKEmVovyuiGjROgyb+hiS2NLTw11qAbGfm
 Bx4FUfRP5LI57sN2uMpbaXrPyX+6sWRvK9UkoNlfAe4ai4piX4216YPlSfnihG3p
 jKscC2DfBMyxWzpl9z2Qv952woX3RhuIL5Gud+9k6wyzWq0YF5P1su19oG97s/E=
 =1gc0
 -END 

buildbots -- Linux and MacOSX

2013-11-12 Thread Kay Schenk
Regarding Jürgen's comments  on a recent thread --

http://markmail.org/message/v5zli2np67qv5ryz

Since  CentOS 5 is our reference distribution for delivered Linux binaries
(I did not know this!) -- and I am assuming this distro might remain as the
reference going forward, does it make sense to try to move forward to set
this up as a buildbot. I know wokr had already started on this. Can someone
give us an update?

https://issues.apache.org/jira/browse/INFRA-6217

I don't know CentOS, but having about 18  years in various *nixes HP/UX,
Solaris, RedHat, SuSE), I could probably help assuming I could work in
command line only to deal with this.

On the MacOSX front, the latest update indicates we don't have hardware :(

https://issues.apache.org/jira/browse/INFRA-4902

Any suggestions? Volunteers with equipment to dedicate to this?



-- 
-
MzK

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


Re: buildbots -- Linux and MacOSX

2013-11-12 Thread Glenn Harvey Liwanag
I can try building the thing on my Mac OS X if that's what you're looking
for. It's my only computer right now and I use it for school so I have to
know first the average build time and the instructions to get the whole
thing done without academics interfering with the work.


On Wed, Nov 13, 2013 at 9:08 AM, Kay Schenk kay.sch...@gmail.com wrote:

 Regarding Jürgen's comments  on a recent thread --

 http://markmail.org/message/v5zli2np67qv5ryz

 Since  CentOS 5 is our reference distribution for delivered Linux binaries
 (I did not know this!) -- and I am assuming this distro might remain as the
 reference going forward, does it make sense to try to move forward to set
 this up as a buildbot. I know wokr had already started on this. Can someone
 give us an update?

 https://issues.apache.org/jira/browse/INFRA-6217

 I don't know CentOS, but having about 18  years in various *nixes HP/UX,
 Solaris, RedHat, SuSE), I could probably help assuming I could work in
 command line only to deal with this.

 On the MacOSX front, the latest update indicates we don't have hardware :(

 https://issues.apache.org/jira/browse/INFRA-4902

 Any suggestions? Volunteers with equipment to dedicate to this?



 --

 -
 MzK

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



Re: Updated migration guide?

2013-11-12 Thread Graham Lauder
On Wed, Nov 13, 2013 at 1:35 PM, Rob Weir robw...@apache.org wrote:

 On Tue, Nov 12, 2013 at 6:58 PM, Keith N. McKenna
 keith.mcke...@comcast.net wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Graham Lauder wrote:
  On Wed, Nov 13, 2013 at 8:24 AM, Rob Weir robw...@apache.org
  wrote:
 
  On Mon, Nov 11, 2013 at 4:58 PM, Keith N. McKenna
  keith.mcke...@comcast.net wrote:
  Rob Weir wrote:
  I'm thinking of starting to create an updated migration
  guide for AOO. If you have any thoughts on this, or want to
  help, let me know.
 
  Target audience includes:
 
  1) Individual Microsoft Office users, where such users
  provide their own technical support.
 
  2) IT departments who support users migrating from MS
  Office to OpenOffice
 
  3) Groups considering moving to AOO and wanting some
  guidance on migration strategy
 
  Rather than starting from scratch, I looked around to see
  if there is anything close that could be updated.   I saw
  that we have a few older versions of this kind of
  document:
 
  1) Migration Guide: A guide to ease your migration to
  OpenOffice.org from other office suites (2004)
 
 
 
 http://www.openoffice.org/documentation/manuals/oooauthors/MigrationGuide.pdf
 
 
 
  2) OpenOffice.org 2.0 Migration Guide (2006)
 
 
 
 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide
 
 
 
  3) OpenOffice.org Migration Guide (2006)
 
  https://wiki.openoffice.org/w/images/7/79/0600MG-MigrationGuide.pdf
 
 
 
  Does anyone know of anything more recent than the 2006 version?
  Does anyone know where the source for the 2006 PDF is?  Or
  was it generated from the wiki?
 
  I believe that all the documentation for Version 2 was done on the
  wiki and was then made into PDF's using an add-on.
 
 
  OK.  If I wanted to start a new revision of the guide, without
  wiping out or replacing the old version, is there any way to do
  this?   For example, is it possible to make a copy of this page
  and the subpages?
 
 
 
 https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide
 
 
 
  I don't see how to do this.  Perhaps it requires admin rights?
 
  -Rob
 
 
  Ack Sorry,  GMail defaults can be a pain... as I was trying to
  say
 
  It shouldn't be too difficult,  I think that you can do this
  using the move tab, you can rename that and the subpages as well
  although that's not a copy per se.
 
  I'll see what I can do, just may have to revert,  if it all turns
  to custard tarts
 
  Cheers GL
 
  Graham;
 
 
  Using the Move command will rename the pages to the new namespace and
  set a redirect on the original to the new pages.
 
  One word of caution. Those pages are covered by the CCBY license. The
  only way I now to redo those pages under an alv2 license would be to
  start over from scratch and not use the prior pages at all. For me it
  makes much more sense to just update the pages with current
  information and keep the license as is. However I bring it up as some
  people have rather strong opinions about using other than the alv2
  license.
 

 I don't see a problem building on the existing content, under the
 stated license.  We're not including these guides in a release.  The
 reason for a copy was to preserve the existing material for users
 while a new version is being prepared.  It could take a few weeks to
 do the update and it could be messy day-to-day.

 -Rob




OK I've set up a new structure, not sure what the 502 error is, but edits
seem to be taking in any case, even though the 502 still keeps popping up.

The old version has been moved to
https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Migration_Guide_2006


And I've shifted an editable version to
https://wiki.openoffice.org/wiki/Documentation/UserGuide/Migration_Guidehttps://wiki.openoffice.org/wiki/Documentation/UserGuide/Migration_Guide/Calc_and_Excel

I've put a link to the old Guide on the bottom of the front page

I noted that there is no link to the Migration guide on the Documentation
front page,  Should I link to both versions on there or just the '06
version.

I just have a couple of subpages that didn't move for some reason to sort

Recommend anyone wanting to contribute use the discussion page and put a
watch on it so you can keep up with what's going on.

Cheers
GL


  Regards
  Keith
 
 
 
 
  Regards Keith
 
  I don't think it would be extremely difficult to update the
  guide. The tasks would be mainly:
 
  1) Update branding, logos, references to websites,
  ownership, license, etc., of OpenOffice.
 
  2) Update screenshots to current UI of AOO
 
  3) Update any technical content that has changed, e.g.,
  platforms supported, file filters, etc.
 
  4) Write content for new migration-relevant features in
  AOO.
 
  5) General technical and editorial review of the content.
 
  Any other ideas?
 
  Regards,
 
  -Rob
 
 
 
 
  -
 
 
  To 

Re: Reporting a problem with the OpenOffice website

2013-11-12 Thread Shenfeng Liu
2013/11/11 Ian Lynch ianrly...@gmail.com

 Apache Open Office is not Microsoft Office. We make it as compatible as we
 possibly can but since MS does not tell us exactly how it organises its
 data that is not always easy. I don't think anyone has ever claimed
 OpenOffice to be able to provide complex MS documents with 100% fidelity.

From the original mail, I'm not quite sure if the reported is about AOO's
interoperability issue to MS Office format, or MS Office's interoperability
issue to ODF format...


 If you draw your diagrams in a drawing program as opposed to a word
 processor you will find it more efficient. Then you can put the diagrams
 into the WP document as .pngs without much risk of things going astray.


 On 10 November 2013 21:30, Marouf Ahmed marou...@hotmail.com wrote:

  I finished my coursework on Open Office with great difficulty. I have
  outrageously angry with the software it took me half an hour to sort out
  images in my coursework. When I opened the document in Microsoft word
  viewer (as my school uses Microsoft office) all my coursework had messed
 up
  I was furious to find that the call outs that I used in open office did
 not
  appear on Microsoft office and that some images had got out of place, it
  had also rearranged my diagram.
 
 
 
  Sent from Windows Mail




 --
 Ian

 Ofqual Accredited IT Qualifications 
 https://theingots.org/community/faq#7.0

 Headline points in the 2014 and 2015 school league tables

 www.theINGOTs.org +44 (0)1827 305940

 The Learning Machine Limited, Reg Office, Unit 4D Gagarin, Lichfield
 Road Industrial Estate, Tamworth, Staffordshire, B79 7GN. Reg No:
 05560797, Registered in England and Wales.



Re: Time to start 4.1 planning?

2013-11-12 Thread Shenfeng Liu
I just updated the 4.1 planning wiki[1]:
(1) I added the section of Proposed Release Schedule, including the beta.
But I left most of the milestones TBD.
(2) I created a wiki page of AOO Feature Enhancement Backlog[2], and left
only those active items (per my reading from the dev list) in 4.1, but
moved the rest to this backlog.

  Any comments are welcome!

[1]
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Planning
[2]
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+Feature+Enhancement+Backlog


- Shenfeng (Simon)




2013/11/13 Marcus (OOo) marcus.m...@wtnet.de

 Am 11/12/2013 10:36 PM, schrieb Rob Weir:

  On Tue, Nov 12, 2013 at 3:51 PM, Marcus (OOo)marcus.m...@wtnet.de
  wrote:

 Am 11/11/2013 10:33 PM, schrieb Rob Weir:

  On Mon, Nov 11, 2013 at 3:21 PM, Marcus (OOo)marcus.m...@wtnet.de
 wrote:


 Am 11/11/2013 04:12 PM, schrieb Jürgen Schmidt:

  On 11/11/13 3:59 PM, Rob Weir wrote:



 On Mon, Nov 11, 2013 at 3:32 AM, Shenfeng Liuliush...@gmail.com
 wrote:



 Hi, all,
  It was one month since 4.0.1 release. And I noticed some some
 great
 works
 are going to be delivered soon. e.g. the IA2 framework from Steve,
 the
 Mac
 64-bit support from Herbert, and Windows Patch mechanism from Andre.

  So I'm thinking, is it a good time to start the 4.1 plan now?
 We
 should
 deliver those great value to our users through a formal release
 ASAP!
 And
 IMO, even only the 3 items above can be enough for a release to be
 called
 4.1. We also want to do OOXML improvement by integrating OSBA
 patches,
 and
 enhance user experience like in-place Input Field, and many other
 things...
 While, I think we can keep the continuous improvement across
 releases.
 From
 the record breaking download number since 4.0 and 4.0.1, I feel that
 keeping regular release is very important to response to our users,
 attract
 more new comers, and bring this product to success.

  So I suggest we start the 4.1 plan now, and set a target date.
 Since
 4.0
 was in July, 4.0.1 was in Oct, I feel some time in 1Q will be a good
 time
 for 4.1.


 Hi Simon,

 Something to think about:   After 4.0.0 we discussed having a public
 beta with out next major release.  If we think this is worth doing,
 then we should plan on two dates:  1) A public beta data, and 2) a
 final release date.   For the beta to be useful I think we would want
 it to last 3-4 weeks, enough time to process any new bug reports,
 identify any critical regressions, and fix them.




 4 weeks between both is a minimum form my pov

 But having a beta is of course the route we should take.




 What about taking into account to keep the possibility to release a
 second
 Beta version? It can include fixes for the most nasty and prominent
 bugs.


 Well, hopefully we do some amount of testing before we have a beta.
 So the goal should be for the beta to have no nasty and prominent
 bugs.  The beta is a form of insurance and a way of setting
 expectations.

 For example, I think these two scenarios are technically equivalent:

 a) release 4.1.0 after normal testing

 b) release 4.1.1 to fix major bugs that we missed in 4.1.0 testing.

 and

 a') release 4.1.0 beta after normal testing

 b') release 4.1.0 GA after fixing important bugs found in beta



 Sure but we want to do a testing phase in public and not just
 technically.


  These are technically the same, and take approximately the same amount
 of time.  The difference is in user expectations.  A beta
 designation tells the cautious user to avoid it.  It encourages users
 who are willing to take more risk and help us by giving feedback.  It
 also helps preserve the brand reputation by ensuring that the actual
 GA releases are high quality.

 (If we're not careful the users will develop a sense to avoid all
 x.y.0 releases, believing them to be low quality.  Other products have
 run into that problem, even with x.y.1 and x.y.2 releases.  I think it
 is better if we can avoid having that kind of reputation.)



 Intersting, one can understand your arguments as points to *do* a second
 Beta release. ;-)


  A 2nd beta might be necessary in some rare cases, but I think in most
 cases we fix the critical bugs found in the beta and just do normal
 re-testing of those areas in a Release Candidate.



 Still no point not to do a second release.

 But before you go on with writting, please understand my suggestion as
 simple suggestion. I don't want to force it. When you deny it with a
 short
 post, then it's fine. No need to find many arguments that speak (maybe)
 against it. ;-)


 I'm not necessarily opposed to have 2, or even 3 betas. (Ha!).  But I
 say let the facts, not preconceptions, determine what we do.  Let's do
 a beta, look at the results, discuss and then determine the next


 Great, then you have understood what I wanted to say.

 Marcus




  steps.  I *predict* that only one beta will be needed.  But I'm not
 insisting on it.

 Regards,

 -Rob

  Marcus




  If we 

Re: Media Wiki Proxy Error

2013-11-12 Thread Shenfeng Liu
2013/11/13 Graham Lauder y...@apache.org

 I'm having issues editing the Media wiki, I keep getting a 502 error.

 Everything works up 'til the submit process.

 Error as follows:


 Proxy Error

 The proxy server received an invalid response from an upstream server.
 The proxy server could not handle the request POST /w/index.php.

 Reason: Error reading from remote server

I met the same issue when editing cwiki today. Tried several times, and the
last try worked...

- Shenfeng (Simon)




 Does this need an infra@ post or a bugzilla issue?

 Cheers
 GL



Re: [proposal] GIT mirror

2013-11-12 Thread janI
On Nov 13, 2013 12:45 AM, Marcus (OOo) marcus.m...@wtnet.de wrote:

 Am 11/12/2013 10:38 PM, schrieb Rob Weir:

 On Tue, Nov 12, 2013 at 3:51 PM, Marcus (OOo)marcus.m...@wtnet.de
 wrote:

 Am 11/12/2013 08:12 PM, schrieb Rob Weir:

 On Tue, Nov 12, 2013 at 2:08 PM, Andrea Pescettipesce...@apache.org
 wrote:


 Herbert Duerr wrote:



 On 12.11.2013 16:48, janI wrote:



 @herbert, if nobody objects will you reopen the ticket, or should I
?



 I have reopened the JIRA issue and requested a read-only mirror for
now.




 And what would be the advantage for real contributors in having a
 read-only
 GIT mirror? The complaints I've seen so far are mostly in the other
 direction (i.e., committing or applying patches). I'm not talking
about
 generic advantages of GIT: everybody here can be assumed to have a
good
 working knowledge of both SVN and GIT. What concrete problems does a
 read-only GIT mirror solve in our case?

 I'm not at all against it, but I'd just like to make sure that a
 read-only
 GIT mirror brings enough concrete advantages, since many GIT niceties
 (local
 commits, proper attribution, quick application of patches) are still
left
 out or significantly limited with this approach.

 By the way, you can find discussions about GIT everywhere at Apache,
 there's
 even a Github account https://github.com/apache and lots of
suggestions
 like
 adopting the newly-released Apache Allura (Incubating) GIT (and more)
 hosting environment. As far as I know, there have been very
significant
 updates in the GIT support at Apache in the last few weeks and I hope
 that
 this is soon summarized in a blog post at
http://blogs.apache.org/infra/
 or
 reflected in the documentation at http://www.apache.org/dev/git.html. So

 this is a good moment to start considering GIT again.


 We should consider the website as well.  Does the CMS have hooks that
 work with git repositories as well?  Or would we need to keep the
 website in SVN?



 Good point. This has to be clarified as we don't want to keep our
website
 volunteers outside just because the CMS system doesn't support Git. To
let
 everybody of them commit via CLI or GUI tools wouldn't be nice.


 But if it is an issue then one solution could be to move the product
 source to git and keep the websites in SVN.  We're generally not
 dealing with multiple complex branches for the website, so the
 advantages of git here are less.


 Sure, to split the things when it makes sense is also an option.

to be sure I mailed infra@ and got this reply:

 Simply put, no.

All sites *must* remain in SVN. The CMS is actually built around SVN, it’s
operations are SVN operations.

to the question if cms can use git.

rgds
jan i


 Marcus

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



Re: [code] solution for issue 33737 - in-place editing of Input Fields

2013-11-12 Thread Peter Eberlein

Hi Andrea,

try to insert a Tab into a writer texttable cell, you have to use CTRL-TAB.

Regards
Peter
Am 13.11.2013 00:21, schrieb Andrea Pescetti:

On 07/11/2013 Oliver-Rainer Wittmann wrote:

I am working on a solution for issue 33737 [1] and I am making good
progress.
I have started the documentation of the solution in our wiki - please
have a look at https://wiki.openoffice.org/wiki/Writer/Input_Fields


This is a nice usability improvement, thank you for documenting it very
clearly.

My only concern is whether it is better to use TAB to travel to the next
input field and CTRL-TAB to insert a TAB, or just use CTRL-TAB to travel
to the next input field and allow normal insertions of TAB within the
field. Would this convention be used only here or do we have a similar
convention in place to travel, say, between text frames or similar?

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] GIT mirror

2013-11-12 Thread Herbert Duerr

On 12.11.2013 20:08, Andrea Pescetti wrote:

Herbert Duerr wrote:

On 12.11.2013 16:48, janI wrote:

@herbert, if nobody objects will you reopen the ticket, or should I ?

I have reopened the JIRA issue and requested a read-only mirror for now.


And what would be the advantage for real contributors in having a
read-only GIT mirror? The complaints I've seen so far are mostly in the
other direction (i.e., committing or applying patches). I'm not talking
about generic advantages of GIT: everybody here can be assumed to have a
good working knowledge of both SVN and GIT. What concrete problems does
a read-only GIT mirror solve in our case?


A git mirror is needed as a first step also when we do the full switch. 
The read-only mirror can start immediately without any disruption and we 
can switch to full git at a convenient time.


And there are other goodies too:
- A R/O mirror gives a reference point. As individual git-svn clones of 
the asf-repo are often different because of svn propedit having an 
official git-mirror would be nice.

- It gives time to rewrite our buildbot recipes.
- It gives time to rewrite our repo2bz service.
- It gives time to rewrite the svnlog2info script.
- It gives time to rewrite our building guides.


I'm not at all against it, but I'd just like to make sure that a
read-only GIT mirror brings enough concrete advantages, since many GIT
niceties (local commits, proper attribution, quick application of
patches) are still left out or significantly limited with this approach.


Local branches, local commits, interactive rebasing, etc. are all 
available directly.


When every service we like now has been converted to run with the 
git-mirror we can switch to full git conventiently.



By the way, you can find discussions about GIT everywhere at Apache,
there's even a Github account https://github.com/apache and lots of
suggestions like adopting the newly-released Apache Allura (Incubating)
GIT (and more) hosting environment. As far as I know, there have been
very significant updates in the GIT support at Apache in the last few
weeks and I hope that this is soon summarized in a blog post at
http://blogs.apache.org/infra/ or reflected in the documentation at
http://www.apache.org/dev/git.html . So this is a good moment to start
considering GIT again.


Absolutely. I'm a big git fan and used it in my daily work since 2005! 
Then I ran git in my CVS checkout, later in the SVN checkout, then the 
git-svn bridge, then the hg-git bridge and finally the git-svn bridge again.


Even when tracking other projects (e.g. to see when boost fixed a 
particular problem) I always look for its git-mirror first. Thats why I 
know how powerful even a read-only git-mirror is.


Herbert


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