Re: Migrate to Git?

[Aliaksandr Autayeu]

P.S. On convenience. Cloning into single directory and setting up single
project makes it works just as well. Decent IDEs handle this easily.

On tracking history. The need to track history of experimental code
obfuscates its poor documentation. If the code if properly documented
(including documenting design decisions), there is no need to search
history. Moreover, if experimental code changed approach or algorithm
radically (with reasons that should be documented), the history might
confuse more than clarify.

Modulo tracking history, multiple modular repos are more flexible than one
jumbo repo.


On 19 August 2016 at 18:01, Aliaksandr Autayeu 
wrote:

> Separating site and code is not enough. Different code requires different
> levels of maintenance, that's why it's better to separate sandbox and
> add-ons from trunk too. Sandbox might become outdated or might not compile.
> It might have a different test or code coverage criteria. It might allow
> warnings on compilation. Such things tends to spread from
> unstable\experimental code to cleaner and more stable places. For example,
> 1 warning stands out and therefore is more likely to be fixed. 5 warnings
> from sandbox might easily cloud 6th one from trunk.
>
> On 19 August 2016 at 16:21, Richard Eckart de Castilho <
> richard.eck...@gmail.com> wrote:
>
>> Keeping site and code in separate repos: +1
>>
>> -- Richard
>>
>> > On 19.08.2016, at 15:17, Anthony Beylerian 
>> wrote:
>> >
>> > @Jörn @Richard
>> >
>> > I believe less bloat is always better for code housekeeping.
>> > For example, although it is small, I think having the site code along
>> with
>> > the toolkit code just seems a bit untidy.
>> >
>> > How about we at least separate those two?
>> > It could also be useful to make a more feature rich site in the future.
>> >
>> > Actually, the Spark team does that too:
>> >
>> > git://git.apache.org/spark.git
>> > git://git.apache.org/spark-website.git
>>
>>
>

Re: Migrate to Git?

[Richard Eckart de Castilho]

Keeping site and code in separate repos: +1

-- Richard

> On 19.08.2016, at 15:17, Anthony Beylerian  
> wrote:
> 
> @Jörn @Richard
> 
> I believe less bloat is always better for code housekeeping.
> For example, although it is small, I think having the site code along with
> the toolkit code just seems a bit untidy.
> 
> How about we at least separate those two?
> It could also be useful to make a more feature rich site in the future.
> 
> Actually, the Spark team does that too:
> 
> git://git.apache.org/spark.git
> git://git.apache.org/spark-website.git

Re: Migrate to Git?

[Anthony Beylerian]

@Jörn @Richard

I believe less bloat is always better for code housekeeping.
For example, although it is small, I think having the site code along with
the toolkit code just seems a bit untidy.

How about we at least separate those two?
It could also be useful to make a more feature rich site in the future.

Actually, the Spark team does that too:

git://git.apache.org/spark.git
git://git.apache.org/spark-website.git


@Madhawa

Did you mean to use branches for the sandboxed projects?

Best,

Anthony

On Fri, Aug 19, 2016 at 7:38 PM, Madhawa Kasun Gunasekara <
madhaw...@gmail.com> wrote:

