Hi, > The Hudson domain name go, the Jenkins name will NOT appear in its place.
That's exactly my opinion, too. > We need to learn and not use brand names as domain (sub) domains. Jenkins is not a brand (currently) but it may get one. More important is: why do we need the product name as part of the URL. The good old style guide @ http://www.w3.org/Provider/Style/URI.html is still correct and clearly says what we should *not* do: Use parts of our infrastructure in URLs. In my opinion, the name of the domain should be something generic and not the product name. We have issues.apache org and not jira.apache.org, same should be for Hudson/Jenkins whatever! > So we need to think of a generic name, apply it real soon - within the next > day or two, then redirect the old Hudson name for a few days. > > get thinking before I just pick one. +1! Just simple: builds.apache.org? > Gav... Uwe P.S.: By the way, all Hudson servers run as user id Hudson, should we also change this, too? -- oh no!
