[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search

CLDR Ticket #10130(accepted)

Opened 2 years ago

Last modified 5 months ago

Reduce load on trac/SVN

Reported by: mark Owned by: rick
Component: infrastructure Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


From email "CLDR SVN repository access and abuse..."

Some concrete ideas

  1. Change all access via




That involves checking
surveytool ...

  1. Password protect


  1. Consider snapshotting http://unicode.org/repos/* as much as possible.

That is, access to one of those URLs goes to a static page. We have a background task to copy new pages into the repository to a static mirror.

Other ideas?


Change History

comment:1 Changed 2 years ago by srl

  1. do not password protect /trac/browser… if we want to remove BROWSER_VIEW permission from the user anonymous that can be done in the trac admin page.
  1. /repos is a WebDAV SVN repository. It doesn't take kindly to snapshotting as proposed here. The options are really to redirect it to an entirely new server, remove it, or leave it alone.

comment:2 Changed 2 years ago by rick

One thing we need to consider clearly before turning off anonymous access to trac/browser is that our main Release/Downloads page refers to it in every line of the table: it points to the "tagged" version, e.g.: http://unicode.org/cldr/trac/browser/tags/release-30

We could add a note at the top of the page giving guest credentials to browse, such as use the username guest with password [whatever]. NOTE: we already have a "guest" in the CLDR owner list... I have no idea if that is a real credential (and if so, I don't know the password or what permissions the guest user has)...

comment:3 Changed 2 years ago by rick

  • Status changed from new to accepted
  • Cc srl added
  • Component changed from unknown to infrastructure
  • Priority changed from assess to major
  • Milestone changed from UNSCH to upcoming
  • Owner changed from anybody to rick

comment:4 Changed 2 years ago by mark

We especially need to be able to point people to particular pages in /trunk/ and /latest/, and I suspect those are the highest frequency cases.

To handle that, I suggest:

That leaves the following cases, I think. I suspect that these are far lower in frequency, but Rick/Steven should confirm.

comment:5 Changed 5 months ago by pedberg

  • Milestone changed from upcoming to UNSCH

CLDR 34 BRS closing item, move all upcoming → UNSCH


Add a comment

Modify Ticket

as accepted

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.