#25393 closed enhancement (duplicate)

Integration of RelaySearch

Reported by: iwakeh Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Relay Search Version:
Severity: Normal Keywords:
Cc: metrics-team Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

RelaySearch (former Atlas) recently was integrated into Metrics code bases more tightly. It is working fine, but should be adapted more to facilitate better maintenance in future.

One question that needs to be decided:

Should RelaySearch be developed as a part of metrics.tp.o that can also be served stand-alone, which is the current situation or just as a part of metrics.tp.o?
The latter would reduce the amount of files and maintenance for RelaySearch once the integration is completed, as it currently duplicates many parts of metrics-web (fonts, css partially, etc), which will cost more maintenance in future.

This ticket should serve for the discussion of the above question and for deriving the next necessary steps.
(There is also a related ticket for metrics-web, see #25392)

Child Tickets

Change History (3)

comment:1 Changed 13 months ago by iwakeh

Component: Metrics/WebsiteMetrics/Relay Search

comment:2 Changed 13 months ago by iwakeh

Update from today's team meeting:
RelaySearch should become a part of metrics-web and not be a stand-alone service anymore.

Next steps:
First work on the basics of #25392 (submodule move, new ant tasks etc.)
Then find out which libraries etc. can be safely reused and adapt project structure.

Last edited 13 months ago by iwakeh (previous) (diff)

comment:3 Changed 11 months ago by iwakeh

Resolution: duplicate
Status: newclosed

Closing, b/c with the decision to make rs part of mw all should be handled in 25392 and its children.

Note: See TracTickets for help on using tickets.