> we can use branches instead of repositories.
>
> Thanks,
> Madhawa
>
> Madhawa
>
> On Fri, Aug 19, 2016 at 1:54 PM, Joern Kottmann 
> wrote:
>
> > Yes, it would be nice to get the next release out with sentiment
> analysis!
> > It is time for the next release anyway.
> >
> > Jörn
> >
> > On Thu, Aug 18, 2016 at 4:33 PM, Chris Mattmann 
> > wrote:
> >
> > > Fantastic, Joern! I have some SentimentAnalysis stuff to hopefully
> commit
> > > and
> > > get refactored. Hopefully after that’s done we can ship a release soon
> > and
> > > publish to Central.
> > >
> > >
> > >
> > > On 8/18/16, 5:50 AM, "Joern Kottmann"  wrote:
> > >
> > > We made some progress here, the repository is now switched to git.
> > >
> > > Please have a look here:
> > > https://issues.apache.org/jira/browse/INFRA-12209
> > >
> > > And there are couple of things we have to do now:
> > > https://issues.apache.org/jira/browse/OPENNLP-860
> > >
> > > The new repository currently only contains the trunk and not the
> > other
> > > stuff like addons, site and sandbox,
> > > I already commented on the infra issue, we might want to change the
> > > layout
> > > of our repository a bit.
> > > Any thoughts on it?
> > >
> > > The old layout is:
> > > addons
> > > trunk
> > > sandbox
> > > site
> > >
> > > BR,
> > > Jörn
> > >
> > > On Tue, Jul 5, 2016 at 3:11 AM, Mattmann, Chris A (3980) <
> > > chris.a.mattm...@jpl.nasa.gov> wrote:
> > >
> > > > Hi Jörn,
> > > >
> > > > #3 is a mirror on Github of our writeable Git repo from #1. Users
> > > > can submit PRs to it, and then it will flow through to dev list
> in
> > > > the form of an email that links to information that we can use to
> > > > easily merge into our writeable ASF repo. Once merged, it will
> sync
> > > > out to Github and close the PR.
> > > >
> > > > HTH!
> > > >
> > > > Cheers,
> > > > Chris
> > > >
> > > > 
> ++
> > > > Chris Mattmann, Ph.D.
> > > > Chief Architect
> > > > Instrument Software and Science Data Systems Section (398)
> > > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > > > Office: 168-519, Mailstop: 168-527
> > > > Email: chris.a.mattm...@nasa.gov
> > > > WWW:  http://sunset.usc.edu/~mattmann/
> > > > 
> ++
> > > > Director, Information Retrieval and Data Science Group (IRDS)
> > > > Adjunct Associate Professor, Computer Science Department
> > > > University of Southern California, Los Angeles, CA 90089 USA
> > > > WWW: http://irds.usc.edu/
> > > > 
> ++
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On 7/4/16, 1:23 PM, "Joern Kottmann"  wrote:
> > > >
> > > > >Can you explain 3, is that a writable mirror at Github?
> > > > >
> > > > >Jörn
> > > > >
> > > > >On Mon, 2016-07-04 at 15:35 +, Mattmann, Chris A (3980)
> wrote:
> > > > >> My +1 as well..I would suggest, specifically:
> > > > >>
> > > > >> 1. Use git-wp
> > > > >> 2. Borrow and adapt this guide which suggests how to do it
> > > > >> (i’m happy to adapt)
> > > > >> http://wiki.apache.org/tika/UsingGit
> > > > >> 3. Turn on writeable git wp mirror’ing to apache/opennlp
> > > > >>
> > > > >> Cheers,
> > > > >> Chris
> > > > >>
> > > > >> 
> > > ++
> > > > >> Chris Mattmann, Ph.D.
> > > > >> Chief Architect
> > > > >> Instrument Software and Science Data Systems Section (398)
> > > > >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > > > >> Office: 168-519, Mailstop: 168-527
> > > > >> Email: chris.a.mattm...@nasa.gov
> > > > >> WWW:  http://sunset.usc.edu/~mattmann/
> > > > >> 
> > > ++
> > > > >> Director, Information Retrieval and Data Science Group (IRDS)
> > > > >> Adjunct Associate Professor, Computer Science Department
> > > > >> 

Re: Migrate to Git?

[Madhawa Kasun Gunasekara]

we can use branches instead of repositories.

Thanks,
Madhawa

Madhawa

On Fri, Aug 19, 2016 at 1:54 PM, Joern Kottmann  wrote:

