Re: [Discussion] Switch to Git?

2017-09-18 Thread Damjan Jovanovic 
On Mon, Sep 18, 2017 at 7:44 PM, Herbert Duerr  wrote:

> On 09/17/2017 04:04 PM, Andrea Pescetti wrote:
> > On 14/09/2017 Dave Fisher wrote:
> >> does SVN vs. GIT prevent new developers from volunteering?
> >
> > I think this is the key question, even though there are many good points
> > also in what others replied.
> >
> > We currently have a couple semi-official GIT mirrors: one on Github in
> > the ASF organization page and the internal one Herbert pointed out. I
> > also remember that Herbert once presented a big GIT repository he had
> > built with all the available history of the OpenOffice code, but I don't
> > know if it is available somewhere.
>
> I had that 2GB blob on my Apache homepage for a couple of years. When
> that home was migrated to the newer locations it was apparently dropped.
> Unless someone mirrored the blob it is currently not available anymore.
> If anyone is really interested in that ancient history I can probably
> resurrect it unless 2+GB blobs are no longer allowed in committer's home
> directories.
>
>
That would be great. I need the old repository to regression test an old
bug in Base. However, is it legal to have commits from the pre-ASLv2 era?


> > I believe that the interested developers (including me, at times) use
> > the git-svn tool when convenient. I think that this is enough to allow
> > the local workflow improvements Damjan was requesting. Or do you see
> > reasons not to use it?
>
> OpenOffice is only a small part of the Apache subversion repository that
> contains many more projects. Most revisions in that repo are not for OOo
> and git-svn apparently has a hard time with this. It is possible but not
> much fun.
>
>
Excellent insight. Never thought of that. git-svn is almost unusable then.


> > As for the new developers, most new developers are probably familiar
> > with the "pull request" convention. This is not supported by either of
> > the current repositories, mostly due to ASF policy. Last time I checked,
> > Infra was still discussing how we can allow pull requests in a way that
> > complies with the policy and I have no idea whether this is resolved.
> > Once we have official support from Infra and a friendly pull request
> > system, this might indeed improve the approach for new developers.
>
> Agreed. The workflow with pull request is so much nicer than handling
> patches...
>
> Best regards,
> Herbert
>
>
Damjan

Re: [Discussion] Switch to Git?

2017-09-18 Thread Herbert Duerr 
On 09/17/2017 04:04 PM, Andrea Pescetti wrote:
> On 14/09/2017 Dave Fisher wrote:
>> does SVN vs. GIT prevent new developers from volunteering?
> 
> I think this is the key question, even though there are many good points
> also in what others replied.
> 
> We currently have a couple semi-official GIT mirrors: one on Github in
> the ASF organization page and the internal one Herbert pointed out. I
> also remember that Herbert once presented a big GIT repository he had
> built with all the available history of the OpenOffice code, but I don't
> know if it is available somewhere.

I had that 2GB blob on my Apache homepage for a couple of years. When
that home was migrated to the newer locations it was apparently dropped.
Unless someone mirrored the blob it is currently not available anymore.
If anyone is really interested in that ancient history I can probably
resurrect it unless 2+GB blobs are no longer allowed in committer's home
directories.

> I believe that the interested developers (including me, at times) use
> the git-svn tool when convenient. I think that this is enough to allow
> the local workflow improvements Damjan was requesting. Or do you see
> reasons not to use it?

OpenOffice is only a small part of the Apache subversion repository that
contains many more projects. Most revisions in that repo are not for OOo
and git-svn apparently has a hard time with this. It is possible but not
much fun.

> As for the new developers, most new developers are probably familiar
> with the "pull request" convention. This is not supported by either of
> the current repositories, mostly due to ASF policy. Last time I checked,
> Infra was still discussing how we can allow pull requests in a way that
> complies with the policy and I have no idea whether this is resolved.
> Once we have official support from Infra and a friendly pull request
> system, this might indeed improve the approach for new developers.

Agreed. The workflow with pull request is so much nicer than handling
patches...

Best regards,
Herbert

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

Re: OS X High Sierra

2017-09-18 Thread Jim Jagielski 
Although not formally tested, 414-RC2 works fine.

> On Sep 16, 2017, at 8:57 AM, Jerome Fleischman  wrote:
> 
> Hi,
> 
> Will Open Office work on the
> new version of OSX High Sierra.
> 
> Jerry Fleischman
> 
> -
> 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: OS X High Sierra

