Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 30288E531 for ; Mon, 14 Jan 2013 21:52:51 +0000 (UTC) Received: (qmail 35305 invoked by uid 500); 14 Jan 2013 21:52:50 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 35069 invoked by uid 500); 14 Jan 2013 21:52:50 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 35059 invoked by uid 99); 14 Jan 2013 21:52:50 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2013 21:52:50 +0000 Received: from localhost (HELO mail-pa0-f41.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2013 21:52:50 +0000 Received: by mail-pa0-f41.google.com with SMTP id bj3so2461879pad.14 for ; Mon, 14 Jan 2013 13:52:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.68.234.167 with SMTP id uf7mr257934633pbc.20.1358200370047; Mon, 14 Jan 2013 13:52:50 -0800 (PST) Received: by 10.68.58.35 with HTTP; Mon, 14 Jan 2013 13:52:49 -0800 (PST) In-Reply-To: References: Date: Mon, 14 Jan 2013 16:52:49 -0500 Message-ID: Subject: Re: Mwiki possible name change. From: Rob Weir To: dev@openoffice.apache.org Content-Type: text/plain; charset=UTF-8 On Mon, Jan 14, 2013 at 3:09 PM, janI wrote: > Hi. > > I want to inform the community about an ongoing discussion in Infra > regarding the use of "wiki.openoffice.org" or "wiki.openoffice.apache.org" > > Background: We decided sometime ago to let me upgrade mwiki, which I did, > with great help from many in here. > > After that there has been a relatively high load on the VM (very positive) > and bi-daily kernel panics due to lack of resources. > > It was then decided to make a new VM with a new ubuntu, instead of an > upgrade in place (to get rid of the kernel panic) which I deemed risky due > to the state (and documentation) of the installation. > > I have completed the work with the new VM, and we were ready to transfer > the live site. > > At that point I learned about plans of using https instead of http. > Infra-root has a policy that all logins (not only for committers) should be > done through https. > > Using https, requires a certificate, and the ongoing discussion is whether > "*.openoffice.org" is really needed or if "*.openoffice.apache.org" would > be ok. > > If I have understood the details correctly (sorry for being vague, but I > have not been able to get a clear answer), the users would address https: > wiki.openoffice.org or http:wiki.openoffice.org and get a response as https: > ooo-wiki.openoffice.org or https:ooo-wiki.openoffice.apache.org. > IMHO renaming goes in the wrong direction. I think we should be looking to get the entire website on to one domain, either all on openoffice.org or all on openoffice.apache.org. Splitting things up is confusing for users, makes extra work for us (and for Infra), confuses the hell out of Google Analytics. I'd really like to see everything under one domain, including our blog and even CWiki (or migrate CWiki over to MWiki). That's my ideal. Is it impossible? > I have written/mailed several times that openoffice.org is a legacy, very > important to AOO, and hope it has been understood. The latest discussion > seems to go in the direction of getting a certificate for openoffice.org, > but there are no guarantees. > Is the issue cost? We could do a mini-fundraising plea on our homepage. I bet we could raise the necessary funds for the certificate. Note: If I understand the security concern with the login, aren't we in the same issue with the phpBB forums? Would a single cert be able to cover that as well? Or do we need one cert per subdomain? Regards, -Rob > I have informed infra, that I cannot participate in works that causes a url > name change, without having a green light from the AOO community. Meaning > that I am now just monitoring what happens and not participating. > > I am sorry to have partly caused the current situation, I wanted to make a > clean installation to make the VM easier to maintain, had I not done that, > the https discussion would problaly never have surfaced. > > I have no deadline for the change, mainly because it is done by others, but > I am convinced that Infra will end with a solution that the community can > accept. > > Please take this as information, I cannot go into a discussion on behalf of > Infra (I am not infra, but we do have other committers that are infra). > > Rgds > jan I.