Re: [VOTE] Release Lucene/Solr 7.7.3 RC1

[Anshum Gupta]

+1

SUCCESS! [0:55:00.675712]

On Tue, Apr 21, 2020 at 2:36 AM Noble Paul  wrote:

> sorry, the direct command is
>
> python3 -u dev-tools/scripts/smokeTestRelease.py
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.7.3-RC1-rev1a0d2a901dfec93676b0fe8be425101ceb754b85/
>
> On Tue, Apr 21, 2020 at 6:15 PM Noble Paul  wrote:
> >
> > Please vote for release candidate ? for Lucene/Solr 7.7.3
> >
> > The artifacts can be downloaded from:
> >
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.7.3-RC1-rev1a0d2a901dfec93676b0fe8be425101ceb754b85
> >
> > You can run the smoke tester directly with this command:
> >
> > python3 -u dev-tools/scripts/smokeTestRelease.py
> >
> /tmp/releases/7.7.3/lucene-solr-7.7.3-RC1-rev1a0d2a901dfec93676b0fe8be425101ceb754b85
> >
> >
> > Here's my +1
> >
> > SUCCESS! [1:48:02.520060]
> >
> > --
> > -
> > Noble Paul
>
>
>
> --
> -
> Noble Paul
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

-- 
Anshum Gupta

Re: Solr Admin UI Refresh 2020

[Marcus Eagan]

Nothing is ever finished.

Yet I agree with you one hundred percent. I don't like the idea that you
can delete a collection from the UI, but that's just me. I didn't want to
get in to the discussion until I was further along.

Marcus

On Wed, Apr 22, 2020 at 9:50 AM Gus Heck  wrote:

> Re Parity: If we are going to drop a feature from the UI it should be an
> explicit decision to do so. I think until we have either
>
> 1) a decision to drop (expressed in the SIP or Jira)
> 2) a working re-implementation
>
> For each feature the new UI should not be considered finished.
>
>
> On Wed, Apr 22, 2020 at 12:14 PM Marcus Eagan 
> wrote:
>
>> Parity is not necessarily a good thing. Maintaining most of the existing
>> functionality is good. I would recommend some of it is removed because it’s
>> dangerous.
>>
>> My choice to pick up the project I did was because it was the most
>> updated of them all and I can change one variable rather than multiple
>> because the Angular name was the same.
>>
>> Thanks Jan and Houston. I need to try the project out later tonight.
>>
>> I’m happy to contribute to any of them.
>> As for the test, the scaffolds are the first step to adding tests. They
>> can be added relatively quickly but even the scaffolds ensure the
>> components compile, which is step forward for the project where it is
>> today. There are a couple months of work on it. I did not intend for
>> anything to be merged yet, but for code to exist for people to test it out.
>>
>> The Angular project is a pain.  However, I will keep the project up and
>> work to support whatever the community needs.
>>
>> My goal is to get an updated Solr Admin UI Im the project to help
>> developers get started, and improve security. Whichever one the community
>> decides on, I will work with everyone to help get it done.
>>
>> Thank you,
>>
>> Marcus
>>
>>
>> On Wed, Apr 22, 2020 at 08:24 Houston Putman 
>> wrote:
>>
>>> I agree with Jan, I think we need some discussions on alternatives and
>>> the pros/cons of each before we invest in implementing a solution.
>>>
>>> I personally have the most experience with React and don't know much
>>> about other frameworks, but I'd love to understand why Angular or Vue.JS
>>> might be a better option.
>>> (Having an implementation to start with is definitely a plus, and it
>>> doesn't look like there is one for React)
>>>
>>> Yasa looks more complete than savantly-net/solr-admin to me, and
>>> definitely warrants at least a look.
>>>
>>> - Houston
>>>
>>> On Wed, Apr 22, 2020 at 7:27 AM Jan Høydahl 
>>> wrote:
>>>
 I spun up the proposed app for the first time today, clicked around and
 browsed the code.
 It appears to me that the app is far less developed than I thought,
 which agrees well with only 12 commits.
 The collections component only knows how to list collections, the
 «create collection» button is dead etc.
 It will be a HUGE effort to bring this to feature parity with current
 AdminUI.
 I cannot find any substantial tests other than scaffold tests verifying
 that ng components are created ok. Could be because there is not that much
 functionality to really test yet?

 Which makes me question again the perhaps premature decision on using
 this repo as a basis.


 So I did a quick test with the VueJS based YASA app (
 https://github.com/kezhenxu94/yasa) and got up and running in a few
 minutes, with a much more feature complete UI.
 It is also a complete drop-in replacement for the old UI, once
 compiled. Downside is that it is older and needs upgrade and to play well
 with CPF.
 So let’s step back for a while and not make hasty choices too early. I
 worked with VueJS in a project and really like it. Vue is the 2nd coolest
 kid on the block after React
 according to https://2019.stateofjs.com/front-end-frameworks/ and
 Wikipedia just chose it over React for their UI makeover.

 Anyway, if you want to test YASA locally, here is a 3 minutes recipe
 for doing so:

https://gist.github.com/janhoy/0f7cddc0d92f9e53db7522fe93ff7003

 To me, this looks like a much better starting point, and the project
 has 2x the contributors, 3x the commits and a MIT license :-)

 Another reason to spend more time in SIP mode, iterating on what is
 best for the project, what alternatives were considered and why certain
 frameworks were selected/rejected etc etc, before spending much more time
 coding.

 Jan

 > 22. apr. 2020 kl. 11:30 skrev Noble Paul :
 >
 > As I see it all the 12 commits to that project is made by Jeremy
 Branham.
 >
 > Kudos to Jan Høydahl to save Solr from potential lawsuit &
 > embarrassment in the future. Awesome, I guess you are a part time
 > private detective
 >
 > On Wed, Apr 22, 2020 at 7:25 PM Ishan Chattopadhyaya
 >  wrote:
 >>
 >>> The shoulders of the 

Re: Solr Admin UI Refresh 2020

[Gus Heck]

Re Parity: If we are going to drop a feature from the UI it should be an
explicit decision to do so. I think until we have either

1) a decision to drop (expressed in the SIP or Jira)
2) a working re-implementation

For each feature the new UI should not be considered finished.


On Wed, Apr 22, 2020 at 12:14 PM Marcus Eagan  wrote:

> Parity is not necessarily a good thing. Maintaining most of the existing
> functionality is good. I would recommend some of it is removed because it’s
> dangerous.
>
> My choice to pick up the project I did was because it was the most updated
> of them all and I can change one variable rather than multiple because the
> Angular name was the same.
>
> Thanks Jan and Houston. I need to try the project out later tonight.
>
> I’m happy to contribute to any of them.
> As for the test, the scaffolds are the first step to adding tests. They
> can be added relatively quickly but even the scaffolds ensure the
> components compile, which is step forward for the project where it is
> today. There are a couple months of work on it. I did not intend for
> anything to be merged yet, but for code to exist for people to test it out.
>
> The Angular project is a pain.  However, I will keep the project up and
> work to support whatever the community needs.
>
> My goal is to get an updated Solr Admin UI Im the project to help
> developers get started, and improve security. Whichever one the community
> decides on, I will work with everyone to help get it done.
>
> Thank you,
>
> Marcus
>
>
> On Wed, Apr 22, 2020 at 08:24 Houston Putman 
> wrote:
>
>> I agree with Jan, I think we need some discussions on alternatives and
>> the pros/cons of each before we invest in implementing a solution.
>>
>> I personally have the most experience with React and don't know much
>> about other frameworks, but I'd love to understand why Angular or Vue.JS
>> might be a better option.
>> (Having an implementation to start with is definitely a plus, and it
>> doesn't look like there is one for React)
>>
>> Yasa looks more complete than savantly-net/solr-admin to me, and
>> definitely warrants at least a look.
>>
>> - Houston
>>
>> On Wed, Apr 22, 2020 at 7:27 AM Jan Høydahl 
>> wrote:
>>
>>> I spun up the proposed app for the first time today, clicked around and
>>> browsed the code.
>>> It appears to me that the app is far less developed than I thought,
>>> which agrees well with only 12 commits.
>>> The collections component only knows how to list collections, the
>>> «create collection» button is dead etc.
>>> It will be a HUGE effort to bring this to feature parity with current
>>> AdminUI.
>>> I cannot find any substantial tests other than scaffold tests verifying
>>> that ng components are created ok. Could be because there is not that much
>>> functionality to really test yet?
>>>
>>> Which makes me question again the perhaps premature decision on using
>>> this repo as a basis.
>>>
>>>
>>> So I did a quick test with the VueJS based YASA app (
>>> https://github.com/kezhenxu94/yasa) and got up and running in a few
>>> minutes, with a much more feature complete UI.
>>> It is also a complete drop-in replacement for the old UI, once compiled.
>>> Downside is that it is older and needs upgrade and to play well with CPF.
>>> So let’s step back for a while and not make hasty choices too early. I
>>> worked with VueJS in a project and really like it. Vue is the 2nd coolest
>>> kid on the block after React
>>> according to https://2019.stateofjs.com/front-end-frameworks/ and
>>> Wikipedia just chose it over React for their UI makeover.
>>>
>>> Anyway, if you want to test YASA locally, here is a 3 minutes recipe for
>>> doing so:
>>>
>>>https://gist.github.com/janhoy/0f7cddc0d92f9e53db7522fe93ff7003
>>>
>>> To me, this looks like a much better starting point, and the project has
>>> 2x the contributors, 3x the commits and a MIT license :-)
>>>
>>> Another reason to spend more time in SIP mode, iterating on what is best
>>> for the project, what alternatives were considered and why certain
>>> frameworks were selected/rejected etc etc, before spending much more time
>>> coding.
>>>
>>> Jan
>>>
>>> > 22. apr. 2020 kl. 11:30 skrev Noble Paul :
>>> >
>>> > As I see it all the 12 commits to that project is made by Jeremy
>>> Branham.
>>> >
>>> > Kudos to Jan Høydahl to save Solr from potential lawsuit &
>>> > embarrassment in the future. Awesome, I guess you are a part time
>>> > private detective
>>> >
>>> > On Wed, Apr 22, 2020 at 7:25 PM Ishan Chattopadhyaya
>>> >  wrote:
>>> >>
>>> >>> The shoulders of the homie that put that scaffold together are
>>> broad! Props to him.
>>> >> Marcus, are you working with Jeremy Branham on this?
>>> >>
>>> >> On Wed, 22 Apr, 2020, 2:25 pm Jan Høydahl, 
>>> wrote:
>>> >>>
>>> >>> WRT legal aspect, the original git repo
>>> https://github.com/savantly-net/solr-admin does not say anything about
>>> copyright or license. I encourage you to reach out to the copyright holder
>>> to 

Re: Solr Admin UI Refresh 2020

[Marcus Eagan]

Also, as an aside, if the community decides to go with Vue, let me know. I
like it a lot more and had more experience with it than Angular in its new
carnation. I would be happy to help update YASA. I won't get into all the
UX considerations if it is more feature complete as much as I would update
the code.

Happy to support, looking for input. Singular goal in my mind - replace
current UI for safety of users, especially new ones.

Thanks,

On Wed, Apr 22, 2020 at 9:14 AM Marcus Eagan  wrote:

> Parity is not necessarily a good thing. Maintaining most of the existing
> functionality is good. I would recommend some of it is removed because it’s
> dangerous.
>
> My choice to pick up the project I did was because it was the most updated
> of them all and I can change one variable rather than multiple because the
> Angular name was the same.
>
> Thanks Jan and Houston. I need to try the project out later tonight.
>
> I’m happy to contribute to any of them.
> As for the test, the scaffolds are the first step to adding tests. They
> can be added relatively quickly but even the scaffolds ensure the
> components compile, which is step forward for the project where it is
> today. There are a couple months of work on it. I did not intend for
> anything to be merged yet, but for code to exist for people to test it out.
>
> The Angular project is a pain.  However, I will keep the project up and
> work to support whatever the community needs.
>
> My goal is to get an updated Solr Admin UI Im the project to help
> developers get started, and improve security. Whichever one the community
> decides on, I will work with everyone to help get it done.
>
> Thank you,
>
> Marcus
>
>
> On Wed, Apr 22, 2020 at 08:24 Houston Putman 
> wrote:
>
>> I agree with Jan, I think we need some discussions on alternatives and
>> the pros/cons of each before we invest in implementing a solution.
>>
>> I personally have the most experience with React and don't know much
>> about other frameworks, but I'd love to understand why Angular or Vue.JS
>> might be a better option.
>> (Having an implementation to start with is definitely a plus, and it
>> doesn't look like there is one for React)
>>
>> Yasa looks more complete than savantly-net/solr-admin to me, and
>> definitely warrants at least a look.
>>
>> - Houston
>>
>> On Wed, Apr 22, 2020 at 7:27 AM Jan Høydahl 
>> wrote:
>>
>>> I spun up the proposed app for the first time today, clicked around and
>>> browsed the code.
>>> It appears to me that the app is far less developed than I thought,
>>> which agrees well with only 12 commits.
>>> The collections component only knows how to list collections, the
>>> «create collection» button is dead etc.
>>> It will be a HUGE effort to bring this to feature parity with current
>>> AdminUI.
>>> I cannot find any substantial tests other than scaffold tests verifying
>>> that ng components are created ok. Could be because there is not that much
>>> functionality to really test yet?
>>>
>>> Which makes me question again the perhaps premature decision on using
>>> this repo as a basis.
>>>
>>>
>>> So I did a quick test with the VueJS based YASA app (
>>> https://github.com/kezhenxu94/yasa) and got up and running in a few
>>> minutes, with a much more feature complete UI.
>>> It is also a complete drop-in replacement for the old UI, once compiled.
>>> Downside is that it is older and needs upgrade and to play well with CPF.
>>> So let’s step back for a while and not make hasty choices too early. I
>>> worked with VueJS in a project and really like it. Vue is the 2nd coolest
>>> kid on the block after React
>>> according to https://2019.stateofjs.com/front-end-frameworks/ and
>>> Wikipedia just chose it over React for their UI makeover.
>>>
>>> Anyway, if you want to test YASA locally, here is a 3 minutes recipe for
>>> doing so:
>>>
>>>https://gist.github.com/janhoy/0f7cddc0d92f9e53db7522fe93ff7003
>>>
>>> To me, this looks like a much better starting point, and the project has
>>> 2x the contributors, 3x the commits and a MIT license :-)
>>>
>>> Another reason to spend more time in SIP mode, iterating on what is best
>>> for the project, what alternatives were considered and why certain
>>> frameworks were selected/rejected etc etc, before spending much more time
>>> coding.
>>>
>>> Jan
>>>
>>> > 22. apr. 2020 kl. 11:30 skrev Noble Paul :
>>> >
>>> > As I see it all the 12 commits to that project is made by Jeremy
>>> Branham.
>>> >
>>> > Kudos to Jan Høydahl to save Solr from potential lawsuit &
>>> > embarrassment in the future. Awesome, I guess you are a part time
>>> > private detective
>>> >
>>> > On Wed, Apr 22, 2020 at 7:25 PM Ishan Chattopadhyaya
>>> >  wrote:
>>> >>
>>> >>> The shoulders of the homie that put that scaffold together are
>>> broad! Props to him.
>>> >> Marcus, are you working with Jeremy Branham on this?
>>> >>
>>> >> On Wed, 22 Apr, 2020, 2:25 pm Jan Høydahl, 
>>> wrote:
>>> >>>
>>> >>> WRT legal aspect, the original git 

Re: Solr Admin UI Refresh 2020

[Marcus Eagan]

Parity is not necessarily a good thing. Maintaining most of the existing
functionality is good. I would recommend some of it is removed because it’s
dangerous.

My choice to pick up the project I did was because it was the most updated
of them all and I can change one variable rather than multiple because the
Angular name was the same.

Thanks Jan and Houston. I need to try the project out later tonight.

I’m happy to contribute to any of them.
As for the test, the scaffolds are the first step to adding tests. They can
be added relatively quickly but even the scaffolds ensure the components
compile, which is step forward for the project where it is today. There are
a couple months of work on it. I did not intend for anything to be merged
yet, but for code to exist for people to test it out.

The Angular project is a pain.  However, I will keep the project up and
work to support whatever the community needs.

My goal is to get an updated Solr Admin UI Im the project to help
developers get started, and improve security. Whichever one the community
decides on, I will work with everyone to help get it done.

Thank you,

Marcus


On Wed, Apr 22, 2020 at 08:24 Houston Putman 
wrote:

> I agree with Jan, I think we need some discussions on alternatives and the
> pros/cons of each before we invest in implementing a solution.
>
> I personally have the most experience with React and don't know much about
> other frameworks, but I'd love to understand why Angular or Vue.JS might be
> a better option.
> (Having an implementation to start with is definitely a plus, and it
> doesn't look like there is one for React)
>
> Yasa looks more complete than savantly-net/solr-admin to me, and
> definitely warrants at least a look.
>
> - Houston
>
> On Wed, Apr 22, 2020 at 7:27 AM Jan Høydahl  wrote:
>
>> I spun up the proposed app for the first time today, clicked around and
>> browsed the code.
>> It appears to me that the app is far less developed than I thought, which
>> agrees well with only 12 commits.
>> The collections component only knows how to list collections, the «create
>> collection» button is dead etc.
>> It will be a HUGE effort to bring this to feature parity with current
>> AdminUI.
>> I cannot find any substantial tests other than scaffold tests verifying
>> that ng components are created ok. Could be because there is not that much
>> functionality to really test yet?
>>
>> Which makes me question again the perhaps premature decision on using
>> this repo as a basis.
>>
>>
>> So I did a quick test with the VueJS based YASA app (
>> https://github.com/kezhenxu94/yasa) and got up and running in a few
>> minutes, with a much more feature complete UI.
>> It is also a complete drop-in replacement for the old UI, once compiled.
>> Downside is that it is older and needs upgrade and to play well with CPF.
>> So let’s step back for a while and not make hasty choices too early. I
>> worked with VueJS in a project and really like it. Vue is the 2nd coolest
>> kid on the block after React
>> according to https://2019.stateofjs.com/front-end-frameworks/ and
>> Wikipedia just chose it over React for their UI makeover.
>>
>> Anyway, if you want to test YASA locally, here is a 3 minutes recipe for
>> doing so:
>>
>>https://gist.github.com/janhoy/0f7cddc0d92f9e53db7522fe93ff7003
>>
>> To me, this looks like a much better starting point, and the project has
>> 2x the contributors, 3x the commits and a MIT license :-)
>>
>> Another reason to spend more time in SIP mode, iterating on what is best
>> for the project, what alternatives were considered and why certain
>> frameworks were selected/rejected etc etc, before spending much more time
>> coding.
>>
>> Jan
>>
>> > 22. apr. 2020 kl. 11:30 skrev Noble Paul :
>> >
>> > As I see it all the 12 commits to that project is made by Jeremy
>> Branham.
>> >
>> > Kudos to Jan Høydahl to save Solr from potential lawsuit &
>> > embarrassment in the future. Awesome, I guess you are a part time
>> > private detective
>> >
>> > On Wed, Apr 22, 2020 at 7:25 PM Ishan Chattopadhyaya
>> >  wrote:
>> >>
>> >>> The shoulders of the homie that put that scaffold together are broad!
>> Props to him.
>> >> Marcus, are you working with Jeremy Branham on this?
>> >>
>> >> On Wed, 22 Apr, 2020, 2:25 pm Jan Høydahl, 
>> wrote:
>> >>>
>> >>> WRT legal aspect, the original git repo
>> https://github.com/savantly-net/solr-admin does not say anything about
>> copyright or license. I encourage you to reach out to the copyright holder
>> to let them/him know about your intentions and get a temporary OK. They may
>> later need to sign a code grant (SGA) in order for the project to legally
>> integrate the code.
>> >>>
>> >>> Jan
>> >>>
>> >>> 22. apr. 2020 kl. 07:42 skrev Mike Drob :
>> >>>
>> >>> In phase 2, will the admin ui be running in the same jetty container
>> as the solr application?
>> >>>
>> >>> On Mon, Apr 20, 2020 at 4:35 PM Marcus Eagan 
>> wrote:
>> 
>>  SIP here:
>> 

Re: Pylucene patch

[Jeff Breidenbach]

+1

Re: Code overviews

[Jason Gerlowski]

Hi Martin,

If you're looking for an overview of how the code is laid out and
structured, there's not a ton there that I'm aware of. In terms of
particular features, the best resource that comes to mind would be
some of the videos of conference talks from the last several years.
I've gotten some mileage personally out of recordings of from the
"Lucene/Solr Revolution" or "Activate" conferences.  The conference is
hosted by Lucidworks, and their youtube channel has playlists for each
year: https://www.youtube.com/channel/UCPItOdfUk_tjlvqggkY-JsA.
(Disclaimer: I work for Lucidworks.). Again, these are mostly useful
if you're interested in a particular feature that happens to be
covered.  If you're looking for a broader overview, you might be out
of luck.

If you're looking for an overview from more of a user perspective
though, there's plenty of resources available.  The Reference Guide is
available online (https://lucene.apache.org/solr/guide) , and there
are a few different books out there on Solr that, while older, are
still pretty good references for the basics. (Solr in Action being
maybe the most popular).

Hope that helps, and good luck getting started.

Best,

Jason

On Mon, Apr 20, 2020 at 10:15 AM Martin Entwistle
 wrote:
>
> Hello,
>
> I am new to the lucene-solr code base and I am attempting to learn how things 
> work.
>
> Are there any guides/diagrams/documents anywhere to help people get 
> orientated?
>
> Many thanks
>
> Martin Entwistle
> Software Developer
> IBM Security
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number 
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
> - To 
> unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional 
> commands, e-mail: dev-h...@lucene.apache.org

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

Re: Pylucene patch

[Andi Vajda]

 Hi Marc,

On Wed, 22 Apr 2020, Marc Jeurissen wrote:


Hi Andi,

I refer to this problem
https://www.mail-archive.com/pylucene-dev@lucene.apache.org/msg02640.html

You fixed it in JCC’s trunk, but apparently not in the official Pylucene 
release.
This means that every time we install Pylucene, we encounter the same problem 
and have to correct it from a local JCC trunk.

Can this be fixed please?


This bug is fixed and the fix is available in this release candidate:
  https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.3.0-rc1/

For it to become an actual release, it needs 3 PMC votes (mine and 2 more).
The vote, which should go for three days has been open since November 3rd, 
2019 (not an unusual situation on this project).


As of today, according to my mail records, only you and me voted for this 
release. That's even less than the usual low turnout.


We still need two more PMC votes and it helps if pylucene users vote too, 
that way I can nag the PMC for their votes.


All, please vote to release PyLucene 8.3.0-rc1 as PyLucene 8.3.0 !

Andi..



Thank you very much

Met vriendelijke groeten,
Marc Jeurissen

Bibliotheek UAntwerpen
Stadscampus – Ve35.303
Venusstraat 35 – 2000 Antwerpen
marc.jeuris...@uantwerpen.be
T +32 3 265 49 71

Re: Solr Admin UI Refresh 2020

[Houston Putman]

I agree with Jan, I think we need some discussions on alternatives and the
pros/cons of each before we invest in implementing a solution.

I personally have the most experience with React and don't know much about
other frameworks, but I'd love to understand why Angular or Vue.JS might be
a better option.
(Having an implementation to start with is definitely a plus, and it
doesn't look like there is one for React)

Yasa looks more complete than savantly-net/solr-admin to me, and definitely
warrants at least a look.

- Houston

On Wed, Apr 22, 2020 at 7:27 AM Jan Høydahl  wrote:

> I spun up the proposed app for the first time today, clicked around and
> browsed the code.
> It appears to me that the app is far less developed than I thought, which
> agrees well with only 12 commits.
> The collections component only knows how to list collections, the «create
> collection» button is dead etc.
> It will be a HUGE effort to bring this to feature parity with current
> AdminUI.
> I cannot find any substantial tests other than scaffold tests verifying
> that ng components are created ok. Could be because there is not that much
> functionality to really test yet?
>
> Which makes me question again the perhaps premature decision on using this
> repo as a basis.
>
>
> So I did a quick test with the VueJS based YASA app (
> https://github.com/kezhenxu94/yasa) and got up and running in a few
> minutes, with a much more feature complete UI.
> It is also a complete drop-in replacement for the old UI, once compiled.
> Downside is that it is older and needs upgrade and to play well with CPF.
> So let’s step back for a while and not make hasty choices too early. I
> worked with VueJS in a project and really like it. Vue is the 2nd coolest
> kid on the block after React
> according to https://2019.stateofjs.com/front-end-frameworks/ and
> Wikipedia just chose it over React for their UI makeover.
>
> Anyway, if you want to test YASA locally, here is a 3 minutes recipe for
> doing so:
>
>https://gist.github.com/janhoy/0f7cddc0d92f9e53db7522fe93ff7003
>
> To me, this looks like a much better starting point, and the project has
> 2x the contributors, 3x the commits and a MIT license :-)
>
> Another reason to spend more time in SIP mode, iterating on what is best
> for the project, what alternatives were considered and why certain
> frameworks were selected/rejected etc etc, before spending much more time
> coding.
>
> Jan
>
> > 22. apr. 2020 kl. 11:30 skrev Noble Paul :
> >
> > As I see it all the 12 commits to that project is made by Jeremy Branham.
> >
> > Kudos to Jan Høydahl to save Solr from potential lawsuit &
> > embarrassment in the future. Awesome, I guess you are a part time
> > private detective
> >
> > On Wed, Apr 22, 2020 at 7:25 PM Ishan Chattopadhyaya
> >  wrote:
> >>
> >>> The shoulders of the homie that put that scaffold together are broad!
> Props to him.
> >> Marcus, are you working with Jeremy Branham on this?
> >>
> >> On Wed, 22 Apr, 2020, 2:25 pm Jan Høydahl, 
> wrote:
> >>>
> >>> WRT legal aspect, the original git repo
> https://github.com/savantly-net/solr-admin does not say anything about
> copyright or license. I encourage you to reach out to the copyright holder
> to let them/him know about your intentions and get a temporary OK. They may
> later need to sign a code grant (SGA) in order for the project to legally
> integrate the code.
> >>>
> >>> Jan
> >>>
> >>> 22. apr. 2020 kl. 07:42 skrev Mike Drob :
> >>>
> >>> In phase 2, will the admin ui be running in the same jetty container
> as the solr application?
> >>>
> >>> On Mon, Apr 20, 2020 at 4:35 PM Marcus Eagan 
> wrote:
> 
>  SIP here:
> https://cwiki.apache.org/confluence/display/SOLR/Updated+Solr+Admin+UI
> 
>  On Mon, Apr 20, 2020 at 9:32 AM Gus Heck  wrote:
> >
> > If Marcus has ability to edit existing pages, why don't we create
> the empty page for him and sort out access granting issues later. I'd hate
> for this much needed SIP to bog down on a technical issue.
> >
> > -Gus
> >
> > On Mon, Apr 20, 2020 at 7:10 AM Jan Høydahl 
> wrote:
> >>
> >> Please retry. I gave edit access to confluence user id
> ‘marcussorealheis’.
> >>
> >> Jan
> >>
> >> 20. apr. 2020 kl. 01:30 skrev Marcus Eagan :
> >>
> >> I do need help. I am not allowed to create a SIP. Or, I have been
> unable to create a SIP in three previous attempts.
> >>
> >> Marcus
> >>
> >> On Sun, Apr 19, 2020 at 3:45 AM Jan Høydahl 
> wrote:
> >>>
> >>> Thanks. The PR is useful for people to try out the UI. But for
> overall replacement plan I really think we neeed that SIP, do you still
> need help with Confluence?
> >>>
> >>> Jan Høydahl
> >>>
> >>> 19. apr. 2020 kl. 06:30 skrev Marcus Eagan  >:
> >>>
> >>> 
> >>> I hope everybody is enjoying their weekend and is in good health.
> >>>
> >>> Filed a Jira, made a PR:
> 

Re: [VOTE] Release Lucene/Solr 7.7.3 RC1

[Andrzej Białecki]

That previous error must have been a glitch, maybe network error?

Anyway, +1 now:

SUCCESS! [1:18:32.928557]

> On 22 Apr 2020, at 00:43, Michael Sokolov  wrote:
> 
> +1
> 
> SUCCESS! [0:55:50.289256]
> 
> On Tue, Apr 21, 2020 at 2:48 PM Atri Sharma  wrote:
>> 
>> +1
>> 
>> SUCCESS! [0:44:583254]
>> 
>> On Wed, 22 Apr 2020 at 00:16, Gus Heck  wrote:
>>> 
>>> +1 (linux ubuntu 18.04)
>>> 
>>> SUCCESS! [0:43:51.661530]
>>> 
>>> On Tue, Apr 21, 2020 at 12:44 PM Houston Putman  
>>> wrote:
 
 +1
 
 
 SUCCESS! [1:23:37.392736]
 
 I also ran the multi-valued field performance test on 7.7.2 and 7.7.3 
 (rc1) to make sure that the backport of SOLR-14013 was successful. 
 Definitely looks like it was.
 
 
 Indexing test
 
 7.7.2 0m0.558s
 
 7.7.3 0m0.926s
 
 
 Sharded Query test
 
 7.7.2 0m16.932s
 
 7.7.3 0m0.281s
 
 
 Non-Distrib Query JavaBin test
 
 7.7.2 0m16.933s
 
 7.7.3 0m0.099s
 
 
 Non-Distrib Query JSON test
 
 7.7.2 0m0.074s
 
 7.7.3 0m0.056s
 
 
 - Houston
 
 
 On Tue, Apr 21, 2020 at 12:36 PM Nhat Nguyen 
  wrote:
> 
> +1
> 
> SUCCESS! [0:48:12.629243]
> 
> On Tue, Apr 21, 2020 at 12:29 PM Michael McCandless 
>  wrote:
>> 
>> +1
>> 
>> SUCCESS! [0:36:47.309043]
>> 
>> Mike McCandless
>> 
>> http://blog.mikemccandless.com
>> 
>> 
>> On Tue, Apr 21, 2020 at 12:22 PM Kevin Risden  wrote:
>>> 
>>> +1 SUCCESS! [1:38:36.140929]
>>> 
>>> Kevin Risden
>>> 
>>> On Tue, Apr 21, 2020 at 10:09 AM Ignacio Vera  wrote:
 
 No issues here
 
 +1 SUCCESS! [1:20:57.847225]
 
 On Tue, Apr 21, 2020 at 3:33 PM Jan Høydahl  
 wrote:
> 
> SUCCESS! [1:05:02.194590]
> No issues
> 
> +1 (did not additional manual checking than running the smoketester)
> 
> Jan
> 
>> 21. apr. 2020 kl. 12:27 skrev Andrzej Białecki :
>> 
>> Hi,
>> 
>> I’m getting the following error, looks like the checksum doesn’t 
>> match the file:
>> 
>> Test Solr...
>> test basics...
>> check changes HTML...
>> download solr-7.7.3-src.tgz...
>>   56.9 MB in 586.29 sec (0.1 MB/sec)
>>   verify sha512 digest
>> Traceback (most recent call last):
>> File "dev-tools/scripts/smokeTestRelease.py", line 1518, in 
>>   main()
>> File "dev-tools/scripts/smokeTestRelease.py", line 1448, in main
>>   smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir, 
>> c.is_signed, c.local_keys, ' '.join(c.test_args))
>> File "dev-tools/scripts/smokeTestRelease.py", line 1504, in smokeTest
>>   checkSigs('solr', solrPath, version, tmpDir, isSigned, keysFile)
>> File "dev-tools/scripts/smokeTestRelease.py", line 366, in checkSigs
>>   verifyDigests(artifact, urlString, tmpDir)
>> File "dev-tools/scripts/smokeTestRelease.py", line 556, in 
>> verifyDigests
>>   raise RuntimeError('SHA512 digest mismatch for %s: expected %s but 
>> got %s' % (artifact, sha512Expected, sha512Actual))
>> RuntimeError: SHA512 digest mismatch for solr-7.7.3-src.tgz: 
>> expected 
>> 549ab2c35ecfba4610921f0951b3b78595da2bcb6e36da2f2a06828a64a01e656c8d424b4ba8d559b638ab62d871827f004f5f02b8e1eed3b9a0e0cbfd31e8ac
>>  but got 
>> 57a34207b6c742eae42cf5a0a15eb773d545902314c593c6f10794e6854e2c9ea6b252e9761da9ed5e13915882d6eddba87971495ff88c2cb643f523b6aaff77
>> 
>> 
>> 
>>> On 21 Apr 2020, at 11:36, Noble Paul  wrote:
>>> 
>>> sorry, the direct command is
>>> 
>>> python3 -u dev-tools/scripts/smokeTestRelease.py
>>> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.7.3-RC1-rev1a0d2a901dfec93676b0fe8be425101ceb754b85/
>>> 
>>> On Tue, Apr 21, 2020 at 6:15 PM Noble Paul  
>>> wrote:
 
 Please vote for release candidate ? for Lucene/Solr 7.7.3
 
 The artifacts can be downloaded from:
 https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.7.3-RC1-rev1a0d2a901dfec93676b0fe8be425101ceb754b85
 
 You can run the smoke tester directly with this command:
 
 python3 -u dev-tools/scripts/smokeTestRelease.py
 /tmp/releases/7.7.3/lucene-solr-7.7.3-RC1-rev1a0d2a901dfec93676b0fe8be425101ceb754b85
 
 
 Here's my +1
 
 SUCCESS! [1:48:02.520060]
 
 --
 -
 Noble Paul
>>> 
>>> 
>>> 

Re: Solr Admin UI Refresh 2020

[Jan Høydahl]

I spun up the proposed app for the first time today, clicked around and browsed 
the code.
It appears to me that the app is far less developed than I thought, which 
agrees well with only 12 commits.
The collections component only knows how to list collections, the «create 
collection» button is dead etc.
It will be a HUGE effort to bring this to feature parity with current AdminUI.
I cannot find any substantial tests other than scaffold tests verifying that ng 
components are created ok. Could be because there is not that much 
functionality to really test yet?

Which makes me question again the perhaps premature decision on using this repo 
as a basis.


So I did a quick test with the VueJS based YASA app 
(https://github.com/kezhenxu94/yasa) and got up and running in a few minutes, 
with a much more feature complete UI.
It is also a complete drop-in replacement for the old UI, once compiled. 
Downside is that it is older and needs upgrade and to play well with CPF.
So let’s step back for a while and not make hasty choices too early. I worked 
with VueJS in a project and really like it. Vue is the 2nd coolest kid on the 
block after React
according to https://2019.stateofjs.com/front-end-frameworks/ and Wikipedia 
just chose it over React for their UI makeover.

Anyway, if you want to test YASA locally, here is a 3 minutes recipe for doing 
so:

   https://gist.github.com/janhoy/0f7cddc0d92f9e53db7522fe93ff7003

To me, this looks like a much better starting point, and the project has 2x the 
contributors, 3x the commits and a MIT license :-)

Another reason to spend more time in SIP mode, iterating on what is best for 
the project, what alternatives were considered and why certain frameworks were 
selected/rejected etc etc, before spending much more time coding.

Jan

> 22. apr. 2020 kl. 11:30 skrev Noble Paul :
> 
> As I see it all the 12 commits to that project is made by Jeremy Branham.
> 
> Kudos to Jan Høydahl to save Solr from potential lawsuit &
> embarrassment in the future. Awesome, I guess you are a part time
> private detective
> 
> On Wed, Apr 22, 2020 at 7:25 PM Ishan Chattopadhyaya
>  wrote:
>> 
>>> The shoulders of the homie that put that scaffold together are broad! Props 
>>> to him.
>> Marcus, are you working with Jeremy Branham on this?
>> 
>> On Wed, 22 Apr, 2020, 2:25 pm Jan Høydahl,  wrote:
>>> 
>>> WRT legal aspect, the original git repo 
>>> https://github.com/savantly-net/solr-admin does not say anything about 
>>> copyright or license. I encourage you to reach out to the copyright holder 
>>> to let them/him know about your intentions and get a temporary OK. They may 
>>> later need to sign a code grant (SGA) in order for the project to legally 
>>> integrate the code.
>>> 
>>> Jan
>>> 
>>> 22. apr. 2020 kl. 07:42 skrev Mike Drob :
>>> 
>>> In phase 2, will the admin ui be running in the same jetty container as the 
>>> solr application?
>>> 
>>> On Mon, Apr 20, 2020 at 4:35 PM Marcus Eagan  wrote:
 
 SIP here: 
 https://cwiki.apache.org/confluence/display/SOLR/Updated+Solr+Admin+UI
 
 On Mon, Apr 20, 2020 at 9:32 AM Gus Heck  wrote:
> 
> If Marcus has ability to edit existing pages, why don't we create the 
> empty page for him and sort out access granting issues later. I'd hate 
> for this much needed SIP to bog down on a technical issue.
> 
> -Gus
> 
> On Mon, Apr 20, 2020 at 7:10 AM Jan Høydahl  wrote:
>> 
>> Please retry. I gave edit access to confluence user id 
>> ‘marcussorealheis’.
>> 
>> Jan
>> 
>> 20. apr. 2020 kl. 01:30 skrev Marcus Eagan :
>> 
>> I do need help. I am not allowed to create a SIP. Or, I have been unable 
>> to create a SIP in three previous attempts.
>> 
>> Marcus
>> 
>> On Sun, Apr 19, 2020 at 3:45 AM Jan Høydahl  
>> wrote:
>>> 
>>> Thanks. The PR is useful for people to try out the UI. But for overall 
>>> replacement plan I really think we neeed that SIP, do you still need 
>>> help with Confluence?
>>> 
>>> Jan Høydahl
>>> 
>>> 19. apr. 2020 kl. 06:30 skrev Marcus Eagan :
>>> 
>>> 
>>> I hope everybody is enjoying their weekend and is in good health.
>>> 
>>> Filed a Jira, made a PR: 
>>> https://issues.apache.org/jira/browse/SOLR-14414
>>> 
>>> Still, quite a bit more work to do. I need to spend some time on the 
>>> query screen, improving the cluster view, and adding alias, and more 
>>> tests. The last three should be pretty easy. Would probably spend a 
>>> couple weeks working on style as well, but that can be an ongoing 
>>> effort, just as making it package manager compatible and using v2 
>>> commands. There are also many areas where the Use of TypeScript or the 
>>> Angular framework will improve. That will come with time, some 
>>> involvement from a few Angular wizards, and a bit of research.
>>> 
>>> Thank you everyone,

Re: Solr Admin UI Refresh 2020

[Ishan Chattopadhyaya]

> Kudos to Jan Høydahl to save Solr from potential lawsuit &
> embarrassment in the future.
Haha, I don't think there'll be any lawsuit or embarrassment. Jeremy
Branham has shared this on SOLR-12276. He might be willing to work on
this.


On Wed, Apr 22, 2020 at 3:01 PM Noble Paul  wrote:
>
> As I see it all the 12 commits to that project is made by Jeremy Branham.
>
> Kudos to Jan Høydahl to save Solr from potential lawsuit &
> embarrassment in the future. Awesome, I guess you are a part time
> private detective
>
> On Wed, Apr 22, 2020 at 7:25 PM Ishan Chattopadhyaya
>  wrote:
> >
> > > The shoulders of the homie that put that scaffold together are broad! 
> > > Props to him.
> > Marcus, are you working with Jeremy Branham on this?
> >
> > On Wed, 22 Apr, 2020, 2:25 pm Jan Høydahl,  wrote:
> >>
> >> WRT legal aspect, the original git repo 
> >> https://github.com/savantly-net/solr-admin does not say anything about 
> >> copyright or license. I encourage you to reach out to the copyright holder 
> >> to let them/him know about your intentions and get a temporary OK. They 
> >> may later need to sign a code grant (SGA) in order for the project to 
> >> legally integrate the code.
> >>
> >> Jan
> >>
> >> 22. apr. 2020 kl. 07:42 skrev Mike Drob :
> >>
> >> In phase 2, will the admin ui be running in the same jetty container as 
> >> the solr application?
> >>
> >> On Mon, Apr 20, 2020 at 4:35 PM Marcus Eagan  wrote:
> >>>
> >>> SIP here: 
> >>> https://cwiki.apache.org/confluence/display/SOLR/Updated+Solr+Admin+UI
> >>>
> >>> On Mon, Apr 20, 2020 at 9:32 AM Gus Heck  wrote:
> 
>  If Marcus has ability to edit existing pages, why don't we create the 
>  empty page for him and sort out access granting issues later. I'd hate 
>  for this much needed SIP to bog down on a technical issue.
> 
>  -Gus
> 
>  On Mon, Apr 20, 2020 at 7:10 AM Jan Høydahl  
>  wrote:
> >
> > Please retry. I gave edit access to confluence user id 
> > ‘marcussorealheis’.
> >
> > Jan
> >
> > 20. apr. 2020 kl. 01:30 skrev Marcus Eagan :
> >
> > I do need help. I am not allowed to create a SIP. Or, I have been 
> > unable to create a SIP in three previous attempts.
> >
> > Marcus
> >
> > On Sun, Apr 19, 2020 at 3:45 AM Jan Høydahl  
> > wrote:
> >>
> >> Thanks. The PR is useful for people to try out the UI. But for overall 
> >> replacement plan I really think we neeed that SIP, do you still need 
> >> help with Confluence?
> >>
> >> Jan Høydahl
> >>
> >> 19. apr. 2020 kl. 06:30 skrev Marcus Eagan :
> >>
> >> 
> >> I hope everybody is enjoying their weekend and is in good health.
> >>
> >> Filed a Jira, made a PR: 
> >> https://issues.apache.org/jira/browse/SOLR-14414
> >>
> >> Still, quite a bit more work to do. I need to spend some time on the 
> >> query screen, improving the cluster view, and adding alias, and more 
> >> tests. The last three should be pretty easy. Would probably spend a 
> >> couple weeks working on style as well, but that can be an ongoing 
> >> effort, just as making it package manager compatible and using v2 
> >> commands. There are also many areas where the Use of TypeScript or the 
> >> Angular framework will improve. That will come with time, some 
> >> involvement from a few Angular wizards, and a bit of research.
> >>
> >> Thank you everyone,
> >>
> >> Marcus
> >>
> >> On Tue, Apr 14, 2020 at 2:01 PM Marcus Eagan  
> >> wrote:
> >>>
> >>>
> >>> Gus, At first it looked like it let me, but today it seemed that it 
> >>> did not allow me to create a SIP.
> >>>
> >>>
> >>>
> >>> On Tue, Apr 14, 2020 at 8:57 AM Gus Heck  wrote:
> >
> > First, sorry you’re having problems with Confluence. I suspect the 
> > issue is permissions. There are only two groups allowed to add 
> > pages to the SOLR space, “lucene” and “lucene-pmc”. I believe these 
> > correspond to ASF LDAP groups, which would mean they include 
> > committers and PMC members only. We can grant you individual 
> > permission to add/edit pages, however; we’ve done this for a 
> > handful of others. I could do this for you, just ping me off-thread 
> > so I can confirm your username.
> 
> 
>  If  that is the issue, then we should advertise clearly on the SIP 
>  page that non-committers wishing to create a SIP should request 
>  access on this list. That's probably a good mechanic because it 
>  ensures that contact with this list is established first. And it 
>  sounds like confluence is allowing him to start editing and then 
>  throwing away all his work on submission which is VERY bad 
>  behavior... Possibly an INFRA ticket if that is indeed the case...
> 
> 

Re: Solr Admin UI Refresh 2020

[Noble Paul]

As I see it all the 12 commits to that project is made by Jeremy Branham.

Kudos to Jan Høydahl to save Solr from potential lawsuit &
embarrassment in the future. Awesome, I guess you are a part time
private detective

On Wed, Apr 22, 2020 at 7:25 PM Ishan Chattopadhyaya
 wrote:
>
> > The shoulders of the homie that put that scaffold together are broad! Props 
> > to him.
> Marcus, are you working with Jeremy Branham on this?
>
> On Wed, 22 Apr, 2020, 2:25 pm Jan Høydahl,  wrote:
>>
>> WRT legal aspect, the original git repo 
>> https://github.com/savantly-net/solr-admin does not say anything about 
>> copyright or license. I encourage you to reach out to the copyright holder 
>> to let them/him know about your intentions and get a temporary OK. They may 
>> later need to sign a code grant (SGA) in order for the project to legally 
>> integrate the code.
>>
>> Jan
>>
>> 22. apr. 2020 kl. 07:42 skrev Mike Drob :
>>
>> In phase 2, will the admin ui be running in the same jetty container as the 
>> solr application?
>>
>> On Mon, Apr 20, 2020 at 4:35 PM Marcus Eagan  wrote:
>>>
>>> SIP here: 
>>> https://cwiki.apache.org/confluence/display/SOLR/Updated+Solr+Admin+UI
>>>
>>> On Mon, Apr 20, 2020 at 9:32 AM Gus Heck  wrote:

 If Marcus has ability to edit existing pages, why don't we create the 
 empty page for him and sort out access granting issues later. I'd hate for 
 this much needed SIP to bog down on a technical issue.

 -Gus

 On Mon, Apr 20, 2020 at 7:10 AM Jan Høydahl  wrote:
>
> Please retry. I gave edit access to confluence user id ‘marcussorealheis’.
>
> Jan
>
> 20. apr. 2020 kl. 01:30 skrev Marcus Eagan :
>
> I do need help. I am not allowed to create a SIP. Or, I have been unable 
> to create a SIP in three previous attempts.
>
> Marcus
>
> On Sun, Apr 19, 2020 at 3:45 AM Jan Høydahl  wrote:
>>
>> Thanks. The PR is useful for people to try out the UI. But for overall 
>> replacement plan I really think we neeed that SIP, do you still need 
>> help with Confluence?
>>
>> Jan Høydahl
>>
>> 19. apr. 2020 kl. 06:30 skrev Marcus Eagan :
>>
>> 
>> I hope everybody is enjoying their weekend and is in good health.
>>
>> Filed a Jira, made a PR: https://issues.apache.org/jira/browse/SOLR-14414
>>
>> Still, quite a bit more work to do. I need to spend some time on the 
>> query screen, improving the cluster view, and adding alias, and more 
>> tests. The last three should be pretty easy. Would probably spend a 
>> couple weeks working on style as well, but that can be an ongoing 
>> effort, just as making it package manager compatible and using v2 
>> commands. There are also many areas where the Use of TypeScript or the 
>> Angular framework will improve. That will come with time, some 
>> involvement from a few Angular wizards, and a bit of research.
>>
>> Thank you everyone,
>>
>> Marcus
>>
>> On Tue, Apr 14, 2020 at 2:01 PM Marcus Eagan  
>> wrote:
>>>
>>>
>>> Gus, At first it looked like it let me, but today it seemed that it did 
>>> not allow me to create a SIP.
>>>
>>>
>>>
>>> On Tue, Apr 14, 2020 at 8:57 AM Gus Heck  wrote:
>
> First, sorry you’re having problems with Confluence. I suspect the 
> issue is permissions. There are only two groups allowed to add pages 
> to the SOLR space, “lucene” and “lucene-pmc”. I believe these 
> correspond to ASF LDAP groups, which would mean they include 
> committers and PMC members only. We can grant you individual 
> permission to add/edit pages, however; we’ve done this for a handful 
> of others. I could do this for you, just ping me off-thread so I can 
> confirm your username.


 If  that is the issue, then we should advertise clearly on the SIP 
 page that non-committers wishing to create a SIP should request access 
 on this list. That's probably a good mechanic because it ensures that 
 contact with this list is established first. And it sounds like 
 confluence is allowing him to start editing and then throwing away all 
 his work on submission which is VERY bad behavior... Possibly an INFRA 
 ticket if that is indeed the case...

 @Marcus can you confirm that you tried to create a page, it appeared 
 to let you and then threw out your work on submission? (or am I 
 reading what you wrote wrong?)
>>>
>>>
>>>
>>> --
>>> Marcus Eagan
>>>
>>
>>
>> --
>> Marcus Eagan
>>
>
>
> --
> Marcus Eagan
>
>


 --
 http://www.needhamsoftware.com (work)
 http://www.the111shift.com (play)
>>>
>>>
>>>
>>> --
>>> Marcus Eagan
>>>
>>


-- 

Re: Solr Admin UI Refresh 2020

[Ishan Chattopadhyaya]

> The shoulders of the homie that put that scaffold together are broad!
Props to him.
Marcus, are you working with Jeremy Branham on this?

On Wed, 22 Apr, 2020, 2:25 pm Jan Høydahl,  wrote:

> WRT legal aspect, the original git repo
> https://github.com/savantly-net/solr-admin does not say anything about
> copyright or license. I encourage you to reach out to the copyright holder
> to let them/him know about your intentions and get a temporary OK. They may
> later need to sign a code grant (SGA) in order for the project to legally
> integrate the code.
>
> Jan
>
> 22. apr. 2020 kl. 07:42 skrev Mike Drob :
>
> In phase 2, will the admin ui be running in the same jetty container as
> the solr application?
>
> On Mon, Apr 20, 2020 at 4:35 PM Marcus Eagan 
> wrote:
>
>> SIP here:
>> https://cwiki.apache.org/confluence/display/SOLR/Updated+Solr+Admin+UI
>>
>> On Mon, Apr 20, 2020 at 9:32 AM Gus Heck  wrote:
>>
>>> If Marcus has ability to edit existing pages, why don't we create the
>>> empty page for him and sort out access granting issues later. I'd hate for
>>> this much needed SIP to bog down on a technical issue.
>>>
>>> -Gus
>>>
>>> On Mon, Apr 20, 2020 at 7:10 AM Jan Høydahl 
>>> wrote:
>>>
 Please retry. I gave edit access to confluence user id
 ‘marcussorealheis’.

 Jan

 20. apr. 2020 kl. 01:30 skrev Marcus Eagan :

 I do need help. I am not allowed to create a SIP. Or, I have been
 unable to create a SIP in three previous attempts.

 Marcus

 On Sun, Apr 19, 2020 at 3:45 AM Jan Høydahl 
 wrote:

> Thanks. The PR is useful for people to try out the UI. But for overall
> replacement plan I really think we neeed that SIP, do you still need help
> with Confluence?
>
> Jan Høydahl
>
> 19. apr. 2020 kl. 06:30 skrev Marcus Eagan :
>
> 
> I hope everybody is enjoying their weekend and is in good health.
>
> Filed a Jira, made a PR:
> https://issues.apache.org/jira/browse/SOLR-14414
>
> Still, quite a bit more work to do. I need to spend some time on the
> query screen, improving the cluster view, and adding alias, and more 
> tests.
> The last three should be pretty easy. Would probably spend a couple weeks
> working on style as well, but that can be an ongoing effort, just as 
> making
> it package manager compatible and using v2 commands. There are also many
> areas where the Use of TypeScript or the Angular framework will improve.
> That will come with time, some involvement from a few Angular wizards, and
> a bit of research.
>
> Thank you everyone,
>
> Marcus
>
> On Tue, Apr 14, 2020 at 2:01 PM Marcus Eagan 
> wrote:
>
>>
>> Gus, At first it looked like it let me, but today it seemed that it
>> did not allow me to create a SIP.
>>
>>
>>
>> On Tue, Apr 14, 2020 at 8:57 AM Gus Heck  wrote:
>>
>>> First, sorry you’re having problems with Confluence. I suspect the
 issue is permissions. There are only two groups allowed to add pages 
 to the
 SOLR space, “lucene” and “lucene-pmc”. I believe these correspond to 
 ASF
 LDAP groups, which would mean they include committers and PMC members 
 only.
 We can grant you individual permission to add/edit pages, however; 
 we’ve
 done this for a handful of others. I could do this for you, just ping 
 me
 off-thread so I can confirm your username.

>>>
>>> If  that is the issue, then we should advertise clearly on the SIP
>>> page that non-committers wishing to create a SIP should request access 
>>> on
>>> this list. That's probably a good mechanic because it ensures that 
>>> contact
>>> with this list is established first. And it sounds like confluence is
>>> allowing him to start editing and then throwing away all his work on
>>> submission which is VERY bad behavior... Possibly an INFRA ticket if 
>>> that
>>> is indeed the case...
>>>
>>> @Marcus can you confirm that you tried to create a page, it appeared
>>> to let you and then threw out your work on submission? (or am I reading
>>> what you wrote wrong?)
>>>
>>
>>
>> --
>> Marcus Eagan
>>
>>
>
> --
> Marcus Eagan
>
>

 --
 Marcus Eagan



>>>
>>> --
>>> http://www.needhamsoftware.com (work)
>>> http://www.the111shift.com (play)
>>>
>>
>>
>> --
>> Marcus Eagan
>>
>>
>

Re: Solr Admin UI Refresh 2020

[Jan Høydahl]

WRT legal aspect, the original git repo 
https://github.com/savantly-net/solr-admin does not say anything about 
copyright or license. I encourage you to reach out to the copyright holder to 
let them/him know about your intentions and get a temporary OK. They may later 
need to sign a code grant (SGA) in order for the project to legally integrate 
the code.

Jan

> 22. apr. 2020 kl. 07:42 skrev Mike Drob :
> 
> In phase 2, will the admin ui be running in the same jetty container as the 
> solr application?
> 
> On Mon, Apr 20, 2020 at 4:35 PM Marcus Eagan  > wrote:
> SIP here: 
> https://cwiki.apache.org/confluence/display/SOLR/Updated+Solr+Admin+UI 
> 
> On Mon, Apr 20, 2020 at 9:32 AM Gus Heck  > wrote:
> If Marcus has ability to edit existing pages, why don't we create the empty 
> page for him and sort out access granting issues later. I'd hate for this 
> much needed SIP to bog down on a technical issue.
> 
> -Gus
> 
> On Mon, Apr 20, 2020 at 7:10 AM Jan Høydahl  > wrote:
> Please retry. I gave edit access to confluence user id ‘marcussorealheis’.
> 
> Jan
> 
>> 20. apr. 2020 kl. 01:30 skrev Marcus Eagan > >:
>> 
>> I do need help. I am not allowed to create a SIP. Or, I have been unable to 
>> create a SIP in three previous attempts.
>> 
>> Marcus
>> 
>> On Sun, Apr 19, 2020 at 3:45 AM Jan Høydahl > > wrote:
>> Thanks. The PR is useful for people to try out the UI. But for overall 
>> replacement plan I really think we neeed that SIP, do you still need help 
>> with Confluence?
>> 
>> Jan Høydahl
>> 
>>> 19. apr. 2020 kl. 06:30 skrev Marcus Eagan >> >:
>>> 
>>> 
>>> I hope everybody is enjoying their weekend and is in good health. 
>>> 
>>> Filed a Jira, made a PR: https://issues.apache.org/jira/browse/SOLR-14414 
>>> 
>>> 
>>> Still, quite a bit more work to do. I need to spend some time on the query 
>>> screen, improving the cluster view, and adding alias, and more tests. The 
>>> last three should be pretty easy. Would probably spend a couple weeks 
>>> working on style as well, but that can be an ongoing effort, just as making 
>>> it package manager compatible and using v2 commands. There are also many 
>>> areas where the Use of TypeScript or the Angular framework will improve. 
>>> That will come with time, some involvement from a few Angular wizards, and 
>>> a bit of research.
>>> 
>>> Thank you everyone,
>>> 
>>> Marcus
>>> 
>>> On Tue, Apr 14, 2020 at 2:01 PM Marcus Eagan >> > wrote:
>>> 
>>> Gus, At first it looked like it let me, but today it seemed that it did not 
>>> allow me to create a SIP.
>>> 
>>> 
>>> 
>>> On Tue, Apr 14, 2020 at 8:57 AM Gus Heck >> > wrote:
>>> First, sorry you’re having problems with Confluence. I suspect the issue is 
>>> permissions. There are only two groups allowed to add pages to the SOLR 
>>> space, “lucene” and “lucene-pmc”. I believe these correspond to ASF LDAP 
>>> groups, which would mean they include committers and PMC members only. We 
>>> can grant you individual permission to add/edit pages, however; we’ve done 
>>> this for a handful of others. I could do this for you, just ping me 
>>> off-thread so I can confirm your username.
>>> 
>>> If  that is the issue, then we should advertise clearly on the SIP page 
>>> that non-committers wishing to create a SIP should request access on this 
>>> list. That's probably a good mechanic because it ensures that contact with 
>>> this list is established first. And it sounds like confluence is allowing 
>>> him to start editing and then throwing away all his work on submission 
>>> which is VERY bad behavior... Possibly an INFRA ticket if that is indeed 
>>> the case...
>>> 
>>> @Marcus can you confirm that you tried to create a page, it appeared to let 
>>> you and then threw out your work on submission? (or am I reading what you 
>>> wrote wrong?)
>>> 
>>> 
>>> -- 
>>> Marcus Eagan
>>> 
>>> 
>>> 
>>> -- 
>>> Marcus Eagan
>>> 
>> 
>> 
>> -- 
>> Marcus Eagan
>> 
> 
> 
> 
> -- 
> http://www.needhamsoftware.com  (work)
> http://www.the111shift.com  (play)
> 
> 
> -- 
> Marcus Eagan
>