> Yes, it would be nice to get the next release out with sentiment analysis!
> It is time for the next release anyway.
>
> Jörn
>
> On Thu, Aug 18, 2016 at 4:33 PM, Chris Mattmann 
> wrote:
>
> > Fantastic, Joern! I have some SentimentAnalysis stuff to hopefully commit
> > and
> > get refactored. Hopefully after that’s done we can ship a release soon
> and
> > publish to Central.
> >
> >
> >
> > On 8/18/16, 5:50 AM, "Joern Kottmann"  wrote:
> >
> > We made some progress here, the repository is now switched to git.
> >
> > Please have a look here:
> > https://issues.apache.org/jira/browse/INFRA-12209
> >
> > And there are couple of things we have to do now:
> > https://issues.apache.org/jira/browse/OPENNLP-860
> >
> > The new repository currently only contains the trunk and not the
> other
> > stuff like addons, site and sandbox,
> > I already commented on the infra issue, we might want to change the
> > layout
> > of our repository a bit.
> > Any thoughts on it?
> >
> > The old layout is:
> > addons
> > trunk
> > sandbox
> > site
> >
> > BR,
> > Jörn
> >
> > On Tue, Jul 5, 2016 at 3:11 AM, Mattmann, Chris A (3980) <
> > chris.a.mattm...@jpl.nasa.gov> wrote:
> >
> > > Hi Jörn,
> > >
> > > #3 is a mirror on Github of our writeable Git repo from #1. Users
> > > can submit PRs to it, and then it will flow through to dev list in
> > > the form of an email that links to information that we can use to
> > > easily merge into our writeable ASF repo. Once merged, it will sync
> > > out to Github and close the PR.
> > >
> > > HTH!
> > >
> > > Cheers,
> > > Chris
> > >
> > > ++
> > > Chris Mattmann, Ph.D.
> > > Chief Architect
> > > Instrument Software and Science Data Systems Section (398)
> > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > > Office: 168-519, Mailstop: 168-527
> > > Email: chris.a.mattm...@nasa.gov
> > > WWW:  http://sunset.usc.edu/~mattmann/
> > > ++
> > > Director, Information Retrieval and Data Science Group (IRDS)
> > > Adjunct Associate Professor, Computer Science Department
> > > University of Southern California, Los Angeles, CA 90089 USA
> > > WWW: http://irds.usc.edu/
> > > ++
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 7/4/16, 1:23 PM, "Joern Kottmann"  wrote:
> > >
> > > >Can you explain 3, is that a writable mirror at Github?
> > > >
> > > >Jörn
> > > >
> > > >On Mon, 2016-07-04 at 15:35 +, Mattmann, Chris A (3980) wrote:
> > > >> My +1 as well..I would suggest, specifically:
> > > >>
> > > >> 1. Use git-wp
> > > >> 2. Borrow and adapt this guide which suggests how to do it
> > > >> (i’m happy to adapt)
> > > >> http://wiki.apache.org/tika/UsingGit
> > > >> 3. Turn on writeable git wp mirror’ing to apache/opennlp
> > > >>
> > > >> Cheers,
> > > >> Chris
> > > >>
> > > >> 
> > ++
> > > >> Chris Mattmann, Ph.D.
> > > >> Chief Architect
> > > >> Instrument Software and Science Data Systems Section (398)
> > > >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > > >> Office: 168-519, Mailstop: 168-527
> > > >> Email: chris.a.mattm...@nasa.gov
> > > >> WWW:  http://sunset.usc.edu/~mattmann/
> > > >> 
> > ++
> > > >> Director, Information Retrieval and Data Science Group (IRDS)
> > > >> Adjunct Associate Professor, Computer Science Department
> > > >> University of Southern California, Los Angeles, CA 90089 USA
> > > >> WWW: http://irds.usc.edu/
> > > >> 
> > ++
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> On 7/4/16, 7:36 AM, "Joern Kottmann" 
> wrote:
> > > >>
> > > >> > Hello all,
> > > >> >
> > > >> > do we still want to do this? Has been a while since we
> discussed
> > > >> > it.
> > > >> > I am happy to get it done if we reach consensus on it again.
> > > >> >
> > > >> > My +1 again.
> > > >> >
> > > >> > Jörn
> > > >> >
> > > >> > On Thu, Dec 20, 2012 at 4:40 PM, Tommaso Teofili
> >  > > >> > mail.com>
> > > >> > wrote:
> > > 

Re: Migrate to Git?

[Richard Eckart de Castilho]

I don't have a vote here, but I'd agree with Jörn: Separate repos will make
it more uncomfortable to track changes across components. 

Should the project switch to a uniform versioning and joint releases, that
would also be more problematic.

The project is not particularly large. Having everything in a single
repo is more convenient and traceable.

Cheers,

-- Richard

> On 19.08.2016, at 11:48, Anthony Beylerian  
> wrote:
> 
> +1 for separate repositories.
> 
> Since they will be under the Apache Github Organization, it will also be
> neater to browse them like this:
> 
> https://github.com/apache?query=opennlp
> 
> I recommend we keep the repository names starting with opennlp-
> 
> For example :
> 
> https://github.com/apache?query=hadoop
> 
> What do you think?
> 
> Best,
> 
> Anthony
> 
> 
> On Fri, Aug 19, 2016 at 6:32 PM, Aliaksandr Autayeu 
> wrote:
> 
>>> 
>>> Why do you think it is better?
>>> 
>> In general, separating apples from oranges. In practice, not having to go
>> through irrelevant stuff while reading, searching, refactoring. Less stuff
>> to clone for build automation. Smaller repos to clone in general.
>> 
>> And you still can do all the above by cloning 4 repos into the same
>> directory and setting up a single project in your favorite IDE, emulating
>> current structure. But at least nothing forces you to do that as single
>> repo forces you to.
>> 
>> However, the above might be subjective. In this case commitocracy it is to
>> decide.
>> 

Re: Migrate to Git?

[Anthony Beylerian]

+1 for separate repositories.

Since they will be under the Apache Github Organization, it will also be
neater to browse them like this:

https://github.com/apache?query=opennlp

I recommend we keep the repository names starting with opennlp-

For example :

https://github.com/apache?query=hadoop

What do you think?

Best,

Anthony


On Fri, Aug 19, 2016 at 6:32 PM, Aliaksandr Autayeu 
wrote:

> >
> > Why do you think it is better?
> >
> In general, separating apples from oranges. In practice, not having to go
> through irrelevant stuff while reading, searching, refactoring. Less stuff
> to clone for build automation. Smaller repos to clone in general.
>
> And you still can do all the above by cloning 4 repos into the same
> directory and setting up a single project in your favorite IDE, emulating
> current structure. But at least nothing forces you to do that as single
> repo forces you to.
>
> However, the above might be subjective. In this case commitocracy it is to
> decide.
>