2017-09-18 Thread Peter kovacs 
The information I have on the new release is that the changes consist of bug 
fixes and a rework of user experience. No fundamental changes are in the 
upcomming release of Max is.

Source of this is a German tech magazine that wrote a summary article for high 
Sierra.

None the less I plan to interview a techie at an Apple store, if there are any 
constraints for older Applications. (Since we build on old release SDK I count 
us in the category.

Possible that we could get an issue with our unsigned package. And I have not 
forgotten about it.


All the best
Peter

Am 17. September 2017 19:07:34 MESZ schrieb Marcus :
>Am 17.09.2017 um 17:57 schrieb Jerome Fleischman:
>> I have been using Microsoft Office forever and just
>> downloaded Open Office.
>> I tested it on a couple of things and it seemed to work on
>> OS Sierra and a Word document and an Excel spreadsheet.
>> 
>> Rumor/word has it that current Microsoft Office apps
>> will not/may not work on the new Mac OS High Sierra.
>> 
>> Microsoft will be charging yearly for their new
>> version so I thought Open Office would be a good
>> alternative.
>> 
>> I guess I will find out soon enough.
>
>OK, when you know it's working on OS Sierra then you already know the 
>little obstacle [1]. As I don't know the changes in OS High Sierra I 
>*assume* it should work as it's just an upgrade from version 10.12 to
>10.13.
>
>[1] 
>https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes#AOO4.1.3ReleaseNotes-KnownIssues
>
>HTH
>
>Marcus
>
>
>
>>> On Sep 17, 2017, at 11:14 AM, Marcus  wrote:
>>>
>>> Am 16.09.2017 um 14:57 schrieb Jerome Fleischman:
>>>
 Will Open Office work on the
 new version of OSX High Sierra.
>>>
>>> I'm not a Mac user, so I cannot provide any experiences.
>>>
>>> Have you used OpenOffice with the previous macOS version? If so, I
>would think that there is no difference.
>>>
>>> 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: [Discussion] Switch to Git?

2017-09-18 Thread Damjan Jovanovic 
Yes, git-svn lacks quite a few features and can be problematic.

Besides, 1 VCS and 1 way of doing things (ie. Git only everywhere) is
always easier to manage than SVN here, a read-only delayed (possibly by
months, when it breaks) Git copy on GitHub, and possibly git-svn on the
users' end.

On Mon, Sep 18, 2017 at 9:25 AM, Peter kovacs  wrote:

> I failed using git svn clone ...
> Git is doing some history scans that cause to run for forever. I have not
> found any way to circumvent that scan.
>
> I have forked the apache repo on github and then pulled from there. That's
> an easier workflow for me.
> What I miss is a push functionallity. But that's for me only convenience.
> I can work with git and svn. No issue for me.
>
> So I am quite neutral on the topic.
>
> All the best
> Peter
>
> Am 17. September 2017 20:12:13 MESZ schrieb Andrea Pescetti <
> pesce...@apache.org>:
> >Patricia Shanahan wrote:
> >> The big new developer issue may be lack of Subversion experience. Git
> >> seems to be the repository-of-the-decade.
> >
> >This can be circumvented by using git as follows:
> >
> >$ git svn clone
> >https://svn.apache.org/repos/asf/openoffice/branches/AOO414
> >
> >and similar. I would honestly use one of the two mirrors I mentioned
> >earlier, but we could include a section describing these methods to get
> >
> >the code without using a dedicated Subversion client.
> >
> >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: [Discussion] Switch to Git?

2017-09-18 Thread Peter kovacs 
I failed using git svn clone ...
Git is doing some history scans that cause to run for forever. I have not found 
any way to circumvent that scan.

I have forked the apache repo on github and then pulled from there. That's an 
easier workflow for me.
What I miss is a push functionallity. But that's for me only convenience. I can 
work with git and svn. No issue for me.

So I am quite neutral on the topic.

All the best 
Peter

Am 17. September 2017 20:12:13 MESZ schrieb Andrea Pescetti 
:
>Patricia Shanahan wrote:
>> The big new developer issue may be lack of Subversion experience. Git
>> seems to be the repository-of-the-decade.
>
>This can be circumvented by using git as follows:
>
>$ git svn clone
>https://svn.apache.org/repos/asf/openoffice/branches/AOO414
>
>and similar. I would honestly use one of the two mirrors I mentioned 
>earlier, but we could include a section describing these methods to get
>
>the code without using a dedicated Subversion client.
>
>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