https://bugzilla.wikimedia.org/show_bug.cgi?id=64557
--- Comment #45 from jeremyb <[email protected]> --- (In reply to Kevin Rutherford from comment #43) > We actually discussed the names earlier, and consensus was to not do a > "wikimediane.org" domain. No, I said you can't use that domain with a WMF wiki. You could use that domain if you host it somewhere else. Your comment 36 seems to conflict with comment 27. Unless "name" does not mean domain name. The name of the site as submitted in patches by John is "Wikimedia New England". So there's no punctuation. But that's fine. I thought we were discussing the /domain name/. (In reply to Kevin Rutherford from comment #27) > Jeremy, there is going to be punctuation in the name, so are you objecting > to the AffCom recommendation? (In reply to Kevin Rutherford from comment #36) > Going off of what Greg said, we have requested "usne.wikimedia.org" because > it is not only shorter, but it also is easier to say in conversation. So, then use usne in conversation, business cards, etc. But my argument was about the canonical address. The name that shows up in your address bar when you visit and therefore the name that shows up in [[special:sitematrix]] and [[special:interwiki]] (and the URLs expanded from interwiki links), links people send in emails/IRC when referring to specific pages on the wiki, etc. We have many tools, services and names of individual machines unrelated to chapters operating under the wikimedia.org parent domain. Some are wikis, many are not. e.g. bugzilla, meta, outreach, icinga, gerrit, wikitech, irc, git, graphite, doc, apt, etc. Maybe it would be apparent to a chemist whether or not usne was a chemical element or not but I can imagine some people being unsure. (actually, confusingly I think we once ran or considered running an application named for a chemical element and we already had a physical machine with the same name. and graphite is a form of a chemical but not the canonical name for that chemical.) It should IMHO at least be apparent to users seeing the address that it is related to the US or at least that "US" and "NE" should be separate tokens. > I > don't really see the need for a hyphen, because this would require that we > would have more punctuation within the domain, and might be harder to > remember offhand. Why do you need to remember it at all? > That being said, a redirect would be nice, but I would > like it if it redirects from us-ne.wikimedia.org to usne.wikimedia.org, > since that is what AffCom and we as an affiliate support. The patches as submitted thus far do exactly the opposite. And I just reviewed/commented on them all. Easy access to them all: https://gerrit.wikimedia.org/r/#/q/bug:64557,n,z re MZMcBride's comments about having chapter wikis at all: * re email services I said in comment 12: "You'll need to register a domain and host that separately." * IMO New England is now at a point where having its own website that it controls (i.e. is not shared with the rest of meta) is reasonable. * /WARNING/: But they are hereby warned in case they didn't already know: some configuration changes that require a shell user may take days or weeks to be deployed. (don't make changes too often and the time it takes to get a change made may vary from request to request) * I think we probably don't want to go creating wikis for every group of 5 editors that meets once a year. (and they probably don't want their own site anyway) New England is clearly much further along than that. In terms of the kinds of activities they run, the frequency of their meetings and the number of people that are involved. What exactly are the arguments against hosting wikis for groups with a record of substantial activity and potential for becoming a chapter in the forseeable future? -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