Re: Migrate to Git?

[Joern Kottmann]

I don't see the advantage of having multiple repositories, because that
makes it harder to check it out and move things around without loosing
history (git mv).

Why do you think it is better?

Jörn

On Thu, Aug 18, 2016 at 4:33 PM, Chris Mattmann  wrote:

> Fantastic, Joern! I have some SentimentAnalysis stuff to hopefully commit
> and
> get refactored. Hopefully after that’s done we can ship a release soon and
> publish to Central.
>
>
>
> On 8/18/16, 5:50 AM, "Joern Kottmann"  wrote:
>
> We made some progress here, the repository is now switched to git.
>
> Please have a look here:
> https://issues.apache.org/jira/browse/INFRA-12209
>
> And there are couple of things we have to do now:
> https://issues.apache.org/jira/browse/OPENNLP-860
>
> The new repository currently only contains the trunk and not the other
> stuff like addons, site and sandbox,
> I already commented on the infra issue, we might want to change the
> layout
> of our repository a bit.
> Any thoughts on it?
>
> The old layout is:
> addons
> trunk
> sandbox
> site
>
> BR,
> Jörn
>
> On Tue, Jul 5, 2016 at 3:11 AM, Mattmann, Chris A (3980) <
> chris.a.mattm...@jpl.nasa.gov> wrote:
>
> > Hi Jörn,
> >
> > #3 is a mirror on Github of our writeable Git repo from #1. Users
> > can submit PRs to it, and then it will flow through to dev list in
> > the form of an email that links to information that we can use to
> > easily merge into our writeable ASF repo. Once merged, it will sync
> > out to Github and close the PR.
> >
> > HTH!
> >
> > Cheers,
> > Chris
> >
> > ++
> > Chris Mattmann, Ph.D.
> > Chief Architect
> > Instrument Software and Science Data Systems Section (398)
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 168-519, Mailstop: 168-527
> > Email: chris.a.mattm...@nasa.gov
> > WWW:  http://sunset.usc.edu/~mattmann/
> > ++
> > Director, Information Retrieval and Data Science Group (IRDS)
> > Adjunct Associate Professor, Computer Science Department
> > University of Southern California, Los Angeles, CA 90089 USA
> > WWW: http://irds.usc.edu/
> > ++
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On 7/4/16, 1:23 PM, "Joern Kottmann"  wrote:
> >
> > >Can you explain 3, is that a writable mirror at Github?
> > >
> > >Jörn
> > >
> > >On Mon, 2016-07-04 at 15:35 +, Mattmann, Chris A (3980) wrote:
> > >> My +1 as well..I would suggest, specifically:
> > >>
> > >> 1. Use git-wp
> > >> 2. Borrow and adapt this guide which suggests how to do it
> > >> (i’m happy to adapt)
> > >> http://wiki.apache.org/tika/UsingGit
> > >> 3. Turn on writeable git wp mirror’ing to apache/opennlp
> > >>
> > >> Cheers,
> > >> Chris
> > >>
> > >> 
> ++
> > >> Chris Mattmann, Ph.D.
> > >> Chief Architect
> > >> Instrument Software and Science Data Systems Section (398)
> > >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > >> Office: 168-519, Mailstop: 168-527
> > >> Email: chris.a.mattm...@nasa.gov
> > >> WWW:  http://sunset.usc.edu/~mattmann/
> > >> 
> ++
> > >> Director, Information Retrieval and Data Science Group (IRDS)
> > >> Adjunct Associate Professor, Computer Science Department
> > >> University of Southern California, Los Angeles, CA 90089 USA
> > >> WWW: http://irds.usc.edu/
> > >> 
> ++
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On 7/4/16, 7:36 AM, "Joern Kottmann"  wrote:
> > >>
> > >> > Hello all,
> > >> >
> > >> > do we still want to do this? Has been a while since we discussed
> > >> > it.
> > >> > I am happy to get it done if we reach consensus on it again.
> > >> >
> > >> > My +1 again.
> > >> >
> > >> > Jörn
> > >> >
> > >> > On Thu, Dec 20, 2012 at 4:40 PM, Tommaso Teofili
>  > >> > mail.com>
> > >> > wrote:
> > >> >
> > >> > > in my opinion that would be good, +1
> > >> > > Tommaso
> > >> > >
> > >> > >
> > >> > > 2012/12/19 Jörn Kottmann 
> > >> > >
> > >> > > > Hi all,
> > >> > > >
> > >> > > > I heard at ApacheCon Europe that it should be possible to
> > >> > > > migrate from
> > >> > > > Subverion