<div class="gmail_quote">On Tue, Dec 20, 2011 at 11:24 AM, M.-A. Lemburg <span dir="ltr"><<a href="mailto:mal@egenix.com">mal@egenix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Paul Boddie wrote:<br>
> On Monday 19 December 2011 23:41:14 Martin v. Löwis wrote:<br>
>>> That's not a problem, I can match both on the domain and on the prefix<br>
>>> -- and I can treat no prefix as yet another match for the prefix.<br>
>>> So, <a href="http://wiki.python.org" target="_blank">wiki.python.org</a> would lead to the python wiki, <a href="http://wiki.jython.org" target="_blank">wiki.jython.org</a> to<br>
>>> the jython wiki, etc. plus there would be redirects from<br>
>>> <a href="http://wiki.python.org/moin/*" target="_blank">wiki.python.org/moin/*</a> and <a href="http://wiki.python.org/jython/*" target="_blank">wiki.python.org/jython/*</a>.<br>
>><br>
>> I think what MAL is saying is that you cannot have <a href="http://wiki.python.org/psf" target="_blank">wiki.python.org/psf</a><br>
>> point to one wiki, and <a href="http://wiki.python.org/" target="_blank">wiki.python.org/</a> point to another one. If you<br>
>> could, it would be ambiguous if <a href="http://wiki.python.org/psf/BoardAgenda" target="_blank">wiki.python.org/psf/BoardAgenda</a><br>
>> is a page in the PSF wiki, or in the Python Wiki.<br>
><br>
> I don't remember the farmconfig limitations, but I'm pretty sure you could get<br>
> Apache to handle this and point /psf to a specific Wiki instance before any<br>
> other instance is offered a chance to handle it.<br>
><br>
>> I'm not sure whether URL stability has been discussed yet in this<br>
>> thread: it's absolutely necessary that the existing URLs continue<br>
>> to work "forever", since people are linking to them. Making them<br>
>> redirect would be an option if implementable.<br>
><br>
> I'm also pretty sure that Anatoly mentioned URL stability. I think the<br>
> simplification would be a reasonable enhancement.<br>
<br>
</div>Why not reverse this and redirect from the <a href="http://wiki.python.org/PageName" target="_blank">wiki.python.org/PageName</a><br>
to <a href="http://wiki.python.org/moin/PageName" target="_blank">wiki.python.org/moin/PageName</a> for all page names that don't<br>
start with (moin/|psf/|jython/) ?<br></blockquote><div><br></div><div>To me this proposal is like - 'Why have short URLs by default if we can have a long ones?'</div><div><div>And I confirm that existing URLs will work "forever" and will redirect to new shorter default page</div>
<div>names.</div></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That way you get your shortened URLs, but don't have to change the<br>
way MoinMoin is configured or play with domain names and new<br>
Apache virtual server setups.</blockquote><div><br></div><div><div>If I was a lazy admin, I'd love this suggestion, but can't agree as a user. If Apache is bothersome to maintain - we can change it to Nginx to make the application more portable. </div>
<div><br></div><div>If you're concerned about positive /moin/ advertisement effect, then from a perspective of a Python web developer/admin, the /moin/ prefix looks exactly like an anti-ad. "Why the heck is this prefix doing here if there is already a wiki.* domain namespace?" "Does MoinMoin support domain names mapping?" "Is it a software that is so hard to customize?"</div>
<div><br></div><div>So, we remove MoinMoin anti-ad, make wiki URLs simple for users and preserve existing links from breaking. It is a fantastic deal for the small cost of Apache reconfiguration. If you like the pitch, just say "O key" and we'll close it. =)</div>
<div><div>-- </div></div>anatoly t.<br></div></div>