sbp commented on issue #166: URL: https://github.com/apache/tooling-trusted-release/issues/166#issuecomment-2970419047
Many of the above are incorrect or inconsistent. The [Apache Lucene.NET website](https://lucenenet.apache.org/), for example, uses `.NET` rather than `.Net`. The [Apache Logging Services committee website](https://logging.apache.org/) shows that they use `Log4j`, `Log4j Kotlin`, `Log4j Scala`, `Log4cxx`, and `Log4Net` as their project names, but the only title case project name in the database is `Log4j` and all the rest are incorrectly in lower case. Apache JDO has an extraneous space. The ` (Dormant)` suffix in the Apache Commons projects should probably not be part of the project name, only the project metadata, and Apache Oltu, which is a retired project, appears to be a similar example. Neither [Apache DataSketches](https://datasketches.apache.org/) nor [Apache Rivet](https://tcl.apache.org/rivet/) should be styled in lower case. [Apache Empire-db](https://empire-db.apache.org/pages/home.html) is styled correctly, as are the Xalan and Xerces projects, bRPC, and cTAKES. This leaves [Apache jclouds](https://jclouds.apache.org/), [mod_ftp](https://httpd.apache.org/mod_ftp/), and [mod_perl](https://perl.apache.org/) as the only projects whose names are correctly styled entirely in lower case. This underlines the fact that users will input invalid display names if we do not assist them. On the other hand, the wide range of styles that we must accommodate makes it very difficult to enforce any patterns. We could say that every word must start with a letter or full stop, and must contain at least one capital letter or underscore; we would have to set "for" and "jclouds" as manual exceptions. If we wanted to go a little further, we could say that names must match one of the following: 1. `( UPPER lower* )+` 2. `lower UPPER+` 3. `"mod_" lower*` Where UPPER and lower are alphanumeric, but this would exclude the ".NET", "Lucene.NET", "C++", and "Empire-db" cases in addition to "for" and "jclouds". We could add these to a list of manually preapproved values. There are approximately 400 projects in the database, so six such values would require an approximately 1.5% manual approval rate. This may be worth incurring for consistent data, but it's hard to explain to users what values are allowed. Users do not easily follow regular expressions in documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org For additional commands, e-mail: dev-h...@tooling.apache.org
