[
https://issues.apache.org/jira/browse/SOLR-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703079#comment-17703079
]
Marcus Eagan edited comment on SOLR-16465 at 3/21/23 7:59 AM:
--------------------------------------------------------------
Hi everyone, long time no Jira rant. I am looking to exercise my brain to stay
sharp as I battle other challenges. I didn't know if I can think of a better
exercise. I am certainly rusty on Javascript and CSS. It's like riding a
bike... that adds a new wheel, every other fortnight.
Here's what I can commit to in my nights and weekends, but for different
reasons than the last time I tried the full re-write. I was a bit naïve:
I'll build login functionality using React and some bundler that will set up a
pretty solid foundation for migrating more functionality.
On the bright side, I know a bit about the login functionality thanks to a few
committers that helped me a bit back in the day. Happy to throw my hat in to
support this important yet challenging aspect of maintaining the project. I
think I've have time to help with the latter stages of the migration, but my
ultimate goal would be to get more people to learn about the project. If I
cannot find people on the internet to help us out, I'd be happy to talk with
folks about sponsoring a talented student looking for a project.
You can expect a PR tomorrow night to kick of the discussion that will likely
happen here. [~janhoy] and [~epugh] Let me know if that sounds good and if I
should invest time as I see the discussion went quiet for a few months
following a few years?
If the answer is yes, I would be surprised if it took more more than a couple
weeks to get something working and looking pretty. A few days in that period
will make it difficult for me to deal with computers, even in the evenings,
otherwise it would be done in a week.
was (Author: marcussorealheis):
Hi everyone, long time no Jira rant. I am looking to exercise my brain to stay
sharp as I battle other challenges. I didn't know if I can think of a better
exercise. I am certainly rusty on Javascript and CSS. It's like riding a
bike... that adds a new wheel, every other fortnight.
Here's what I can commit to in my nights and weekends, but for different
reasons than the last time I tried the full re-write. I was a bit naïve:
I'll build login functionality using React and some bundler that will set up a
pretty solid foundation for migrating more functionality.
On the bright side, I know a bit about the login functionality thanks to a few
committers that helped me a bit back in the day. Happy to throw my hat in to
support this important yet challenging aspect of maintaining the project. I
think I've have time to help with the latter stages of the migration, but my
ultimate goal would be to get more people to learn about the project. If I
cannot find people on the internet to help us out, I'd be happy to talk with
folks about sponsoring a talented student looking for a project.
You can expect a PR tomorrow night to kick of the discussion that will likely
happen here. [~janhoy] Let me know if that sounds good and if I should invest
time as I see the discussion went quiet for a few months following a few years?
If the answer is yes, I would be surprised if it took more more than a couple
weeks to get something working and looking pretty. A few days in that period
will make it difficult for me to deal with computers, even in the evenings,
otherwise it would be done in a week.
> Start the migration of the Admin UI to Angular
> ----------------------------------------------
>
> Key: SOLR-16465
> URL: https://issues.apache.org/jira/browse/SOLR-16465
> Project: Solr
> Issue Type: Wish
> Components: Admin UI
> Reporter: Jeb Nix
> Priority: Major
>
> I suggest using
> [ngUpgrade|https://angular.io/guide/upgrade#upgrading-with-ngupgrade] to
> start a linear migration process to Angular from Angular JS. ngUpgrade will
> reach the end of life at the end of 2023, so we will only get a year of using
> it seamlessly, but this seems to me like the last resort regarding a linear
> migration of the Admin UI codebase. The need for this is of course to migrate
> the current Admin UI project to newer technology, instead of writing it all
> from the start (or implementing the same stuff once more in YASA).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
